Note-taking method
Best GTD for Consultants
Getting Things Done — a workflow for capturing and processing tasks. For consultants, the working week is context-switching across clients with no bridge between engagements. The rest of this page is the method, cut for that week.
By tentus team · Updated 2026-09-20
What GTD actually asks of you
Get every commitment out of your head and into one trusted inbox, then decide the very next physical action for each.
Lists are organized by the verb — call, draft, review — never by topic. The non-negotiable part is the review: without it the lists rot into noise within two weeks.
How consultants put it to work
- 1
Client contexts that separate cleanly
Keep an explicit index for each engagement and check the source of every item before a handoff. Labels and linked notes do not enforce client isolation inside a workspace. Review access and remove unrelated client material before sharing.
- 2
Deliverables linked to their findings
Every number in the deck traces back to the interview or analysis it came from. When a client's CFO challenges a figure, the trail is one link, not an afternoon.
- 3
Patterns across engagements
Anonymized, the same problem appearing at three clients is a practice asset. Connections across client contexts are where the repeatable insight — and the next productized offer — hides.
The capture habit, the linking, and the retrieval are the parts tentus automates — gtd without the daily upkeep.
Try it with tentus
tentus makes GTD practical for consultants. Capture, link, and retrieve without the busywork.
Other methods worth trying
Zettelkasten
A slip-box method for connecting atomic ideas into a web of knowledge.
PARA Method
Organize information by Projects, Areas, Resources, and Archives.
Atomic Notes
One idea per note, linked to others through context.
Progressive Summarization
Layer summaries on top of captured content as you revisit it.
GTD for other roles
Product Managers
juggling research, specs, stakeholder feedback, and launch plans across multiple tools.
Software Engineers
losing context between code reviews, incident postmortems, and technical research.
Designers
scattered moodboards, design critiques, and research that never gets referenced again.
Researchers
drowning in PDFs and citations with no way to connect findings across projects.