20 CONTEXT Framework Examples

I am the CTO of a 300-person logistics company. Our board is conservative and skeptical of technology spending. We have been running an AI pilot in route optimisation for 6 months with measurable results.

Create a 6-slide presentation outline that makes a compelling case for a 150K AI expansion budget for next year.

Lead with ROI data from the pilot, not with AI hype. Avoid the word 'transformation.' The CFO will challenge every number, so include source citations. Address the risk of NOT investing.

Confident, data-driven, and pragmatic. Speak like a business leader, not a technologist.

Slide 1 example headline: 'Our AI pilot saved 340 driver-hours in 6 months. Here is what happens when we scale it.'

6 slides. Each slide has a headline (under 12 words), 3 bullet points, and a speaker note of 2-3 sentences. Deliver as a numbered outline.

I am the CEO of a 50-person digital agency. Q3 revenue was up 12% but two key clients have signalled they may reduce budgets in Q4. Team morale is high after winning an industry award last month.

Write an internal all-hands email summarising Q3 performance and setting expectations for Q4.

Be transparent about the client risk without causing panic. Frame Q4 as a challenge we can manage, not a crisis. Mention the award but do not dwell on it. Include specific actions the team can take.

Honest, steady, and motivating. The tone of a leader who trusts their team with the truth.

Opening line style: 'Q3 was strong. Not perfect, but strong. Here is where we stand.'

300-400 words. Subject line plus email body. End with 3 specific priorities for Q4 as a numbered list.

I am the head of marketing at a B2B SaaS company selling project management software. We are launching a new AI-powered resource allocation feature. Our email list is 15,000 project managers and operations directors.

Write a 3-email launch sequence: teaser (1 week before), launch day, and follow-up (3 days after).

Our audience is skeptical of AI claims. Lead with the problem (resource allocation is manual and painful), not the technology. Include a free trial CTA, not a demo booking CTA. Avoid exclamation marks.

Professional, empathetic, slightly understated. We are solving a real pain point, not hyping a feature.

Subject line style we have used successfully before: 'The resource allocation problem nobody talks about'

Each email: subject line, preview text (under 90 characters), and body (150-200 words). Use short paragraphs, no bullet points in body. End each with a single clear CTA.

I am the founder of an AI consulting firm. I have 8,000 LinkedIn followers, mostly mid-level managers and directors at companies with 200-2,000 employees. My posts that perform best are contrarian takes backed by data.

Write a LinkedIn post about why most companies fail at AI adoption, and what they should do instead.

Do not blame the technology. The argument is that companies fail because they start with tools instead of problems. Do not mention specific AI tools by name. Include a specific statistic (use the McKinsey 2024 finding that 72% of companies have adopted AI but only 1 in 4 report measurable value).

Direct, slightly provocative, but constructive. Not cynical. End on a hopeful note.

Hook style: 'Unpopular opinion: [bold claim]. Here is why.' followed by short paragraphs, each 1-2 sentences.

200-250 words. No hashtags in the body. Add 3 relevant hashtags at the very end. Use line breaks between every 1-2 sentences for mobile readability.

I am a PhD candidate in organisational psychology. I am writing the literature review chapter of my thesis on the impact of remote work on team cohesion. My supervisor expects APA formatting and critical analysis, not just description.

Summarise the 5 most cited papers on remote work and team cohesion from 2020-2024 and identify the key themes, contradictions, and gaps.

Distinguish between studies that measure team cohesion via self-report surveys vs. behavioural metrics. Note any papers that conflate 'remote work' with 'hybrid work.' Flag methodological weaknesses.

Academic but readable. Critical, not cynical. The voice of a researcher who respects the literature but sees its limitations.

Theme summary example: 'Theme 1: Communication frequency as a proxy for cohesion. Smith (2021) and Patel (2022) both find that...'

800-1,000 words. Organise by theme, not by paper. Include in-text citations in APA format. End with a 'Gaps and opportunities' paragraph.

I am a product manager at a fintech startup building a personal finance app for Gen Z users (18-25). We have 3 direct competitors: Monzo, Revolut, and Cash App. I need to present this analysis to our leadership team next week.

Create a competitive analysis comparing our 3 competitors across pricing, features, user experience, and market positioning.

Focus on features relevant to Gen Z specifically (budgeting tools, social payments, savings gamification). Exclude enterprise or business banking features. Be objective about where competitors are genuinely ahead of us.

Analytical and honest. This is an internal document, so no need to spin anything. Call out threats clearly.

Feature comparison format: 'Budgeting: Monzo [rating/description] | Revolut [rating/description] | Cash App [rating/description] | Us [gap/opportunity]'

