Notes are often where a project starts and where its context gets lost. The brief sits in one place, the spreadsheet in another, and the next action somewhere in a conversation. A useful working note brings those pieces close enough to think with.
Give the page a clear purpose
Start with a sentence that explains what the note is for. Add the question you are trying to answer, the decision you need to make or the outcome you are working toward. This gives every section that follows a reason to exist.
For a launch plan, you might keep four sections: the brief, source material, open questions and next steps. Leave room for the page to change as you learn. A note should support the work rather than become another structure to maintain.
Keep working files close
LumenNotes can bring documents and other working material into the page. Use a reference to the spreadsheet or file when you need the underlying work to remain editable, rather than pasting a screenshot that will become outdated.
Keep the context around the file short and useful. Explain what the reader should notice, which assumptions are still open and which version the team should use. A file can hold the numbers; the note can explain why they matter.
- Put the current brief near the top.
- Link the source behind an important claim.
- Keep a clear distinction between a question and a decision.
- Give each next step an owner when the work is shared.
Delegate a bounded piece of work
When a section needs research, analysis or a first draft, describe that specific job to an agent. Give it the relevant material and tell it what kind of result belongs back in the note.
Using this launch brief and the linked planning sheet, draft a short risks section. Separate confirmed issues from assumptions. Include the source for each confirmed issue. Leave the existing note unchanged until I review the draft.Continue writing while the task runs. Review the returned result before adding it to the page. An agent’s proposed wording should remain distinguishable from a decision you have actually made.
Close the loop after a meeting
If you use a transcript, turn it into a short record of decisions, open questions and owners. Check the important points against the source before assigning work. Transcription is a network-backed feature, so review the recording and data-sharing requirements for your situation.
At the end of the session, update the next steps and remove instructions that no longer apply. Keep the sources available without letting them overwhelm the current plan.
The result should be a page you can return to tomorrow and immediately continue from. For the wider project structure around that page, see A space for every project.
