Scenario. You are overseeing a mid-market CSM omni-channel rollout. A critical third-party vendor is delaying API delivery, threatening the go-live date. Simultaneously, your internal architecture team refuses to sign off on a brittle integration and insists on a two-week refactoring cycle. The client program director demands the original launch date to meet board reporting commitments. You must facilitate a multi-party decision session that balances vendor constraints, internal technical standards, and client launch expectations.
Problem to solve. Facilitate the trade-off discussion, sequence decisions under pressure, and drive a unified resolution path that protects delivery standards and stakeholder alignment. Walk us through how you structure the conversation and what decision you advocate for.
Format
cross-functional-decision · 45 min · ~2 hr prep
Success criteria
- Establishes a clear decision framework and prioritizes critical path dependencies
- Facilitates balanced input without letting one party dominate
- Articulates a risk-aware resolution that aligns technical integrity with commercial timelines
- Secures explicit commitments and next steps from all parties
What to review beforehand
- Cross-vendor dependency mapping and integration acceptance criteria
- ServiceNow CSM baseline architecture vs. custom connector patterns
- Standard escalation and change-control protocols for mid-project blockers
Ground rules
- Focus on driving the discussion, sequencing trade-offs, and securing commitments
- Ask clarifying questions to uncover non-negotiable constraints before proposing solutions
- You control the meeting structure and decision cadence
- Treat all role-players as autonomous stakeholders with legitimate constraints
Roles in scenario
Internal Lead Architect (cross_functional_partner, played by peer)
Motivation. Protect platform integrity and prevent technical debt from destabilizing downstream ServiceNow modules.
Constraints
- Will not approve brittle API handoffs that bypass security gates
- Requires two weeks for refactoring to meet enterprise standards
- Limited senior engineering bandwidth for emergency patches
Tensions to introduce
- Insists on refactoring despite client launch pressure
- Questions vendor competence and API documentation quality
- Pushes for a delayed go-live if standards cannot be met
In-character guidance
- Provide honest technical constraints when asked about refactoring scope
- Acknowledge commercial pressure but maintain firm quality thresholds
- Offer conditional pathways if risk mitigation and testing windows are guaranteed
Do not
- Do not volunteer alternative architecture designs unless explicitly asked
- Do not concede to a brittle integration without explicit risk acceptance
- Do not coach the candidate or break character into advisory mode
Vendor Integration Manager (external_partner, played by cross_functional)
Motivation. Protect contractual margins and deliver a stable, testable API without overcommitting engineering resources.
Constraints
- Can only deliver partial API endpoints by the original deadline
- Requires explicit acceptance criteria to avoid scope disputes
- Limited support hours for emergency debugging
Tensions to introduce
- Pushes for a phased handoff rather than full delivery
- Resists internal refactoring requests as out-of-contract
- Demands clear liability boundaries if delays cascade
In-character guidance
- Answer honestly about delivery capacity and contractual limits when asked
- Express willingness to collaborate if acceptance criteria and timelines are clarified
- Maintain professional firmness on scope boundaries
Do not
- Do not volunteer contract clauses or pricing details unless asked
- Do not agree to accelerated timelines without explicit trade-offs
- Do not escalate hostility or provide unsolicited technical guidance
Client Program Director (executive_sponsor, played by hiring_manager)
Motivation. Hit the board-mandated launch date to secure executive sponsorship and demonstrate platform ROI.
Constraints
- Fixed budget for this quarter with no contingency for delays
- Internal marketing and training campaigns are already scheduled
- Requires a clear risk narrative for executive reporting
Tensions to introduce
- Rejects any proposal that shifts the go-live date
- Questions why vendor and internal teams cannot simply work faster
- Demands a unified risk mitigation plan before approving any compromise
In-character guidance
- Provide honest answers about internal reporting deadlines and budget constraints
- Press for a clear risk narrative and accountability matrix
- Remain firm on launch expectations but open to phased value delivery
Do not
- Do not volunteer executive escalation paths or political context unless asked
- Do not accept a vague compromise without explicit milestones
- Do not coach the candidate or soften the commercial pressure
Scoring anchors
- Exceeds
- Drives a structured, risk-aware decision that aligns technical standards, vendor capacity, and client launch expectations, securing clear commitments and a unified mitigation path.
- Meets
- Facilitates a balanced discussion, identifies key constraints, proposes a reasonable compromise, and establishes next steps with clear ownership.
- Below
- Loses control of the conversation, fails to ask clarifying questions, proposes an unworkable or risky compromise, or leaves accountability and next steps ambiguous.