Upgrade to Pro — share decks privately, control downloads, hide ads and more …

WORKSHOP: How to handle the "technical" in tech...

Avatar for Clare Sudbery Clare Sudbery
June 14, 2025
7

WORKSHOP: How to handle the "technical" in technical leadership

Note: These are the slides I used while running this workshop at LDX3 in London, June 2025. They're not designed to work as a standalone resource, but I'm sharing them here for reference for those who attended these workshops.

How technical do technical leaders have to be? Are you worried that you’re too hands-on, or not hands-on enough? Are you exhausting yourself trying to keep up with every technical detail in your domain?

Sometimes individual contributors are promoted to leadership positions and worry that they won’t be as hands-on as they used to be. Sometimes they worry that they no longer have time to stay up to date with modern technology and / or the state of their team’s code base(s). Sometimes it’s the other way around: Somebody who has never been hands-on in the technical realm is given a leadership position, and worries they’re “not technical enough”.

Whatever your position, this workshop will help you to overcome your worries and figure out the best attitude and approach for you and your circumstances.

Takeaways
- How to embrace the difference between individual contributor and technical leader
- How to take a step back from “knowing all the things”
- How to make the most of the knowledge and experience of your team
- How to identify when technical knowledge matters, and when it doesn’t
- How to identify the things you need to know

Avatar for Clare Sudbery

Clare Sudbery

June 14, 2025
Tweet

Transcript

  1. Sudbery Software Engineering Ltd Does your team want help to

    improve their software delivery? Coaching, keynotes & workshops Events and info: bit.ly/claresudbery Mastodon: mastodon.social/@ClareSudbery LinkedIn: bit.ly/lin-csudbery Podcast: bit.ly/3XvyNbU
  2. @ClareSudbery Workshop lasts 80 mins We’ll have a 10-min break

    after approx 35 mins We finish Mon 13:20, and Tue 12:50 00:00 – 05:00 MANY
  3. @ClareSudbery 2 minutes Write your biggest worry on a sticky

    note Be specific (not just "I worry I'm not technical enough") Write clearly – people need to read it Add your name and remember what you wrote! 05:00 – 10:00
  4. @ClareSudbery This half of the room, put your sticky notes

    up Spread them out along the wall 05:00 – 10:00 MANY
  5. @ClareSudbery Other half of the room, take one sticky note

    each One that’s close to your worry …or is a worry that you share 05:00 – 10:00 MANY
  6. @ClareSudbery Walk around, waving your sticky note Find the person

    who wrote it Form a pair / three with them Introduce yourselves! Name + role 10:00 – 15:00 MANY
  7. @ClareSudbery Which category are you? • Leadership after being hands-on

    technical • Leadership after NOT being in a technical role • Senior developer aspiring to leadership • [new categories] 15:00 – 20:00
  8. @ClareSudbery 3 minutes Write down ONE piece of advice to

    address your worry On a sticky note Individually (not in pairs) [Note for Clare: Put big stickies up] 15:00 – 20:00
  9. Ilianna: Terraform Kirsty: Hadoop Mircea: iOS Native Esra: SonarQube Georgia:

    Golang Rob: AWS Scott: AiOps Andy: Encryption Anik: PySpark Jon: CentOS 7 THE WHEEL OF CONFUSION
  10. Terraform CentOS 7 Hadoop iOS Native SonarQube Golang AWS AiOps

    PySpark Recursion THE WHEEL OF CONFUSION
  11. Terraform CentOS 7 Hadoop iOS Native SonarQube Golang AWS AiOps

    Recursion Encryption THE WHEEL OF CONFUSION
  12. Terraform CentOS 7 Hadoop iOS Native Golang AWS AiOps 398373

    Encryption PySpark THE WHEEL OF CONFUSION
  13. @ClareSudbery The Stupidity Manifesto LET’S STOP MAKING EACH OTHER FEEL

    STUPID. INSTEAD, LET’S… • ENCOURAGE EVERYONE TO ASK QUESTIONS • Lead by example: Be honest when we’re confused • Value curiosity over knowledge • Prioritise clarity over jargon • Remember we all forget stuff • Get excited about teaching and learning • Acknowledge the broad range of knowledge in our industry, and avoid judging someone if their knowledge doesn’t match ours • LET’S STOP MAKING EACH OTHER FEEL STUPID. Sign the manifesto:
  14. @ClareSudbery FORM TWO QUEUES, HALF THE ROOM EACH EACH QUEUE

    LEADING TO ONE END OF THE ROW OF BIG STICKIES TAKE WITH YOU: • A PEN • YOUR ADVICE STICKY • A BLANK STICKY 50:00 – 55:00
  15. Read all the big sticky notes You should have: A

    pen, your advice sticky, a blank sticky - Take your advice and add it to any similar big sticky - If nothing similar, put in separate area ~~~~~~~~~ - Circle back to the end of the queue - Find a sticky DIFFERENT to yours - Copy it down onto a blank sticky - Take it back to your pair 50:00 – 55:00 @ClareSudbery
  16. @ClareSudbery 2 minutes Discuss the sticky notes you have In

    your pairs Are they useful? Why? Why not? 55:00 – 60:00 MANY
  17. @ClareSudbery 3 minutes Write new stickies headed either “INSPIRED” or

    “STILL WORRIED” In your pairs Make sure you include the headings on the stickies! It will help me. 55:00 – 60:00 MANY
  18. Sudbery Software Engineering Ltd Does your team want help to

    improve their software delivery? Coaching, keynotes & workshops Events and info: bit.ly/claresudbery Mastodon: mastodon.social/@ClareSudbery LinkedIn: bit.ly/lin-csudbery Podcast: bit.ly/3XvyNbU