Practice : Explicit Trade-off Logs
Purpose and Strategic Importance
Explicit Trade-off Logs make product decisions transparent by documenting what was chosen, what was sacrificed, and why. This creates organisational memory, reduces hidden risks, and builds trust with stakeholders.
This practice shifts decision-making from implicit compromises to visible, deliberate choices.
Without trade-off logs, stakeholders are surprised by outcomes, teams overcommit, and alignment breaks down.
Description of the Practice
- Decisions are recorded with context, options considered, trade-offs chosen, and rationale.
- Logs are accessible to all, building transparency across teams and leadership.
- They act as a reference for revisiting decisions when context shifts.
How to Practise It (Playbook)
1. Getting Started
- Introduce a lightweight template (e.g., decision, trade-off, rationale, impact).
- Capture trade-offs during backlog prioritisation or roadmap reviews.
- Store logs in a shared space (wiki, Miro, Jira).
2. Scaling and Maturing
- Standardise trade-off logging across teams.
- Integrate logs into governance reviews.
- Revisit logs regularly to assess whether trade-offs still hold.
3. Team Behaviours to Encourage
- Transparency in decision rationale.
- Openness to questioning assumptions.
- Accountability for long-term consequences.
4. Watch Out For…
- Overly detailed logs becoming bureaucratic.
- Logs written but not shared or referenced.
- Avoiding difficult conversations about sacrifices.
5. Signals of Success
- Qualitative: Stakeholders report fewer surprises in product direction.
- Quantitative: Reduction in escalations due to unclear decisions.