Prompt This, Not That
See exactly what separates a weak prompt from a powerful one — with 24 real-world comparisons across 8 categories.
Write a blog post
Role + Audience + Structure + Specificity
Vague and generic
Write me a blog post about AI in healthcare.
- No role specified
- No format or length guidance
- No target audience
- Too vague — could go in any direction
Structured and specific
You are a healthcare technology journalist who specializes in AI adoption. Write a 1,200-word blog post for hospital CTOs explaining 3 practical ways generative AI is reducing diagnostic errors in radiology departments. Use a professional but accessible tone. Include a brief intro, one section per use case with a real-world example, and a conclusion with actionable next steps.
- Clear expert role assigned
- Defined format and word count
- Target audience specified (hospital CTOs)
- Specific angle with concrete deliverables
~3x more detailed and relevant output
Write email subject lines
Constraints + Examples + Quantity
No constraints
Give me some email subject lines for a sale.
- No brand or product context
- No character-length limits
- No tone guidance
- No quantity specified
Constrained and targeted
Generate 10 email subject lines for a 48-hour flash sale on premium leather handbags (brand: LuxCraft, audience: women 30-45). Each line must be under 50 characters, create urgency, and avoid spam-trigger words like "FREE" or "ACT NOW." Include 3 emoji variations and 3 question-style lines.
- Brand and audience context provided
- Character limit enforced
- Spam-word avoidance rule
- Quantity and style variations requested
~5x more usable options with higher open-rate potential
Write API documentation
Template + Audience Levels + Examples
Zero context
Document this API endpoint.
- No endpoint details provided
- No format template
- No audience skill level
- No example request/response specified
Templated and thorough
Write REST API documentation for a POST /api/v2/orders endpoint that creates a new order. Use this template for each section: Description, Authentication (Bearer token), Request Headers, Request Body (JSON schema with types and required fields), Response (success 201 + error 400/401/422), Rate Limits, and a cURL Example. Target audience: mid-level developers integrating for the first time. Use concise language — no marketing fluff.
- Specific endpoint with method
- Clear documentation template
- Developer skill level defined
- Explicit section structure
~4x more developer-friendly documentation
Debug a code issue
Context + Error + Environment + Constraints
No context at all
My code is broken. It doesn't work. Can you fix it?
- No code provided
- No error message
- No language or framework mentioned
- No description of expected vs actual behavior
Complete debugging context
I have a Next.js 14 API route (App Router, TypeScript) that should return paginated users from a PostgreSQL database using Drizzle ORM. When I call GET /api/users?page=2, I get a 500 error: "TypeError: Cannot read properties of undefined (reading 'map')." Here's the route handler: ```typescript export async function GET(req: NextRequest) { const page = req.nextUrl.searchParams.get("page"); const users = await db.select().from(usersTable).limit(10).offset(page * 10); return NextResponse.json(users.map(u => u.name)); } ``` Node 20, Drizzle 0.30. What's wrong and how do I fix it?
- Exact tech stack specified
- Error message included verbatim
- Relevant code snippet provided
- Expected behavior is clear from context
~4x faster to a working solution
Review a pull request
Checklist + Priorities + Scope
Undefined criteria
Review this code and tell me if it's good.
- No review criteria specified
- No priority guidance
- "Good" is subjective and undefined
- No context about the codebase
Prioritized review checklist
Review this TypeScript React component for a production e-commerce checkout flow. Focus on these areas in priority order: 1. Security: XSS vulnerabilities, unsafe data handling 2. Error handling: missing try/catch, unhandled promise rejections 3. Performance: unnecessary re-renders, missing memoization 4. Accessibility: ARIA labels, keyboard navigation 5. Code style: naming consistency, dead code For each issue, rate severity (critical/warning/suggestion) and provide a fix. Ignore styling opinions — we use Prettier.
- Clear review criteria with priorities
- Severity rating system defined
- Scope boundaries set (ignore styling)
- Production context given
~3x more actionable review feedback
Refactor a function
Before/After + Design Patterns + Constraints
Entirely subjective
Make this function better.
- "Better" is undefined
- No refactoring goals
- No constraints on approach
- No mention of backwards compatibility
Goal-oriented with constraints
Refactor this 80-line order processing function into smaller, testable units using the Strategy pattern. Requirements: - Preserve the existing function signature (it's called by 12 other modules) - Extract discount calculation, tax computation, and shipping logic into separate pure functions - Each extracted function should be independently unit-testable - Add TypeScript discriminated unions for order types instead of the current string checks - Keep it under 5 functions total — don't over-abstract Return the refactored code with a brief explanation of each extraction decision.
- Specific design pattern named
- Backwards compatibility required
- Testability as an explicit goal
- Anti-over-engineering constraint
~3x cleaner, more maintainable output
Analyze a market opportunity
Framework + Data Sources + Output Format
Impossibly broad
Tell me about the AI market.
- No specific market segment
- No analysis framework
- No time horizon
- No output format specified
Framework-driven and specific
Conduct a market analysis of AI-powered customer support tools for mid-market SaaS companies (50-500 employees) using Porter's Five Forces framework. For each force, provide: - Current state (strong/moderate/weak) - 2-3 supporting data points or trends - Implication for a new entrant Conclude with a 2x2 opportunity matrix (market attractiveness vs. competitive intensity) and recommend the single best entry strategy. Format as a structured report with headers.
- Precise market segment defined
- Established framework (Porter's Five Forces)
- Structured output format
- Actionable conclusion requested
~4x more actionable strategic analysis
Develop a pricing strategy
Scenario Modeling + Constraints + Metrics
Missing all key variables
How should I price my SaaS product?
- No product details or value proposition
- No target customer segment
- No cost structure information
- No competitive context
Data-driven with scenarios
Design a 3-tier pricing strategy for a B2B project management SaaS tool. Context: - Target: remote teams of 10-200 people - COGS per user: $2.50/month - Key competitors: Asana ($10.99/user), Monday ($9/user), Linear ($8/user) - Our unique differentiator: built-in async video updates For each tier, specify: name, price/user/month, included features, usage limits, and target persona. Model 3 scenarios (aggressive, moderate, premium) with projected revenue at 1K, 5K, and 10K users. Recommend the scenario that maximizes expansion revenue potential.
- Cost structure provided
- Competitive landscape included
- Multiple scenarios requested
- Revenue modeling with projections
~5x more decision-ready pricing analysis
Write an investor pitch
Narrative Arc + Metrics + Audience Psychology
No substance to work with
Help me write a pitch deck for my startup.
- No startup details provided
- No stage or funding ask
- No audience type specified
- No existing traction mentioned
Investor-ready narrative
Write the narrative script for a 5-minute Series A pitch to enterprise-focused VCs. Our startup: - Product: AI compliance monitoring for fintech (auto-detects regulatory violations) - Traction: $1.2M ARR, 18 customers, 140% net revenue retention - Ask: $12M Series A - Moat: proprietary dataset of 50K+ regulatory rulings Structure: Problem → Market Size → Solution Demo Flow → Traction → Business Model → Team → Ask. End each section with a transition sentence. Tone: confident but not arrogant. Include 2-3 metrics per section where applicable.
- Key metrics provided upfront
- Clear pitch structure defined
- Audience type specified (enterprise VCs)
- Tone and transitions guided
~3x more compelling and structured pitch
Conduct a literature review
Scope Boundaries + Synthesis + Critical Lens
Unfocused question
What does the research say about remote work?
- No specific research question
- No time frame for literature
- No discipline or field specified
- No desired depth or format
Scoped and analytical
Synthesize findings from organizational psychology and management research (2019-2025) on how fully remote work affects team innovation output. Focus on: 1. Serendipitous idea generation vs. structured brainstorming 2. Psychological safety in remote vs. in-person settings 3. Knowledge transfer speed across remote teams For each theme, summarize the dominant finding, note any contradictory evidence, and rate the evidence quality (strong/moderate/limited). Conclude with 3 testable hypotheses for future research. Use APA-style in-text citations where possible.
- Specific research question defined
- Time-bounded (2019-2025)
- Thematic structure provided
- Evidence quality rating requested
~4x more rigorous and structured review
Summarize a research paper
Layered Summary + Critical Questions
No summarization criteria
Summarize this paper for me.
- No summary depth specified
- No target audience for the summary
- No focus areas highlighted
- No critical evaluation requested
Multi-layered with critical lens
Summarize this research paper at three levels: 1. **One-liner** (Twitter-length, under 280 chars) 2. **Executive summary** (3-5 bullet points for a non-technical product manager) 3. **Technical deep-dive** (2 paragraphs covering methodology, key findings, and limitations) After the summary, list: (a) the single strongest claim and its supporting evidence, (b) the weakest assumption in the methodology, and (c) one follow-up question this paper doesn't answer.
- Three summary depths for different audiences
- Critical evaluation built in
- Specific deliverables defined
- Encourages deeper thinking, not just parroting
~3x more useful summary for decision-making
Compare theoretical frameworks
Structured Comparison Matrix + Application
Surface-level request
Compare Agile and Waterfall.
- No comparison dimensions specified
- No use-case context
- No decision criteria
- Will produce a generic textbook answer
Context-rich comparison matrix
Compare Agile (Scrum), Kanban, and Shape Up as development methodologies for a 15-person product team building a B2B analytics platform. Create a comparison matrix with these dimensions: - Team structure requirements - Planning overhead (hours/sprint) - Handling of unplanned work and bugs - Suitability for regulatory/compliance features - Client-facing delivery predictability Rate each as Strong/Adequate/Weak per dimension. Recommend which methodology to use for: (1) the core platform build, and (2) the post-launch maintenance phase. Justify each recommendation in 2 sentences.
- Three frameworks, not just two
- Specific comparison dimensions
- Real-world team context provided
- Phase-specific recommendations requested
~3x more useful for choosing an approach
Generate a story concept
Genre Blending + Constraints + Theme
Completely open-ended
Give me a story idea.
- No genre or tone
- No length or format
- No thematic interests
- Will produce a generic, forgettable idea
Genre-blended with structure
Generate a short story concept that blends noir detective fiction with solarpunk aesthetics. Setting: a self-sustaining vertical farm city in 2087. The protagonist is a food-safety investigator who discovers that the city's algae-based protein supply has been deliberately contaminated. Provide: a one-paragraph premise, 3 key characters (name, role, secret motivation), the central conflict, and a twist ending that reframes the antagonist's actions as morally ambiguous. Target length for the final story: 4,000 words.
- Specific genre fusion defined
- World-building details provided
- Character depth requested
- Moral ambiguity adds sophistication
~4x more original and developed concept
Name a product or brand
Linguistic Constraints + Cultural Checks + Rationale
No naming criteria
Come up with a name for my app.
- No product description
- No naming style preferences
- No domain/trademark considerations
- No cultural sensitivity check
Linguistically aware and practical
Generate 15 name candidates for a mobile app that helps freelancers track time and auto-generate invoices. Requirements: - 2 syllables max, easy to spell and pronounce in English and Spanish - Must have a .com domain available (check plausibility — avoid real words) - Avoid names starting with "i" or ending in "-ly" (oversaturated) - Include 5 coined words, 5 word-mashups, and 5 metaphorical names For each name, provide: pronunciation guide, the rationale behind it, and one potential risk (trademark conflict, negative connotation in other languages, etc.).
- Phonetic and syllable constraints
- Domain availability considered
- Anti-patterns specified
- Risk assessment per candidate
~5x more viable naming candidates
Create a design brief
Mood Board + Anti-References + Technical Specs
No brief whatsoever
Design a logo for my company.
- No company description
- No style preferences or anti-preferences
- No color or format constraints
- No usage context specified
Anti-references + technical specs
Create a design brief for a logo for "Terraform Analytics," a B2B data infrastructure startup targeting enterprise DevOps teams. Style direction: - Modern, geometric, minimal — think Stripe, Linear, Vercel aesthetic - NOT: playful, hand-drawn, gradient-heavy, or clip-art style Constraints: - Must work at 16x16px (favicon) and billboard scale - Monochrome first, color version second - No more than 2 colors + black/white - Must be recognizable without the wordmark Deliverables: logomark concept description, color palette (hex codes), typography pairing suggestion, and 3 usage mockups (business card, website header, Slack icon).
- Brand personality defined with references
- Anti-references clarify what to avoid
- Technical size constraints specified
- Deliverables clearly listed
~3x more aligned designer output
Create a meeting agenda
Time-Boxing + Outcomes + Roles
Generic request
Create an agenda for our team meeting.
- No meeting purpose
- No time constraints
- No attendee context
- No desired outcomes
Time-boxed with outcomes
Create a 45-minute sprint retrospective agenda for a 7-person product engineering team. The sprint had 2 missed deadlines and 1 production incident. Structure each agenda item with: topic, time allocation, facilitator action, and expected output. Include: 1. Icebreaker (3 min) 2. Sprint metrics review (5 min) 3. What went well — each person shares one thing (7 min) 4. What went wrong — focus on the 2 missed deadlines (10 min) 5. Incident post-mortem summary (8 min) 6. Action items with DRI assignments (10 min) 7. Parking lot (2 min) End with a template for the follow-up email summarizing decisions and action items.
- Meeting type and context provided
- Time allocation per item
- Specific team challenges addressed
- Follow-up template included
~3x more productive meetings
Plan a productive week
Energy Mapping + Priority Matrix + Constraints
No information to work with
Help me plan my week.
- No tasks or goals listed
- No schedule constraints
- No priority criteria
- No energy or preference patterns
Energy-aware and realistic
Help me plan next week (Mon-Fri). Context: - I'm a product manager, deep-work hours are 9-11am - Fixed meetings: Mon 2pm standup (30min), Wed 10am all-hands (1hr), Fri 3pm demo (1hr) - Must-complete: product spec for Feature X (4hrs), quarterly OKR review (2hrs), 3 user interview analysis write-ups (1hr each) - Nice-to-have: competitor audit, team 1:1 prep - Energy: high Mon/Tue, low Wed after all-hands, rebounds Thu/Fri Create a daily schedule that front-loads deep work in high-energy slots, batches meetings, and reserves 30min/day for email triage. Flag if anything doesn't fit and suggest what to defer to next week.
- Energy patterns considered
- Fixed commitments listed
- Tasks with time estimates provided
- Overflow handling requested
~2x more realistic and achievable plans
Make a tough decision
Multi-Criteria Analysis + Pre-Mortem + Reversibility
No decision context
Should I take this job offer?
- No comparison criteria
- No current situation context
- No values or priorities stated
- Expecting a yes/no from insufficient data
Weighted matrix with pre-mortem
Help me evaluate a career decision using a weighted decision matrix. Option A: Stay at current company (Series B startup, VP Eng, $180K + 0.5% equity) Option B: Join BigCorp as Senior Director ($240K + $80K RSU/yr, no startup upside) My priorities (weight 1-5): - Financial security: 4 - Career growth potential: 5 - Work-life balance: 3 - Team/culture fit: 4 - Learning new skills: 3 For each option, rate each criterion (1-10), calculate weighted scores, and identify the winner. Then run a pre-mortem: "It's 18 months later and I regret this choice — what went wrong?" for each option. Finally, assess reversibility — how easy is it to switch back?
- Both options detailed with specifics
- Weighted criteria match personal values
- Pre-mortem surfaces hidden risks
- Reversibility check reduces anxiety
~3x more rigorous decision process
Write a complex SQL query
Schema Context + Expected Output + Edge Cases
Missing everything
Write a SQL query to get user data.
- No table schema provided
- No specific columns needed
- No filters or conditions
- No expected output format
Schema-aware with edge cases
Write a PostgreSQL query for this schema: - users (id, email, created_at, plan_type) - orders (id, user_id, total_amount, status, created_at) - order_items (id, order_id, product_id, quantity, unit_price) I need: the top 10 users by total revenue in the last 90 days, but only those with 3+ completed orders. Return: user email, order count, total revenue, average order value, and days since first order. Edge cases to handle: users with refunded orders (status = 'refunded') should have those amounts subtracted, not excluded. Use CTEs for readability. Add an index suggestion if the query would be slow on 1M+ users.
- Complete schema provided
- Specific output columns defined
- Edge case handling specified
- Performance consideration included
~4x more accurate queries on first attempt
Choose a data visualization
Data Shape + Audience + Message
No data context
What chart should I use for my data?
- No data shape or size described
- No message or story to tell
- No audience context
- No tool constraints
Message-driven visualization
Recommend the best visualization type for this data and audience: Data: Monthly recurring revenue (MRR) by customer segment (Enterprise, Mid-Market, SMB) over 24 months, with a target line at $500K total MRR. 3 series, 24 data points each. Audience: Board of directors — they have 30 seconds to glance at this in a quarterly report. Message I want to convey: Enterprise segment is growing 3x faster than SMB, and we'll hit the $500K target 2 months early. Constraints: Must work in Google Slides, printed in grayscale. Recommend chart type, label strategy, color/pattern encoding, and one annotation to highlight the key insight.
- Data shape fully described
- Audience and time constraint specified
- Core message explicitly stated
- Practical constraints (grayscale, Slides) included
~3x more effective data communication
Clean messy data
Schema + Rules + Validation + Audit Trail
No cleaning rules
Clean up this CSV file.
- No schema or column definitions
- No data quality rules specified
- No handling instructions for edge cases
- No validation criteria
Rule-based with audit trail
Write a Python (pandas) data cleaning pipeline for a customer CSV with these columns: name, email, phone, signup_date, country, revenue. Cleaning rules: 1. Names: title case, strip whitespace, flag rows where name contains digits 2. Email: lowercase, validate format (regex), deduplicate on email (keep most recent signup_date) 3. Phone: normalize to E.164 format, mark invalid numbers as NULL (don't drop the row) 4. Dates: parse mixed formats (MM/DD/YYYY, YYYY-MM-DD, "Jan 5 2024"), flag future dates as errors 5. Country: map common misspellings ("US", "usa", "United States" → "US"), use ISO 3166-1 alpha-2 6. Revenue: convert to float, handle "$1,234.56" format, flag negative values Output: cleaned DataFrame + a separate "audit_log" DataFrame listing every change made (row index, column, old value, new value, rule applied). Include a summary print statement showing rows processed, rows cleaned, and rows flagged.
- Column-by-column rules defined
- Edge case handling for each field
- Audit trail for accountability
- Summary statistics included
~4x more reliable data pipeline
Prepare for a difficult conversation
Scenario Planning + Scripts + Emotional Mapping
No context or nuance
How do I tell my employee they're underperforming?
- No specific performance issues cited
- No relationship context
- No desired outcome defined
- No communication style preferences
Empathetic with scripts
Help me prepare for a performance conversation with a senior engineer who has missed 3 consecutive sprint commitments and whose code review turnaround has gone from 4 hours to 3 days over the past quarter. Context: They were a top performer until ~3 months ago. I suspect burnout but haven't confirmed. We have a good relationship. Company uses a PIP process but I want to avoid that if possible. Provide: 1. An opening statement that's direct but empathetic (2-3 sentences) 2. 3 specific, behavioral (not personal) examples I can reference 3. A script for transitioning from "here's the problem" to "how can I help" 4. Responses to likely reactions: defensive, emotional, or disengaged 5. A follow-up plan with check-in cadence Tone: caring but honest. I want them to leave feeling supported, not attacked.
- Specific behavioral examples provided
- Relationship context given
- Multiple reaction scenarios prepared
- Desired emotional outcome stated
~3x more prepared and confident in delivery
Write a project status update
Audience Layering + RAG Format + Action Items
No project context
Write a status update for my project.
- No project details
- No audience specified
- No time period covered
- No format preference
Audience-aware and scannable
Write a weekly project status update for a mobile app redesign project (3-month timeline, currently in week 6 of 12). Audience: VP of Product + VP of Engineering (they have 2 minutes to read this) Use this format: - Status: (at risk — 3 days behind schedule) - One-line summary (what they need to know in 10 seconds) - Progress: 3 bullet points on what shipped this week - Risks: 2 items with likelihood (high/med/low) and mitigation plan - Blockers: 1 item that needs their decision (design system migration — go/no-go by Friday) - Next week: 3 planned deliverables Keep it under 200 words total. No fluff, no filler.
- Specific project timeline context
- Audience reading time considered
- Structured format with word limit
- Explicit decision request included
~3x more effective stakeholder communication
Write a negotiation email
BATNA + Anchoring + Tone Calibration
No leverage or context
Write an email asking for a raise.
- No current compensation details
- No accomplishments listed
- No market data referenced
- No specific ask amount
Data-backed with emotional intelligence
Write a salary negotiation email to my VP of Engineering. Context: - Current: $165K base, Senior Software Engineer, 2.5 years at the company - Ask: $195K base (18% increase) + promotion to Staff Engineer - Market data: Levels.fyi shows Staff SWE median at $205K for our city/company size - Key wins: Led the payment system migration (saved $340K/yr in vendor costs), mentored 3 junior devs (all promoted), reduced deploy time by 60% - BATNA: I have a competing offer at $200K but prefer to stay Tone: Appreciative and forward-looking, not threatening. Reference the competing offer as "an opportunity I've been exploring" — don't frame it as an ultimatum. Open with gratitude for growth opportunities, transition to impact/data, close with the specific ask. Under 250 words.
- Specific numbers and market data
- Concrete accomplishments with metrics
- BATNA mentioned tastefully
- Tone carefully calibrated
~3x more persuasive negotiation position
Showing 24 of 24 comparisons
Frequently asked questions
Continue exploring