Break a project into steps

Unit ID: AIT-M09-U01 Estimated active time: 15-20 minutes

The main idea

AI can help list steps, but real constraints come from you.

A generated step list is a reasonable generic sequence. It does not know who is on leave, which approval takes two weeks, or what failed last time.

Why this matters

The generic list is still useful — it catches steps you would have forgotten. It becomes dangerous only when it is treated as a plan rather than as a prompt for one.

Safe example

A course launch checklist needs content, review, upload, test, and communication steps.

Five phases. The one most often missing from a generated list is review, because it has no visible output.

Better working habit

Ask for phases, dependencies, and review points.

Dependencies are what turn a list into a plan. Without them every step looks equally ready to start.

What to watch for

Do not accept unrealistic timelines.

Generated estimates assume nobody is waiting on anyone. Most real delay is waiting.

Mini practice

Break a safe project into steps with dependencies.

Then mark every step that depends on someone outside your control.

Check yourself

Before moving on, answer:

• Which steps depend on people outside my control?
• Where are the review points, and do they have owners?
• Which constraint do I know about that the list does not?