CPO Role Design Questionnaire
Define the CEO-CPO contract before hiring a senior product leader
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 94%
The CPO Role Design Questionnaire begins with the CEO rather than a generic executive job description. First ask what the CEO genuinely wants to spend time on and retain. Then assign ownership for product vision, roadmap execution, and cross-functional decisions. Clarify the primary problem the hire must solve, such as process, strategy, team building, or attracting stronger talent. Next define how the role intersects with engineering, design, data science, general management, and operations. Convert those choices into explicit swim lanes and accountability before choosing a title or candidate. The mechanism is simple: role clarity precedes hiring. If the CEO still intends to own the roadmap and execution, a nominal CPO will have little meaningful work and conflict is likely. Designing the contract first reveals whether the company needs a CPO, VP of Product, or a broader GM-style leader.
Origin
Gupta described a questionnaire he gives CEOs who are considering a VP of Product or CPO. His first question is what the CEO wants to do, followed by questions about the organizational outcome, talent needs, adjacent functions, and the division of responsibility among senior leaders.
Core principles
- 01The CEO's desired work determines whether a senior product role has room to operate
- 02Product vision must remain coherent with company vision
- 03Senior product leadership includes execution and operational excellence
- 04Clear swim lanes prevent overlap from becoming leadership conflict
- 05The title and candidate must match the actual organizational problem
How to run it
- 1
Start with the CEO
Ask what the CEO wants to spend time on after the hire and what they are truly willing to delegate. Make the answer behavioral rather than aspirational.
Pro tip List the recurring product decisions the CEO currently makes and mark which ones will transfer.
Watch out Do not hire a CPO while expecting the CEO to keep full ownership of both roadmap and execution.
- 2
Define the leadership outcome
Choose the main improvement the role must produce: stronger process, sharper strategy, team building, talent attraction, or a specific combination. Use that outcome to shape the search.
Pro tip Rank the outcomes instead of calling all of them equally important.
- 3
Assign core product ownership
Specify who owns product vision, how it connects to company vision, and who is accountable for roadmap execution. Include operational excellence rather than treating the job as strategy alone.
Pro tip Write down decision rights for vision, priorities, trade-offs, and delivery.
Watch out A grand product vision divorced from company reality creates leadership conflict.
- 4
Map adjacent functions
Decide how the role works with engineering, design, data science, marketing, sales, GMs, and operations. Determine whether the company needs a functional product leader or a broader technical product leader.
Pro tip Test whether every function would respect the proposed leader's competence and authority.
Watch out A GM-style role is harder when the leader lacks credibility in the functions reporting to them.
- 5
Write the contract before hiring
Turn the decisions into explicit swim lanes, interfaces, and success measures. Only then select the title, seniority, and candidate profile that fit the actual role.
Pro tip Review the contract with the CEO, CTO, and other executives whose work will intersect with the hire.
In the wild
An illustrative technical founder says she wants a CPO but also wants to own product vision, roadmap priorities, and execution reviews. The questionnaire exposes that the proposed executive would lack clear accountability. The company instead narrows the immediate need to product operations and team development while the founder retains product leadership.
→ The company avoids an inflated title and hires for the work it is actually ready to delegate.
An illustrative scaling company needs one person to make trade-offs across product, engineering, design, and data. It defines single-threaded accountability, tests candidates for credibility across those functions, and hires a broader technical product leader rather than a narrowly functional CPO.
→ Decision rights and organizational scope match the leader's mandate from the start.
Common mistakes
Hiring the title first
Starting with a fashionable executive title hides the organizational problem and encourages a mismatch between candidate and mandate.
Leaving CEO overlap implicit
Unspoken overlap around vision, roadmap, and execution creates the same conflict seen when a founder hires the first PM without defining swim lanes.
Treating CPO work as vision only
Gupta emphasizes that senior product leaders remain accountable for execution and operational excellence, not just strategy.
Is it for you?
Best for
Founders and CEOs preparing to hire their first VP of Product or CPO at a growing technology company.
Not ideal for
Organizations seeking a standard CPO job description without deciding what their CEO and adjacent leaders will own.
From the episode
Manik Gupta (ex-CPO Uber, Google Maps) on how to build consumer apps, why it’s useful to be optimistic about technology, creating inflections in your PM career, the changing CPO role, and more