What is the FLOW Framework?
FLOW is a prompt engineering framework built around four components: Function, Level, Output, and Win Metric. Its central innovation is the Win Metric — an explicit definition of what a successful output looks like, stated before the AI begins work.
- F — Function: What Should the AI Do?
- L — Level: At What Expertise and Complexity?
- O — Output: Define the Exact Deliverable Format
- W — Win Metric: Define What Success Looks Like
Most prompts tell the AI what to do but leave quality judgment entirely to the model. FLOW closes that gap by asking you to articulate the real-world test your output must pass: Can a CFO present it in a board meeting? Does a junior developer implement it without asking follow-up questions? Does the query run in under 30 seconds? When you define the win condition upfront, the AI can calibrate toward it.
The Level component adds a second dimension of control: you specify not just the topic but the expertise level and complexity tier of the response, ensuring the output is right for your actual audience rather than a generic reader.
When to Use the FLOW Framework
Business Analysis
Define the function (analyse unit economics), the audience level (senior management), and the win condition (presentable to a board) to get analysis that actually drives decisions.
Performance Optimisation
Set a measurable win metric for technical optimisation tasks — query execution time, load speed, memory usage — so the AI targets a real benchmark, not a vague improvement.
Code Review
Specify the function (review this PR), the level (senior engineer standard), and a win metric (a junior developer can action every comment without clarification).
Executive Deliverables
Produce strategy memos, board decks, and executive summaries calibrated to the specific expertise level and time constraints of senior leadership.
Technical Documentation
Specify the audience level and define the win condition (a new hire can onboard using this doc alone) to ensure documentation is complete and appropriately detailed.
Conversion & Copy Optimisation
Set copy function and audience level, then define the win metric as a specific conversion outcome or user action — keeping creative work grounded in business objectives.
How to Use the FLOW Framework
- F
Function — What Should the AI Do?
State the primary function clearly and specifically. "Analyse", "optimise", "write", "review", "summarize" — be precise about the action. Include any key inputs the AI needs to perform the function. This is your instruction, not your goal.
- L
Level — At What Expertise and Complexity?
Specify the expertise tier of the response and the assumed knowledge level of the reader. This could be a role ("senior management consultant"), an education level ("assumes MBA-level financial literacy"), or a complexity instruction ("explain without jargon, suitable for a non-technical executive").
- O
Output — Define the Exact Deliverable Format
Describe the structure, format, and sections of the output. Use numbered lists, specify tables, name sections, and set length expectations. A precise Output spec prevents the AI from choosing an arbitrary format that doesn't fit your workflow.
- W
Win Metric — Define What Success Looks Like
State the real-world test your output must pass. Frame it in terms of who will use the output and what they need to do with it. The Win Metric is the quality bar — concrete, verifiable, and audience-specific. It is the most important component for high-stakes deliverables.
Prompt Examples
Function: Analyse the unit economics of a direct-to-consumer subscription box business and identify the three biggest levers for improving profitability. Level: Senior management consultant at a top-tier strategy firm. Assume the reader has an MBA and is fluent in financial modelling, LTV/CAC ratios, contribution margins, and cohort analysis. Output: A structured two-page memo with: 1. Executive summary (3–4 sentences) 2. Current unit economics snapshot (table format) 3. Three profitability levers, each with: diagnosis, root cause, and recommended action 4. Prioritisation matrix (impact vs. effort, 2x2) Win Metric: The memo is successful if a CFO could read it in under 5 minutes, immediately understand the top priority, and walk into a board meeting ready to present the recommendation with confidence.
Function: Optimise the following SQL query for a PostgreSQL 15 database. The query runs a daily report on a 50-million-row orders table and currently takes 4 minutes 20 seconds to execute. [Paste query here] Level: Database performance engineer with deep expertise in PostgreSQL query planning, indexing strategies, partition pruning, and EXPLAIN ANALYSE output interpretation. Write explanations at a level appropriate for a senior backend engineer who understands SQL but is not a DBA specialist. Output: 1. Annotated EXPLAIN ANALYSE breakdown of the current bottlenecks 2. Optimised version of the query with inline comments explaining each change 3. Index recommendations (DDL statements ready to run) 4. Expected performance improvement and reasoning Win Metric: The optimised query should run in under 30 seconds on equivalent hardware. Each recommendation must include the specific bottleneck it addresses so the engineer can validate the fix independently.
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Win Metric anchors the AI to a concrete, verifiable quality standard | Requires upfront thinking to articulate a meaningful Win Metric |
| Level component ensures output is calibrated for the actual audience | Less suited for exploratory or open-ended creative tasks |
| Output spec prevents arbitrary formatting choices | Four components can be over-engineering for simple, low-stakes requests |
| Excellent for business-critical and technically complex deliverables |
Frequently Asked Questions
What does FLOW stand for?
FLOW stands for Function, Level, Output, and Win Metric. Function defines what the AI should do, Level sets the expertise and complexity tier of the response, Output specifies the exact deliverable format, and Win Metric defines how success will be judged — making the quality bar explicit before the AI begins.
What makes FLOW different from other frameworks?
FLOW's defining feature is the Win Metric — a concrete definition of what a successful output looks like. Instead of leaving quality judgment to the AI, you explicitly state the standard the output must meet. This is especially valuable for performance-critical, business, or technical tasks where vague outputs are costly.
When should I use the FLOW framework?
Use FLOW for performance-oriented, business-critical, or technically complex tasks where quality matters as much as completion: strategic memos, database optimisation, code reviews, business analysis, and any deliverable where you can articulate a clear success standard upfront.
How do I write a good Win Metric?
A good Win Metric describes the real-world test your output must pass. Think about who will use the output and what they need to do with it: 'A CFO could present this in 5 minutes', 'A junior developer can implement this without asking questions', 'The query runs in under 30 seconds'. Concrete, role-based tests work best.
What should the Level component specify?
Level should specify both the expertise level of the response (beginner, intermediate, expert, executive) and any complexity constraints (technical depth, vocabulary assumed, length expectations). It ensures the output is calibrated for your actual audience rather than defaulting to generic explanations.
Can FLOW be used for creative tasks?
Yes, with adaptation. For creative work, the Win Metric becomes qualitative: 'The copy should feel like Patagonia's brand voice', 'The story should make the reader feel urgency without panic'. As long as you can describe what success feels like, FLOW's structure keeps creative briefs anchored in clear expectations.
How does FLOW compare to the SMART framework?
Both FLOW and SMART emphasise measurable outcomes. SMART comes from project management goal-setting and works well for broad task scoping. FLOW is more granular — it focuses on the deliverable format and quality bar rather than the overall goal. They can be used together: SMART to define the project goal, FLOW to specify each AI-generated deliverable within it.