Structured as: Executive Summary (100 words), Comparison Table, Detailed Analysis per competitor (200 words each), Key Threats, and Recommended Actions. Total 800-1,000 words.

I am a backend developer working on a Node.js REST API using Express and TypeScript. Our database is PostgreSQL with Prisma as the ORM. We follow the repository pattern and have existing middleware for authentication and error handling.

Write a complete CRUD endpoint for a 'projects' resource, including the route handler, service layer, and Prisma schema.

Include input validation using Zod. Handle the case where a user tries to access a project they do not own (return 403, not 404, for security). Use our existing auth middleware to extract the user ID from the JWT. Do not use any deprecated Express methods.

Clean, well-commented production code. Comments should explain 'why,' not 'what.'

Follow the pattern of our existing users endpoint: route calls service, service calls repository, repository calls Prisma. Here is the users route for reference: [paste existing code].

Deliver as 3 separate files: routes/projects.ts, services/projectService.ts, and the Prisma schema addition. Include JSDoc comments on exported functions.

I am a senior developer reviewing a pull request from a junior team member. The PR adds a new notification service to our React Native app. The code works but has several issues I want to address constructively.

Write code review comments for the following issues: missing error handling in the API call, a useEffect with missing dependencies, and inline styles that should use our design tokens.

Be constructive, not critical. Explain why each change matters, not just what to change. Reference our team coding standards where relevant. Do not rewrite their code entirely; suggest specific, minimal changes.

Supportive and educational. Like a mentor who wants the junior developer to understand the reasoning, not just follow orders.

Comment style: 'Nice work getting this working! One thing to consider here: [explanation]. A small change that would help: [suggestion]. This matters because [reason].'

3 separate review comments, each 50-80 words. Format each as: Location (file:line), Comment, Suggested change (as a code snippet).

I am an account executive at an AI training company. I am reaching out to the VP of Operations at a 500-person manufacturing company. From their LinkedIn, I can see they recently posted about struggling with quality control bottlenecks.

Write a cold email that gets a reply. The goal is to book a 15-minute discovery call, not to sell our product.

Reference their specific LinkedIn post about quality control. Do not pitch our product in the first email. Ask a genuine question about their challenge. Keep it under 100 words because executives do not read long cold emails. No attachments, no links in the first email.

Peer-to-peer, not salesperson-to-prospect. Curious and direct. Zero corporate jargon.

Opening line style: 'Saw your post about [specific thing]. We are seeing the same pattern at 3 other manufacturers we work with.'

Subject line (under 6 words, no clickbait), email body (80-100 words, 3 short paragraphs), and a single question as the CTA. No signature block beyond name and company.

I am a solutions consultant at a cybersecurity firm. We have completed a 3-week assessment of a healthcare company with 2,000 employees. They have 14 critical vulnerabilities, no incident response plan, and are facing a HIPAA audit in 4 months.

Write the executive summary section of our remediation proposal. This is the section the CEO reads before deciding whether to approve the budget.

Lead with regulatory risk (the HIPAA audit), not technical vulnerabilities. Quantify the potential cost of a breach (average healthcare breach cost). Do not list all 14 vulnerabilities in the summary. Frame our solution as risk reduction, not technology purchase.

Urgent but measured. The kind of tone that makes an executive act without feeling manipulated.

Opening sentence style: 'In 4 months, [Company] will face a HIPAA compliance audit. Based on our assessment, there are 14 unresolved vulnerabilities that put both compliance and patient data at risk.'

250-300 words. 4 paragraphs: risk overview, key findings (top 3 only), recommended approach (high level), and investment range with ROI framing. No technical jargon.

I am the HR director at a 150-person e-commerce company. We are creating a brand new role: AI Operations Coordinator. This person will sit between the tech team and business units, helping departments use AI tools effectively. No one in our company has done this role before.

Write a job description that attracts candidates who are practical AI users, not AI researchers or data scientists.

Emphasise that this is a coordination and enablement role, not a technical build role. Required skills should focus on communication, project management, and hands-on AI tool experience rather than ML or coding. Include 'nice to have' skills separately from requirements. Avoid 'rockstar,' 'ninja,' or gendered language.

Professional, clear, and inviting. The kind of job description that makes someone think 'that is exactly what I do, but nobody has given it a title before.'

Responsibility format: 'Work with [department] to identify [specific type of] opportunities for AI-assisted workflows, then build and document the process.'

Structure: Role title, 2-sentence summary, 6-8 responsibilities, 5 required qualifications, 3 nice-to-haves, and a 2-sentence 'about us' section. Total 400-500 words.

