Operationalizing the Market‑Sizing Process

10.1  Team Roles, Governance, and Decision Gateways

A market‑sizing project pulls in strategists, data scientists, finance partners, product managers, and sometimes external specialists. Without crisp division of labor and decision rights, projects drift, assumptions proliferate, and stakeholder trust erodes. Establishing a robust governance structure at the outset prevents those pitfalls.

Core Roles and Responsibilities

• Executive Sponsor
  Owns the business question, secures funding, and resolves scope clashes. Sponsors rarely touch spreadsheets but make the go/no‑go calls at each stage gate.
• Engagement Lead (EL)
  Single point of accountability for day‑to‑day execution—sets the workplan, manages interdependencies, and presents interim findings. Typically a director‑level strategy or corporate‑finance leader.
• Methodology Architect
  Designs the analytical approach—top‑down, bottom‑up, supply‑side, or hybrid—and ensures consistency with the playbook. Serves as arbiter when methodological disputes arise.
• Data Engineering & Analytics Team
  Builds and maintains data pipelines, cleanses inputs, runs econometric or NLP models, and populates the dashboard. They enforce version control and reproducibility standards.
• Subject‑Matter Experts (SMEs)
  Provide domain context—regulatory insight, technical feasibility, customer behavior. SMEs validate driver trees and trigger assumptions.
• Quality‑Assurance Reviewer (QA)
  Operates independently from the core team; inspects logic, sources, and audit trail at predefined checkpoints. Think of QA as the in‑house red team.
• Finance Partner
  Integrates market‑size outputs into valuation models, budget allocations, and investor messaging. Finance ensures price bases, currency, and inflation treatments align with corporate standards.

Governance Cadence and Stage Gates

1. Kickoff Gate – Sponsor, EL, Methodology Architect, and Finance approve the project charter: business question, boundary definition, precision target, and resource estimate.
2. Scoping Gate (end of Week 1) – Driver tree, data source list, granularity plan, and initial order‑of‑magnitude check signed off. QA confirms that critical assumptions carry ownership tags.
3. Methodology Gate – Choice of analytical lens (top‑down, bottom‑up, supply‑side) validated. Architects must document why alternatives were rejected and how triangulation will occur.
4. Data‑Lock Gate – All primary sources ingested, cleaned, and logged; gaps highlighted with mitigation plans. Sponsor authorizes spend on any paid datasets at this gate only—curbing scope creep.
5. First‑Draft Gate – Core numbers (TAM, SAM) produced; sensitivity tornado and basic scenario ranges generated. QA performs a full audit trace, flagging unresolved anomalies.
6. Triangulation Gate – Independent lens outputs reconciled using the Three‑Lens Framework (Chapter 7). Any >15 percent delta must be resolved or explicitly carried as a caveat.
7. Executive Review Gate – Sponsor and C‑suite review final numbers, scenario bands, and key risks. Decisions on investment, resourcing, or external disclosure are taken here.
8. Post‑Mortem Gate – Two weeks after delivery, the team captures lessons learned, updates the playbook, and archives the model with documentation for future refresh.

Decision Rights and RACI at a Glance

• Responsible (R) – Engagement Lead, Data Team for building the model.
• Accountable (A) – Executive Sponsor for scope and go/no‑go; QA Reviewer for methodological integrity.
• Consulted (C) – Methodology Architect, SMEs, Finance Partner at each gate.
• Informed (I) – Product, Sales, IR teams—receive dashboard outputs and narrative summaries.

Quality‑Assurance Protocols

• Code freeze 48 hours before each gate for reproducibility.
• Automated linting catches hard‑coded numbers in calculation cells.
• Source Trace Audit ensures every external figure links to the Source Log.
• Bias Scan—peer reviewer checks for optimism bias, double counting, and denominator mismatches.

Tools and Documentation

• Project Charter template—one‑pager capturing scope, success metrics, and key stakeholders.
• Stage‑Gate Checklist auto‑generated from the charter, integrated with project‑management software (Jira, Asana).
• Decision Log records each gate verdict, rationale, and action items—vital for audit trails and Sarbanes‑Oxley compliance.
• Live Dashboard in Tableau or Power BI pulls from the master workbook; permissioned for read‑only access by broader stakeholders.

Common Governance Pitfalls and How to Avoid Them

• Role ambiguity—multiple leads editing the same assumptions. Fix with a crisp RACI and locking critical input sheets.
• Gate skipping—pressure to meet a board date tempts teams to merge gates. Enforce lightweight virtual check‑ins rather than skipping.
• Late SME engagement—domain experts brought in after numbers are baked. Schedule SME reviews before Methodology and Data‑Lock Gates.
• Uncontrolled version sprawl—files circulate via email. Mandate a single source‑of‑truth repository with branch control.

Quick‑Action Checklist

• Charter signed by Sponsor and EL.
• RACI is published and accessible to the whole team.
• Gate calendar scheduled with reminders.
• QA function staffed and independent.
• Tool stack defined—data lake, model workbook, dashboard platform.
• Decision Log initiated; audit trail enabled from Day 1.

With governance and stage‑gates institutionalized, market‑sizing shifts from artisanal craft to industrial discipline—delivering faster turnarounds, fewer surprises, and a credibility premium that compounds with every successful engagement.