What is the D.E.E.P. Framework?
The D.E.E.P. framework is an iterative prompt engineering approach that structures content creation as a four-stage progressive refinement process. Its stages — Define, Expand, Evaluate, and Polish — guide the AI through a disciplined workflow that mirrors how skilled human writers and researchers approach complex documents.
- D — Define: Establish scope and success criteria
- E — Expand: Generate the full draft
- E — Evaluate: Critique against the definition
- P — Polish: Refine to final form
Unlike single-shot prompt frameworks that ask the AI to produce a finished output in one step, DEEP acknowledges that high-quality content cannot reliably emerge from a single generation event. By separating the work into four explicit stages with distinct objectives, DEEP dramatically increases the quality of final outputs — particularly for research synthesis, strategic analysis, white papers, and long-form editorial content.
- Define: Establish the scope, angle, audience, and success criteria before any content is generated.
- Expand: Generate the full draft based on the defined parameters.
- Evaluate: Critically assess the draft against the definition criteria, identifying gaps, weaknesses, and improvement opportunities.
- Polish: Refine the draft into final, publication-ready form based on the evaluation findings.
When to Use the D.E.E.P. Framework
Research Synthesis
Define the research question and evaluation criteria, expand into a comprehensive synthesis, evaluate for gaps and bias, and polish into a structured research summary or literature review.
White Papers and Reports
Use DEEP's structured stages to take complex strategic or technical topics from rough outline through full draft to polished, publication-ready long-form documents.
Long-Form Editorial Content
Produce well-argued, nuanced articles and essays that go through genuine critical evaluation before reaching final form — not just a first-draft output with light editing.
Strategic Memos and Analysis
Define the decision criteria, expand the analysis, evaluate the rigor of each section, and polish into an executive document where every claim is supported and every recommendation is clearly argued.
Academic and Technical Writing
Structure the Define stage around the research question and methodology, expand into a structured draft, evaluate against academic standards, and polish to meet journal or thesis requirements.
Collaborative Human-AI Editing
Assign each DEEP stage to the appropriate collaborator — human strategist for Define, AI for Expand, human editor for Evaluate, AI for Polish — creating a structured editorial workflow.
How to Use the D.E.E.P. Framework
- 1
Define — Establish scope and success criteria
Before any content is generated, define the document's purpose, audience, core argument or findings, and what a successful output looks like. This definition becomes the benchmark for the Evaluate stage. A weak Define stage produces a weak Evaluate stage because there are no agreed criteria to assess the draft against. Invest time here — it pays dividends in every subsequent stage.
- 2
Expand — Generate the full draft
Instruct the AI to produce a complete, unrestrained first draft based on the Define output. At this stage, completeness matters more than perfection. Ask the AI to cover all sub-topics, develop all arguments, and include all necessary sections — even if some will be revised or cut. A complete draft is easier to evaluate and refine than a cautious, abbreviated one.
- 3
Evaluate — Critique against the definition
Ask the AI (or perform yourself) a structured critique of the Expand draft using the Define criteria. Good evaluation prompts ask for: gaps in argumentation, unsupported claims, structural problems, unclear sections, tonal inconsistencies, and missed opportunities. The Evaluate stage should produce a prioritized list of specific improvements — not vague feedback like "make it more engaging".
- 4
Polish — Refine to final form
Apply the Evaluate findings to produce a final, publication-ready version. The Polish stage should address every specific improvement identified in Evaluate. Ask the AI to confirm which evaluation points have been addressed in the revision. A polished DEEP output should be indistinguishable from carefully edited professional writing.
Prompt Examples
Work through the following four stages to produce a white paper section on AI adoption barriers in mid-market financial services. DEFINE: Clarify the scope. The audience is CIOs and CTOs at banks and insurance companies with 200-2000 employees. The key argument is that the primary barrier is not technology cost but organizational readiness. Identify the three main sub-topics to cover. EXPAND: Write a full 500-word draft section covering all three sub-topics. Use a formal but accessible tone. Include at least two concrete examples or data references (you may use plausible illustrative statistics if real data is not available, clearly noted as illustrative). EVALUATE: Review the draft. Identify: (1) any logical gaps or unsupported claims, (2) any sections that repeat or could be tightened, (3) whether the organizational readiness argument is sufficiently foregrounded. POLISH: Rewrite the section incorporating all evaluation improvements. Ensure the final version flows as a single cohesive piece of professional writing with no evaluation notes visible.
Use the DEEP framework to develop a strategic recommendation memo on whether our company should expand into the German market in the next 18 months. DEFINE: State the decision criteria that should drive the recommendation. Identify the 4 most important factors to analyze: market size potential, competitive landscape, regulatory complexity, and operational cost to enter. EXPAND: Write a structured memo draft with one section per factor. Each section should include an analysis statement, the key risk or opportunity, and a preliminary recommendation weight (high/medium/low consideration). EVALUATE: Assess the draft. Are the four factors treated with equal rigor? Is the overall recommendation clear, or does the memo avoid committing to a direction? What is the weakest section? POLISH: Revise into a final executive memo with a clear recommendation in the opening paragraph, supporting analysis in the body, and a single closing paragraph stating the proposed next step.
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Produces significantly higher quality output than single-shot prompting | Higher token cost than single-shot frameworks |
| Evaluation stage catches gaps before they reach the final draft | Requires more time and prompting effort per document |
| Maps naturally to professional editorial and research workflows | Evaluate stage quality depends on the specificity of the Define stage |
| Define stage prevents scope creep and misaligned output | Not well-suited for quick, short-form content requests |
Frequently Asked Questions
What does D.E.E.P. stand for in prompt engineering?
D.E.E.P. stands for Define, Expand, Evaluate, and Polish. It is an iterative prompt framework that guides both the AI and the human through a four-stage refinement process. Rather than expecting a perfect output from a single prompt, DEEP structures the work as progressive development: define the scope, expand into a full draft, evaluate critically, and polish to final quality.
Why is DEEP called an iterative framework?
DEEP is iterative because it treats content creation as a multi-stage process rather than a single generation event. Each stage — Define, Expand, Evaluate, Polish — produces output that feeds the next stage. You can run DEEP as a series of four separate prompts or as one structured mega-prompt that instructs the AI to work through all four stages in sequence. Either way, the process involves building on and critiquing previous output.
When should I use the DEEP framework?
Use DEEP for high-stakes content that requires genuine quality — research reports, white papers, long-form articles, strategic plans, and executive presentations. DEEP is the right choice when you cannot afford to publish a first draft, when the content will be reviewed by senior stakeholders, or when the topic is complex enough that a single prompt is unlikely to capture all the necessary nuance.
Can I use DEEP in a single prompt or does it require multiple exchanges?
DEEP can be used both ways. In a single-prompt approach, you instruct the AI to work through all four stages sequentially, explicitly completing each stage before proceeding to the next. In a multi-turn approach, you use a separate prompt for each stage, reviewing and adjusting between turns. The multi-turn approach gives you more control and the ability to redirect at each stage; the single-prompt approach is faster but less controllable.
What happens in the Evaluate stage of DEEP?
In the Evaluate stage, the AI — or you — critically reviews the expanded draft against the original definition criteria. A good Evaluate prompt asks the AI to identify gaps in the argument, check factual accuracy, assess whether the structure serves the reader, flag any sections that are unclear or unsupported, and suggest specific improvements before the Polish stage. Treating evaluation seriously is what separates DEEP outputs from ordinary first drafts.
How is DEEP different from simply asking for a draft and then asking for revisions?
Simple draft-then-revise prompting lacks the explicit Define and Evaluate stages that give DEEP its structure. In DEEP, Define ensures the scope, angle, and success criteria are agreed before any writing begins. Evaluate uses specific criteria — derived from the Define stage — to assess the draft. This prevents the common problem of revising in circles because the quality bar was never clearly established at the start.
Is DEEP suitable for collaborative workflows with human editors?
Yes, DEEP maps naturally onto collaborative workflows. The Define stage can be completed by a human strategist or editor. The Expand stage is delegated to the AI. The Evaluate stage is performed by a human editor using the AI's draft. The Polish stage can be a human-AI collaboration where the human provides specific revision notes and the AI implements them. DEEP's structure makes the human-AI collaboration explicit and organized.