Re:Coding as an Engineering Manager
by lbotos on Thursday November 01, 2018 @05:20PM
(#18358573)
Current Manager. It's "Support Engineering" but currently:
- Metrics for the business to understand what our pain points are
- 1:1 Prep and post 1:1 vision planning ("Is everyone aligned?")
- Performance review prep (time of year)
- Chasing down other managers to try and get problems fixed that were surfaced in 1:1s
- a "net" above the team, to filter out any business side bs that would go their way that would be a distraction. (The team has to trust that I have their best interest in mind. That's why a net, I let them know, and they can see)
- Capacity Planning (Do we have enough people for the growth plan? Oh, did the growth plan get updated? Lemme take another look...)
- Hiring
- Reviewing Resumes
- Are our policies up to date?
- Process thinking (usually surfaced by pain points from 1:1s)
- Metrics for the business to understand what our pain points are
- 1:1 Prep and post 1:1 vision planning ("Is everyone aligned?")
- Performance review prep (time of year)
- Chasing down other managers to try and get problems fixed that were surfaced in 1:1s
- a "net" above the team, to filter out any business side bs that would go their way that would be a distraction. (The team has to trust that I have their best interest in mind. That's why a net, I let them know, and they can see)
- Capacity Planning (Do we have enough people for the growth plan? Oh, did the growth plan get updated? Lemme take another look...)
- Hiring
- Reviewing Resumes
- Are our policies up to date?
- Process thinking (usually surfaced by pain points from 1:1s)
It's a lot of meta thinking