I am an HR manager at a 200-person SaaS company transitioning from annual reviews to quarterly check-ins. Managers have complained that the current template is too long and does not lead to useful conversations. We want something that takes 30 minutes, not 2 hours.

Create a quarterly performance check-in template that managers can complete in 15 minutes of prep and discuss in a 30-minute meeting.

Focus on forward-looking goals and blockers, not backward-looking evaluation. Include a self-assessment section so the employee comes prepared too. Avoid rating scales (1-5) as we are moving away from those. Include one question about AI tool adoption since we are rolling out AI across departments.

Conversational and practical. This should feel like a useful conversation guide, not a compliance form.

Question style: 'What is the one thing that, if unblocked, would have the biggest impact on your next quarter?' rather than 'Rate your performance against objectives.'

Two sections: Manager Prep (5 questions, each with a 1-2 sentence guidance note) and Meeting Agenda (structured for 30 minutes with time allocations). Deliver as a single document.

I am the FP&A analyst at a Series B startup with 80 employees. We closed a funding round 6 months ago and have 18 months of runway at current burn rate. The CEO and board want a monthly financial summary that focuses on burn rate, revenue growth, and path to profitability.

Create a monthly financial summary template with placeholder sections that I can fill in each month with our actual numbers.

Include a runway calculation that updates based on current burn rate and cash position. Add a section for 'variance vs. plan' since we have a board-approved budget. Flag any line items that are more than 15% over budget. Do not include balance sheet details; this is a management report, not an accounting document.

Clear, precise, and forward-looking. The tone of an analyst who understands the numbers and can explain what they mean for the business.

Metric format: 'Monthly Recurring Revenue: [amount] | vs Plan: [+/- %] | vs Prior Month: [+/- %] | Trend: [arrow or word]'

One page. Sections: Key Metrics Dashboard (5-6 metrics in the format above), Revenue Breakdown, Cost Breakdown with variance flags, Runway Update, and 1-2 sentence Analyst Commentary. Use a table for the metrics.

I am a finance director at a mid-size retail chain (40 stores). The operations team wants to invest 200K in an AI-powered inventory management system. I need to present the financial case to the CFO, who approves all capital expenditure over 100K.

Write a 1-page investment memo that presents the financial case for the AI inventory system, including expected ROI and payback period.

