geek's guide to leading teams

121
@patkua THE GEEK’S GUIDE TO LEADING TEAMS

Upload: patrick-kua

Post on 21-Apr-2017

27.258 views

Category:

Leadership & Management


1 download

TRANSCRIPT

Page 1: Geek's Guide to Leading Teams

@ p a t k u a

THE GEEK’S GUIDE TO LEADING TEAMS

Page 2: Geek's Guide to Leading Teams

ABOUT @PATKUA

2

http://tiny.cc/twtl http://tiny.cc/retros

ArchitectDeveloper

LeaderCoach

Life-long learnerAuthor

Page 3: Geek's Guide to Leading Teams

WHY DO WE NEED A TECH LEAD?

Page 4: Geek's Guide to Leading Teams
Page 5: Geek's Guide to Leading Teams
Page 6: Geek's Guide to Leading Teams
Page 7: Geek's Guide to Leading Teams
Page 8: Geek's Guide to Leading Teams
Page 9: Geek's Guide to Leading Teams
Page 10: Geek's Guide to Leading Teams
Page 11: Geek's Guide to Leading Teams
Page 12: Geek's Guide to Leading Teams
Page 13: Geek's Guide to Leading Teams

?

Page 14: Geek's Guide to Leading Teams

7

http

://w

ww.fli

ckr.c

om/p

hoto

s/dc

arlb

om/3

4683

5885

9/

Page 15: Geek's Guide to Leading Teams

THINK THIS DOESN’T HAPPEN IN THE REAL WORLD?

Page 16: Geek's Guide to Leading Teams

@julianboot

Page 17: Geek's Guide to Leading Teams

@julianboot@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

Source: http://twitter.com/julianboot/status/232830267822309376

Page 18: Geek's Guide to Leading Teams

A SIMPLE TEST FOR AN EFFECTIVE TECH LEAD...

Page 19: Geek's Guide to Leading Teams

Does the codebase look like it was written by a single person?

Yes No

Page 20: Geek's Guide to Leading Teams

WHAT DOES A GOOD TECH LEAD FOCUS ON?

Page 21: Geek's Guide to Leading Teams

ProgrammingP

PeopleP

ProcessP

Page 22: Geek's Guide to Leading Teams

Programming

PeopleP

ProcessP

Page 23: Geek's Guide to Leading Teams

Programming

People

ProcessP

Programming

Page 24: Geek's Guide to Leading Teams

Programming

People

Process

Programming

People

Page 25: Geek's Guide to Leading Teams

Programming

People

Process

Programming

People

Process

Page 26: Geek's Guide to Leading Teams

PROGRAMMING

Page 27: Geek's Guide to Leading Teams

PROGRAMMING

Do effective Technical Leaders need to code?

Page 28: Geek's Guide to Leading Teams

PROGRAMMING

Do effective Technical Leaders need to code?

DEFINITELY

Page 29: Geek's Guide to Leading Teams

Do effective Technical Leaders need to code?

DEFINITELY

PROGRAMMING

Page 30: Geek's Guide to Leading Teams

Do effective Technical Leaders need to code?

DEFINITELY

PROGRAMMING

Page 31: Geek's Guide to Leading Teams

Do effective Technical Leaders need to code?

DEFINITELY

At least 30% of the time with the team

PROGRAMMING

Page 32: Geek's Guide to Leading Teams

PROGRAMMING

Page 33: Geek's Guide to Leading Teams

PROGRAMMING

http://bit.ly/15Rm4z

Page 34: Geek's Guide to Leading Teams

...respect is the currency of the realm

PROGRAMMING

http://bit.ly/15Rm4z

Page 35: Geek's Guide to Leading Teams

...respect is the currency of the realm

PROGRAMMING

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...

http://bit.ly/15Rm4z

Page 36: Geek's Guide to Leading Teams

Consistency over Cleverness

PROGRAMMING

Page 37: Geek's Guide to Leading Teams

PROGRAMMING

Page 38: Geek's Guide to Leading Teams

PROGRAMMING

Page 39: Geek's Guide to Leading Teams

