Claude as a Thinking and Planning Partner

Lesson 3: Building Multi-Step Plans Through Structured Conversation

Lesson Objectives

By the end of this lesson, students should be able to:

  • Use multi-turn conversation to build a plan incrementally
  • Apply structured decomposition to break complex goals into phases
  • Ask Claude to identify risks and gaps in a plan before finalizing it

Lesson Content

Planning is a conversation, not a single prompt.

Most useful plans are not produced in a single prompt. They emerge through an iterative conversation: you establish the goal, Claude proposes a structure, you refine the scope, Claude fills in the phases, you identify risks, Claude builds mitigations. Each turn builds on the last.

This is the natural workflow of professional planning – you do not expect to write a project plan in one sitting. Use Claude the same way: as a thinking partner you work with across multiple turns.

The structured decomposition technique.

For complex goals, start by asking Claude to decompose the goal into major phases or components. Do not ask it to write the full plan immediately. Ask it to show you the structure first.

Example:

I need to build a launch plan for a new internal software tool at a 200-person company. The tool will replace our current spreadsheet-based expense tracking system. Before writing the full plan, give me an outline of the major phases you would organize this into, and flag any questions you have about our situation that would change the structure.

Review the structure. Correct what is wrong. Add missing phases. Then ask Claude to build out each phase in depth – one at a time.

Progressive refinement.

After each phase is drafted, ask review questions:

  • "What assumptions does this phase make that I should verify?"
  • "What could go wrong in this phase that isn't addressed?"
  • "Is there a dependency between this phase and phase three that we haven't accounted for?"
  • "What would a skeptical stakeholder say is missing from this phase?"

These questions build a plan that has been actively pressure-tested rather than passively generated.

Using Claude as a project risk spotter.

After building a plan, submit it back to Claude with a direct request: "Review this plan and identify the top five risks that could cause it to fail. For each risk, rate the likelihood (High/Medium/Low) and suggest one mitigation." This adversarial review often catches things you cannot see because you are too close to the plan.

Maintaining continuity across a long planning session.

In a long planning conversation, periodically ask Claude to summarize what has been decided: "Summarize the plan as it stands now, including any decisions we've made and any open questions." This gives you a running record and helps you catch if Claude has drifted from earlier decisions.

Enroll to continue this lesson.

The preview above shows the lesson objectives and opening lesson content. Enroll to view the full lesson, complete the practice work, and take the lesson quiz.

Log In / Create Account
Back to Course