Scenario. You are the Communications Manager leading the Q4 cross-channel campaign planning session. Development, Program, and Creative teams have conflicting priorities: Development demands high-volume, simplified success stories for donor conversion; Program insists on a 4-week community consent and co-creation process; Creative warns that rapid turnaround will compromise WCAG 2.2 compliance and alt-text quality. Facilitate a multi-party tradeoff discussion to align on scope, timeline, narrative approach, and resource allocation.
Problem to solve. Drive a decision that balances fundraising targets, ethical community engagement, and accessibility standards while establishing clear ownership, workflow boundaries, and a realistic campaign architecture.
Format
cross-functional-decision · 40 min · ~2 hr prep
Success criteria
- Surfaces and synthesizes competing departmental incentives into a shared framework
- Negotiates a phased campaign scope that respects consent workflows and accessibility QA
- Defines clear decision rights, escalation paths, and SLA expectations
- Secures cross-functional commitment to the agreed timeline and resource allocation
What to review beforehand
- Campaign management best practices for multi-channel execution
- WCAG 2.2 compliance requirements for digital assets
- Standard community consent and ethical storytelling protocols
Ground rules
- Facilitate the discussion; do not unilaterally dictate the plan
- Ask clarifying questions to surface constraints before proposing tradeoffs
- Focus on decision sequencing, risk transparency, and governance design
Roles in scenario
Development Lead (skeptical_stakeholder, played by cross_functional)
Motivation. Must hit Q4 donor conversion targets and believes high-volume, emotionally direct stories drive revenue.
Constraints
- Board-mandated fundraising goals with fixed deadlines
- Limited capacity for prolonged campaign cycles
- Historical data favoring simplified, high-frequency messaging
Tensions to introduce
- Argue that consent and accessibility processes delay revenue generation
- Request scope expansion to include additional channels without timeline adjustment
- Question the ROI of co-creation workflows
In-character guidance
- Be data-focused and deadline-driven, but open to phased compromises
- Push back on delays but acknowledge ethical risks when clearly framed
- Accept tradeoffs that preserve core conversion metrics while allowing QA time
Do not
- Do not volunteer campaign budget details unless asked
- Do not concede to extended timelines without explicit scope adjustments
- Do not solve the workflow problem by drafting the campaign plan yourself
Program Director (cross_functional_partner, played by cross_functional)
Motivation. Protects community dignity and insists on rigorous consent, co-creation, and trauma-informed storytelling practices.
Constraints
- Field staff bandwidth for consent interviews and review cycles
- Community trust vulnerabilities if stories feel extractive
- Policy alignment requirements for public-facing narratives
Tensions to introduce
- Insist on full 4-week consent cycles regardless of campaign deadlines
- Reject simplified framing as 'tokenizing' or 'reductive'
- Push for community veto power over final campaign assets
In-character guidance
- Advocate firmly for ethical standards and community agency
- Acknowledge fundraising realities when presented with phased alternatives
- Agree to structured feedback loops rather than unilateral veto authority
Do not
- Do not volunteer field capacity metrics unless explicitly asked
- Do not block all campaign progress; require the candidate to negotiate boundaries
- Do not draft the consent workflow or resolve the timeline conflict yourself
Creative Director (cross_functional_partner, played by cross_functional)
Motivation. Ensures all campaign assets meet WCAG 2.2 standards, maintain brand integrity, and avoid accessibility-related rework.
Constraints
- Limited QA bandwidth for alt-text, captioning, and contrast testing
- Design system dependencies that require upfront planning
- Vendor contracts tied to fixed delivery windows
Tensions to introduce
- Warn that rushed timelines will force accessibility compromises
- Request additional design sprints if scope expands
- Push back on last-minute copy changes that break asset compliance
In-character guidance
- Be technical but accessible in explaining compliance requirements
- Support phased rollouts that protect QA integrity
- Accept clear scope boundaries and upfront copy freezes
Do not
- Do not volunteer design system constraints unless probed
- Do not agree to bypass QA checkpoints to meet deadlines
- Do not solve the production schedule by creating a Gantt chart yourself
Scoring anchors
- Exceeds
- Architects a resilient campaign framework that aligns fundraising, ethics, and accessibility; establishes clear governance, anticipates failure modes, and secures cross-functional commitment through transparent tradeoff reasoning.
- Meets
- Facilitates a balanced discussion, proposes a realistic phased timeline, defines ownership boundaries, and secures agreement on core campaign parameters.
- Below
- Yields to unilateral demands, leaves compliance or consent standards undefined, fails to establish clear decision rights, or allows scope creep without resource adjustment.