alexe-ev Communicate Decisions & Trade-offs
Purpose
Help product teams communicate difficult decisions and explicit trade-offs in ways that build understanding, alignment, and trust — even when the answer isn't perfect.
Skill type
Conceptual skill
Use this skill when
- A difficult product decision needs to be communicated to stakeholders
- A deprioritization or "we won't do this" decision needs explanation
- A trade-off has been made and affected teams need to understand it
- A decision memo or communication needs to be structured
Do not use this skill when
- The goal is the decision itself (use build-roadmap-prioritization or relevant skill)
- The goal is executive narrative building (use build-executive-narrative)
Required inputs
- Decision made and alternatives considered
- Affected stakeholders or teams
Optional inputs
- Rationale for the decision
- Data or context supporting the decision
- Known objections or concerns
Upstream context
Works best when:
- Decision has been made with clear rationale
- Stakeholders are identified
Downstream handoff
Output can feed:
- map-stakeholder-influence (identify who needs to hear the decision and how)
Instructions
- State the decision clearly and early (don't bury the lede).
- Explain what was considered: alternatives, trade-offs, constraints.
- Explain the rationale: why this choice over others.
- Acknowledge what is being given up (the cost of the decision).
- Explain what happens next.
- Anticipate and address likely objections.
Output
Provide:
- Decision statement
- Alternatives considered
- Trade-off summary (what was chosen, what was given up)
- Rationale
- Next steps
- Objection handling (likely concerns and responses)
- Communication format recommendation (memo, meeting, Slack, etc.)
Risks / caveats
- Decisions communicated without rationale generate distrust
- Acknowledging trade-offs honestly builds more credibility than pretending the decision is perfect
- Stakeholders who feel heard are more likely to accept difficult decisions