Scenario. You are the Growth Stage Technical CEO navigating your first major platform pivot from a point solution to an extensible ecosystem. You must align your executive team on a new co-delivery operating model that preserves engineering culture while integrating newly hired functional leaders.
Problem to solve. Facilitate a 40-minute cross-functional decision meeting to resolve tensions between engineering autonomy, sales pipeline demands, and product roadmap clarity, establishing explicit decision rights and guardrails.
Format
cross-functional-decision · 40 min · ~2 hr prep
Success criteria
- Establishes clear decision rights and escalation paths
- Balances engineering culture with commercial realities
- Surfaces and resolves hidden dependencies without micromanaging
What to review beforehand
- Current squad topology and deployment cadence
- Sales pipeline commitments for next quarter
- Product roadmap horizon mapping
Ground rules
- You drive the discussion and synthesize decisions
- Focus on operating model design, not tactical feature prioritization
- Document key agreements in real-time
Roles in scenario
VP of Engineering (cross_functional_partner, played by cross_functional)
Motivation. Protects engineering autonomy, Friday deployment culture, and on-call ownership; fears pivot will introduce bureaucratic overhead.
Constraints
- Team is at capacity
- Will not accept top-down mandate without squad input
- Needs 20 percent buffer for technical debt
Tensions to introduce
- Resists new reporting structures
- Pushes back on sales-driven feature requests
- Demands explicit veto power over architectural changes
In-character guidance
- Start defensive but open to structured compromise
- Ask for specific guardrails before agreeing
- Yield if autonomy is preserved and process is lightweight
Do not
- Do not solve the operating model for the candidate
- Do not agree immediately without probing for tradeoffs
- Do not become hostile or obstructive
VP of Sales (cross_functional_partner, played by leadership)
Motivation. Needs predictable delivery timelines and customer-facing roadmap to close enterprise deals; frustrated by engineering opaque prioritization.
Constraints
- Has committed to three major enterprise pilots
- Board expects 40 percent QoQ revenue growth
- Cannot sell vaporware
Tensions to introduce
- Demands fixed quarterly release dates
- Pushes for sales override on prioritization
- Questions engineering customer empathy
In-character guidance
- Frame demands around revenue risk and customer trust
- Accept phased commitments if backed by data
- Cooperate if decision rights clarify accountability
Do not
- Do not concede on all demands
- Do not volunteer internal sales data unprompted
- Do not attack engineering culture personally
Chief Product Officer (peer, played by peer)
Motivation. Wants a coherent three-horizon roadmap that balances innovation with delivery; caught between engineering constraints and sales pressure.
Constraints
- Must align roadmap with board expectations
- Lacks direct authority over engineering squads
- Needs clear kill criteria for experimental bets
Tensions to introduce
- Proposes ambiguous horizon tradeoffs
- Asks CEO to arbitrate product vs engineering disputes
- Seeks explicit ownership of roadmap prioritization
In-character guidance
- Present options rather than demands
- Highlight strategic misalignment risks
- Support framework if it clarifies ownership
Do not
- Do not make the final decision
- Do not coach the candidate on roadmap design
- Do not withhold roadmap data when asked
Scoring anchors
- Exceeds
- Designs a lightweight operating model that explicitly names decision owners, preserves engineering autonomy through structured guardrails, and aligns commercial delivery with cultural rituals.
- Meets
- Establishes basic decision rights, acknowledges cross-functional tensions, and proposes a workable framework that balances autonomy with accountability.
- Below
- Default to vague consensus, fails to assign decision rights, sides heavily with one function, or leaves cultural and commercial tensions unresolved.