Drive on an engineering team is sustained attention on an outcome — shipping a slice, closing an incident, finishing a design — not hours in a chair. Burnout is not a badge; neither is waiting for inspiration.
What actually moves work
- A goal small enough to finish this week, with a visible “done.”
- Removing the fake work (status meetings with no decision, reviews that sit three days).
- Autonomy inside a constraint: you choose how, the SLO and the date are not optional.
Pink’s popular trio (autonomy, mastery, purpose) is a decent checklist. If any one is missing for months, people leave or quietly stop caring. Managers cannot “motivate” that away with pizza.
Example
What breaks it: a week of status meetings, and no merge.
Better: a slice with a visible done this week. The SLO and the date stay. The team picks how.
Pitfalls
- Confusing busyness with drive (always in meetings, never merging).
- Crunch as a planning strategy.
- Only rewarding the firefight, never the boring reliability work that prevented it.
See accountability and self development.