Break Down Complex Tasks

You ask ChatGPT for a complete marketing strategy in a single prompt. The response arrives: long, well-written, and perfectly unusable. Each section gets four lines of generalities. The problem isn’t the model; it’s the command. You’re asking it to do in one go what requires ten distinct steps, several of which depend on the previous ones. Knowing how to break down work before handing it off to AI is exactly the skill that separates intermediate users from experts.

Why a single question isn’t enough

OpenAI’s help center offers simple advice: if your task is complex, break it into smaller, targeted prompts and treat prompting as a conversation. When you stack five objectives into a single request, the response risks skimming all of them instead of deep-diving into one. By breaking it down, you get a detailed result at every step and, crucially, you keep control over the work’s direction. Think of a construction project: no one asks an architect to design the plans, choose the materials, and start construction in the same breath. Each step builds on the previous one and gets validated before moving to the next.

The method comes down to four moves. First, define the final deliverable precisely. Then, list the sub-deliverables that make it up. Next, order them by dependency so you know what must be produced before what. Finally, turn each step into a dedicated prompt that explicitly reuses results from earlier steps.

A business plan, step by step

Instead of “Write a business plan for my SaaS,” which will yield ten pages of generalities, start with the ground truth: the market. This first response serves as the factual foundation for everything else, and you can correct it while the cost of correction is still zero.

You are a market analyst specializing in B2B SaaS.

Analyze the market for payroll management tools for French SMEs
(10-250 employees). Cover:
1. Market size and estimated growth
2. Key players and estimated market shares
3. Key trends (3-5)
4. Barriers to entry
5. Identified opportunities

Format: One paragraph per point, with quantitative data where possible.

Once you’ve read and amended this analysis, positioning follows naturally. Note the first sentence of the next prompt: it explicitly ties the work to what came before. This prevents the model from starting with a blank page and serving up generic positioning unrelated to the market you just described.

Based on the market analysis you just produced, define our
strategic positioning.

Our product: An automated payroll solution with integrated AI
that reduces processing time by 70%.

Define:
1. Priority target segment (and why)
2. Unique value proposition (one sentence)
3. Positioning relative to the 3 main competitors
4. Key messages (3 maximum)

The business model comes third, not earlier: you can’t set a price before knowing who you’re selling to and who you’re fighting against.

Consistent with the defined positioning, build the business model.

Define:
1. Pricing structure (plans and prices)
2. Estimated main costs
3. Revenue projection over 3 years (conservative assumptions)
4. Estimated break-even point
5. Key metrics to track

Format: Quantitative tables with explicit assumptions.

The sales strategy, operational plan, and detailed financial plan follow the same logic: each in its own prompt, each opening with a reminder of what was decided before.

Ask for the outline before the content

A simple variation saves hours of rework: request the outline first, validate it, and only then ask for the writing. The example below concerns an onboarding guide, but the mechanics apply to any long document—technical memo, white paper, product documentation.

Prompt 1:
I need to write a complete guide on onboarding new employees
for our company (150 employees, tech sector, fully remote).
Propose a detailed outline with chapters, sub-chapters, and the
key content for each section. Do not write the guide, just the outline.

Prompt 2 (after validating the outline):
The outline is approved. Now write Chapter 1: "Before Day One"
following the outline. 800 words, welcoming and practical tone.

Prompt 3:
Excellent. Now Chapter 2: "The First Week"...

Correcting an outline takes two minutes; correcting twenty pages of already-written text takes two hours, and you’ll often end up keeping mediocre text rather than starting over. That’s the whole point of placing the checkpoint before the writing effort, where changing your mind is still free.

What chains together and what runs in parallel

Not all sub-tasks follow one another. A chain like market analysis -> positioning -> pricing -> financial plan is strictly sequential: each link consumes the previous one, and skipping a step makes the next arbitrary. However, writing product descriptions, drafting emails for a nurturing sequence, and preparing social media visuals are three independent tasks. You can handle them in three separate conversations opened in parallel while you attend to other things. Spotting dependencies tells you where you must wait and where you can move forward simultaneously—that’s very often where you save the most time on a project.

Assign a different role to each step

When a project spans several disciplines, switch experts at each link rather than letting a generic assistant handle the whole chain. You don’t write a PRD with the same lens you use to produce a technical estimate, and the launch plan even less so: the vocabulary, priorities, and even the questions asked differ. The breakdown below passes the same project through four pairs of hands, each inheriting the work of the previous ones.

Project: Launch a new feature for our SaaS product.

Step 1 (Product Manager):
You are a senior PM. Write the PRD (Product Requirements Document) for
the automated reporting feature...

Step 2 (UX Designer):
You are a UX designer. Based on this PRD, propose the user flows
and text-based wireframes for the main screens...

Step 3 (Developer):
You are a tech lead. Based on the PRD and wireframes, estimate
the development effort and propose a technical architecture...

Step 4 (Marketer):
You are a product marketing manager. Based on the PRD, write the launch
plan (messaging, channels, timeline)...

Your turn

Map out a real project. Take a real project you need to lead and have it mapped out before writing a single line of content.

My project: [DESCRIBE YOUR PROJECT]

Help me break this project down into distinct steps.
For each step, indicate:
1. The step's objective
2. Necessary information (input)
3. The deliverable produced (output)
4. Dependencies with other steps

Then propose an optimal execution order.

This plan becomes your roadmap: one dedicated prompt per step. Then watch for three pitfalls during execution. If a sub-task produces a very long, general response, it’s likely still decomposable, and you’re falling back into the original trap. If coherence is lost from one step to the next—a target segment changing mid-stream, a tone drifting—it means you forgot to summarize prior decisions at the top of the new prompt. And if you chain steps without ever rereading, you sacrifice the intermediate validation point, which is the main benefit of the entire method.

Official sources: How do I create a good prompt for an AI model? (OpenAI help center) · Prompting (ChatGPT documentation)

Key takeaways

• Break complex tasks into sub-tasks handled and validated one by one
• Ask for the outline before execution: correcting an outline costs far less than rewriting text
• Identify dependencies to know what chains together and what runs in parallel
• Summarize decisions from previous steps at the top of each new prompt
• For long projects, ChatGPT Work can chain steps, provided you ask for a plan and keep control over submissions