RACE Framework: When and How to Use It

While RISE focuses on structured tasks, the RACE framework shines when context is king. If you're creating content, writing communications, or any task where background information significantly impacts quality, RACE is your go-to framework.

What is RACE?

RACE is an acronym for:

• Role - Who should the AI be?
• Action - What specific action should it take?
• Context - What background information is relevant?
• Execution - How should the output be delivered?

The key difference from RISE is the emphasis on Context over Steps. RACE recognizes that for many creative and communication tasks, understanding the situation matters more than following a prescribed process.

When RACE Beats RISE

Use RACE when:

• Writing marketing content
• Crafting communications (emails, messages, announcements)
• Creating content for specific audiences
• Tasks where tone and voice matter greatly
• Situations with complex background information

Use RISE when:

• Following a defined process
• Analytical tasks with clear steps
• Technical documentation
• Tasks with structured deliverables

Breaking Down RACE

Role: Your Persona Foundation

Same as RISE—define who the AI should be. RACE roles often emphasize communication expertise.

RACE-optimized roles:

• "You are a brand voice specialist who has developed tone guidelines for Apple, Nike, and Airbnb"
• "You are an internal communications director skilled at delivering difficult news with empathy"
• "You are a social media strategist who grew three B2B SaaS accounts from 0 to 100k followers"

Action: The Core Task

In RACE, the Action is typically a content creation or communication task. Be specific about:

• What type of content
• What goal it should achieve
• What reaction you want from readers

Strong actions:

• "Write a product announcement email that generates excitement while managing expectations about the timeline"
• "Create a LinkedIn post that positions our CEO as a thought leader without sounding self-promotional"
• "Draft a response to a customer complaint that turns a detractor into an advocate"

Context: The Game-Changer

This is where RACE differentiates itself. Context includes everything the AI needs to understand the situation:

Context elements:

• Audience: Who will read this? What do they know? What do they care about?
• Situation: What's happening? What led to this moment?
• Constraints: Brand guidelines, legal requirements, sensitivities
• Goals: Beyond the immediate task, what's the larger objective?
• History: What's been communicated before? What's the relationship?

Example rich context:

CONTEXT:
- Audience: Enterprise customers paying $50k+/year, mostly CTOs and VPs of Engineering
- Situation: We're raising prices 15% due to increased infrastructure costs
- Relationship: These customers have been with us 2+ years on average
- Their concerns: They're already justifying our cost to their CFOs
- Our goal: Retain 95% of customers while implementing the increase
- Constraints: We cannot offer grandfather pricing for more than 6 months
- What we can offer: Annual commitment discount, free migration to new features
- Previous communication: We sent a "product updates" email 2 weeks ago mentioning "investments in infrastructure"

Execution: The Delivery Details

Execution covers the practical aspects of how the output should be formatted and delivered:

• Format and length
• Tone and style
• Structure
• Specific phrases to include or avoid
• Call-to-action requirements

Example:

EXECUTION:
- Length: 250-300 words (email should feel personal, not like a mass communication)
- Tone: Direct but warm—acknowledge the impact while showing confidence
- Structure:
  1. Acknowledge their partnership (1 sentence)
  2. State the change clearly (1-2 sentences)
  3. Explain the why briefly (2-3 sentences)
  4. Present the value they're getting (2-3 sentences)
  5. Offer the options (bullet points)
  6. Clear next step
- Must include: Specific date the change takes effect
- Must avoid: Apologetic language, "we hope you understand"
- CTA: Schedule a call with their account manager

Complete RACE Examples

Example 1: Price Increase Email

ROLE: You are a customer success director at a B2B SaaS company known for transparent, honest communication with customers.

ACTION: Write an email announcing a 15% price increase to enterprise customers that maintains trust and minimizes churn.

CONTEXT:
- Audience: CTOs and VPs of Engineering at companies with 500+ employees
- Current relationship: Average tenure 2.3 years, high satisfaction scores
- Reason for increase: Significant infrastructure investments to improve reliability (now 99.99% uptime vs 99.9%)
- Market context: Competitors have raised prices 20-30% in the past year
- Customer concerns: They're already justifying costs to finance teams
- Available incentives: 10% discount for annual commitment, early access to new enterprise features
- Timeline: Increase takes effect in 60 days