PROGRAMMING

Page 40: Geek's Guide to Leading Teams

PROGRAMMING

Page 41: Geek's Guide to Leading Teams

PROGRAMMING

Page 42: Geek's Guide to Leading Teams

PROGRAMMING

There are more important topics to spend time on...

Page 43: Geek's Guide to Leading Teams

Team Culture

PROGRAMMING

Page 44: Geek's Guide to Leading Teams

Team Culture

PROGRAMMING

Page 45: Geek's Guide to Leading Teams

Team Culture

How long does the build stay broken?

PROGRAMMING

Page 46: Geek's Guide to Leading Teams

Team Culture

How long does the build stay broken? Do people avoid

conflict?

PROGRAMMING

Page 47: Geek's Guide to Leading Teams

Team Culture

How long does the build stay broken? Do people avoid

conflict?

Do people offer new ideas?

PROGRAMMING

Page 48: Geek's Guide to Leading Teams

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?

PROGRAMMING

Page 49: Geek's Guide to Leading Teams

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?

Do people feel okay to admit being wrong?

PROGRAMMING

Page 50: Geek's Guide to Leading Teams

PROGRAMMING

Vision

Page 51: Geek's Guide to Leading Teams

PEOPLE

Page 52: Geek's Guide to Leading Teams

PEOPLE

Strength in Diversity

Page 53: Geek's Guide to Leading Teams

PEOPLE

Page 54: Geek's Guide to Leading Teams

PEOPLE

Page 55: Geek's Guide to Leading Teams

Fortune 500 companies with 3 or more women on the Board gain a significant performance advantage over those with the fewest

PEOPLE

Page 56: Geek's Guide to Leading Teams

Fortune 500 companies with 3 or more women on the Board gain a significant performance advantage over those with the fewest

PEOPLE

Return on Sales

73%

Return on Equity Return on Invested Capital

83%112%

Source: Catalyst (2007) http://bit.ly/nEEfGX

Page 57: Geek's Guide to Leading Teams

“...over the past six years, companies with at least some female board representation outperformed those with no women on the board in terms of share price performance.”

PEOPLE

Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

Page 58: Geek's Guide to Leading Teams

“...over the past six years, companies with at least some female board representation outperformed those with no women on the board in terms of share price performance.”

PEOPLE

Return on Equity

12%

Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

Page 59: Geek's Guide to Leading Teams

“...over the past six years, companies with at least some female board representation outperformed those with no women on the board in terms of share price performance.”

PEOPLE

Return on Equity

12% 16%

Return on Equity

Source: Credit Suisse Research Institute (August 2012) http://bit.ly/Oozuvl

Page 60: Geek's Guide to Leading Teams

PEOPLE

Page 61: Geek's Guide to Leading Teams

Collective Accuracy = Average Accuracy + Diversity*

PEOPLE

Page 62: Geek's Guide to Leading Teams

Collective Accuracy = Average Accuracy + Diversity*

PEOPLE

* Requires ability to integrate

Page 63: Geek's Guide to Leading Teams

TRUST ISN’T BUILT IN ONE DAY

https://www.flickr.com/photos/create-learning/3676366324/sizes/o/

Page 64: Geek's Guide to Leading Teams

PEOPLE

Growing People

Page 65: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Source: Csikszentmihalyi, Flow (1990)

Page 66: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Source: Csikszentmihalyi, Flow (1990)

Page 67: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Source: Csikszentmihalyi, Flow (1990)

Boredom

Page 68: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 69: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 70: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 71: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 72: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 73: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 74: Geek's Guide to Leading Teams

PEOPLE

Skill/AbilityLOW HIGH

Chal

leng

eH

IGH

LOW

Anxiety

Boredom

Csikszentmihalyi, "Flow: The Psychology of Optimal Experience" (1990)

Flow

Page 75: Geek's Guide to Leading Teams

PEOPLE

Maximising Potential

Page 76: Geek's Guide to Leading Teams

PEOPLE

40

Skills

Page 77: Geek's Guide to Leading Teams

PEOPLE

41

Skills

