What is the IDEA Framework?
IDEA is a structured prompt engineering framework designed around the reality that creative and design tasks are inherently iterative. The acronym stands for Intent, Details, Examples, and Adjustments — four components that together create a prompt optimized not just for a good first output but for efficient collaboration across multiple revision cycles.
- I — Intent: State what you want to accomplish
- D — Details: Specify all concrete requirements
- E — Examples: Provide style and tone references
- A — Adjustments: Encode your revision rules
The framework's most distinctive innovation is the Adjustments component. Instead of waiting until the model produces an output to explain what you want changed, IDEA asks you to encode your revision logic upfront. When you tell the model "if I say 'punchier', do X" before the first output, every subsequent revision request is processed with complete clarity — the model knows exactly what each feedback signal means.
This approach is particularly valuable for creative tasks where the definition of "better" is personal and difficult to articulate in the moment. By thinking through your likely adjustments before you see the first draft, you also clarify your own preferences — often producing a better first output even before any iteration occurs.
When to Use the IDEA Framework
Copywriting & Content
Email campaigns, landing pages, social media posts, and headlines — any copy that will go through multiple rounds of revision before publication.
Design Briefs
Brief a model to generate UI copy, naming options, taglines, or brand messaging where style and tone preferences are difficult to articulate without iteration.
Creative Writing
Short stories, blog posts, scripts, and other long-form creative content where the first draft establishes direction and subsequent drafts refine it.
UI & Product Copy
Microcopy, onboarding flows, error messages, and button labels — small-scale text where the right wording requires several rounds of refinement.
Marketing & Brand
Brand voice development, positioning statements, and campaign concepts that need to be tested against multiple angles before settling on the right direction.
Ideation & Brainstorming
Generate an initial set of ideas, then use Adjustments to steer subsequent rounds toward the most promising directions without starting from scratch.
How to Use the IDEA Framework
- 1
Intent — State what you want to accomplish
Define the purpose of the creative output in one or two sentences. Include who it is for, what it should do, and what context it will appear in. Intent anchors all subsequent components and prevents the model from interpreting Details and Examples in a vacuum.
- 2
Details — Specify all concrete requirements
List every constraint and requirement: word count, format, tone, audience, what to include, what to avoid, and any technical or brand guidelines. The Details component is where you prevent the model from making assumptions on things you care about deeply.
- 3
Examples — Provide style and tone references
Share one to three examples that illustrate the style, tone, or structure you are aiming for. These can be direct quotes, links, or descriptions of existing work. Explain what aspect of each example you want the model to draw from — style, structure, register, or approach.
- 4
Adjustments — Encode your revision rules
Anticipate the feedback you are most likely to give and tell the model what each signal means. Use the pattern: "If I say [feedback word], then [specific action]." This is the component that makes IDEA uniquely powerful for iterative work — it transforms vague feedback into precise instructions the model can act on reliably.
Prompt Examples
Intent: Write a product launch email announcing the release of our new AI writing assistant, "Compose", to our existing customer base of 8,000 small business owners. Details: The email should be 180–220 words. Subject line must create curiosity without being clickbait. The body should lead with the key benefit (save 3 hours per week on business writing), mention 3 core features in a scannable format, include one social proof element (we have a quote from a beta user), and end with a single clear CTA linking to the product page. Tone: warm, confident, and direct. No exclamation marks. Examples: The tone and structure of Basecamp's product announcement emails — plain-spoken, benefit-first, no hype. Reference: "Basecamp 3 is here. Here's what it does for you..." style of opening. Adjustments: If I say "punchier", tighten each sentence and lead with a stronger verb. If I say "more formal", shift to a professional but still approachable register. If I say "different angle", rewrite the opening to lead with the time-saving benefit differently — try a before/after structure instead.
Intent: Design a landing page headline and three supporting subheadlines for a B2B SaaS product that automates expense reporting for finance teams. Details: The main headline should be under 10 words and communicate the primary value proposition: eliminating manual expense reconciliation. Each subheadline (25–40 words) should support a different pillar: speed, accuracy, and integration with existing accounting software. Audience: Finance Directors and CFOs at companies with 100–500 employees. Register: authoritative, outcome-focused, minimal jargon. Avoid the word "seamless." Examples: Style reference — Stripe's homepage copy: clear, specific, confident without being aggressive. Also reference Rippling's finance product messaging for the target audience register. Adjustments: If I say "more technical", introduce specific metrics (e.g., "reduces close time by 4 days"). If I say "simpler", strip each headline to its core claim with no qualifiers. If I say "try again", start from a completely different angle — consider leading with the problem rather than the solution.
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Adjustments component eliminates ambiguous feedback and accelerates iteration | Requires upfront thinking about your revision preferences before seeing the first output |
| Examples component communicates style more precisely than description alone | Less suited for analytical or research tasks where iteration is not the primary workflow |
| Beginner-friendly — four components are intuitive and easy to apply | Examples component can introduce unintended style bias if references are poorly chosen |
| Works across any domain where iteration is expected, not just creative writing |
Frequently Asked Questions
What does IDEA stand for in prompt engineering?
IDEA stands for Intent, Details, Examples, and Adjustments. It is a four-component framework designed for creative tasks, iterative work, and design briefs. Its defining feature is the Adjustments component, which builds a feedback loop directly into the initial prompt — telling the model how to respond when you request changes.
What makes IDEA different from other prompt frameworks?
Most prompt frameworks are designed to get the right answer on the first try. IDEA is designed for iterative work — where the first output is a starting point, not a final deliverable. The Adjustments component explicitly tells the model how to handle revision requests, making it ideal for creative collaboration where you refine output over multiple turns.
What should I include in the 'Adjustments' component?
Adjustments should tell the model your revision preferences and how to interpret feedback signals. For example: 'If I say shorter, reduce by at least 30%. If I say more formal, shift the register to match a Harvard Business Review article. If I say try again, produce a completely different approach rather than a slight variation.' The more specific your adjustment rules, the faster you converge on the result you want.
Can I use IDEA for non-creative tasks?
IDEA works for any task that benefits from iteration — not just creative writing. Code generation, UI copy, email templates, and marketing headlines all benefit from the IDEA structure because they are rarely perfect on the first attempt. The framework's iterative nature is its core advantage, regardless of the domain.
How detailed should the 'Details' component be?
Details should cover every specific requirement that is not captured by the Intent. Length, tone, format, technical constraints, brand guidelines, audience, and any explicit inclusions or exclusions all belong here. The Details component is where you prevent the model from making assumptions about things you actually have strong preferences about.
What is the difference between Examples and Details in IDEA?
Details are your requirements — what the output must do or be. Examples are references — things that illustrate the style, tone, or structure you are aiming for, even if the content is completely different. For instance, Details might say 'use a conversational tone', while Examples might link to or quote a specific piece of writing that embodies that tone better than any description could.
How many examples should I include in the Examples component?
One to three examples is typically sufficient. Too few and the model has insufficient signal about your preferences. Too many and the model may average across conflicting styles rather than applying a clear direction. If your examples vary significantly in style, note which aspect of each example you want the model to take inspiration from.