Leveling Up: Assuming Technical Leadership

Most software developers would make lousy managers, but many of the experienced developers that I have met and worked with have more to offer in terms of technical leadership than they share with their managers and team. As an industry, we need you to leverage your experience for the benefit of us all. In this session we will examine some clues that you may be ready to "level up". We'll discuss when and how to appropriately exercise technical leadership and when to keep our mouths shut.

Attendees will leave this session with a toolkit of tactics to influence their teams, companies and clients to make better choices in the pursuit of greater user value.

Transcript

1. Leveling Up H. Alan Stevens
2. Leveling Up Assuming Technical Leadership H. Alan Stevens
5. Contact Me Email/IM: alanstevens@gmail.com Blog: http://halanstevens.com Twitter: @alanstevens
6. Technical competence is assumed!
7. What you need to know:
8. •Trust What you need to know:
9. •Trust •Tell a story What you need to know:
10. •Trust •Tell a story •Value others What you need to know:
11. Leadership is not a formal role assigned from without.
12. Leadership Myths
13. Leadership Is Innate
14. Leadership Is Innate
15. Leadership is possessing power over others
16. Leadership is possessing power over others
17. Leaders are positively influential
18. Leaders are positively influential
19. Leaders entirely control group outcomes
20. Leaders entirely control group outcomes
21. All groups have a designated leader
22. All groups have a designated leader
23. Group members resist leaders
24. Group members resist leaders
25. What Leadership Is
26. Leadership is an attitude you embody.
27. Dreyfus Model of Skills Acquisition Source: Pragmatic Thinking and Learning Pragmatic Press 2008
28. Leadership requires pushing back.
29. Leadership Means Accepting Reality.
30. Budget Scope Schedule
31. Leadership requires you to become immune to hype.
32. http://en.wikipedia.org/wiki/Hype_cycle
33. How To Lead
34. TRUST
35. Food
36. Humor
37. Promote a culture of safety
38. TELL A STORY
39. Emotions not Facts
40. Use metaphor
41. Associative Neurons
42. Invite them to join you on a journey.
43. Leadership is about a vision, not a task or an objective.
44. VALUE OTHERS
45. Raise the value of the whole team
46. Encourage others to value you by demonstrating that you value them.
47. scarcity vs. abundance mentality
48. You can't raise yourself up by keeping others down.
49. http://sivers.org/ff
50. It was the first follower that transformed a lone nut into a leader.
51. There is no movement without the first follower.
52. We're told we all need to be leaders, but that would be really ineffective.
53. The best way to make a movement, if you really care, is to courageously follow and show others how to follow.
54. When you find a lone nut doing something great, have the guts to be the first person to stand up and join in.
55. New followers emulate other followers, not the leader.
56. Being a first follower is an under- appreciated form of leadership.
61. A players hire A players. B players hire C players.
62. A players hire A+ players, not merely A players.
63. A players hire A+ players, not merely A players. Guy Kawasaki
64. Be willing and prepared to stand out.
65. Thanks For Listening! Email/IM: alanstevens@gmail.com Blog: http://halanstevens.com Twitter: @alanstevens