GET/v1/decisions
Decision Making
Clear decision ownership prevents the most common team dysfunction: decisions that get relitigated because nobody knew who owned them.
| Decision type | Owner | EM role | Example |
|---|---|---|---|
| Technical implementation | Lead engineer | Available, not approving | Library choice, code structure |
| Architecture | EM + Tech lead | Ensures alignment, documents outcome | New service boundary, data model |
| Scope trade-offs | EM + PM | Represents engineering capacity/risk | Cutting scope for a launch deadline |
| Hiring | EM (debrief consensus) | Breaks ties, owns final call | Extend offer vs. pass |
| Team process | Team (retro-driven) | Facilitates, implements changes | Standup format, PR review SLA |
| Compensation / promo | EM + HR | Primary advocate and owner | Promotion packet, comp adjustment |
Decision log
Every significant technical or process decision gets a short written record: the context, options considered, decision made, and who owns the outcome. This prevents decision fatigue from revisiting settled questions and helps new team members get up to speed fast.