lessons
Engineering management
Lesson playbook — delete process, pathfinding, responsibility assignment, and keeping managers technical.
Topics: lessons
Tags: management engineering playbooks
Engineering management here means organizing hard technical work without drowning in process.
Pattern
Prefer pathfinders who own outcomes. Delete meetings and rules that don’t change physics or production. Keep layers thin.
Playbook
- Name a single owner for every critical path.
- Kill multi-hop approvals that add no information.
- Require managers to understand the design they manage.
- Use war-room intensity for real crises only.
- Write postmortems that change process, not just blame.
Examples (labeled)
| Domain | Pattern | Label |
|---|---|---|
| Production hell lore | Extreme hands-on management | Anecdote-heavy — source carefully |
| Launch campaigns | Mission control style ops | Aerospace practice |
| Software orgs | Small teams shipping FSD/Grok features | Company practice claims |
Failure modes
- Heroic founder bottleneck
- Process deletion of necessary safety reviews
- Burnout as culture