ThemeKnowledge & Systems
CardCard 24 of 66
Questions5 to explore

History

Story & background of the company

How an organization got here shapes how it behaves, and teams that do not know the history keep re-litigating decisions that were already made.

Company history is not nostalgia. It is context. Knowing why a process exists, why a product was built a certain way, or why a partnership formed helps people make better decisions now without starting from scratch every time.

The most valuable history is rarely in official announcements. It is in the stories: the pivot that saved the company, the customer who shaped the product, the failure that changed how the team operates. Those stories carry tacit knowledge that is hard to transfer any other way.

History does not need to be a comprehensive archive. A timeline of key moments, a set of founding stories, and a record of major decisions with the reasoning behind them will serve most organizations far better than a detailed chronicle nobody reads.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Founding story & key moments

How the organization started, who the early people were, and the moments that shaped its direction: pivots, crises, breakthroughs, and the decisions that defined what it became.

Major decisions & reasoning

The significant choices that changed direction, killed projects, or set strategy, and the thinking behind them at the time. This is the context that prevents the same debates from happening again.

Product & service evolution

How the offering has changed over time: what existed, what was discontinued, what was relaunched, and why. Especially useful for support, sales, and anyone building on what came before.

People & exits

Who founded the organization, who played key roles, and how leadership has changed. Notes on significant departures help preserve institutional knowledge that would otherwise disappear with them.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

What story about the early days would help a new person understand why the organization works the way it does today?
Which past decisions still shape current processes, even if the original reason is no longer obvious?
Are there product decisions, pivots, or failed experiments that carry lessons the current team has not formally documented?
Who in the organization holds the most institutional memory, and what happens when they leave?
What would a new person need to know about the company's history to avoid repeating a mistake the team already made?

Things to notice

History recorded only by founders risks becoming myth. Where possible, collect accounts from multiple people who were present for the same events.
Positive-only histories are not very useful. The failures, the near-misses, and the hard calls tend to carry more transferable lessons than the success stories.
History documents are often created once and never updated. Build in a trigger to add to the record when something significant happens, rather than waiting for a retrospective years later.