Vision to Value · 13 / 16

Appendix B: Decision System Blueprints and Economic Artifacts (Templates)

This appendix holds the templates that make the decision system carry weight in practice. The Decision Interface Charter, Decision Record Template, Operating Calendar Stub, and Canonical Rituals reference describe the machinery. The three economic artifacts that follow (Business-Case / Continuation-Threshold Template, Portfolio-Review Financial Pre-Read, GTM-to-P&L Traceability View) describe how the decision system is fed with evidence and reconciled against realized outcomes. Product Operations owns the machinery signals; Business Operations owns the economic signals; the templates belong together because the review they gate is one review. The Board Bet Review Charter (Chapter 7) is a specialization of the Decision Interface Charter below, adapted for the quarterly board surface.

New to the blueprint? If you are a newly-seated CPO, VP Product, or Director of Product Operations installing this for the first time, start with the ninety-day sequence in Appendix A - it walks the first Charter install, the first cadence, and the first re-decision, in order, before you expand. The templates in this appendix are the artifacts; the guide in Appendix A is the sequence for landing them.

Decision Interface Charter Template

PM-level contribution: surface the decision class that needs the charter; scope is decision-shape, not decision-content.

Decision:

• Decision type (launch readiness / pricing exceptions / platform intake / portfolio stop-continue / etc.):
• Accountable owner (single name / role):
• Decision forum & cadence (where it is decided, how often it is reviewed):
• Decision deadline (latest date the decision must be made):
• Decision record location (doc/link):
• Primary stakeholders (input providers vs. informed):

Context (2-3 lines):

Non-negotiables / constraints (what cannot be violated):

Success criteria (define "success" as outcomes; include a time horizon):

• Leading indicators (T+2 weeks):
• Mid indicators (T+6 weeks):
• Lagging indicators (T+12 weeks):

Required inputs (grouped by tier; who must provide what, by when):

Core inputs (the three strategic formulation surfaces; each reads in its own right, not as commentary on the others):

• Product:
• PMM/Marketing:
• Business Development / Partner (if the strategy depends on an external party):

Empowerment inputs (gating, not consultative). Business Operations pre-read and Competitive Intelligence (CI) market read are gating inputs to the portfolio review, not consultative; if absent or stale, the review cannot adjourn with a continue decision on that bet.

• Business Operations (P&L posture, booking-data view, portfolio-review pre-read):
• Competitive context (alternatives, substitutes, category position, win/loss signal, market-timing window, category-motion read):

Execution inputs (the seats that will carry the commitment into outcomes):

• Engineering:
• Design (with embedded discovery inputs):
• Product Operations (cadence, decision-record readiness, observability signal set):
• Customer Success/Support:
• Value Realization (cohort readiness, adoption-depth baseline, expansion gate):

Peer inputs (rotated by decision type):

• Sales/RevOps:
• Finance/Legal/Security (if relevant):
• Data/Analytics (if the decision depends on new instrumentation):

Decision rules (how this decision gets made):

• What "good enough" evidence looks like:
• Default if inputs are missing:
• Explicit "say no" boundaries (what cannot be promised / done):
• Escalation rule (exact trigger, not feelings):

Exception handling (how exceptions are requested, approved, and logged):

Communication plan (who is told, when, and how):

Learning loop (how outcomes flow back into the system):

• Review date(s):
• Re-decision triggers (what outcome/risk automatically reopens the decision). Include at minimum one outcome-evidence trigger (metrics miss guardrails) and one market-evidence trigger (competitor launches a substitute in the target segment, new entrant redefines the category, or a pricing move compresses the premium):

Decision Record Template (copy/paste)

PM-level contribution: author the record at the decision moment, not in retrospect; PM-Director audits for reconstructibility.

Decision ID (immutable; format: DR-YYYY-NNN):

Title (one sentence; decision stated in active voice):

Accountable owner (single name + role at time of decision):

Date decided:

Decision forum (where decided; link to meeting note or charter):

Status: active / superseded / closed

Decision statement (what was decided, in plain language - 2-3 sentences):

Context at time of decision (what was true when this was decided - 3-5 bullets):

