FOCUS Framework: A Structured Approach for High-Level Output Control

Function: Create a product description for our new wireless earbuds that persuades tech-savvy consumers to purchase while highlighting our key differentiators in sound quality and battery life.

Outcome: The goal is to achieve a 4% conversion rate on our product page (1.5% above category average) and reduce return rates by setting accurate expectations about fit and features.

Context: Our "SonicClear Pro" earbuds target professionals aged 25-45 who value premium audio experiences and are willing to pay more for quality. They're typically iPhone users who listen to music during commutes and workouts, and take calls throughout the day. Our brand emphasizes precision engineering and minimalist design. Key competitors are Sony WF-1000XM4, Apple AirPods Pro, and Bose QuietComfort Earbuds.

Usage: This description will appear on our product detail page on our e-commerce site, with the first 50 words also used in marketplace listings (Amazon, Best Buy). It will be displayed immediately below the product image gallery and above the technical specifications table.

Specifics:
- 250-300 words in total
- Include 3-4 short paragraphs with one H2 subheading ("Why SonicClear Pro?")
- Highlight our proprietary noise-cancellation technology, 9-hour battery life, and customizable EQ
- Use sensory language for the sound quality description
- Incorporate 2-3 subtle references to our aerospace-grade aluminum construction
- Maintain our brand voice: confident without arrogance, technical without jargon
- Include exactly one rhetorical question to engage the reader
- No mention of specific prices (these will be dynamically inserted)
- Include the word "premium" no more than twice

Function: Create a customer support response that resolves a billing complaint while retaining the customer and rebuilding trust after they were incorrectly charged twice for their monthly subscription.

Outcome: The goal is to prevent cancellation, offer appropriate compensation without escalation to a manager, and convert this negative experience into continued loyalty (measured by subscription retention and next NPS score).

Context: Our customer, Michael, has been a premium subscriber to our project management software for 2 years. He's historically been a promoter (9/10 NPS score) but is now frustrated after discovering a double charge ($79 charged twice) on his company credit card, which required him to justify the expense to his finance department. This is our fault due to a payment processing error that affected approximately 50 customers last month.

Usage: This will be sent as an email response to the customer's support ticket from our "Customer Success Team" address, with options for the customer to reply directly or schedule a call if needed. Our ticketing system will tag this as a "Billing Error - Double Charge" resolution for tracking.

