There is a particular tiredness in explaining your own business again — to a colleague, to a new helper, to an AI assistant that has forgotten what you told it last week. The work gets done each time, and none of the explaining is kept.
An assistant that remembers changes that. The first conversation is long, because you are building a record: what the business is, how you work, what a good result looks like. Keeping useful context gives later conversations a starting point, instead of requiring the same briefing again.
Memory is the part of delegation that compounds, and it deserves the same care as anything you hand over. This note is about what to write down, what to leave out, and how to keep the record true.
Memory is the context you choose to share
Memory is not a recording of everything you have ever said. It is the short list of facts, preferences, and formats you decided were worth keeping — the context you choose to share.
That definition matters for two reasons. The record stays small enough to read, and you decide what goes into it. In practice, it usually holds things like:
- What the business does and who it serves.
- How you like work delivered: tone, length, what leads.
- What to flag early and what to leave alone.
- Details that rarely change: names, terms, standing arrangements.
A record you can read is a record you can correct.
Write down what you would tell a new helper
The test for what belongs in memory is simple: what would you tell someone helping you for the first time?
You do not need a specification. A paragraph in plain words is enough. For example:
I run a small design studio. Most of my work is brand projects for restaurants and cafés. Client updates go out on Fridays and open with what shipped. Keep them under a page. If something is blocked, say so early — I would rather hear it on Wednesday than read it in the Friday summary.
That paragraph gives your assistant a useful starting point. You can refine the instructions as you review its work, rather than rebuilding the brief each time.
You are not recording everything. You are removing the explanations that keep coming back.
Keep the record current when something changes
Facts move. A project ends. A supplier changes. The way you want client updates written shifts with the work. A stale fact is worse than a missing one, because it looks like knowledge.
When something changes, say so plainly and ask for confirmation that the record has been updated. Then review it the way you would review notes left by a careful colleague. Try a monthly review as a starting point: ask what has been noted about your business, read the list, and request corrections to anything that is no longer true. Review sooner when important details change.
The record is only as useful as the last correction.
Decide what stays out of memory
Memory is a convenience, not a requirement. Nothing has to go into it.
Share what the work needs and no more. Financial accounts, credentials, and private matters belong in the places built to hold them, not in a conversation. If a detail is sensitive, leave it out of the record and provide it only for the task that needs it.
The aim is a record you would be comfortable reading aloud to the people who work with you. If a line fails that test, it does not belong in memory.
Convenience should never cost you control.
Check what your AI assistant has learned before relying on it
Treat a new record the way you treat a new helper. Verify before you depend on it.
- Ask what it knows about your business, and read the answer.
- Give it one small real task and read the result closely.
- Correct the record, not only the output. If a summary opens in the wrong place, fix the preference behind it — not just this week's draft.
Trust should come from what you have seen work, not from how certain something sounds.
Fixing the record once is cheaper than fixing the same output forever.
When memory meets the work that repeats
Memory is what makes the rest of the delegation lighter. A routine built on a remembered preference starts closer to right, and the instructions shrink instead of growing. Our note on turning one weekly chore into a routine covers building the routine itself; giving the work away once covers why remembered context matters when work repeats.
Describe the work once, keep the description, and let the schedule carry it.
Memory is the part that compounds.
What memory should never decide
An assistant that remembers your business is not one that decides for it. Pricing, hiring, a difficult conversation with a supplier — those stay with you. What moves off your plate is the remembering: the gathering of context that stands between you and the decision.
Nothing goes out under your name without your approval. Remembered context is preparation; acting on it stays yours.
You keep the judgment. The record keeps the details.
Start with one page of context
This week, write one page. What the business does, how you like work delivered, and what to flag early. Share it, read what is kept, and hand over one small task to see how much of the explaining you skip.
If you want to try that with Rilke, explore the personal AI assistant or compare the plans.
Start with a useful brief. Keep it current as the work changes.