Strengths

Page 78: Geek's Guide to Leading Teams

PEOPLE

42

Skills

StrengthsGoals

Page 79: Geek's Guide to Leading Teams

PEOPLE

43

Skills

StrengthsGoals

Interests

Page 80: Geek's Guide to Leading Teams

PEOPLE

44

Skills

StrengthsGoals

Interests

Sweet Spot

Page 81: Geek's Guide to Leading Teams

PEOPLE

45

Skills

StrengthsGoals

Interests

Page 82: Geek's Guide to Leading Teams

PEOPLE

45

Skills

StrengthsGoals

Interests

Page 83: Geek's Guide to Leading Teams

PEOPLE

45

Skills

StrengthsGoals

Interests

Page 84: Geek's Guide to Leading Teams

PEOPLE

45

Skills

StrengthsGoals

Interests

Page 85: Geek's Guide to Leading Teams

PEOPLE

Learning Activities

Page 86: Geek's Guide to Leading Teams

PEOPLE

Learning Activities

Brown Bag sessions

Spike Showcases

Team code reviews

Technical Retrospectives

Pair Programming

Video/ Book Club

Page 87: Geek's Guide to Leading Teams

PEOPLE

“Bad Is Stronger Than Good” (2001) Baumeister et al

Beware the bad apple

Page 88: Geek's Guide to Leading Teams

PEOPLE

“Bad Is Stronger Than Good” (2001) Baumeister et al

Beware the bad apple

Page 89: Geek's Guide to Leading Teams

PROCESS

Page 90: Geek's Guide to Leading Teams

PROCESS

Is it okay to tell people what to do?

Page 91: Geek's Guide to Leading Teams

PROCESS

Is it okay to tell people what to do?

YES

but only sometimes

Page 92: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Page 93: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Page 94: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Directing

Page 95: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

CoachingDirecting

Page 96: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g CoachingDirecting

Page 97: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g CoachingDirecting

Delega

ting

Page 98: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g CoachingDirecting

Delega

ting

Page 99: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

HighDirecting BehaviourLow

High

Supp

ortin

g Be

havi

our

Supp

ortin

g Coaching

Directing

Delega

ting

Page 100: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Page 101: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Development level of an individual

Page 102: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Dev

elop

ing

Development level of an individual

Dev

elop

ed

Page 103: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Page 104: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitment

Page 105: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitmentVariable commitment

Moderate-high competence

Page 106: Geek's Guide to Leading Teams

SITUATIONAL LEADERSHIP MODEL

Dev

elop

ing

Development level of an individual

Dev

elop

ed Low competence

High commitment

Low-some competence

Low commitmentVariable commitment

Moderate-high competence

High commitment

High competence

Page 107: Geek's Guide to Leading Teams

PROCESS

Tuckman’s Model

Page 108: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Page 109: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming

Page 110: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming Storming

Page 111: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming Storming Norming

Page 112: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming Storming Norming Performing

Page 113: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming Storming Norming Performing Adjourning

Page 114: Geek's Guide to Leading Teams

TUCKMAN’S STAGES OF GROUP DEVELOPMENT

Forming Storming Norming Performing Adjourning

Page 115: Geek's Guide to Leading Teams

PROCESS

Essentially, all models are wrong, but some are useful.

—George E. P. Box

Page 116: Geek's Guide to Leading Teams

PROCESS

Make time for you

Page 117: Geek's Guide to Leading Teams

57http://www.flickr.com/photos/mbeo52/5062096969/sizes/l/

Page 118: Geek's Guide to Leading Teams

58https://www.flickr.com/photos/sushicam/5584789234/sizes/o/

Page 119: Geek's Guide to Leading Teams

PROCESS

Monday Tuesday Wednesday Thursday Friday

9AM

6PM

Email Time

Planning Time

Email Time

1:1s

Email Time

Planning Time

Next week planning

Email Time

Page 120: Geek's Guide to Leading Teams

CONCLUDING THOUGHTS

Page 121: Geek's Guide to Leading Teams

@patkua Patrick Kua

THANK YOU