Why this is hard to get right
The Memo That Had to Do Everything at Once
Maya had been the VP of Engineering for three years. She'd inherited a 40-person team, doubled it, and survived two reorgs. But when the CEO asked every function lead to publish a vision and operating principles memo before the all-hands, Maya froze.
She knew the problem. The last memo she'd written — a "team charter" drafted under deadline pressure — read like a motivational poster. Words like excellence and ownership appeared six times. Nobody referenced it after the meeting. One engineer later admitted he hadn't read past the second paragraph.
This time she needed something real: a document that would survive Monday morning standups, a contentious sprint planning session, and a recruiter's first conversation with a candidate. It needed to be short enough to actually read and specific enough to change behavior.
Her first AI attempt reflected exactly what she typed: "Write a vision and operating principles memo for my engineering team." The output was polished and generic. Five principles, each one a corporate virtue. No examples. No teeth. No reason for her team to believe it was written by anyone who'd ever debugged a production incident at 2 a.m.
She tried again with more detail, but it still drifted — too long, mixed tone, principles that contradicted each other when applied to real situations. She spent an hour editing instead of leading.
The core challenge with this type of memo isn't writing. It's structured thinking under pressure. You have to simultaneously hold your audience's context, your business constraints, the values you actually believe in, and the behaviors you want to see — then compress all of it into something a person will read in four minutes and remember for a year.
A well-crafted prompt solves this by forcing that structure before a single word of the memo is written. When Maya specified her team's size and tenure mix, the target growth number her org was supporting, the specific tradeoffs she wanted principles to resolve (build vs. buy, speed vs. quality), and a Do/Don't format for each principle, the AI finally produced something she recognized as hers.
She sent the memo on a Thursday. By the following Tuesday, two engineers had quoted a principle back to her during a roadmap debate. That's the test. Not whether the memo sounded good — whether it changed a decision.
Common mistakes to avoid
Writing Principles as Virtues, Not Behaviors
Prompting for 'values like integrity and excellence' produces aspirational slogans, not decision rules. Behaviors are testable; virtues are not. Ask specifically for 'a principle that guides how the team resolves tradeoffs between speed and quality' and you'll get something managers can actually apply in a sprint review or hiring debrief.
Omitting the Business Context That Anchors the Memo
Without revenue stage, growth goals, or strategic bets, AI defaults to generic leadership language. The memo becomes indistinguishable from any other company's. Specifying metrics like ARR, headcount velocity, or a key initiative (e.g., enterprise expansion) grounds principles in real stakes and makes the 'Why Now' section credible.
Not Specifying Audience Tenure and Role Mix
A memo for 5 senior engineers reads very differently from one for a 250-person mixed-tenure team. Tone, assumed context, and example relevance all shift. Failing to specify this forces AI to average across audiences, producing a memo that feels slightly off for everyone and resonant for no one.
Skipping Anti-Pattern Examples
Listing what the team should do is only half the job. Without explicit 'Don't' examples, principles stay abstract and open to conflicting interpretations. Prompt specifically for counterexamples or failure modes for each principle — this is what turns a values document into an alignment tool that survives real disagreements.
Leaving Format and Length Undefined
Open-ended prompts produce memos that are too long, poorly structured, or formatted for the wrong medium. A 700-word memo will not be read at an all-hands. Specify section names, word limits, and output format (scannable bullets vs. narrative paragraphs) to ensure the AI produces something people will actually engage with.
Ignoring Measurable Commitments
A memo without commitments is a speech. Without 2–3 specific, trackable commitments from leadership, operating principles feel decorative rather than binding. Prompt explicitly for commitments tied to the memo's principles — this signals to the team that the memo will be revisited and evaluated, not forgotten after the launch meeting.
The transformation
Write a memo about our company vision and values for the team.
Role: You are a CEO writing a memo. Goal: Define a 12-month vision and 5 operating principles that guide decisions. Audience: 250-person B2B SaaS team (product, GTM, operations). Mixed tenure. Context: ARR $28M, targeting 40% YoY growth; key bet is enterprise expansion. Tone: Direct, optimistic, concrete; avoid buzzwords. Format: 1-page memo with sections: 1) Vision (3 sentences), 2) Why Now, 3) Operating Principles (5 bullets, each with a “Do/Don’t”), 4) Commitments (3 measurable), 5) How to apply. Constraints: Max 400 words. Use real examples from sales cycle and roadmap tradeoffs.
Why this works
Role Anchors Voice
The After Prompt opens with 'Role: You are a CEO writing a memo.' This single line prevents the AI from defaulting to a neutral, committee-speak tone. Role assignment tells the model whose perspective, authority level, and communication style to adopt — producing a memo that sounds like a leader, not a template.
Business Context Kills Platitudes
Specifying 'ARR $28M, targeting 40% YoY growth; key bet is enterprise expansion' gives the AI concrete stakes to write around. Strategic anchors force the model to connect principles to real business pressure rather than inventing generic virtues. Every principle in the output can be traced back to a specific growth challenge.
Structured Format Produces Scannable Output
The After Prompt defines five labeled sections including a 'Do/Don't' format for each principle and a word limit of 400. Structural constraints prevent AI from generating long-form prose that no one reads. The Do/Don't format specifically converts abstract values into observable behaviors — the key test of a usable operating principles memo.
Audience Specificity Shapes Relevance
The After Prompt describes '250-person B2B SaaS team (product, GTM, operations). Mixed tenure.' This detail calibrates the AI's assumptions about what readers already know, what examples will land, and how formal or direct the tone should be. Audience profiling eliminates the vague, inoffensive middle ground that satisfies no one.
Real Examples as Constraints
The instruction to 'use real examples from sales cycle and roadmap tradeoffs' prevents the AI from generating hypothetical scenarios that feel invented. Domain-specific constraints signal that the memo must connect to actual decisions the team has faced — which is precisely what separates a memo people quote from one they file away.
The framework behind the prompt
The Theory Behind Operating Memos That Actually Work
The gap between a values document and a useful operating memo is the gap between declarative and procedural knowledge — knowing what matters vs. knowing how to act when it matters most.
Organizational psychologist Karl Weick's work on sensemaking argues that people don't act based on abstract values — they act based on the stories and examples that make those values concrete. A memo that lists "integrity" as a principle gives team members nothing to work with. A memo that defines integrity as "we tell a customer their timeline is unrealistic before they sign the contract, not after" gives them a script.
This is why the Do/Don't structure in the After Prompt is more than a formatting choice. It operationalizes values by naming both the desired behavior and its counterpart. Research in behavioral economics confirms that loss framing (what not to do) often produces stronger behavioral change than gain framing (what to aspire to) — which is why explicitly defining anti-patterns matters.
The STAR framework (Situation, Task, Action, Result) informs how strong operating memos embed examples: each principle becomes more persuasive when readers can place it in a recognizable situation. The After Prompt's instruction to "use real examples from sales cycle and roadmap tradeoffs" applies this logic directly.
Amazon's Leadership Principles — arguably the most widely studied internal operating principles document in modern business — succeed because each principle includes an explanation of when and how it applies, often with tension built in. They don't list virtues. They describe decision rules.
The OKR framework (Objectives and Key Results), popularized by John Doerr, separates the "what" (vision) from the "how" (operating principles) and the "measure" (commitments). The memo structure in the After Prompt mirrors this logic: Vision sets direction, principles guide behavior, and measurable commitments create accountability.
When leaders understand that a memo's job is to reduce decision latency — helping people make faster, more consistent choices without escalation — they write very differently. The prompt structure on this page is designed to get you there from the first draft.
Prompt variations
Role: You are a first-time founder writing a company memo at 18 employees, preparing to scale to 50.
Goal: Write a one-page vision and operating principles memo that codifies culture before rapid hiring dilutes it.
Audience: Early team of engineers, a designer, and two salespeople. High trust, low process. Average tenure 14 months.
Context: B2C consumer app, 80K MAU, raising a Series A. Key tension: moving fast vs. building quality foundations.
Tone: Honest, direct, slightly informal. No corporate language. Write like you would talk to the team at a Friday lunch.
Format: 1) Where we're going (2 sentences), 2) Why it matters now (1 short paragraph), 3) How we work together (4 principles, each with one real example from the last 6 months), 4) What I commit to as founder (3 specifics).
Constraints: Under 350 words. No jargon. If a principle can't be explained to a new hire in 30 seconds, rewrite it.
Role: You are a VP of Customer Success writing a team memo, not a company-wide communication.
Goal: Define a 12-month team vision and 4 operating principles that guide how the CS team handles renewals, escalations, and expansion conversations.
Audience: 35 customer success managers across three regions. Mix of tenures from 3 months to 6 years. Some skepticism about new processes after a difficult Q3.
Context: Net revenue retention is 104%, target is 115%. New enterprise segment requires a different engagement model than mid-market. Two open leadership roles on the team.
Tone: Direct and empathetic. Acknowledge recent challenges. Avoid over-promising. Focus on practical guidance.
Format: 1) Team vision (2 sentences), 2) What changed and why this memo exists (1 paragraph), 3) Operating principles (4 bullets, each with: the principle, a real scenario where it applies, and what NOT to do), 4) My commitments to you (3 specifics with timelines).
Constraints: 400 words max. Must be readable in under 4 minutes. No acronyms without explanation.
Role: You are a CEO drafting a strategic memo to share with your board and executive team ahead of an annual planning session.
Goal: Articulate a 3-year company vision and the 5 operating principles the leadership team will use to evaluate major decisions and resource allocation.
Audience: 6-person board (3 investors, 2 independents, CEO) and 8-person exec team. Sophisticated readers who will push back on vague claims.
Context: Series B SaaS company, $55M ARR, expanding into EMEA. Key strategic choices ahead: build vs. acquire, platform vs. point solution, direct sales vs. channel.
Tone: Confident and substantive. No cheerleading. Show the reasoning behind each principle, not just the conclusion.
Format: Executive summary (3 sentences), Vision statement (1 paragraph), Strategic context (why these principles now — 1 paragraph), Operating Principles (5 principles, each with rationale and one strategic tradeoff it resolves), Commitments and review cadence.
Constraints: 600 words max. Each principle must directly address one of the three key strategic choices listed above.
Role: You are a COO writing a memo for a fully distributed, async-first team of 120 people across 14 time zones.
Goal: Define a team vision and 5 operating principles that solve the specific coordination and culture challenges of remote work at scale.
Audience: Entire company. Roles span engineering, marketing, support, and operations. English is a second language for roughly 40% of the team.
Context: The company has grown 3x in 18 months through remote hiring. Communication gaps, timezone friction, and inconsistent decision-making are the top three complaints from the most recent engagement survey.
Tone: Inclusive and precise. Avoid idioms or culturally specific references. Short sentences. Active voice throughout.
Format: 1) Where we're headed (2 sentences), 2) The coordination problems we're solving (4 bullet points, each naming a specific pain from the engagement survey), 3) Operating principles (5 bullets, each with: the principle, how it applies async, and one tool or practice that supports it), 4) How decisions get made (a 3-step escalation model).
Constraints: 450 words max. Plain language score of 8th grade or lower. Include one concrete example per principle.
When to use this prompt
Marketing Leaders
Align brand messaging and campaign prioritization with a shared vision and principles that guide tradeoffs across channels.
Product Managers
Frame roadmap decisions and discovery practices with principles that clarify customer value, quality bars, and iteration cadence.
Sales Directors
Set expectations for ideal customer profile, deal qualification, and discount discipline tied to the company vision.
Customer Success Leaders
Define renewal and expansion priorities, escalation paths, and customer communication standards grounded in operating principles.
Founders of Growing Startups
Codify culture and decision rules as headcount scales, reducing confusion during rapid hiring and role changes.
Pro tips
- 1
Anchor principles to real decisions to drive behavior change, not slogans.
- 2
Define 2–3 measurable commitments so teams can track adoption and impact.
- 3
Specify anti-patterns with clear “Don’t” examples to reduce ambiguity.
- 4
Name the audience’s pain points to tailor tone and examples for relevance.
The single best way to evaluate whether a principle is real is the tradeoff test: can you use this principle to make a decision when two good options conflict?
For each principle your AI generates, ask yourself: does this help me choose between two reasonable paths when the answer isn't obvious? If the answer is no, the principle is a value, not a rule.
Here's how to sharpen a weak principle:
- Weak: 'We prioritize customer success'
- Strong: 'When speed-to-ship conflicts with customer experience quality, we delay the release'
To build this into your prompt, add a line like: 'For each principle, identify the specific tradeoff it resolves (e.g., speed vs. quality, individual performance vs. team output, short-term revenue vs. long-term relationship).' This forces the AI to write principles that do real work.
You can also ask the AI to stress-test each principle with a hypothetical scenario: 'Show how a team member would apply this principle during a heated roadmap debate.' If the principle guides the decision, it's strong. If the answer is 'it depends,' rewrite the principle with more specificity.
The goal isn't to eliminate judgment — it's to make judgment more consistent across the team.
The structure of a vision and operating principles memo stays largely consistent across industries, but the language, examples, and principle domains shift significantly depending on your sector.
SaaS and Tech: Focus principles on product tradeoffs (build vs. buy, speed vs. reliability), customer segmentation decisions, and engineering culture norms. Use metrics like NPS, ARR, and deployment frequency as anchors.
Professional Services (consulting, law, accounting): Principles tend to govern client relationship quality, knowledge-sharing norms, and utilization vs. development tradeoffs. Tone is typically more formal.
Healthcare and Regulated Industries: Compliance, patient/customer safety, and documentation standards often appear as explicit principles rather than implied constraints. Word your constraints section carefully.
Consumer Brands and Retail: Creative standards, speed-to-market, and brand voice consistency are common principle domains. Examples from seasonal campaigns or product launches resonate well.
Nonprofits and Mission-Driven Organizations: Principles often address resource allocation under scarcity, stakeholder communication, and mission fidelity vs. growth. Avoid corporate growth language — replace with impact metrics.
In each case, specify the sector in your prompt and include 1–2 domain-specific tradeoffs you want the principles to resolve. The AI will calibrate its language and examples accordingly.
A well-written vision and operating principles memo has a use life well beyond the launch all-hands. Teams that deliberately embed memos into onboarding consistently report faster cultural alignment and fewer recurring disagreements about how decisions should get made.
Here's how to build this into your prompting strategy:
Design for the new hire reader. Add a line to your prompt: 'Write this so a new team member joining in 90 days can use it to understand how we make decisions without needing to ask.' This forces the AI to define terms, include context, and avoid in-group shorthand.
Create a companion FAQ. After generating the memo, run a second prompt: 'Generate 5 questions a new hire might ask after reading this memo, with answers.' This surfaces gaps in clarity before they cost you onboarding time.
Build a decision log. Prompt for a one-page addendum: 'List 3 recent decisions we made that demonstrate each principle in action.' This gives new hires real evidence that the principles aren't aspirational — they're how the team actually works.
Set a six-month review. Include in the memo's commitment section a specific review meeting (e.g., 'We'll review these principles at the H2 kickoff and update any that no longer reflect how we work'). This signals to the team — and to new hires — that the document is maintained, not abandoned.
When not to use this prompt
When This Prompt Type Is Not the Right Tool
A vision and operating principles memo works best when you have genuine clarity about direction and enough credibility to set norms. There are several situations where this format will produce more problems than it solves.
Avoid this prompt type when:
- The strategy itself is unsettled. If leadership is still debating the direction, a memo will feel premature and may need to be retracted, which damages credibility more than silence.
- You're in a crisis or active restructuring. During a layoff, reorg, or leadership change, teams need specific near-term guidance — not a 12-month vision document.
- You haven't consulted the people receiving it. A memo that arrives without any prior conversation signals that principles were imposed rather than co-created. Consider a workshop prompt or a draft-for-input approach instead.
- The audience is an external stakeholder. For boards, investors, or partners, use a strategy memo or investor update format — a vision and operating principles memo is an internal alignment tool.
Better alternatives in these cases:
- Use a team FAQ prompt for post-reorg communication
- Use a strategic narrative prompt for board-facing alignment
- Use a retrospective analysis prompt before drafting principles — discover what behaviors actually drove results before codifying them
Troubleshooting
The AI generates principles that sound identical to every other company's values
Add the specific tradeoffs your team actually faces. Instead of asking for 'principles that guide our team,' write: 'Generate principles that resolve these three recurring tensions: (1) shipping fast vs. building for scale, (2) supporting existing customers vs. acquiring new ones, (3) team autonomy vs. cross-functional alignment.' Tradeoff-specific prompts produce decision-specific principles.
The memo is too long and reads like a strategy deck, not a memo
Set hard structural constraints in the prompt. Add: 'The output must be a single page. Each section has a maximum word count: Vision = 50 words, Why Now = 75 words, each Principle = 40 words. If a section exceeds its limit, cut — don't summarize.' Explicit section-level limits prevent AI from padding to demonstrate thoroughness.
The Do/Don't examples feel made up and wouldn't happen in our actual work
Provide seed examples in your prompt. Add: 'Use these real situations as the basis for Do/Don't examples: (1) the decision to delay the Q2 release for a compliance fix, (2) the debate about prioritizing enterprise features over SMB requests.' Grounding examples in actual events produces examples that team members will recognize and trust.
The tone is either too inspirational or too dry — it doesn't sound like me
Give the AI a tonal reference. Add a line: 'Tone reference: direct and a bit blunt, like a prepared talk at a team offsite rather than a keynote speech. Avoid words like 'empower,' 'leverage,' or 'synergy.' Use short sentences. Write the way a person talks, not the way a press release reads.' Then review the first draft and flag 3 phrases that feel off-brand — revise the prompt with those as explicit exclusions.
The measurable commitments section is vague (e.g., 'we'll invest in your growth')
Require specificity in commitments by format. Add: 'Each commitment must include: (1) what will happen, (2) by when, and (3) how the team will know it happened. Example format: 'I will run a monthly 1:1 with every team lead to discuss principle application by the first Friday of each month.'' This constraint forces AI to write commitments that can actually be tracked.
How to measure success
How to Evaluate the Quality of Your AI-Generated Memo
Don't evaluate AI output by how polished it sounds. Evaluate it by whether it would actually change behavior.
Run these checks on the draft:
- The new hire test: Could a person joining in 30 days use this memo to make a real decision without asking for clarification? If not, the principles are too abstract.
- The conflict test: Pick two team members with historically different working styles. Would this memo help them resolve a disagreement, or would they each cite it to justify their existing preference?
- The specificity check: Count how many times vague words appear: empower, leverage, excellence, ownership. Each one is a signal the AI defaulted to a placeholder. Replace with observable behaviors.
- The commitment check: Are the 3 commitments measurable? Each should have a what, a when, and a how-we'll-know format.
- The length check: Can a busy manager read this in under 4 minutes? If not, cut — don't edit.
- The recognition test: Read the Do/Don't examples aloud. Do they sound like situations that actually happen in your org? If the scenarios feel invented, replace them with real ones.
Now try it on something of your own
Reading about the framework is one thing. Watching it sharpen your own prompt is another — takes 90 seconds, no signup.
Turn your strategy, team context, and values into a memo your team will actually read and use.
Try one of these
Frequently asked questions
A values document typically lists abstract virtues. A vision and operating principles memo is more operational — it combines a time-bound directional statement with behavioral rules that guide day-to-day decisions. The key difference: principles should be specific enough to resolve real disagreements. If two team members could use the same principle to justify opposite decisions, it's a value, not a principle.
For internal team memos, 350–450 words is the practical ceiling. Longer memos signal that the writer hasn't done the hard work of prioritizing. For board-facing or executive-level memos, you can extend to 600 words, but every sentence must earn its place. The format constraint in your prompt (e.g., 'max 400 words') is one of the most important inputs you can provide.
Add a context sentence that names the challenge directly: 'The team experienced a difficult Q3 reorg and there is moderate skepticism about new initiatives.' This signals the AI to adjust tone — less aspirational, more grounded and empathetic. You can also prompt for a 'What changed and why this memo exists now' section, which acknowledges history without dwelling on it.
Generic principles happen when the prompt lacks specific tradeoffs. Replace abstract virtues with the actual tensions your team faces: 'Write a principle that resolves how the team decides between shipping a feature quickly versus delaying it for quality review.' The more specific the tension, the more specific the principle. See the troubleshooting section for additional fixes.
A hybrid approach works best. Use AI to generate the structure, draft principles, and Do/Don't examples. Then revise the language to match your actual communication style and replace any placeholder examples with real incidents your team experienced. The memo needs to sound like you — AI gets you to 70%, your editing gets you to 100%.
Four to six is the practical range. Fewer than four often means the principles are too broad. More than seven means the list won't be remembered. Five is the most common number in well-adopted memos — it's enough to cover the major decision domains without overwhelming. Specify the exact number in your prompt so the AI doesn't pad the list.
Yes, and team-level memos are often more actionable because the audience is narrower and examples can be more specific. Adjust the audience field to name your specific function (e.g., 'a 30-person product team'), replace company-wide metrics with team-level KPIs, and focus principles on the decisions that come up weekly in your team's work — not abstract company values.
Most leaders update these annually or after a major strategic shift (funding round, reorg, pivot). Include a review cadence in your memo's commitments section — e.g., 'We'll revisit these principles at the H1 offsite.' This makes the memo feel like a living document rather than a one-time artifact, and it signals to the team that the principles are meant to evolve.