FinishTrax guide
Why nested tasks can make a large project easier to read
Nested tasks show which small actions belong to which result. They are useful when one task is really a project, but they are unnecessary when a short flat list already explains the work.
Short answer: Use nesting when the relationship between tasks matters. Keep a flat list when order and grouping do not matter. The goal is clearer work, not the deepest possible outline.
A parent task answers “why?”
“Request the invoice” is easier to understand when it sits under “Submit the tax return.” The parent gives the action context. The child gives the parent a next step.
Three useful reasons to nest
Keep context
A small action stays connected to the result that makes it important.
Hide detail
Close a branch when you only need the project name, then open it when you are ready to work.
See honest progress
FinishTrax calculates parent progress from completed children instead of asking you to guess a percentage.
When not to add another level
- The next action is already obvious.
- The list is short and all items belong together.
- Adding a level would only repeat the same words.
- You are outlining to avoid starting, not to remove uncertainty.
FinishTrax allows unlimited depth, but unlimited is a capability, not a target. Stop breaking work down when the next useful action is clear enough to begin.
A simple way to build the outline
- Write the result as the parent task.
- Add the few actions that must happen next.
- Break down only the child that still feels too large or unclear.
- Complete work and let progress roll up.
- Change the structure when the project changes.