The main cost savings come from reducing overstock (currently 8% of inventory value) and stockouts (estimated 3% lost sales). Use conservative estimates (assume 50% improvement, not the vendor's claimed 80%). Include implementation costs and a 3-month productivity dip during rollout. The CFO will reject anything that looks like a vendor pitch.

Analytical and conservative. This should read like internal financial analysis, not a sales document.

ROI calculation format: 'Annual overstock cost: [current] x [expected reduction %] = [annual saving]. Payback: [total investment] / [annual saving] = [months].'

One page. Structure: Investment Overview (50 words), Cost Breakdown (table), Projected Savings (table with conservative/moderate/optimistic scenarios), Payback Period, Risk Factors (3 bullets), and Recommendation (2 sentences).

I am a corporate trainer designing a half-day workshop on AI for non-technical managers at a financial services company. The 20 attendees have heard of ChatGPT but most have not used it beyond basic questions. The company has approved Claude and ChatGPT for internal use.

Design a 4-hour workshop curriculum that takes participants from AI-curious to confidently using AI for their daily management tasks.

Every module must include a hands-on exercise, not just slides. Use real management scenarios (writing reports, preparing for 1:1s, analysing data) rather than generic demos. Avoid technical content about how AI works; focus entirely on practical application. Include a 15-minute break.

Practical, encouraging, and jargon-free. The facilitator guide should read like clear instructions, not an academic syllabus.

Module format: 'Module 2: AI for Weekly Reports (45 min). Learning outcome: Participants can draft a weekly status report using the CONTEXT framework. Activity: Each participant uses AI to write their actual next weekly report.'

4 modules plus intro and wrap-up. Each module: title, duration, learning outcome, facilitator talking points (3-4 bullets), hands-on exercise description, and materials needed. Total workshop time: 4 hours including breaks.

I am a university lecturer teaching a postgraduate course on digital business strategy. I am setting a new assignment: students must use AI to analyse a real company's digital strategy and present recommendations. This is the first time I am explicitly allowing AI use in an assessed assignment.

Create an assessment rubric that evaluates how effectively students use AI as an analytical tool, not just whether their final output is polished.

Students must submit their AI prompts alongside their analysis. The rubric should reward sophisticated prompting and critical evaluation of AI output, not just the final deliverable. Penalise uncritical acceptance of AI output (no fact-checking, no original analysis added). Include a section on AI transparency and attribution.

Academic, precise, and fair. The rubric should leave no ambiguity about what earns each grade band.

Criterion format: 'AI Prompting Quality — Distinction (70%+): Demonstrates iterative, sophisticated prompting using a structured framework. Prompts show clear reasoning about what information the AI needs.'

4 criteria, each with 4 grade bands (Distinction, Merit, Pass, Fail). Each cell has 2-3 sentences describing the standard. Include a 100-word preamble explaining the rubric to students. Format as a table.

I am the founder of a sustainable packaging startup. We make compostable alternatives to plastic packaging for food brands. We started 3 years ago after I saw the plastic waste problem firsthand while working in the food industry. We now serve 45 food brands across the UK.

Write the 'Our Story' page for our website that explains why we exist and what drives us.

The story should start with the personal moment that triggered the company, not with the product. Avoid guilt-tripping the reader about plastic use. Position sustainability as smart business, not sacrifice. Do not use the phrases 'save the planet' or 'eco-warrior.' Include our growth (3 years, 45 brands) as proof of traction.

Warm, genuine, and quietly determined. Like a founder who cares deeply but is not preachy about it.

Opening style: 'In 2021, I was standing in a food production warehouse surrounded by 3 tonnes of plastic shrink wrap that would be used once and thrown away. I thought: there has to be a better way.'

400-500 words. 5 paragraphs: the origin moment, the problem we saw, the solution we built, where we are now (traction), and where we are going. End with a single-sentence mission statement.

I run a weekly newsletter about the intersection of AI and design with 5,000 subscribers. This week's edition covers 3 topics: a new AI image tool that designers are split on, a case study of AI in a branding project, and a practical prompt template for generating mood boards.

Write the newsletter introduction paragraph that hooks readers and previews the 3 topics.

The hook should reference the controversy around the new AI image tool without taking a side yet. Tease the case study outcome without revealing it. Position the prompt template as the most actionable section. Do not use 'In this week's edition' as an opener.

Conversational, curious, and slightly opinionated. Like texting a smart friend about interesting things you found this week.

Previous intro that performed well (42% open rate): 'A designer I respect told me last week that AI will never understand visual hierarchy. Then I showed her what Claude did with a single prompt. She went quiet for a minute.'

80-120 words. 3-4 sentences. Must work as email preview text (the first sentence needs to hook in 50 characters). End with a subtle CTA to keep reading.

I am the head of strategy at a UK-based project management software company (200 employees, 20M ARR). Our board wants us to evaluate entering the US market. We currently have 12% of revenue from US customers who found us organically, but no US sales team or marketing presence.

Create a market entry analysis framework that I can populate with our data and present to the board as part of the go/no-go decision.

Include a section on regulatory and compliance differences (data residency, SOC 2 requirements). Address the pricing challenge (our UK pricing is 30% below US competitors). Consider the timezone support challenge. Do not assume we should enter the US market; this must be genuinely balanced.

Strategic and balanced. The board should feel this is rigorous analysis, not a foregone conclusion. Present risks and opportunities with equal weight.

Section format: 'Market Opportunity: [total addressable market], [current penetration], [growth rate]. Key Finding: [1-sentence insight]. Implication: [what this means for our decision].'

Structure: Executive Summary (100 words), Market Sizing, Competitive Landscape, Go-to-Market Options (3 scenarios with cost estimates), Risk Assessment (regulatory, operational, financial), and Recommendation Framework (criteria for the go/no-go decision). Total: 1,000-1,200 words.

I am the Chief Digital Officer at a 1,000-person insurance company. The CEO has asked me to present a 12-month AI adoption roadmap to the executive committee. We have no current AI initiatives beyond a few individuals using ChatGPT informally. Our IT team is stretched, and there is union representation for 40% of our workforce.

Create a phased 12-month AI adoption roadmap that balances quick wins with sustainable infrastructure, and addresses workforce concerns proactively.

Phase 1 must deliver measurable results within 90 days to maintain executive support. Address the union relationship early; frame AI as augmentation, include union reps in the steering committee. Do not recommend building custom AI models; focus on integrating commercial AI tools into existing workflows. Include a governance framework. Budget should assume we do not hire an AI team in year 1.

Pragmatic, politically aware, and results-oriented. This needs to feel achievable, not aspirational.

Phase format: 'Phase 1: Quick Wins (Months 1-3). Goal: Demonstrate measurable value. Focus areas: [3 specific workflows]. Expected outcome: [quantified result]. Investment: [amount]. Risk: [primary risk and mitigation].'

4 phases across 12 months. Each phase: name, duration, goal, 3 focus areas with specific use cases, expected outcomes (quantified), investment required, primary risk and mitigation. Include a governance section and a workforce communication plan. Total: 1,200-1,500 words.