A large goal looks like one task even though it contains research, decisions, dependencies, and different kinds of work. Splitting it into activity alone can create a busy list with no finish line.
The short answer
Work backward from the finished result to milestones, then forward from the nearest milestone to executable actions.
Use four levels
| Level | Question |
|---|---|
| Outcome | What will exist when the goal is complete? |
| Milestone | Which intermediate result proves movement? |
| Dependency | What input, decision, or resource is required? |
| Action | What can begin in one block? |
Decompose in five steps
- Define completion and scope boundaries.
- Choose three to five stage results.
- Identify dependencies between stages.
- Expand only the nearest stage into actions.
- Select one action with no unresolved prerequisite.
For a portfolio, the outcome may be four published cases. The first milestone is selecting projects; the first action is listing six candidates and the evidence available for each.
Write tasks with a finish line
Weak task names describe a topic: “website,” “research,” or “presentation.” A useful action begins with a verb and ends in an observable state: “compare three hosting options against cost and support criteria” or “draft the opening five slides for review.”
If an action still feels impossible to start, check for a hidden decision or missing input. “Write the proposal” may actually require choosing an audience, finding last quarter’s numbers, and agreeing on the offer. Those are dependencies, not signs that you need more motivation.
Estimate by uncertainty as well as size
Two tasks that both take an hour may have very different risks. A familiar edit is predictable; a new integration may uncover additional work. Mark uncertain actions and test them early. The goal is not a perfect estimate but earlier information about the route.
You can use three simple labels:
- ready: inputs and completion criteria are clear;
- blocked: another decision or resource is required;
- discovery: the action exists to learn what comes next.
This keeps discovery work from masquerading as a firm delivery commitment.
Avoid false detail
Do not map every future action before early uncertainty is resolved. Detail the next stage, complete or test it, and update the route with evidence.
Avoid breaking work into fragments so small that the list becomes harder to manage than the project. “Open the document” may help as a temporary starting cue, but it is not usually a meaningful project task. Stop decomposing when an action can fit a realistic work block and has a clear completion rule.
Use goal vs. action to keep deliverables and behaviors distinct, and starting a hard task when the next action still feels too expensive.
How to use Flamy
Add current actions, not the entire project tree. Use XP for a real completion rule and replace the task when the next milestone changes.
For multi-step projects, keep the milestone map in your project notes and move only the active actions into the daily system. This preserves context without turning today’s list into a warehouse of future work.
Find the first step today
- State the finished result.
- Choose the nearest milestone.
- Name its dependencies.
- Write one executable action.
- Schedule its first block.