Systems of Engineering Management

1. Introduction
"There are few things peaceful about managing in rapidly growing companies, but I've never found anywhere better to learn and to grow."
"Organizational design sets the right people in the right places, empowers them to make decisions, and then holds them accountable for their results."
2. Organizations
"The fundamental challenge of organizational design is sizing teams."
Some rules of thumb:
- Managers should support six to eight engineers
- MoMs should support four to six managers
- On-call rotations want eight engineers
- Small teams (fewer than four members) are not teams
Innovation and maintenance should be done by the same teams, otherwise it's very easy to establish a two-class culture.
Four possible team states and what to do:
- Falling behind: add people
- Treading water: reduce WIP
- Repaying debt: add time
- Innovating: add slack
"I have found it much easier to have rapid growth periods for any given team, followed by consolidation/jelling periods during which the team jells. The organization will never stop growing, but each team will."
As a leader, try to fix one team at a time, not all of them at once.
"One of the most exciting aspects of organizational design is that there are so many different approaches that work well."
"Productively integrating large numbers of engineers is hard."
Roughly each order of magnitude of engineers requires a new layer of management.
"You only get value from projects when they finish: to make progress, above all else, you must ensure that some of your projects finish."
"The second most effective time thief that I've found [after hiring] is ad hoc interruptions: getting pings on HipChat or Slack, taps on the shoulder, alerts from your on-call system, high-volume email lists, and so on."
"The one thing that I've found at companies with very few interruptions and have observed almost nowhere else: really great, consistently available documentation."
3. Tools
"Systems thinking is the most universally useful toolkit I've found."
Developer velocity is commonly tracked via:
- Delivery lead time
- Deployment frequency
- Change fail rate
- Time to restore service
"Product management is an iterative elimination tournament, with each round consisting of problem discovery, problem selection, and solution validation."
"Agreeing on strategy and vision has been the most effective approach that I've found to alignment at scale."
Strategy vs Vision:
- Purpose
- S: Approach to a specific challenge
- V: A gentle, aligning pressure
- Character
- S: Practical
- V: Aspirational
- Time Frame
- S: Variable
- V: Long Term
- Specificity
- S: Accurate, detailed
- V: Illustrative, directional
- Quantity
- S: As many as useful
- V: As few as possible
Useful structure for strategy docs: diagnosis, policies and actions.
"You'll know a vision is succeeding when people reference the document to make their own decisions."
"Migrations are both essential and frustratingly frequent as your codebase ages and your business grows: most tools and processes only support one order of magnitude of growth before becoming ineffective."
"There are two managerial skills that have a disproportionate impact on your organization's success: making technical migrations cheap, and running clean reorganizations."
"There are two best kinds of reorganizations:
- The one that solves a structural problem.
- The one that you don't do."
Manager to engineer ratio:
- 3-5 if you expect manager to do IC work
- 5-8 otherwise
Common way to lead without authority: Model, document, share.
"Time management is the enduring meta-problem of leadership."
4. Approaches
"Keeping an organization aligned is challenging in the best of times, and exceptions undermine one of the most powerful mechanisms for alignment: consistency."
"Policy success is directly dependent on how we handle requests for exception. Granting exceptions undermines people's sense of fairness, and sets a precedent that undermines future policy."
"Exception debt" can build up if too many exceptions are made.
"With the right people, any process works, and with the wrong people, no process works."
"As a leader you can't run from problems; engage 'em head-on."
"Do the right thing for the company, the right thing for the team, and the right thing for yourself, in that order."
"Smaller companies expect more execution focus than relationship management focus from their managers."
"Many organizations become bottlenecked on approvals, which is a sure proxy for lack of trust."
5. Culture
"Every important people decision should have a rubric around how folks are evaluated."
Providing opportunities (career, projects, growth, learning, ...) and a strong sense of membership are two key pillars of fostering a strong culture.
"Having a wide cohort of coworkers who lead critical projects is one of the most important signifiers of good organizational health."
"The balancing of positive and negative freedoms is a fundamental task of managers and management."
6. Careers
Main sources of candidates:
- Referral
- Inbound
- Sourced
The Hiring Funnel:
- Identify candidates
- Motivating them to apply
- Evaluating them
- Closing them
Should measure and track all of these, and ideally extend the process by additional tracked phases
- Onboarding
- Impact
7. Promotions & Retention
"The most sacred responsibilities of management are selecting your company's role model, identifying whom to promote, and deciding who needs to leave."
Three key tools of performance management:
- Career ladders
- Performance designations
- Performance cycles
Any role with >10 people should have a fleshed out career ladder.
For each level, should have clear expectation for each value. Level boundaries should be clear.
"If there is one component of performance management that you're going to invest in doing well, make it the ladders: everything else builds on this foundation."
Performance designations often start simple as a five-point scale, sometimes later growing more complex, e.g. 3x3 grid.
"Calibrations fall soundly in the unenviable category of things that are terrible but have no obvious replacement."
"Surprise is the cardinal sin of performance management."
8. Appendix
"One tension in management is staying far enough out of the details to let folks innovate, yet staying near enough to keep the work well-aligned with your company's value structure."
"Around the time your team reaches three engineers, you'll want to be running a sprint process."