The record
Keep the reasoning when the people change
Documents preserve the result of a decision more easily than its reasoning. What this means for handovers, business memory and the next person or agent doing the work.
The next person needs to know why
A handover can contain every current document and still leave the next person poorly prepared. The agreement shows the final terms, but not necessarily why a concession was made. The procedure describes what to do, but may leave out the exception that explains a customer’s arrangement.
The missing knowledge often remains with someone who was part of the discussion. They can explain which options were rejected, what constraint mattered and what would need to change before the decision should be reconsidered.
At Orcinta, we see this as a continuity problem. A business should be able to keep using the reasoning behind its work as people change roles and responsibilities. Retaining access to a folder is only part of that job.
Connect the decision to the records behind it
A useful account of a decision brings together the proposal, the evidence considered, the person who decided and the outcome. It also connects that account to the work it still affects. This gives a new colleague a way to understand both the current position and the reason it exists.
Atlassian’s decision-making guidance explicitly recommends preserving the final decision so future teams can understand how and why it was reached. The lesson we draw is that a decision becomes more reusable when its explanation remains attached to it.
The business should not have to rewrite all its history in a new system to achieve this. Agreements, messages and recorded approvals already contain much of the background. The opportunity is to connect those records, surface unresolved questions and keep the explanation current.
Sources: [1]
Let new knowledge improve the picture without rewriting the past
Business memory has to handle correction as well as accumulation. A new document can establish that an assumption was wrong. A later agreement can replace earlier terms. People need the current answer, but they may also need to understand a decision made before the update arrived.
Martin Fowler’s explanation of bitemporal history separates what was true in the world from what the system knew at a particular time. The business value is straightforward: later information should improve today’s understanding without making yesterday’s decision appear to have used evidence that was unavailable.
This matters during a handover and during a review. A colleague asking why a decision was made needs the reasoning available then. An auditor examining it needs a faithful history. An agent acting now needs the current terms. These are different questions about the same business record.
Sources: [2]
Useful memory becomes more valuable as work continues
Each new decision can add context to the next one. A supplier’s response clarifies an earlier constraint. A completed action establishes an outcome. A customer update changes which commitment needs attention. Over time, the business has less background to reconstruct from scratch.
This is what we mean when we say Orcinta grows with the business. The value comes from a connected history of real work, rather than a collection that is simply larger. New evidence should make the relationships, exceptions and reasons easier to understand.
Access remains part of that usefulness. A person or agent should receive the knowledge they are authorized to use. A better memory does not mean every colleague can inspect every source.
A good handover then becomes an introduction to the current responsibility, with the relevant history already available. The next person can spend more time deciding what to do and less time finding someone who remembers why things are this way.
A business keeps more of its knowledge when the reasons remain connected to the work.
Sources and further reading
- 1DACI decision-making framework
Atlassian Team Playbook
- 2Bitemporal History
Martin Fowler, April 2021