Choose the AI context workflow that fits your work
An “AI second brain” can sound like one enormous system that must cover every project, person, and decision in your life. That is usually the wrong starting point. A useful system begins with one repeated situation where missing context creates friction.
Pick the pattern by the moment of use
Choose the point where you most often have to reconstruct background:
- Decision pattern: keep the goal, constraints, options, and reason for the final choice together.
- Project restart pattern: keep the current state, last decision, next action, and unresolved question ready for the next session.
- Client or stakeholder pattern: keep agreed goals and boundaries separate for each relationship, with sensitive details removed before any AI handoff.
- Research-to-draft pattern: keep source notes, working claims, open questions, and voice guidelines connected.
- Weekly planning pattern: bring current goals, fixed commitments, and unfinished decisions into one review.
These are not different products. They are different routes through the same Capture, Organize, Consult, Act loop.
Use one test before building
Ask: “What question do I repeatedly answer from memory?” Then collect only the notes that question needs. If the pattern does not improve a real handoff or decision, more structure will not rescue it.
Avoid combining personal, client, financial, and health context just because one vault can technically hold all of it. Different material can require different privacy boundaries. Choose what can be shared before choosing automation.
Compare the five AI context workflows
Use this table to choose by the question you need to answer, not by the amount of information you could collect.
| If you repeatedly need to… | Start with this pattern | Keep these fields | A successful first use looks like… |
|---|---|---|---|
| make a choice without reopening old debates | Decision | question, goal, constraints, options, decision, reason, review trigger | the next discussion starts with what changed |
| resume work after a gap | Project restart | outcome, current state, last decision, next action, blocker | you can name the next action in two minutes |
| prepare for a client or stakeholder conversation | Relationship | shared goal, agreed boundaries, open issue, next conversation | the brief excludes unrelated private history |
| turn research into a draft | Research-to-draft | sources, working claim, counterpoint, open question, voice rule | the draft cites the supplied sources and flags gaps |
| plan a week without losing important constraints | Weekly planning | current goals, fixed commitments, unfinished decisions, available capacity | the plan respects the commitments already made |
Do not start with two patterns “just in case.” Choose the row tied to a real recurring question. A week of use will show whether it deserves to grow.
Copy a one-pattern test card
The artifact below is deliberately smaller than a complete system. Fill it once, use it for one real question, and review the result.
# Pattern test
Repeated moment: [When do I reconstruct background?]
Pattern chosen: [Decision / Project restart / Relationship / Research-to-draft / Weekly planning]
Question this pattern must help answer:
- [One recurring question]
Minimum context:
- Current goal:
- Constraint:
- Last relevant decision:
- Open question or next action:
Privacy boundary:
- Give:
- Blur:
- Keep local:
After one week:
- What information changed the answer?
- What did I collect but never use?
- What was missing?
- Keep, revise, or stop this pattern:For example, the design studio would choose the Decision pattern for a pricing question. It would keep the goal of fewer, higher-value projects, the constraint protecting two long-standing clients, and the earlier failed blanket increase. It would not combine that brief with unrelated client correspondence or financial records.
Let the pattern expand from evidence
Run one pattern for a week. Notice which background was missing, which note went stale, and which step felt too slow. Adjust that part. A pattern earns another template or tool only when the same friction returns.
For a place to keep the notes, see the minimal Obsidian setup. For help moving material between tools, see the context toolkit.
Join the Starter Kit waitlist if you want one notification when the kit is ready.