FREE TIER · OPEN ACCESS ⏱ 12 mins·Orientation

Breaking Big Projects into Small Runs

How do you turn an overwhelming project into a sequence of small, testable actions?

Learn the six core stages: Task, Source, Work, Result, Check, and Return. Choose one small personal task, write a stopping test that checks both format and usefulness to your reader, and save your initial Return Card.

Before you start

Pick one small task from your current work that you can finish in under twenty minutes.

Why Big Prompts Fail

When you start a project with an AI assistant, typing a broad prompt is tempting. You might ask for a full marketing plan, a new company website, or a complete career transition strategy. The model responds with pages of smooth text. However, when you inspect the draft, you find that none of it matches your specific numbers, real clients, or true schedule.

Fixing a bloated draft takes more time than writing the text by hand. You get better results when you break your project into small runs that produce one clear file at a time.

The Six Stages of a Working Run

Every run follows six steps:

Task: Name the reader, the exact file you will create, and the test that tells you when you are done.
Source: Collect only the real files, notes, or message threads needed for this single step.
Work: Give the model clear instructions and run the draft.
Result: Review the raw output before you edit or paste it anywhere.
Check: Test the output against your source notes and your stopping test.
Return: Save your final file, write down what you decided, and set your next step.

Worked Example: Planning a Focused Run

Here is how an operations manager plans a twenty-minute run instead of asking for a whole project at once.

Task: Create a three-point checklist for onboarding a new freelance designer.
Recipient: Sarah, lead project manager.
Deliverable: A plain text file named designer_onboarding.txt.
Stopping test: The checklist covers account access, project files, and time tracking, fits on half a page, and gives Sarah exact login steps she can paste directly into her welcome email without editing.
Source: An email thread from the last hire and the company software list.
Work: Ask the tool to turn those two sources into three ordered steps.
Result: Inspect the draft to ensure it mentions only tools the company actually uses.
Check: Confirm that software login links match company accounts and that the instructions give Sarah immediate next actions.
Return: Save designer_onboarding.txt into the team folder and log the completion.

By defining both the shape of the file and its practical use for the reader before writing any prompt, the manager knows immediately whether the output succeeds.

Try it

Set up your Return Card for one personal task you want to finish today.

You can keep this card in a local project folder on your computer (such as my-project/return_card.txt) or type it into the form fields at the web page /courses/workspace. Note that /courses/workspace is a web form that stores your text entries in your browser, not a filesystem editor that saves files to your disk.

If working locally on your computer, create a dedicated folder for your personal project (for example, mkdir my-project) and open a new file named return_card.txt. If using the web workspace, open the Task stage in the workspace. The workspace opens Task. Scroll below the map to Task draft and notes. That is where your brief goes.
Fill in these four lines for your personal task as one brief in that text area (or in your local file):

Recipient: [Name or role of the actual person who will read or use this]
Deliverable: [Exact file name and format you will make, e.g., summary.txt]
Limit: [Measurable size constraint, e.g., under 200 words or 3 bullet points]
Stopping Test: [What the recipient can immediately do with this file that proves it worked]

Save your local file, or click Save a version in the web workspace. Return to this lesson, then reopen your Task notes. Confirm that all four lines are still there. If working locally, close and reopen my-project/return_card.txt instead.

Check your attempt

Check your Return Card against these three points:

Is your deliverable a single, specific file name (like client_update.txt or status_brief.md) rather than an entire project?
Does your limit give an exact boundary (like 'under 200 words' or '3 numbered steps')?
Does your stopping test name a concrete use for the recipient (such as 'Sarah can paste step 1 directly into Slack without rewriting') rather than just a word count?

Try a different case

Choose a separate task from a past project that ran over schedule. In your local practice folder, create practice_card.txt. Write down the recipient, deliverable file name, limit, and a stopping test that ties the output to the reader's immediate next action within a 15-minute run.

Check this attempt

Review your practice_card.txt. Can someone else read your stopping test and verify both the size limit and the reader's next action within ten seconds? If the test relies on vague phrases like 'clear' or 'good quality', replace them with an observable action the reader can take upon opening the file.

Save your work

A saved return_card.txt (or saved entry in /courses/workspace) containing a named recipient, a concrete deliverable file name, a measurable limit, and a test tied to the reader's next action.

If your Return Card has a concrete deliverable and an actionable stopping test, proceed to lesson A1 to gather your real source text. If your stopping test only checks word length without reader usefulness, revise the test before moving forward.

Apply in Your work → All lessons