The four components of high performing teams | Lisa van Gelder |

Поделиться
HTML-код
  • Опубликовано: 17 окт 2024
  • Do you have a great team & a great mission but don't understand why the pace of delivery is so slow? Architecture & tech stack is only one part of the story. I believe high performing teams need four things to be effective:
    Mastery - The skills & knowledge needed to do a great job, and a clear path to get to the next level.
    Autonomy - The space to figure out their own solution to a problem & how they want to work
    Purpose - A clear sense of direction, and the knowledge of how what they’re working on fits into the big picture & helps their team succeed.
    Safety - A team that is afraid won’t take risks or experiment, a team that is afraid of finger-pointing won’t learn from mistakes.
    In this talk, I’ll explain why those four things are key to teams being successful and give examples of how I’ve turned teams around by fixing the lack of one or more of them. Attendees will leave with practical examples of how to diagnose & change their teams.
    About Lisa van Gelder
    Lisa has been in software for almost 20 years, working in a wide range of companies from early stage startups to large media companies like the BBC & the Guardian newspaper. She used to debug code, now she debugs teams for a living. Lisa is currently VP, Engineering at Meetup. She is mostly powered by coffee.
    Find out more: austin2019.the...
    Lead Dev is a community for technical leaders. We have a series of conferences and meetups designed with the needs and pain points of technical team leads in mind. We programme each conference around our three key themes of Team, Tech & Tools. The talks are designed to help very practically with common problems in these areas. To find out more about us, visit:
    theleaddevelop...

Комментарии • 4

  • @jasonmongue6162
    @jasonmongue6162 4 года назад +1

    Excellent presentation Lisa. Really like how you broke down your team debugging approach.

  • @meurigjones207
    @meurigjones207 4 года назад

    Really useful and well presented. "Management" should watch this.

  • @nagkumar
    @nagkumar 4 года назад

    2nd Team Fixing First Team mess, we call it a #CleanCode Team, which bridges the gaps od done w.r.t to #coredevelopment and #qa team. There is a strong need for this in-between bridge #cleancode team or #NFRteam which takes care of all of the non-functional requirements.
    #tejasoft has been recommending this to IT services and Indian product MNCs on such an approach for 10 years for non-intrusive upskilling and attack genuine skill gaps which are common due to low-cost engineering. 3 Team Development team rocks and solves most of the engineering issues.