Governance Forum

Purpose

Conduct a structured decision meeting where the Portfolio Manager, executives, and functional leaders review A3.4 evidence, deliberate on each prototype, and make binding go/no-go decisions—separating evidence review from opinion, deliberation from decision, and recommendation from authority to minimise cognitive biases that derail investment decisions.

The governance forum is the mechanism through which A3.5 decisions are made. Without it, go/no-go decisions happen in hallways, emails, and one-on-one meetings —where political influence replaces evidence, anchoring replaces analysis, and the highest-status person's opinion becomes the decision.

When to Use

Use governance forum when:

• Making A3.5 go/no-go decisions (mandatory—forum is A3.5's core mechanism)
• Investment exceeds $500K (threshold for formal governance)
• Multiple prototypes require comparative portfolio-level decisions
• Stakeholders have conflicting views on a prototype's future
• Decision requires cross-functional buy-in (engineering capacity, budget, strategic alignment)

Do NOT use when:

• Decision is unambiguous—e.g. all lenses fail, recommendation is unanimous kill. Portfolio Manager can decide directly; forum time is better spent on contested decisions
• As ongoing status meetings—forums are decision events, not reporting events

Sample Size and Duration

Forum duration: 3–5 hours (1 prototype: 2–3 hours; 2–3 prototypes: 4–5 hours)

Attendees: 5–8 people (Portfolio Manager + 4–7 decision participants)

Preparation: Pre-read review 1–2 hours per attendee; Portfolio Manager preparation 4–8 hours

Post-forum: Decision documentation 2–4 hours; communication 2–4 hours

Total A3.5 effort: 40–60 person-hours across all participants (including preparation and follow-up)

Prerequisites

• Gate A3.5-1 passed: All A3.4 reports reviewed, portfolio context current, budget/team confirmed
• Pre-read distributed: A3.4 evaluation reports, ROI models, risk registers, SWOT analysis sent to attendees ≥48 hours before forum
• Attendees confirmed: Portfolio Manager (chair), Product Owners (presenters), CFO/Finance, CTO/Engineering, VP Product/Strategy, 1–2 additional functional leads
• Decision criteria established: Three-lens pass/fail thresholds, portfolio constraints, risk tolerance agreed before the meeting
• Agenda published: Timed phases with explicit rules per phase
• Room/logistics: 3–5 hours blocked; no interruptions; recording/minutes assigned

Complete Procedure

Phase~1: Evidence Review (60–90 minutes)

Rules: Clarifying questions only. No opinions. No debate. No reactions (positive or negative).

For each prototype (20–30 minutes each):

1. Product Owner presents A3.4 summary: three-lens verdicts, key metrics, recommendation, confidence level (5 minutes)
2. Product Owner presents ROI summary: expected NPV, scenarios, break-even thresholds, killer variables (5 minutes)
3. Product Owner presents risk profile and SWOT highlights (5 minutes)
4. Clarifying questions from forum members (5–15 minutes). Questions that probe data: “What was the Week~6–8 retention trend?” Not opinions disguised as questions: “Don't you think retention is too low?”

Why separate evidence from deliberation: Lovallo and Sibony showed that when the first speaker expresses an opinion, subsequent speakers anchor on it. By presenting evidence without opinions first, all forum members form independent assessments before hearing each other's views.

Phase~2: Deliberation (60–90 minutes)

Rules: Opinions permitted. Every objection must be classified as evidence-based or non-evidence-based.

For each prototype (20–30 minutes each):

1. Portfolio Manager states the A3.4 recommendation
2. Supporter argument: One member argues for the recommendation (2–3 minutes)
3. Devil's advocate: One member argues against the recommendation (2–3 minutes) —assigned in advance, not voluntary. The devil's advocate's job is to find the strongest possible counter-argument, even if they personally agree with the recommendation
4. Open discussion: Forum members raise concerns, question assumptions, propose conditions (10–15 minutes)
5. Objection classification: Portfolio Manager flags non-evidence objections—sunk cost (“We've spent $300K”), political (“The sponsor wants this”), optical (“The board expects three launches”)—and separates them from evidence-based concerns (“Retention is below target”, “NPV is negative in worst case”)

Phase~3: Portfolio Context (30–45 minutes)

Rules: Shift from per-prototype to portfolio-level thinking.

• Resource-reality check: Budget available vs. required for all go candidates. Team capacity. Timeline. “Can we afford all recommended go decisions?”
• Portfolio balance: Risk distribution (core/adjacent/transformational). Strategic theme coverage. Time horizon balance.
• Opportunity cost: What are we not doing by committing resources here? Are there pipeline concepts waiting for capacity?
• Forced ranking (if resource-constrained): If budget supports only 1 of 2 go candidates, which gets priority? Rank by strategic value × evidence strength.

Phase~4: Decision (30–45 minutes)

Rules: Decisions are binding. Dissent documented but does not block.

For each prototype:

1. Portfolio Manager states proposed decision: Go / Conditional Go / Pause / Kill
2. For Conditional Go: explicit conditions stated (milestones, deadlines, kill criteria)
3. Forum votes or reaches consensus (mechanism pre-agreed: majority, supermajority, or Portfolio Manager decides after hearing views)
4. Dissent documented: Who dissented, why, what evidence they cited. Dissent is respected (“disagree and commit”), not suppressed
5. Decision recorded: Decision, rationale, conditions, vote count, dissent—in writing, during the meeting

Quality Criteria

1. Structured phases: Evidence review, deliberation, portfolio context, and decision separated with explicit rules per phase
2. Evidence-first: No opinions expressed until Phase~2
3. Devil's advocate: Counter-argument presented for every go recommendation
4. Non-evidence objections flagged: Sunk cost, political, and optical arguments identified and separated
5. Decisions binding: Every prototype decided with rationale; no concepts left in limbo
6. Dissent documented: Disagreement recorded with respect; “disagree and commit” practiced
7. Time-bounded: ≤5 hours; decisions not deferred to future meetings

Theoretical Foundation

Seminal references:

• : Lovallo and Sibony's McKinsey research demonstrated that structured decision processes reduce bias by 40–60% compared to unstructured deliberation. Key mechanisms: separating advocacy from decision, requiring devil's advocate, documenting dissent, and using pre-committed criteria. The governance forum operationalises all four.
• : Identified the biases that governance forums must counteract: anchoring (first opinion dominates), groupthink (consensus suppresses dissent), sunk cost (“we've invested too much to stop”), and confirmation bias (seeking evidence supporting the preferred outcome).

Contemporary references:

• : Established the gate meeting as the operational centre of stage-gate governance: prepared attendees, structured agenda, evidence-based criteria, real-time decisions (not deferrals), and documented outcomes. Cooper's principle: “Gates must have teeth”—the forum has decision authority, not advisory status.
• : Demonstrated that effective governance requires psychological safety for dissent. If junior members cannot challenge senior executives' positions, the forum becomes a rubber-stamp ceremony. The VP's C015 dissent (disagree and commit) is only possible in a psychologically safe forum.

Forum vs. Other Decision Approaches

Handling Common Forum Dynamics

Challenges and Solutions

Challenge 1: Forum as Rubber Stamp

Symptoms: 100% approval rate across 3 years. No concept ever killed. Forum takes 45 minutes for 3 prototypes.

Solutions: Track kill rate (target 20–40%). 0% kill rate is a process failure, not a success. Require devil's advocate for every go recommendation. Portfolio Manager reviews forum effectiveness quarterly: “Are we making real decisions or performing governance?”

Challenge 2: Political Override Post-Forum

Symptoms: Forum kills C015 (4–1 vote). Following week, sponsor arranges private meeting with CEO. C015 is resurrected with no new evidence.

Solutions: Forum decisions are binding. Post-forum overrides require: (a) new evidence not available at forum, (b) written justification, (c) documented in portfolio record with override accountability (named person). This doesn't prevent overrides—it makes them costly and visible.

Challenge 3: Insufficient Preparation

Symptoms: Attendees arrive without reading pre-read. Phase~1 becomes a 2-hour presentation. No time for deliberation. Decisions rushed.

Solutions: Send pre-read 48+ hours before forum. Open Phase~1 with: “The reports were distributed Tuesday. I'll assume everyone has read them. We'll proceed to clarifying questions.” If an attendee clearly hasn't read, their clarifying questions reveal it—but the forum doesn't slow for them.

Relationship to Other Methods

Governance Forum receives input from:

• Three-Lens Evaluation (the referenced method): Per-lens verdicts and overall recommendation are the primary decision input
• ROI Modelling (the referenced method): NPV, IRR, payback period for financial justification
• Sensitivity Analysis (the referenced method): “What would have to go wrong?” framing for deliberation
• Risk Assessment Matrix (the referenced method): Risk profile and unmitigatable risks for deliberation
• SWOT Analysis (the referenced method): Strategic context, W+T danger zones for strategic discussion

Governance Forum provides output to:

• A4 Charters: Go decisions with scope, budget, team, timeline, kill criteria
• Kill/Pause Memos: Documented rationale, learnings, reusable assets, revival conditions
• I1 Portfolio: Pipeline update reflecting decisions
• B3 Finance: Budget authorisations for A4–A7
• B2 HR: Team assignments for A4 squads
• Stakeholder Communications: All-hands announcement, team briefings, board updates

Tools and Templates

• Agenda template: Timed 4-phase structure with rules per phase (distribute with pre-read)
• Decision record: Structured template capturing decision, rationale, conditions, vote, dissent per prototype
• Pre-read package: A3.4 evaluation reports, ROI summaries, risk registers, SWOT analyses (compiled by Portfolio Manager)
• Facilitation: Timer (enforce phase boundaries); whiteboard/Miro (capture objections by type); decision log (real-time documentation)
• Post-forum: Confluence/Notion (decision record archive); email (stakeholder communication template)

• A. C. Edmondson (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
• D. Kahneman (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
• D. Lovallo & O. Sibony (2010). The Case for Behavioral Strategy. McKinsey Quarterly. (2). pp. 30–43.
• E. Schmidt & J. Rosenberg (2014). How Google Works. Grand Central Publishing.
• J. Bezos (2016). 2015 Letter to Shareholders. https://www.aboutamazon.com/news/company-news/2015-letter-to-shareholders.
• R. G. Cooper (2017). Winning at New Products: Creating Value Through Innovation. 4 ed. Basic Books.