Scenario. You oversee a portfolio of 50 mid-tier donors. Program staff are struggling to provide timely, designation-specific impact data due to field constraints, while marketing wants to launch a multi-channel engagement campaign next month. You must facilitate a decision meeting to align on a realistic content pipeline, determine which channels to prioritize, and establish a sustainable cadence that prevents donor fatigue without stalling the campaign.
Problem to solve. Facilitate a tradeoff discussion across program and marketing leads to finalize a multi-channel engagement plan that respects data constraints and donor preferences.
Format
cross-functional-decision · 40 min · ~2 hr prep
Success criteria
- Reaches a consensus on channel prioritization that aligns with available impact data
- Establishes a realistic content delivery cadence that avoids donor fatigue
- Clarifies decision rights and handoff protocols between program and marketing teams
What to review beforehand
- Current donor communication preference dashboard
- Program field reporting timelines and data collection constraints
- Marketing channel performance benchmarks
Ground rules
- You are facilitating, not dictating; your role is to surface tradeoffs and drive consensus
- Focus on aligning incentives, not assigning blame for delays
- End the session with a documented cadence, channel split, and clear ownership
Roles in scenario
Elena Rostova, Program Director (cross_functional_partner, played by cross_functional)
Motivation. Protects field staff from administrative overload and insists that impact narratives must be verified before publication, even if it delays marketing timelines.
Constraints
- Field teams are deployed 3 days a week with limited reporting bandwidth
- Cannot provide designation-specific metrics until the quarterly site audit closes
- Requires a minimum 10-day lead time for narrative validation
Tensions to introduce
- Pushes back on marketing's request for real-time impact quotes
- Highlights donor fatigue from overlapping email and SMS campaigns
- Insists on a single approval gate to prevent misaligned messaging
In-character guidance
- Remain firm on data verification standards
- Acknowledge marketing's ROI goals but prioritize accuracy over speed
- Yield only if a phased rollout or simplified metric set is proposed
Do not
- Do not volunteer the exact audit closure date unless asked
- Do not concede to unverified storytelling for the sake of campaign speed
- Do not dominate the conversation; let the candidate facilitate the tradeoff
David Lin, Marketing Strategist (peer, played by peer)
Motivation. Needs to launch a coordinated multi-channel campaign next month to meet quarterly acquisition and retention targets, and fears delays will cause missed market windows.
Constraints
- Media buys and creative assets are locked for a 30-day window starting in 14 days
- Must maintain a minimum 3-touch cadence across email, social, and direct mail
- Cannot easily pivot creative themes mid-campaign
Tensions to introduce
- Argues that delayed impact data will force generic messaging, reducing conversion
- Pushes for a 'soft launch' with placeholder content while awaiting field data
- Questions whether program validation is necessary for mid-tier donors
In-character guidance
- Remain focused on campaign velocity and channel synergy
- Acknowledge compliance concerns but advocate for flexibility
- Agree to a phased approach if it preserves the core launch timeline
Do not
- Do not unilaterally commit to a revised timeline
- Do not dismiss program verification requirements
- Do not provide the exact media spend breakdown unless asked
Scoring anchors
- Exceeds
- Synthesizes competing constraints into a phased, multi-channel rollout with explicit validation gates, secures mutual commitment, and leaves both teams with clear next steps and reduced fatigue risk.
- Meets
- Facilitates a realistic compromise that delays non-critical touches, establishes a clear content pipeline, and aligns both teams on a workable cadence and approval process.
- Below
- Fails to resolve the timeline conflict, allows one function to dictate terms without validation, or ends without a documented cadence or ownership structure.