10 Real-World Prompts — Part 1

Practice with 10 real scenarios covering email writing, data analysis, content creation, and more.

10 min read
2 quiz questions

Theory is nothing without practice. In this lab, you'll work through 10 real-world prompting challenges. For each one, we show you a bad prompt, explain why it fails, and then provide an expert-level prompt using the techniques from this track. Try writing your own prompt before looking at the solution.

Scenario: You need to decline a vendor's proposal without burning the relationship. You might work with them in the future.

Bad prompt: "Write a rejection email to a vendor." Why it fails: No context about the relationship, no tone guidance, no specifics about what to include or avoid.

Challenge 1 — Expert Solution

Demonstrates applying RTCFC framework to a real professional email.

You are a senior procurement manager who values long-term vendor relationships.

Write an email declining Acme Corp's proposal for our Q3 cloud infrastructure upgrade. Key context:
- Their proposal was $45K over our budget
- Their technical approach was solid but the timeline was too aggressive
- We may have projects for them next year

Tone: Warm but direct. Professional without being cold.
Structure: Appreciation → Specific reason (budget, not quality) → Door open for future → Warm close
Length: Under 150 words
Do NOT: Apologize excessively, be vague about the reason, or promise future work

Scenario: You have messy meeting notes and need a clean summary with action items for your team.

Challenge 2 — Expert Solution

Structured meeting summary that extracts decisions, actions, and open questions.

Convert these raw meeting notes into a structured summary.

Format:
## Meeting Summary: [Auto-detect meeting topic]
**Date:** [Extract from notes or write "Not specified"]

### Key Decisions (bullet list — only firm decisions, not discussions)
### Action Items (table: Owner | Task | Deadline)
### Open Questions (bullet list — unresolved items needing follow-up)
### Parking Lot (items mentioned but deferred)

Rules:
- If a deadline isn't mentioned, write "TBD" — don't invent one
- If ownership is unclear, write "Unassigned"
- Keep decision bullets to one sentence each
- Do not add information that isn't in the notes

Notes:
[PASTE RAW NOTES]

Scenario: You have sales data and need to present insights to your CEO.

Challenge 3 — Expert Solution

CEO-ready data analysis with actionable insights and clear formatting.

You are a data analyst presenting to a non-technical CEO who makes decisions fast.

Analyze this sales data and provide insights:
[PASTE DATA]

Format your response as:
1. **Headline number**: The single most important metric, with trend (e.g., "Revenue up 23% QoQ")
2. **Three insights**: Each with: the finding (1 sentence), why it matters (1 sentence), what to do about it (1 sentence)
3. **One risk**: Something in the data that should concern us
4. **Recommended next step**: One specific action with expected impact

Constraints:
- No jargon — explain any technical terms
- Use dollar amounts and percentages, not abstract trends
- Total response under 250 words
- Bold all key numbers

Scenario: You're launching a new product and need descriptions for your website.

Challenge 4 — Expert Solution

Product description with precise voice, format, and content constraints.

Write a product description for our new wireless noise-canceling earbuds (the "SoundPod Pro").

Target buyer: Remote workers aged 25-40 who take video calls all day and listen to music while working.

Product specs: 35-hour battery, hybrid ANC, 4 microphones for calls, IPX5 water resistance, USB-C fast charging (10 min = 3 hours), 6.2g per earbud.

Format:
- Headline: Under 8 words, benefit-focused
- Subheadline: 1 sentence expanding on the headline
- Body: 3 short paragraphs (2-3 sentences each) — each focused on one benefit
- Spec line: Single line with key specs separated by " | "
- CTA: Button text + one support line

Voice: Confident, clean, minimal. Like Apple meets Notion.
Do NOT: Use superlatives (best, greatest), exclamation points, or the word "revolutionize"

Scenario: You want to learn about a complex topic from scratch.

Challenge 5 — Expert Solution

Structured learning prompt that builds understanding from zero.

I want to understand [COMPLEX TOPIC]. I have zero background in this field but I'm a quick learner.

Teach me in this structure:
1. **One-sentence summary**: What is this in the simplest possible terms?
2. **Why it matters**: One real-world impact that affects my daily life
3. **The core concept**: Explain the fundamental idea using an analogy to something I already understand (cooking, sports, or building things)
4. **How it works**: 5-step simplified process — each step is one sentence
5. **Common misconception**: One thing most people get wrong and the truth
6. **Go deeper**: 3 specific questions I should explore next, ranked from easiest to hardest

Constraints:
- No jargon without immediate definition in parentheses
- Each section should be 2-4 sentences maximum
- Total response under 400 words

Prompt Templates

Before/After Prompt Upgrade

Transforms a basic prompt into an expert-level prompt with explanations.

I have this basic prompt that isn't getting great results:

"[YOUR BASIC PROMPT]"

Upgrade it by adding:
1. A specific role for the AI
2. Detailed context about my situation
3. An explicit output format
4. 3-5 constraints (including what to avoid)
5. A quality benchmark or success criteria

Show me the upgraded prompt and explain each improvement.

Practice Scenario Generator

Generates practice scenarios to sharpen your prompting skills.

Generate 5 realistic prompting challenges for me to practice. For each:
1. Describe a real-world scenario (2 sentences)
2. Give me a "bad prompt" that a beginner would write
3. List 3 specific problems with the bad prompt
4. Don't give me the solution — I want to try it myself

Make the scenarios diverse: include writing, analysis, creative, technical, and strategic tasks.

Test Your Knowledge

Knowledge Check

1 / 2

What makes the "Expert Solution" prompts different from the "Bad" prompts?

Key Takeaways

  • Bad prompts lack context, format, constraints, and specificity
  • Expert prompts apply RTCFC systematically to every challenge
  • Audience definition shapes vocabulary, length, and focus
  • Negative constraints (what NOT to do) are as important as positive instructions
  • Practice building structured prompts for diverse real-world scenarios