How to Plan a Project With AI

Quick Answer

Define the goal and constraints first, then use AI to decompose it into phases, tasks, and milestones. Use AI again to write the project brief, timeline narrative, and risk register. Review everything as the domain expert, AI gives you structure, you provide judgment.

What This Workflow Helps You Do

• Break large goals into manageable, sequenced tasks
• Identify risks and dependencies before they become problems
• Write project briefs and status documents quickly

Step-by-Step Process

Step 1: Define project parameters

Before prompting AI, clarify:

• Goal: What does success look like at the end?
• Deadline: Hard deadline or target date?
• Team: Who is involved and what are their roles?
• Resources: Budget, tools, time available per person?
• Constraints: What can’t change? What’s already decided?
• Known risks: What could go wrong?

Step 2: Break the project into phases and tasks

Break down the following project into phases, milestones, and tasks.

Project: [describe the project in 2–3 sentences]
Goal: [what success looks like]
Deadline: [date]
Team: [list the people involved and their roles]
Known constraints: [budget, timeline, tool, or people constraints]

Create a project plan with:
- 3–5 phases with names and purpose
- Key milestones (decisions or deliverables that mark progress)
- 4–8 tasks per phase with brief descriptions
- Suggested order and dependencies (which tasks must come before others)
- Estimated time for each task (rough, in hours or days)

Flag any tasks where I should pressure-test the timeline — places where things commonly take longer than expected.

Step 3: Identify risks and dependencies

Review this project plan and identify risks and dependencies: [paste your plan]

1. What are the 5 biggest risks to this project completing on time?
2. What dependencies exist (task B can't start until task A is done)?
3. What assumptions is this plan making that might not hold?
4. What decisions need to be made early that we might be tempted to delay?
5. What's the single most likely reason this project slips?

For each risk, suggest a simple mitigation approach.

Step 4: Write the project brief

Write a project brief for the following project.

Project name: [name]
Goal: [what we're doing and why]
Scope (included): [what's in scope]
Out of scope: [what we're explicitly not doing]
Key stakeholders: [names and roles]
Timeline: [start date to deadline, key milestones]
Resources: [team, budget, tools]
Success criteria: [how we'll know it's done and done well]
Open decisions: [anything not yet resolved]

Format as a one-page brief that a stakeholder who wasn't in the planning meeting could read and understand. Plain language, no jargon.

Step 5: Create a status update template

Create a weekly project status update template for [project name].

This update goes to: [stakeholders — e.g., leadership team, client, department head]
The project runs [start] to [end date].

Template should include:
- Status indicator (on track / at risk / delayed)
- Progress this week (what moved forward)
- Planned for next week
- Blockers or risks that need attention
- Decisions needed from stakeholders (if any)

Keep it to one page maximum. This should take 10 minutes to fill in each week.

Common Mistakes

Asking AI for tasks before defining the goal clearly. AI will generate a task list that looks complete but may solve the wrong problem. Always start with a clear, specific goal.

Accepting AI timeline estimates at face value. AI generates plausible time estimates that often underestimate complexity. Pressure-test every estimate against your experience and add buffer.

Building a plan and then not reviewing it with the team. A solo-planned project that the team sees for the first time in kickoff is missing a review step. Use AI to create the draft, use the team to validate it.