EXECUTION:
- Length: 280-320 words
- Tone: Confident and direct, not apologetic—we're worth the investment
- From: CEO (adds weight to the message)
- Subject line: Include—sets expectation without alarming
- Structure: Relationship acknowledgment → Clear announcement → Brief reasoning → Value delivered → Options → Next step
- Avoid: "We hope you understand," "Unfortunately," excessive justification
- Include: Specific percentage, specific date, specific person to contact
- CTA: Reply to schedule a call with account manager

Example 2: LinkedIn Thought Leadership

ROLE: You are a LinkedIn content strategist who specializes in authentic thought leadership—content that builds credibility without feeling like marketing.

ACTION: Write a LinkedIn post sharing lessons from a major product launch failure that positions our founder as humble and insightful.

CONTEXT:
- Founder: Sarah Chen, CEO of a developer tools startup
- Situation: Their v2.0 launch 6 months ago had major bugs, causing customer complaints
- What they learned: Rushed launch to hit a board deadline, skipped beta testing
- Current situation: v2.1 is now stable, customers are happy, they've rebuilt trust
- Goal: Turn this failure into thought leadership; show vulnerability builds trust
- Audience: Engineering leaders, CTOs, other founders
- Voice: Direct, slightly self-deprecating, genuinely reflective (not performatively humble)
- Founder's style: Uses data, admits mistakes directly, gives actionable advice

EXECUTION:
- Length: 150-200 words (LinkedIn sweet spot)
- Format: No emojis, no "Here's what I learned:" cliché opening
- Hook: Start with the most painful moment
- Structure: Specific failure → What went wrong → The real lesson → Advice for others
- Tone: Like talking to a peer at a conference, not a keynote speech
- End with: A genuine question that invites engagement
- Avoid: Humble-bragging, "And that's why we're now successful," inspiration-porn

Example 3: Internal Change Announcement

ROLE: You are an internal communications expert skilled at delivering organizational changes in ways that maintain morale and reduce anxiety.

ACTION: Write a Slack message from the VP of Engineering announcing a team restructure.

CONTEXT:
- Change: Consolidating 4 small teams into 2 larger teams
- Why: Better resource allocation, reduce coordination overhead
- Impact: 3 managers becoming senior ICs (lateral move, same pay)
- No layoffs: This is critical to emphasize—people will assume the worst
- Affected people: Already had 1:1 conversations, this is the team-wide announcement
- Team culture: Direct, doesn't like corporate-speak, appreciates honesty
- Timing: End of Q1, right before a big product push
- Previous context: Team has been through a lot of changes in past year

EXECUTION:
- Length: 200-250 words
- Format: Slack message (can use line breaks, no formal salutation)
- Tone: Direct but human—acknowledge this is another change
- Structure:
  1. What's changing (2 sentences, super clear)
  2. What's NOT changing (no layoffs, same mission)
  3. Why (honest, not corporate justification)
  4. Impact on individuals (they've been talked to)
  5. What happens next (specific dates/actions)
  6. Invitation to discuss
- Must include: "No layoffs," specific start date, offer to discuss
- Avoid: "Exciting changes," "This is a great opportunity," corporate jargon

RACE vs RISE: Quick Comparison

| Aspect | RISE | RACE | |--------|------|------| | Emphasis | Process/Steps | Context/Background | | Best for | Structured tasks | Creative/communication tasks | | Output | Deliverables | Content | | Key strength | Thoroughness | Relevance |

When to Combine RACE + Other Frameworks

RACE works well combined with:

• Chain-of-Thought: For content that requires reasoning (e.g., "Think through the customer's perspective before writing")
• Tree-of-Thought: For exploring multiple content angles before committing

Your RACE Template

ROLE: You are a [specific expert] known for [relevant strength].

ACTION: [Specific content/communication task] that achieves [goal].

CONTEXT:
- Audience: [Who, what they know, what they care about]
- Situation: [What's happening, what led to this]
- Relationship: [History, current standing]
- Goals: [Immediate and longer-term]
- Constraints: [Requirements, sensitivities, limitations]

EXECUTION:
- Format: [Structure, length]
- Tone: [Voice, style]
- Include: [Must-haves]
- Avoid: [Must-not-haves]
- CTA: [Desired next action]

Next Steps

Master context-rich prompting with RACE, then explore when other frameworks might serve you better in our Complete Frameworks Guide.

Try the Prompt Optimizer to automatically apply RACE to your content prompts.

Marcus Johnson is a Developer Advocate at PromptWizz, specializing in prompt engineering for content and communications.