Founder decision journal: An easy seven-field template

Why is a founder’s memory not enough?

A failed campaign is often remembered as “I could see a problem from the start.” Yet before launch, the whole team may have been highly confident. Without a record made at the time of the decision, hindsight is easily shaped by the final result. It becomes difficult to know whether the business lacked data, reasoned incorrectly, or encountered a new condition.

The journal is not an executive’s self-defense document. It is a starting point for an evidence-based conversation. Keep it brief but sufficient for a colleague to understand why the option was chosen and when it should be reviewed.

Which decisions are worth recording?

Prioritize decisions that change commitments: opening a new channel, discontinuing a product, allocating resources, changing customer service, or running a significantly costly experiment. Tasks with clear procedures can use the existing task-management system without a separate record.

The level of detail should reflect reversibility and consequences. A small experiment may need only a few lines. A choice with lasting impact requires more data, participants, and implementation conditions. This framework does not replace specialist approval processes or mandatory records where applicable.

Decision journal template: Seven fields

Write the first version before implementation and retain the original when updating. If conditions change, add a dated update rather than rewriting the record to make it look as though you predicted correctly all along.

Hypothetical scenario: Testing a new partner channel

A business wants to test customer referrals from a partner for two weeks. Its initial assumptions are that the customers will be a good fit and the team can handle additional work without affecting existing customers. The record should state the test scope, handler, resource limits, and how customers from the channel will be identified.

The business decides to reduce a less urgent activity to free up time. Review triggers include delayed service for existing customers or insufficient information to advise new prospects. After two weeks, the team records not just the number of prospects received, but also qualified prospects, service time, costs, and unexpected issues.

If prospects are few but well matched, outreach may need improvement. If prospects are numerous but resource demands exceed the plan, immediate expansion may not be the best choice. The lesson lies in which assumptions were tested, not just the total number.

Separate decision quality from outcomes

Assess the process using what could be known at the time: were enough options considered, were assumptions supported, were trade-offs clear, and were review conditions set? Then assess the outcome to update understanding. The two steps are related but not identical.

An inadequately checked option may happen to produce a good outcome. Conversely, a carefully bounded experiment can fail because the market changes. Do not use this distinction to evade responsibility; the owner still needs to explain deviations and improve the process.

Use the record in a review meeting

Choose a few high-impact decisions, read the original record, and ask: which data was useful, which assumptions were wrong, which conditions emerged later, and what should we check earlier next time? End with a specific change: add an input criterion, narrow an experiment, or clarify approval authority.

Avoid turning the meeting into a contest to prove who was right. If people fear blame simply for expressing uncertainty, records will become safe but uninformative. Leaders need to encourage honest reporting while maintaining accountability for agreed commitments.

Start with one decision this week

Choose the nearest decision requiring resources, use the seven-field template, and schedule a review. No new software is needed: a document shared with those involved is enough to start. Avoid placing sensitive customer or employee information in an unnecessarily widely shared record.

After several uses, check whether the journal improves subsequent decisions. If it is written but never reread, shorten it and add review to the management meeting. The ultimate purpose is learning from decisions, not creating more documents.

Suggested actions