Aligned autonomy
Direction, priorities and boundary standards set centrally, with methods left to teams. It answers what to standardise across teams (standardise where teams meet, and leave the inside to the team), and it is the balance an operating cadence strikes.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Deciding what an organisation-wide standard should contain; any time more meetings are proposed as the answer to a failure of coordination.
Where it stops working
Where "where teams meet" ends and "team internals" begin is a judgment, and it gets redrawn when a boundary fails. Drawn too wide, it becomes central control of methods. Drawn too narrow, it leaves the seams in chaos.
Where the standard uses it
- DE-5Designing how work flowsProcess selection, developer experience, and AI-assisted workflows.
- TJ-3Code review and quality standardsIncluding standards for AI-generated code.
Used alongside it
- AI-assisted developer productivity contested
- Code review as knowledge transfer research
- Contract at the boundary practice
- Developer experience practice
- Goodhart's law practice
- Quality as a system practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Aligned autonomy. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.aligned-autonomy). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/aligned-autonomy