Maya adds “Prepare for the team meeting” to Today. Then a message interrupts her. When she returns, the title reminds her about the meeting, but not what she had planned to bring.
The missing information is small: what this meeting needs to achieve, what is ready, and what she should do next. We will build that record inside one task. Maya and the meeting are illustrative examples; the note content is shown in full below.
A title captures the commitment
A title is enough to get the task out of Maya’s head. It is not yet enough to resume the preparation. She still needs to choose what progress to discuss, which product idea to share, and whether the agenda is ready.
She leaves the parent task untagged. At this point it is work to prepare, rather than a lasting topic that needs organizing.
Prepare for the team meeting
Write something, or press '/' for commands
Write what the next session needs
Maya gives the meeting a short purpose: progress, one useful idea, and clear next steps. The discussion section holds two questions the team should answer. These lines guide what belongs in the agenda.
She then adds three subtasks: review the week’s progress, prepare a product thought, and put together the agenda. The preparation now has a shape she can continue after another interruption. The note is a working record, so she updates it as the plan changes.
Prepare for the team meeting
Keep it focused: progress, one useful idea, and clear next steps.
Discussion notes
What moved forward this week? Where do we need a decision?
To prepare
Give a subtask its own reason to exist
“Review this week’s progress” and “Put together the agenda” have results Maya can check separately. If one needs a different day, she can schedule that subtask without moving the whole meeting task.
“Progress, one idea, next steps” is guidance for the meeting. It can stay as a sentence in the note. Creating a checkbox for every sentence would make the list harder to scan.
“Product thinking to share” needs room for an example and an explanation, so Maya opens that subtask and writes there. The parent keeps the overall preparation together; the child keeps the thinking with the piece of work it supports.
Keep the useful thought under a lasting topic
Her product thought is about asking new users to organize information before they have anything to organize. She records the friction, two things to try, and the idea behind them. This is enough to discuss; it does not claim that either change has been tested.
That note may help with later product decisions, so she adds Product under Areas. The agenda and progress check remain untagged. Later she can open Product and read the same note. She has a route back to the useful idea without having to remember which meeting it came from.
Product thinking to share
Make the next step obvious.
A useful product helps people move forward without having to figure out the interface first.
A small friction
We ask new users to organize everything before they have anything worth organizing.
What to try
- Let people start with one thing they need to do.
- Introduce structure when it becomes useful.
Clarity before more features.
Leave a restart point before closing
Before pausing, Maya writes: “Product thought ready; next, finish the agenda.” When she returns, she can open the remaining subtask and continue. Once the meeting preparation is done, she can complete it; the product note remains available by topic.
- Result: What should exist when this is done?
- Current state: What is ready, and where is the current version?
- Decision: What did I choose, and why?
- Open question: What answer is still missing?
- Next: What is the first useful step when I return?
Try this on one task you expect to interrupt. Omit any part you do not need. The test is whether you can return, understand the current state, and begin the next step without reconstructing the work.