Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Geek’s Guide
to Leading Teams
@patkua
Patrick Kua
Available on leanpub (http://tiny.cc/twtl)
Why do we need
a Tech Lead?
Why do we need
a Tech Lead?
?
Source: http://twitter.com/julianboot/status/232830267822309376
@thejayfields: I had ten guys on my
last project, all of th...
A simple test for an
effective Tech Lead...
Does the codebase look like it
was written by a single person?
Yes
No
What do effective
Tech Leads focus on?
Tech People
Business You
The “Tech” in Tech
Lead
TECH
Do effective Technical Leaders
need to code?
Definitely!
At least 30% of the
time with the team
http://bit.ly/15Rm4z
“...respect is the currency of
the realm”
http://bit.ly/15Rm4z
http://bit.ly/15Rm4z
““The amount of respect an IT pro
pays someone is a measure of how
tolerable that person is when it c...
Consistency over Cleverness
http://www.emacswiki.org/emacs/TabsSpacesBoth
Tabs OR Spaces
2 Spaces OR 4 Spaces
CamelCase OR Underscore
Curly brace end of line
OR next line
Brackets OR not
Team Culture
How long does the build
stay broken?
Do people avoid
conflict?
Do people offer new
ideas?
Do people flag when
they need help...
Vision
Vision
Yes
No
Can everyone draw the same
architecture diagram?
Free download: http://bit.ly/1Esrn7f
Riding Paradox
Riding Paradox
“Paradox” by Michael Berg
Consistency vs Improvement
Delivering vs Learning
Technical vs Business
People
Analytical
Activator
Intellection
Achiever
Strategic
Input
Woo
Collective
Accuracy
=
Average Accuracy
+ Diversity*
* Requires ability to integrate
Trust isn’t built in one day
Growing People
Skill/Ability
ChallengeHIGHLOW
LOW HIGH
Skill/Ability
ChallengeHIGHLOW
LOW HIGH
Anxiety
Skill/Ability
ChallengeHIGHLOW
LOW HIGH
Boredom
Skill/Ability
ChallengeHIGHLOW
LOW HIGH
Flow
Anxiety
Boredom
Learning Activities
Brown Bag sessions
Spike Showcases
Team code reviews
Technical
Retrospectives
Pair Programming
Video/B...
“Bad Is Stronger Than Good” (2001) Baumeister et al
Beware the bad apple
Bridging the Business
Technical Business
Translating between realms
Business
Opportunities
You
9am
6pm
Monday Tuesday Wednesday Thursday Friday
Email Time Email Time
Planning
Time
1:1s
Email Time
Planning
Time
Email T...
People The Tech of a Tech Lead
Bridging the Business You
Questions?
@patkua
Patrick Kua
The Geek’s Guide to Leading Teams - Patrick Kua
The Geek’s Guide to Leading Teams - Patrick Kua
The Geek’s Guide to Leading Teams - Patrick Kua
The Geek’s Guide to Leading Teams - Patrick Kua
Upcoming SlideShare
Loading in …5
×

The Geek’s Guide to Leading Teams - Patrick Kua

1,937 views

Published on

Talkin with

Published in: Software
  • Login to see the comments

The Geek’s Guide to Leading Teams - Patrick Kua

  1. 1. The Geek’s Guide to Leading Teams @patkua Patrick Kua
  2. 2. Available on leanpub (http://tiny.cc/twtl)
  3. 3. Why do we need a Tech Lead?
  4. 4. Why do we need a Tech Lead?
  5. 5. ?
  6. 6. Source: http://twitter.com/julianboot/status/232830267822309376 @thejayfields: I had ten guys on my last project, all of them had opinions and all of them were expressed in the code base #speakerconf @julianboot
  7. 7. A simple test for an effective Tech Lead...
  8. 8. Does the codebase look like it was written by a single person? Yes No
  9. 9. What do effective Tech Leads focus on?
  10. 10. Tech People Business You
  11. 11. The “Tech” in Tech Lead
  12. 12. TECH Do effective Technical Leaders need to code? Definitely! At least 30% of the time with the team
  13. 13. http://bit.ly/15Rm4z
  14. 14. “...respect is the currency of the realm” http://bit.ly/15Rm4z
  15. 15. http://bit.ly/15Rm4z ““The amount of respect an IT pro pays someone is a measure of how tolerable that person is when it comes to getting things done...””
  16. 16. Consistency over Cleverness
  17. 17. http://www.emacswiki.org/emacs/TabsSpacesBoth
  18. 18. Tabs OR Spaces 2 Spaces OR 4 Spaces CamelCase OR Underscore Curly brace end of line OR next line Brackets OR not
  19. 19. Team Culture
  20. 20. How long does the build stay broken? Do people avoid conflict? Do people offer new ideas? Do people flag when they need help? Do people feel okay to admit being wrong? Team Culture
  21. 21. Vision
  22. 22. Vision Yes No Can everyone draw the same architecture diagram?
  23. 23. Free download: http://bit.ly/1Esrn7f
  24. 24. Riding Paradox
  25. 25. Riding Paradox “Paradox” by Michael Berg Consistency vs Improvement Delivering vs Learning Technical vs Business
  26. 26. People
  27. 27. Analytical Activator Intellection Achiever Strategic Input Woo
  28. 28. Collective Accuracy = Average Accuracy + Diversity* * Requires ability to integrate
  29. 29. Trust isn’t built in one day
  30. 30. Growing People
  31. 31. Skill/Ability ChallengeHIGHLOW LOW HIGH
  32. 32. Skill/Ability ChallengeHIGHLOW LOW HIGH Anxiety
  33. 33. Skill/Ability ChallengeHIGHLOW LOW HIGH Boredom
  34. 34. Skill/Ability ChallengeHIGHLOW LOW HIGH Flow Anxiety Boredom
  35. 35. Learning Activities Brown Bag sessions Spike Showcases Team code reviews Technical Retrospectives Pair Programming Video/Book Club
  36. 36. “Bad Is Stronger Than Good” (2001) Baumeister et al Beware the bad apple
  37. 37. Bridging the Business
  38. 38. Technical Business Translating between realms
  39. 39. Business Opportunities
  40. 40. You
  41. 41. 9am 6pm Monday Tuesday Wednesday Thursday Friday Email Time Email Time Planning Time 1:1s Email Time Planning Time Email Time Next week planning
  42. 42. People The Tech of a Tech Lead Bridging the Business You
  43. 43. Questions? @patkua Patrick Kua

×