Options considered (at least two; why each was considered and why the winning option was chosen):

Required inputs used (who provided what; version/date of each input):

Assumptions this decision depends on (the 2-4 assumptions whose invalidation would force reopen):

Success criteria (T+2 / T+6 / T+12 indicators - link to metric definition, not just the name):

Re-decision trigger (exact condition that forces formal reopen - not feelings):

Related decisions (parent decision; sibling decisions; decisions this one supersedes):

Review date(s) (when this record is audited for findability, not just content):

Record location (canonical link - must be durable, searchable, and linkable from the charter that governs this decision type).

Hygiene rule: A decision record that cannot be found in 30 seconds by someone who was not in the room is not a decision record - it is a meeting note. Product Operations audits findability quarterly.

Operating Calendar Stub (copy/paste)

Purpose: a single published, versioned calendar that sequences the rituals in the Canonical Rituals table, so the organization stops negotiating schedule ad-hoc.

Fields (per ritual):

• Ritual name (must match Canonical Rituals table):
• Owner:
• Cadence window (fixed day/time; not "when calendars align"):
• Pre-read deadline (how long before the meeting inputs must land):
• Decision artifact location (where the output will be written - must match Decision Record Template):
• Calendar version and review date (annual review cadence):

Sequencing rules (stated once at the top of the calendar):

• Portfolio review sits upstream of product-line review (quarterly before monthly), not the reverse
• Launch Readiness Review dates are derived from committed ship dates, not negotiated per-launch
• Team Outcome Reviews are immutable weekly - they do not move for executive schedules
• A ritual that misses its scheduled window twice in a cycle triggers a charter review, not a calendar slip

The operating calendar is itself an artifact. Publish it, version it, audit it annually. A calendar that lives only in individual leaders' heads is a Product Operations failure.

Canonical Rituals of a Product Organization (Reference)

The rituals named throughout this book, assembled in one place so the reader can inventory them against their own operating calendar. All rituals are named in the body of the book; nothing here is new. What is new is the catalogue.

The operating calendar is itself an artifact. Publish it, version it, and review it annually. When a ritual in this table does not exist or does not produce the stated output, that is a diagnostic - not a failure of attendance.

Business-Case / Continuation-Threshold Template

PM-level contribution: maintain the threshold math and the evidence record; PM-Director signs; CPO reviews.

Purpose. A structured document that every strategic bet must carry from formulation through portfolio review. Replaces the ad-hoc business case (written once at approval, never revisited) with a living artifact whose continuation-threshold field is evaluated at each portfolio review. Prevents the failure mode Chapter 2 names - continued investment in bets whose assumptions have invalidated - by making the evidence required for the next increment explicit at the time of the current increment, not retrofitted after a miss.

Owner. Product Business Operations Director. Finance supplies enterprise-level financial methodology; the PM supplies product content; Business Operations owns the artifact and its evolution across portfolio cycles.

Consumers. VP Product / CPO (portfolio review; renew / revise / kill decision). PM / Director PM for the bet (commitment sequencing, re-decision trigger authoring). CFO (capital envelope reconciliation against enterprise plan). PMM Director (commercial motion economics, pricing coherence with business case). Chief Architect (reversibility and dependency reads inform cost-of-delay).

Named fields.

