RAZOOM Teams
Better decisions should survive the meeting.
What teams get.
Shared Cases
One Case, worked on by everyone who owns the decision.
Collaborative evidence
Colleagues add evidence; provenance stays attached.
Comments
Discussion anchored to the claim or assumption it concerns.
Review
Analyses reviewed before they inform a decision.
Approvals
Explicit sign-off on recommendations and escalations.
Roles
Who can contribute, review, approve or only read.
Shared organizational context
Strategy, constraints and definitions every Case can use.
Decision history
Every past decision with its rationale, searchable.
Decision Memory
Understand not only what your organization decided — but why.
Months later, the decision is questioned. Instead of reconstructing it from memory and email threads, the Case that produced it answers.
Why did we reject Project Atlas in March?
Decision: Rejected — revisit if enterprise pipeline exceeds 40 qualified accounts.
- Evidence
- 14 customer interviews; pipeline data Q4–Q1; build estimate from platform team.
- Assumptions
- Enterprise sales cycle of 9 months. Platform team at full capacity until Q3.
- Scenarios
- Build now, partner, defer. Defer dominated in 2 of 3 plausible futures.
- Dissenting views
- Product lead argued early entry would secure two anchor customers. Preserved in full.
- Decision threshold
- Building pays back only above 40 qualified enterprise accounts. Pipeline: 23.
- Final rationale
- Opportunity real but premature; capital better spent on retention this half.
Decide together. Remember why.
Teams is coming after the first individual release. Tell us how your team makes difficult decisions today.
