Separate the first action from a task’s stopping point
Published · Updated · Sources checked 2026-11-06
Use a fictional announcement draft to separate the first visible action from enough for one session. Keep unfinished facts and restart notes clear.
A task can become easier to approach when its first visible action is separated from its session stopping point. The first action helps you begin without redesigning the entire task. The stopping point defines what “enough for this session” means, so an unfinished task does not have to look like a failure.
A fictional announcement task
Imagine Maya is drafting a short announcement for a fictional neighborhood library that will temporarily change its opening hours during a painting project. The final announcement will eventually need a date, two revised hours, and confirmation details. Maya does not have all of that information yet.
Instead of writing, *“Draft the library announcement,”* she separates the work into two practical checkpoints:
- First visible action: Open a blank note and type the heading, “Library opening-hour update.”
- Stopping point for this session: Reach a draft that includes a place for the new date, a place for both revised hours, and a visible note asking for confirmation.
The first action is deliberately small and visible. The stopping point is a separate checkpoint, not a promise that the announcement is complete.
Entering the public task fields
Maya can use the activity field for the broader task:
Draft a short announcement about temporary library opening-hour changes.
She can then use the smallest-action field for the concrete opening move:
Open a blank note and type: Library opening-hour update.
These are public task fields, so their use is optional. To select Focus on this step, Maya must enter both fields. She can also choose to plan entirely on paper.
When she selects Focus on this step, Lumahari displays the words from those fields. That gives Maya a compact way to distinguish *what to begin with* from *where this session may stop*. The activity remains useful context, while the smallest action stays concrete.
Drafting to the stopping point
Maya now writes a deliberately short draft:
Library opening-hour update
Our hours will change temporarily while painting work is underway.
New opening date: __________
Monday–Friday hours: __________
Saturday hours: __________
Check: confirm both schedules and the display date before sharing.
She has reached her session stopping point, but the announcement is not finished. Maya adds a clear incomplete-state note:
Incomplete: Add the confirmed date, replace both blank schedules, and verify the display details.
That note prevents the session draft from being mistaken for a ready-to-share announcement. It also separates the next pass from the current stopping point.
At this stage, Maya may select I did this step to acknowledge completion of the defined step. The displayed step was opening a note and typing a heading. She can acknowledge that action once it is done; the broader draft is a separate session result. It does not mean the fictional library announcement is ready for publication.
Using the optional timer
Maya can also work with the optional 2-, 5-, or 10-minute timer. She might choose five minutes, start the timer, and draft only the heading and incomplete placeholders. If she reaches her stopping point early, she can acknowledge the step and reset the timer for later use. If she needs to pause, the timer can be paused; it has no sound or notifications.
The timer is optional and does not need to determine the task structure. Maya’s stopping point remains a written checkpoint that she can understand after the timer ends. A timer session and a task session are related, but they are not necessarily the same length.
Parking temporary details
During the draft, Maya notices that the painting contractor’s name and the confirmation date may matter later, but neither is needed for the present stopping point. She can park those details in temporary notes:
Contractor name: check with facilities.
Confirmation date: add after checking the revised schedule.
Temporary parking notes give uncertain details a place without adding them to the active draft. If Maya selects Clear thoughts, the app asks for confirmation before removing the whole parking area. She should copy lasting details elsewhere before clearing it.
Entries clear on refresh or leaving, so Maya should copy any lasting notes elsewhere. The task starter keeps entries only in the current page’s memory. Refreshing or leaving clears them. This makes it important to distinguish disposable scratch work from information Maya wants to retain.
A clear restart note
When Maya returns, she does not need to reconstruct the whole task from memory. Her draft, stopping point and incomplete-state note belong in her own document, which she can consult later.
Before leaving, she can write:
Restart here: Open the draft, ask facilities for the confirmed date, replace both blank schedules, and remove the incomplete-state note only after checking every detail.
This restart note is concrete without pretending the remaining work is automatic. She must copy any relevant notes before refreshing or leaving. Once cleared, the temporary page cannot recover them.
Using the task fields
Enter one activity and one smallest action, up to 200 characters each, then select Focus on this step. Both inputs are required. Park a thought holds up to 3,000 characters. Clear thoughts removes that whole area after confirmation. Choose a different step lets you edit the current instruction; there is no task history.
The task starter keeps entries only in the current page’s memory. Refreshing or leaving clears them. Copy lasting notes elsewhere before leaving.
For a related next step, see how to break a small project into a next step and how to choose between two tasks and start one. Find more examples in the task initiation guide hub.
Sources
General information, not a diagnosis or personalized treatment advice.