• Bet ID (immutable; format: SB-YYYY-NNN; links to Decision Record)
• Bet title (one sentence; the bet stated as hypothesis, not feature)
• Accountable owner (single name + role)
• Date authored / date of current revision / revision number
• Investment envelope (explicit funded amount for the current increment - engineering, design, PMM, CS capacity translated to dollars; not "the team's budget")
• Expected return shape (revenue / margin / retention / strategic-position / defensive; named, not implied; with time horizon)
• Cost-of-delay estimate (what the organization forgoes per quarter of delay; references the alternatives named in the portfolio pre-read)
• Unit-economics hypothesis (per-customer or per-account economics the bet depends on; named inputs, not assumed)
• Continuation threshold (the load-bearing field) - the specific evidence this bet must produce by the next portfolio review to earn its next increment of investment. Must be outcome-evidence, not activity-evidence ("2,000 activated accounts in segment X with retention above 85% at T+90", not "launched v2"). Must reference leading / mid / lagging indicators per Chapter 2.
• Assumptions the threshold depends on (the two-to-four assumptions whose invalidation forces the bet back to formulation, not just re-scope)
• Re-decision trigger (exact conditions that reopen the bet between portfolio reviews; at minimum one outcome-evidence trigger and one market-evidence trigger, matching the Decision Record's re-decision field - threads the artifacts)
• Alternatives considered (what the same envelope would fund instead; named, not generic)
• Scarcity dimension (capital / capacity / attention per Chapter 2's three-constraint frame)

Cadence. Authored at commitment-hardening (Chapter 2's Elaboration-to-Commitment gate). Refreshed at every portfolio review (quarterly) - the continuation-threshold field is re-evaluated against evidence to date. Archived when the bet is closed; continuation-threshold misses and successes both feed the learning loop.

Gating status. Gating input to the portfolio review per the sensor-compulsion protocol above (defined in Chapter 8, Principle 6). If the business case is absent, stale (older than one portfolio cycle without refresh), or has no continuation-threshold field authored, the portfolio review cannot adjourn with a continue decision on the bet. The review can still adjourn with a pause or a kill decision - absence of the artifact is not a default-to-continue.

Re-decision trigger relationship. The re-decision trigger field in this artifact is the same trigger carried in the bet's Decision Record. When the trigger fires (outcome evidence misses continuation threshold or market evidence invalidates assumptions), the bet returns to formulation review. This artifact names the economic shape of the re-decision; the Decision Record names the decision context; they must match.

What this artifact is not. Not an enterprise-level financial model (FP&A owns company-wide modeling; this is bet-level). Not a PRD (the PM's PRD describes what is being built; this describes what the organization is investing in). Not a retrospective (the Outcome Review evaluates a bet after its outcome horizon closes; this artifact is forward-looking at every cycle). Not a pricing model (pricing is PMM-owned and appears as an input to unit-economics hypothesis, not as the artifact's subject).

Launch Narrative Brief (PMM Instance Template)

PM-level contribution: provide the empowerment inputs the Director of Product Marketing carries into the interface; PM does not own the brief itself.

The Launch Narrative Brief is the PMM's instance of the Decision Interface Charter, instantiated at the launch altitude. It carries nine fields, in the order PMM authors them. A brief that cannot be reconstructed in thirty seconds by a PMM who was not in the room fails the same hygiene rule the Board Bet Review Charter carries.

Field 1: Launch-bet fit. The strategic bet this launch serves, named from the portfolio record. One sentence. If the launch does not trace to a named bet, the launch is a feature announcement, which is the anti-pattern Chapters 5-6 toolkit describes.

Field 2: Three-tier message hierarchy. Tier 1 message: the one sentence the category needs to hear (belongs to Corporate and CMO narrative). Tier 2 message: the one sentence the buyer needs to hear to shortlist (belongs to PMM and positioning). Tier 3 message: the three to five product-specific sentences the evaluator needs to hear to choose (belongs to PMM with Product input). Each tier names its owner; a tier without a named owner is a tier that will drift to whoever writes the collateral first.

Field 3: Named-alternative competitive frame. The 2-3 named competitive alternatives the buyer will evaluate this launch against, with the differentiation axis PMM owns against each. "Named" is load-bearing; generic competitive frame (market-segment competitors, rising challengers) does not count.

Field 4: Proof obligation. The evidence PMM commits to producing within 90 days of launch, traceable to the Tier 1, 2, and 3 messages. If the Tier 1 message claims "category leadership in X," the proof obligation names the metric, the source, and the publish date.

Field 5: Success chain instrumentation. Awareness metric (owner: Marketing). Adoption metric (owner: Product). Revenue metric (owner: Sales Ops). Each metric named with its source system, its cadence of read, and its owner. A launch without all three is a launch without a success chain.

Field 6: Re-decision trigger. The specific signal that would reopen the positioning decision post-launch. Example: "If cohort adoption at Week 4 is below 40% of target across two consecutive launches, reopen the positioning frame."

Field 7: Director of Product Marketing sign-off. Brief is not approved until the Director of Product Marketing signs Fields 1 through 6 on the record, with date and reasoning. This is the charter discipline applied at launch altitude.

Field 8: Sales enablement handoff. Named artifact delivered to Sales (battlecard, demo flow, objection-handler), with a named owner on the Sales side and a named date.

Field 9: Auditable-by. Marketing team (for awareness integrity), Product (for adoption integrity), Sales Ops (for revenue integrity). All three can read the brief on demand; the brief is one of the inputs to the CPO-CMO interface.

Portfolio-Review Financial Pre-Read

Purpose. The artifact that converts the quarterly portfolio review from a status readout into a capital-allocation decision forum. Without it, portfolio reviews default to the failure mode named in the Canonical Rituals table: becomes status readout; no stop decisions made. The pre-read is what lets the PLT make defensible renew / revise / kill calls against the three scarcity constraints - capital, capacity, attention - by putting comparable per-bet economics in front of every decision-maker 48 hours before the review.

Owner. Product Business Operations Director. Synthesized from each bet's Business-Case / Continuation-Threshold Template (above) and from booking-data / P&L hygiene work. Finance supplies enterprise reconciliation; PMs supply bet-level inputs.

Consumers. VP Product / CPO (chair of portfolio review; primary decision-maker). PLT members (all seats, per Chapter 1 PLT definition). CI Director (paired with market-read pre-read for the same review). CFO (reconciliation against enterprise capital plan).

Named fields (per bet in the portfolio).

• Bet ID and title (threaded to Business-Case / Continuation-Threshold Template)
• Sunk cost to date (cumulative investment across prior increments; engineering, design, PMM, CS)
• Marginal investment required for next increment (the envelope the bet is asking for this cycle)
• Continuation-threshold evidence to date (actual leading / mid / lagging indicators vs. the threshold authored at prior review; red / amber / green against each)
• Unit-economics read (current cohort economics vs. hypothesis; named deltas)
• Opportunity cost of next increment (what the same envelope would fund across the alternatives named in the business case; quantified, not abstract)
• Re-decision trigger status (fired / armed / resolved; if fired, this bet is escalated to formulation review before portfolio adjourns)
• Business Operations disposition recommendation (renew / revise / kill, with the specific evidence supporting the recommendation; the sensor output, not the decision)

Named fields (portfolio-level summary).

• Capital envelope for the planning window (total portfolio budget across bets)
• Capacity constraint read (engineering, design, PMM throughput actually available vs. nominal)
• Attention constraint read (count of bets currently in committed state vs. PLT working-memory capacity)
• Disposition mix (ratio of bets recommended for renew / revise / kill; feeds the bet-disposition-mix observability signal per Chapter 5)
• Reconciliation to prior cycle (which bets moved disposition state since last review, with reason)

Cadence. Published to PLT 48 hours before each quarterly portfolio review. Archived after the review with PLT decisions annotated against recommendations (Business Operations recommended kill / PLT decided revise / reason on record). Quarterly review cadence is non-negotiable per the Canonical Rituals table.

Gating status. Gating input to the portfolio review per the sensor-compulsion protocol. If the pre-read is absent, stale (older than 72 hours at review start), or missing fields on any active bet, the portfolio review cannot adjourn with a continue decision on the affected bets. This is the single most load-bearing gating relationship in the empowerment tier - it is what converts Business Operations from advisory to accountable.

Re-decision trigger relationship. The pre-read is where re-decision triggers fire in practice. When a bet's continuation-threshold evidence comes in red, the pre-read surfaces it; when Business Operations recommends kill and PLT decides revise, the revision must author a new continuation-threshold field in the Business-Case template before the decision is recorded. No bet exits a portfolio review in committed state without a refreshed continuation threshold - the pre-read enforces the refresh.

What this artifact is not. Not a status update (the pre-read is decision-supporting; PMs provide status through their own Team Outcome Reviews). Not a demand for Finance-grade rigor (pre-read economics are decision-grade - defensible, comparable, traceable - not audit-grade). Not a replacement for the bet's own business case (the pre-read synthesizes across bets; the business case lives per-bet). Not a kill-recommendation engine (the pre-read surfaces evidence; the PLT decides. Business Operations is sensor, not decider - this is what the empowerment tier means).

GTM-to-P&L Traceability View

Purpose. The report that connects strategic product investment to realized business outcome at bet-level, portfolio-level, and business-level. Answers the question Chapter 2 names but does not operationalize: did the bet the organization made actually move the commercial results the bet promised? Closes the bidirectional tracking responsibility in the Business Operations definition - product initiatives moving booking data in the expected direction, and booking-data deltas surfacing where bets are under- or over-performing their commercial hypothesis. Prevents the GTM-to-P&L disconnection failure mode where sales motion is instrumented through RevOps, product motion is instrumented through Product Operations, and the seam between them is unowned.

Owner. Product Business Operations Director. Consumes data from RevOps (pipeline, booking), from PMM (campaign performance, pricing realization), from CS-ops (expansion, retention by cohort), and from Product analytics (adoption depth by cohort mapped to bet). No single other function owns the integration.

Consumers. VP Product / CPO (bet-to-commercial-outcome read for portfolio decisions). CFO (product-portfolio contribution to enterprise P&L; reconciliation with enterprise financial plan). Sales Director / RevOps (product-pull on pipeline; where GTM motion is and is not converting bet intent into booking data). PMM Director (pricing realization vs. pricing hypothesis; segment-mix vs. ICP hypothesis). Value Realization lead (adoption-depth trajectory vs. commercial-outcome trajectory; the leading-to-lagging bridge).

Named fields.

• Bet-level roll-up (per active bet): committed envelope, realized revenue contribution (new + expansion), realized margin contribution, cohort adoption-depth trajectory, pricing realization vs. hypothesis, segment-mix vs. ICP hypothesis
• Portfolio-level roll-up: portfolio contribution to enterprise ARR / NRR / GRR, contribution-to-envelope ratio (realized commercial outcome per dollar of committed investment, across the portfolio)
• GTM-motion cut (per bet): where in the sales funnel the bet's commercial motion is converting or leaking (top-of-funnel demand, sales-qualified conversion, closed-won rate, time-to-first-value, expansion motion); named against the sales system's instrumentation, not against an independent shadow system
• Regional / segment P&L cut: where the product-initiative-to-business translation is strongest and weakest, by region and segment; the booking-data hygiene work cashed as a report
• Variance flags: bets where realized commercial outcome deviates from business-case hypothesis by > 20%; armed as potential re-decision triggers

Cadence. Monthly refresh for the portfolio-level and regional cuts (bookings close cadence). Quarterly refresh for the bet-level roll-up (aligned with portfolio review). On-demand for specific-bet drill-down when a variance flag arms. Variance flags are reviewed at the monthly Product-line Review (per Canonical Rituals) and can escalate to off-cycle portfolio review.

Gating status. Consultative to the portfolio review, not gating. The Portfolio-Review Financial Pre-Read is the gating artifact; the traceability view is what the pre-read draws bet-level commercial evidence from. Gating to the Product-line Review at bet-level - a line review cannot adjourn with a continue decision on a bet whose traceability view shows an armed variance flag, without first routing the flag to the bet's re-decision trigger evaluation.

Re-decision trigger relationship. Variance flags in this view are candidate re-decision triggers. When a flag arms (> 20% deviation between realized and hypothesized), the bet's Business-Case / Continuation-Threshold Template is pulled, the re-decision trigger field is evaluated, and if the trigger fires the bet goes to formulation review. The traceability view is therefore the empowerment-tier sensor that surfaces economic invalidation in near-real-time, ahead of the quarterly portfolio cycle.

What this artifact is not. Not a sales dashboard (Sales Director owns pipeline and quota dashboards; this view is bet-to-commercial-outcome, not rep-to-quota). Not a product-analytics dashboard (PM owns adoption-depth and feature-usage analysis; this view consumes adoption depth as one input among several). Not a CFO dashboard (CFO owns enterprise P&L; this view is the product-portfolio contribution to that P&L, not the P&L itself). Not a replacement for the Value Realization Report (Value Realization measures whether customers reach promised value; this view measures whether bets move business results. Both must exist).