COAST Framework: Context-Optimized Audience-Specific Tailoring

Context: Our food delivery service experienced a data breach last week that potentially exposed customer names, email addresses, and order history (but not payment details or passwords). We've identified and fixed the vulnerability and engaged a third-party security firm to audit our systems.

Objective: To notify affected customers about the breach while maintaining trust and providing clear next steps for account security.

Audience: Our 50,000+ active customers who range from tech-savvy young professionals to less technically experienced older adults, all of whom are understandably concerned about their data security.

Style: A clear, straightforward email with obvious section headers, bullet points for action items, and links to more detailed resources. Include an FAQ section addressing common concerns.

Tone: Transparent and apologetic but reassuring, avoiding technical jargon while still providing enough detail to demonstrate competence and honesty.

Context: Our online learning platform is launching a new series of data science courses aimed at career-changers. We've noticed high drop-out rates in technical courses because students struggle to see practical applications.

Objective: To create an introductory lesson that demystifies machine learning concepts and motivates students by showing immediate real-world applications they might encounter in entry-level roles.

Audience: Career-changers aged 25-45 with undergraduate degrees but minimal technical background. They're motivated by career advancement and salary potential but anxious about their ability to learn technical concepts.

Style: A visual-heavy presentation with conceptual diagrams, real-world examples first followed by gentle introduction to the underlying math, and frequent knowledge checkpoints. Include analogies that connect to everyday experiences.

Tone: Encouraging and supportive while maintaining intellectual rigor. Address anxiety directly with phrases like "You might be thinking this looks complicated, but let's break it down..."

Context: We're a sustainable fashion brand launching our first swimwear collection made from recycled ocean plastic. Each purchase removes 5 pounds of plastic waste from the environment. Our competitors feature sustainability but typically charge 30-50% premium prices.

Objective: To promote our new swimwear collection in a way that highlights our environmental impact while positioning our price point (15% premium to conventional swimwear) as accessible sustainable fashion.

Audience: Environmentally conscious women aged 25-40 who want to make sustainable choices but are price-sensitive. They're active on social media and influenced by both environmental impact and style considerations.

Style: Instagram-optimized content with visually striking imagery of both the products and ocean conservation impact. Include specific impact metrics as graphic overlays and emotion-evoking captions with clear call-to-action.

Tone: Passionate about environmental issues without being preachy, celebratory of conscious consumer choices, and positioning buyers as part of a movement rather than just shoppers.

Context: Our SaaS analytics platform has released a significant UI redesign based on 6 months of user research. The new interface improves workflow efficiency by 40% for experienced users but requires learning new navigation patterns. We're receiving 30% more support tickets than normal.

Objective: To create a support response template that acknowledges user frustration, helps them navigate the new interface, collects specific feedback, and highlights benefits they might not have discovered yet.

Audience: Marketing analysts at mid-sized companies who use our platform daily for reporting. They're pressed for time, resistant to workflow changes, but interested in features that save them time once mastered.

Style: A concise, scannable email with personalized troubleshooting steps, embedded screenshots highlighting new navigation paths, and links to relevant video tutorials (timestamped to specific features). Include a "Quick Wins" section showing shortcuts they might have missed.

Tone: Empathetic about disruption to their workflow while confidently guiding them through changes. Avoid defensiveness about the redesign while maintaining enthusiasm for the improvements.

Context: We've developed a new GraphQL API to replace our legacy REST API. The new API offers more flexible queries, improved performance, and new features, but requires a different implementation approach. We'll support both APIs for 6 months before deprecating the REST version.

Objective: To create a migration guide that helps existing customers transition from our REST API to our GraphQL API with minimal disruption to their applications.

Audience: Backend developers with experience in our REST API but varying levels of GraphQL knowledge. They need to understand both conceptual differences and specific code-level changes required.

Style: A comprehensive technical guide with side-by-side comparison examples, migration checklists, and complete code samples for common operations. Organize by use case rather than by endpoint. Include a troubleshooting section addressing common migration errors.

Tone: Technically precise and efficient with information but encouraging about the benefits of migration. Acknowledge the investment of time required while emphasizing long-term advantages.

Context: Our company (200 employees) is transitioning from a traditional 9-5 office environment to a hybrid work model where employees can work remotely 3 days per week. This follows 6 months of pilot testing with selected departments. The transition will happen in phases over 2 months.

Objective: To inform all employees about the new hybrid work policy, explain the implementation timeline, address common concerns, and establish clear expectations for both in-office and remote work days.

Audience: Our diverse workforce spanning five departments with varying roles and remote work suitability. Some employees have expressed enthusiasm for the change while others have concerns about team cohesion and management oversight.

Style: A comprehensive policy document with an executive summary at the top, clearly defined sections covering scheduling, technology support, office space changes, and performance expectations. Include a visual timeline for implementation and an FAQ section.

Tone: Clear and authoritative regarding policy details while being empathetic toward the significant change this represents. Convey excitement about the benefits while acknowledging legitimate concerns.