Although leadership skills have been analyzed for so long, there is something in the way we choose and raise our technical leads that defy all laws. We often think that the brightest and most creative person in the team will eventually become a technical lead, which actually happens in most cases. The exciting part, though, the process of becoming a technical lead starts when we actually take over the role. What seemed to be a gratification for excellent results can become a long list of failures if you don’t really, really prepare for the challenge. Luckily we can learn from each other’s mistakes, so join us to touch some hot spots in the technical leadership journey.

1. and how to fix it …
How to
FAIL BIG
at Being a
TECH LEAD

2. ABOUT
US Bogdan Sucaciu
Tech Lead @ 8x8
Pluralsight Author
Mihaela Ghidersa
Tech Lead @ Strongbytes
Microsoft MVP

4. WHAT is a
TECHNICAL
LEAD
ANYWAY?

5. FAIL #1
Perfection over
excellence

6. Don’t be this guy

7. Set
Boundaries

8. FAIL #2
Poor communication
skills

9. TECHNICAL
LEADER
Leadership
Management
Technical skills

11. Be vulnerable.
You can’t know it ALL. Own it!

12. FAIL#3
Democracy over
Dictatorship

13. Time / Team
Maturity
Democracy
Dictatorship
Fail #3: Democracy over Dictatorship

14. Time / Team
Maturity
Democracy
Dictatorship
Fail #3: Democracy over Dictatorship
Standards

15. • Write the unwritten rules ( GIT, Agile
flow, testing, etc. )
• It’s your job to facilitate
• Observe strong views
• Rotate clashing views
Ways of Working ( WoW Meeting )
NEW
TOOL

16. FAIL #4
Tech skills are
everything

17. COMMUNICATION
!== CONNECTION

18. Be Firm on Principles but
Flexible on Methods
- Zig Ziglar
Extreme coding standards vs. Delivery

19. OODA Loop
● Observe — Understand the context
● Orient — Decide and align on important directions
● Decide — Align on the direction of action
● Act — Go for it!

20. FAIL#5
Know-it-all Attitude

21. FAIL#5
• Consult with the team, you don’t know
everything
• Be open to new ideas
• Don’t fall for extreme delegation ( being lazy )
Easy
but tedious
Difficult
but exciting
vs
Know-it-all Attitude

22. FAIL#5
• Consult with the team, you don’t know
everything
• Be open to new ideas
• Don’t fall for extreme delegation ( being lazy )
Easy
but tedious
Difficult
but exciting
vs
Know-it-all Attitude

23. FAIL #6
Place yourself
outside the team

24. Team lead
vs.
Tech lead

25. “A star wants to see herself
rise to the top. A leader
wants to see those around
her become stars.”
Simon Sinek

26. Lesson#1:
Listen to the team first, then
give your perspective.

27. Lesson#2:
On achievements praise the team.
On failures, you own it.

28. DON’Ts Become a control
freak

29. FAIL#7
Control Freak

30. QUICK
TACTICS
Let people fail ( even if you are aware of
their failure )
Q: “Suggestion” or “solution”?
Apply delay tactics for x minutes

31. Zoom out & delegate
Educate and mentor your team
Celebrate success and don’t dwell on failures
DOs
Gain technical proficiency
Look at your system from different
perspectives

32. Build on your
leadership
style
Mihaela Ghidersa
@MihaelaGhidersa
linkedin.com/in/ghidersam/
Bogdan Sucaciu
@bsucaciu
linkedin.com/in/bogdan-sucaciu