In a client project, decisions don't necessarily disappear. What often disappears is the reason they were taken.
A few months later, we find the final document, the report, or the email sent to the client. On the other hand, it becomes more difficult to answer simple questions precisely: What options were considered? Why was one of them ruled out? What level of risk was accepted? What information tipped the scales in the decision?
Save the history of decisions related to a client project involves maintaining this approach with the case, without turning every assignment into an administrative procedure.
A single decision provides little information
Write:
«Option B Selected»
allows you to see the result.
But this information quickly becomes insufficient when the context is missing.
Let's consider a decision made during a mission:
«We're keeping our current service provider.»
Six months later, this statement no longer makes it clear whether that choice was motivated by price, the timeline, a contractual issue, the lack of a credible alternative, or simply a temporary decision.
A useful decision must therefore offer more than just its outcome.
The goal is not to document every discussion. It is to preserve the elements that will make it possible to understand the reasoning again once the details are no longer fresh in my memory.
What to Keep on File with a Decision
For a history to remain usable, a key decision should be able to reproduce at least the following:
- the problem or question to be solved; ;
- the context at the time of the decision; ;
- the main options considered; ;
- the option selected; ;
- the reasons for the choice; ;
- the alternatives that were ruled out and, where relevant, why; ;
- the identified risks or consequences; ;
- the documents, notes, or reports used as sources; ;
- the date of the decision and its connection to the project.
This is usually enough to understand a decision without having to reread the entire case file.
A record of decisions is not a meeting minutes
The two pieces of information may be related, but they do not serve the same purpose.
A report primarily addresses:
What was discussed or addressed during that meeting?
The decision history addresses:
What was ultimately decided, and why?
A single meeting can yield several pieces of information, but only one fundamental decision.
Conversely, a decision may result from several exchanges, documents, and analyses spread out over several days.
If a decision is confined to a meeting minutes, it becomes difficult to find without knowing in advance which document it is in.
That is why important decisions must be treated as identifiable components of the project.
The Problem of Dispersed Decision-Making
In a traditional organization, the decision-making process may be divided among several tools.
Part of it is in an email.
Another one in a personal note.
The document used for arbitration is located in Finder.
The final decision may have been made during a phone call.
So the result exists somewhere, but The chain that helps us understand how we got here no longer really exists as a whole.
A few months later, the consultant must rebuild this chain.
This work is rarely complex. It is mostly repetitive and avoidable.
Creating a Useful Decision Log
A minutes of decisions should not be an exhaustive list of all the choices made during a project.
If everything becomes a decision, nothing matters anymore.
Instead, you should document the decisions that may have future implications: choosing a solution, a change in direction, a significant exception, rejecting an option, a decision involving risk, or any factor that could be called into question later.
The right question to ask when documenting a decision is simple:
If someone asks me in six months why we made that choice, will I need to go over the reasoning again?
If so, the decision is probably worth keeping.
A concrete example
A consultant is evaluating three options for his client.
Option A is the least expensive, but it takes four months to implement.
Option B costs more, but can be implemented in six weeks.
Solution C offers more features, but involves a contractual dependency that is considered too significant.
The customer ultimately chose Option B.
Store only:
«Option B Selected»
causes one to lose sight of what is essential.
A usable log should make it possible to retrieve:
Background: Deployment must be completed by the end of the quarter.
Options: A, B, and C.
Decision: Solution B.
Main reason: a deadline that fits the client's schedule.
Option A ruled out: It takes too long.
Option C ruled out: disproportionate contractual obligation.
Source : Comparative analysis and meeting on March 12.
Eight months later, the consultant no longer needs to reconstruct the conversation.
The reasoning is still there.
Timelines give meaning to decisions
A decision should not be viewed in isolation from the rest of the project.
We need to be able to understand what happened before and after.
For example:
March 5 — Receipt of three proposals.
March 8 — Comparison of costs and timelines.
March 12 — meeting with the client.
March 13 — Decision: Option B.
March 20 — contract signed.
This timeline helps distinguish a simple event from a pivotal decision.
It also helps us understand how a project has evolved.
History then becomes more than just a series of dates: it shows the path taken by the file.
In Mnemosyne, the decision rests with the case file's history
Mnémosyne treats decisions as elements of professional memory.
A decision may include its context, the issue addressed, the options considered, the choice made, the reasons for that choice, the options rejected, the risks, the consequences, and the sources related to it.
It also remains linked to the client, the case, or the assignment in question.
The principle is important: A decision is not a single note.
It is part of a continuum:
context → reasoning → decision → sources → case history.
This structure then makes it possible to retrieve important decisions from the case file’s history without having to know a file’s name or the exact date of a meeting.
Always being able to go back to the source
A reliable record must remain verifiable.
If a decision states that an option was rejected for a specific reason, it must be possible to refer back to the document, note, or record that supports that information.
Mnémosyne maintains this traceability approach.
A summary of a report is therefore no substitute for the original sources.
It allows you to quickly identify what matters, and then return to the original information when more details are needed.
This is particularly important in a professional context: a useful interpretation should not turn an interpretation into an established fact.
Memory must remain usable without AI
The retention of a decision should not depend on artificial intelligence.
The context, reasons, options, and sources constitute the structured data in the file.
They remain readable and usable independently of Clara.
Intelligent assistance can then help locate, reconcile, or reconstruct information, but it does not replace the professional’s documented reasoning.
This distinction prevents an important decision from being based solely on a generated summary whose source would be difficult to verify.
What are the benefits for the consultant?
The appeal becomes especially apparent over time.
During the assignment, it takes just a few minutes to document a few key decisions.
Several months later, this can save you from having to reread dozens of emails, several notes, and various documents just to understand why a particular course of action was chosen.
For an independent consultant, maintaining the history of decisions related to a client project It also makes it possible to resume a project more quickly, provide more precise responses to clients, and avoid having to repeat an analysis that has already been conducted.
Value, therefore, does not lie in the accumulation of information.
It lies in the ability to reconstruct the line of reasoning when it is no longer in memory.
Conclusion
A client project should not consist solely of what has been produced.
It should also preserve the decisions that have shaped its development.
A good record makes it possible to trace the decision that was made, but more importantly, its context, the alternatives considered, the reasons for the decision, and the sources used.
It is this approach that transforms simple project tracking into decision-making memory.
Mnémosyne is designed around this principle: preserving enough context so that a decision remains understandable as time goes by.