Specifics:
- Professional but empathetic tone throughout
- Begin with a sincere apology that acknowledges the specific inconvenience caused
- Clearly explain what happened without technical jargon or making excuses
- Offer immediate refund of the duplicate charge plus one month of service free as compensation
- Include the exact refund amount ($79) and when it will appear (3-5 business days)
- Provide a direct phone number and email for a named customer success manager
- Keep the email under 200 words for readability
- End with a forward-looking statement that rebuilds confidence
- Include the ticket number [#12789] in the subject line
- No corporate platitudes like "your satisfaction is our top priority"

Function: Create a quarterly business update email that informs stakeholders about our Q3 performance while setting expectations for Q4.

Outcome: Maintain investor confidence during a transitional period and prepare them for potentially lower Q4 numbers due to product development investments.

Context: Our SaaS company has exceeded revenue targets for 8 consecutive quarters, but we're planning to reinvest 15% more in R&D next quarter. Our stakeholders are primarily early investors who value transparency and long-term growth over short-term gains.

Usage: This will be sent as an email directly from our CEO to our 25 stakeholders, with a follow-up investor call scheduled for those who want more details.

Specifics:
- Maintain a confident but realistic tone
- 400-500 words total
- Include 3 bullet points highlighting Q3 wins
- Clearly explain the strategic rationale for increased R&D spending
- Include one forward-looking statement with projected returns from the new investment
- Attach a one-page summary of financial highlights (already created)
- No technical jargon without explanation
- End with an invitation to the optional follow-up call with calendar link

Function: Create social media copy for a carousel post that educates our audience about sustainable fashion practices while promoting our upcoming eco-friendly clothing line.

Outcome: Generate 500+ pre-launch email sign-ups and position our brand as an authority in sustainable fashion to support our eco-credentials.

Context: Our clothing brand is launching a limited collection made from recycled ocean plastic. Our audience is environmentally-conscious millennials and Gen Z (18-35) who are willing to pay more for sustainable products but are skeptical of greenwashing. We're known for transparency and have third-party certification for our sustainability claims.

Usage: This will be posted on Instagram as a 10-slide carousel. The first slide will be designed separately with the title "5 Ways Fast Fashion Damages Our Planet." The copy will be paired with statistical infographics and end with a slide about our solution.

Specifics:
- Each slide should have 30-50 words of copy maximum
- Active, slightly urgent tone without being alarmist
- Include at least 3 verifiable statistics about fashion industry waste
- Maintain a solutions-oriented approach (not just pointing out problems)
- Slides 1-5: Focus on environmental impact problems
- Slides 6-8: Introduce our innovative approach to these problems
- Slide 9: Feature key product highlights from the new collection
- Slide 10: Clear CTA to join the pre-launch list with early access benefit
- Avoid clichéd sustainability phrases like "save the planet"
- Include exactly 5 relevant hashtags at the end of the last slide

Function: Create a step-by-step API integration guide that enables developers to successfully implement our payment processing solution into their e-commerce platforms.

Outcome: Reduce integration support tickets by 30% and decrease average integration time from 2 weeks to 5 days or less.

Context: Our RESTful API serves small to mid-size e-commerce businesses with development teams that have moderate technical expertise. The most common integration issues currently involve authentication and webhook configuration. We recently updated to API v2.0 with significant changes to the authentication process.

Usage: This documentation will be published in our developer portal as both a webpage and downloadable PDF. It will be the primary resource shared with new customers during onboarding.

Specifics:
- 1200-1500 words with clear H2 and H3 headings for navigation
- Include a "Prerequisites" section listing required technical knowledge and tools
- Provide code examples in both Python and JavaScript (our two most common languages)
- Use numbered lists for sequential steps, bullet points for options/alternatives
- Include screenshots of the developer dashboard for key configuration steps
- Add warning/note callouts for common pitfalls
- Include a troubleshooting section addressing the top 5 integration errors
- Provide working example of webhook configuration with sample payload
- Maintain a professional but accessible tone (avoid unnecessary technical jargon)
- End with links to reference documentation and support resources

Function: Create a lesson plan that teaches high school students how to analyze primary historical sources while developing critical thinking skills about media bias.

Outcome: Students will demonstrate the ability to identify perspective, bias, and historical context in primary sources as measured by a 30% improvement on the source analysis rubric.

Context: This is for an 11th grade US History class in a public high school with diverse learning needs. Students have basic analytical skills but struggle with identifying subtle bias and contextualizing historical perspectives. The lesson aligns with state standards for historical thinking and media literacy.

Usage: This will be delivered as a 55-minute in-class lesson followed by a homework assignment. It will be part of a larger unit on civil rights movements and will incorporate both digital and physical historical sources.

Specifics:
- Follow standard lesson plan format with objectives, materials, procedure, assessment, and extension activities
- Include a 10-15 minute teacher-led introduction with key concepts
- Design a 25-minute student activity using the SOAPS analysis method (Subject, Occasion, Audience, Purpose, Speaker)
- Create clear step-by-step instructions for analyzing 2-3 primary sources (news articles from different perspectives on the same civil rights event)
- Include 3-5 guiding questions for each source that scaffold analysis difficulty
- Add modifications for diverse learners (both enrichment and support)
- Include formative assessment checkpoint halfway through the activity
- Design a exit ticket that measures initial understanding
- Create a rubric for the homework assignment with clear success criteria
- Maintain an engaging, inquiry-based approach throughout
- Total student-facing content should be adaptable to a double-sided worksheet

Function: Create an onboarding sequence that guides new users through the key features of our productivity app while encouraging completion of profile setup and first project creation.

Outcome: Increase new user activation (defined as completing profile and creating first project) from 35% to 60% and improve 30-day retention by at least 25%.

Context: Our app helps freelancers and small teams manage projects and track time. New users typically sign up during high-stress periods when they need immediate organization help. Our data shows users who complete their profile and create a project in the first session have 3x higher retention. Our user base is primarily creative professionals aged 25-45 who value both aesthetics and efficiency.

Usage: This will be implemented as a series of in-app messages, tooltips, and modals that appear during the user's first session, triggered by specific actions and inaction timeframes.

Specifics:
- Create content for a 5-step guided experience (Welcome, Profile Setup, Dashboard Tour, First Project, Next Steps)
- Each step should have a headline (max 8 words), description (max 25 words), and action button text
- Maintain a helpful but unobtrusive tone (users are likely already overwhelmed)
- Include micro-rewards/encouragement after completing each step
- For profile setup, explain the benefit of each field in one short sentence
- If a user becomes inactive for 45 seconds, include a single help prompt
- Add skip options for each non-essential step with gentle consequence reminder
- Include a progress indicator showing completion percentage
- Final screen should highlight the 3 most valuable next actions with their benefits
- Maximum of 120 total words across all screens (excluding button text)
- Use conversational language that addresses the user directly ("you/your")