Fit the Mandate on Two Pages
The Two-Page Mandate
Companion to The CTO You Actually Need · Updated 2026-09-29
Use this structure. Put supporting detail in the dossier, not in the core mandate.
- Why the role exists. One paragraph connecting business change, evidence-backed constraint, and executive-sized work.
- First 12–24 month outcomes. Three to five outcomes. For each: business result, capability created, evidence, and guardrail.
- Scope and exclusions. Functions, products, systems, geography, budget, team, and external obligations. Name what is outside the role.
- Decision rights. The five to ten most consequential decisions with the CTO’s right and final escalation.
- Essential relationships. CEO, product, engineering, CIO, CISO, finance, sales, operations, business units, board, customers, regulators, or partners as relevant. Name predictable conflict.
- Inherited conditions. Team, commitments, risk, vendors, architecture, financial limits, founder role, and work that cannot be stopped.
- Evolution and review. How the role may change and the dates for 30-, 90-, 180-, and 365-day review.
