Slide 1
Slide 1 text
Making the Switch to
Engineering Management
Justin Carmony - Utah PHP Usergroup - June 2018
Slide 2
Slide 2 text
Goal: Give You Things to Think About
& Possible Next Steps
Slide 3
Slide 3 text
Y.M.M.V!
(Your Mileage May Vary)
Based on my personal experiences
Slide 4
Slide 4 text
More Conversation, Less Presentation
Slide 5
Slide 5 text
Who am I?
Sr. Director of Engineering, Deseret Digital Media
- Analytics
- Advertising Platforms
- KSL.com News
- Publishing Technologies
Member of the Utah Open Source Community
Been breaking & making web stuff for 15+ years
Slide 6
Slide 6 text
Poll
Engineers? Team Leads? Managers? Manager of Managers?
Slide 7
Slide 7 text
Story
Slide 8
Slide 8 text
What is a manager?
Slide 9
Slide 9 text
Two Primary Types
Individual Contributor
●
Success is measured by the results
of your individual contributors
●
Primary focus is still technical /
code
Manager
●
Success is measured by the results
of your team
●
Primary focus are people /
outcomes
Slide 10
Slide 10 text
Aspects of Being a Manager*
* - in no particular order
Slide 11
Slide 11 text
Aspect: A Mental Shift
Slide 12
Slide 12 text
Senior Engineer to Junior Manager
Slide 13
Slide 13 text
You’re Going To Make Mistakes
Slide 14
Slide 14 text
Thinking People First,
Not Code
Slide 15
Slide 15 text
Example: “We’re having stability problems”
Slide 16
Slide 16 text
Individual Contributor
Manager
Slide 17
Slide 17 text
If you’re “doing well” but your team isn’t
YOU ARE FAILING!
Slide 18
Slide 18 text
Mental Shift:
Your are responsible for 100% of the code,
which you will write 5% of.
Slide 19
Slide 19 text
Aspect: Mentoring
(aka growth)
Slide 20
Slide 20 text
You Cannot Scale
You must grow people to do more!
Slide 21
Slide 21 text
Taking time, on a regular basis, to think about
someone’s growth versus logistics
Slide 22
Slide 22 text
Carmony Mentoring Style
●
Kick off one-on-one, discuss goals, career aspirations, etc
●
Meet every 4-6 weeks for 1 hour
●
Discuss a topic
●
Create items to work on
●
Follow up on the items next meeting
●
Rinse & Repeat
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
Spencer’s Story
Slide 25
Slide 25 text
Aspect: 1-on-1s
(aka Logistics)
Slide 26
Slide 26 text
1-on-1’s
●
Two things I cover:
○
Logistics
○
Moral / How People Are Doing
●
Logistics
○
“Where are we at on this project?”
○
“How are you feeling about it?”
○
“Any impediments”
○
Note: not a full blown status report, just checking in
●
Moral
○
“How are you feeling?”
○
“Anything I can do to help you out?”
Slide 27
Slide 27 text
Adapt your 1-on-1 style to each direct report
Slide 28
Slide 28 text
Aspect: Course Corrections
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
Aspect: Stakeholders
Slide 31
Slide 31 text
Managing Expectations
Slide 32
Slide 32 text
Being a Shield
(aka going to meetings)
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
You get disrupted so your team doesn’t!
Slide 35
Slide 35 text
Become your Stakeholder’s best avenue
to solve problems
Slide 36
Slide 36 text
Communicate, Communicate, Communicate
Slide 37
Slide 37 text
Aspect: Be a Defender!
Slide 38
Slide 38 text
Not so
“Secret Weapon”:
The Manager’s Path
Slide 39
Slide 39 text
Resources
Slide 40
Slide 40 text
Additional Resources
●
Camille Fournier’s Blog - http://www.elidedbranches.com/
●
Lara Hogan’s Blog - https://larahogan.me/blog/
●
Michael Loop’s Blog - http://randsinrepose.com/
Slide 41
Slide 41 text
Questions?