Founders and operators build a great deal of knowledge that never gets written down. The decisions, the reasoning, and the results live in email threads, in memory, and in the minds of people who may later leave. When you start a new venture, or advise one, that experience is far more useful if it is captured in a form you can draw on.
This checklist explains how to document operating experience as you gain it. It covers what is worth recording, how to capture it while it is fresh, how to keep the record lawful and confidential, and how to turn notes into something you can actually use.
Why documenting experience matters
Experience fades faster than people expect. The context around a decision disappears within months, and you are left with an outcome and no memory of why it happened. A record made at the time preserves the reasoning, which is the part that transfers to a new venture.
A written record also strengthens your public profile and your ability to explain your work. When you can describe a decision, the constraints you faced, and what followed, you communicate at a level that a list of achievements never reaches.
A record also survives the company. Founders move on, teams dissolve, and the files that remain are often incomplete. Keeping your own notes means the learning stays with you regardless of what happens to the business.
What counts as operating experience
Operating experience is broader than a job title. It includes the decisions you made, the systems you built, the people you hired and developed, and the problems you worked through. It also includes the things that did not work.
A useful record captures several categories:
- Decisions: what you chose, what you rejected, and the reasoning behind the choice.
- Context: the constraints at the time, such as budget, team size, or market conditions.
- Actions: what you did, and who else was involved.
- Results: what happened, described honestly and with the timeframe.
- Lessons: what you would do differently, and what you would repeat.
Not every decision deserves an entry. Focus on the ones that changed something: a pricing change, a hire, a product direction, a partnership, or a process that stuck.
Capturing decisions while they are fresh
The best moment to write is shortly after the decision, while the reasoning is still clear. Waiting until the end of a project means reconstructing why you acted, which invites hindsight and flattery.
Build a light habit rather than a large one. A few minutes at the end of a significant week is enough to capture the decisions that mattered. Keep the entry short: the situation, the choice, the reasoning, and what you expect to happen.
A simple entry template
A small, repeatable template makes the habit easier. For each entry, note the date, the decision, the options you considered, the reason you chose, and the result so far. Add a line for what you would tell your future self about it. This last line is often the most valuable when you return to the notes later.
Recording evidence and outcomes
Where you can, attach the evidence that supports your recollection. This might be a document you produced, a metric before and after, or a short note from a colleague about what changed. Evidence turns a memory into something you can rely on and, where appropriate, share.
Describe outcomes carefully. Separate the change you caused from the changes that happened around you, and note the timeframe. Overstated results are easy to write once and hard to correct later, and a record built on exaggeration is worse than no record at all.
Numbers that are confidential should be stored carefully and marked as such. You may be able to describe the direction of a change in public even when the figure itself cannot be shared.
Keeping the record confidential and lawful
A private operating record will contain sensitive material. Treat it accordingly. Store it somewhere secure, and keep client, customer, and employee information out of any version you might share.
Respect the agreements you signed. Confidentiality and non-disclosure terms usually survive the end of an engagement, and they often cover strategy and figures. Before reusing any detail in public, check what your agreement allows, and where the terms are unclear, seek advice rather than assuming.
Employee information deserves particular care. Notes about individuals should be factual, relevant, and stored lawfully under data protection rules. If you are unsure how a record should be handled, consult the relevant official guidance or a qualified adviser.
Turning notes into a usable file
A pile of entries is only useful if you can find what you need. Keep your record organised by venture and by theme, so you can pull together the experience that fits a new situation.
When you begin a new venture, review the relevant entries and pull out the patterns: the decisions that worked, the constraints that recurred, and the mistakes that were avoidable. This review turns scattered notes into judgement you can apply. You can also draw on it when you write publicly or advise others, provided you respect confidentiality.
Contributing to BGTC Voice
BGTC Voice publishes practical writing from founders and operators who want to explain how they build. If you have a method for documenting your operating experience, or a way of turning old notes into useful judgement, an article on the approach is a useful contribution. Submissions should describe the method and keep any confidential figures, names, or company details out of the text.
Practical checklist
- [ ] Record significant decisions shortly after you make them.
- [ ] Note the options you rejected and the reasoning behind the choice.
- [ ] Capture the constraints that shaped the decision at the time.
- [ ] Attach the evidence that supports your recollection of events.
- [ ] Describe outcomes honestly, separating your action from outside change.
- [ ] Keep confidential figures and personal data out of shared versions.
- [ ] Check what your agreements allow before reusing any detail.
- [ ] Organise entries by venture and theme so you can find them later.