Overview⚓︎
Most tools help teams manage work.
DMS helps them preserve decision context.
The Decision Memory System (DMS) is a focused product for recording the question, choices, reasons, decision, expectation, outcome, and lesson behind an important decision.
The Problem⚓︎
Teams usually remember what they decided. They often lose why they decided it.
When that decision memory fades:
- the same debates happen again
- the same mistakes are repeated
- important context leaves with the people who held it
DMS gives users a place to preserve that context in a structured record.
Simple Flow⚓︎
DMS follows a straightforward flow:
- Open a Topic with a clear question or problem.
- Move it to Considering and add Choices and Reasons.
- Move it to Chosen when one option is selected and an Expectation is recorded.
- Move it to Waiting while the result becomes clear.
- Move it to Reviewing to record the Outcome and Lesson.
- Move it to Closed when the Topic becomes part of the decision record.
DMS is not a task manager, a general note app, or a document repository. It is designed for preserving decision memory.
Who It Serves⚓︎
DMS creates value at three levels:
Personal⚓︎
People can use DMS to keep a record of important personal decisions, compare expectations with outcomes, and improve judgment over time.
Team⚓︎
Teams can use DMS to preserve trade-offs, reduce repeated debate, and make earlier decisions easier to understand during onboarding or handoffs.
Organization⚓︎
Organizations can use DMS to preserve institutional memory, reduce context loss across role changes, and build reusable lessons from earlier decisions.
What Makes It Different⚓︎
DMS keeps the parts of decision-making that most systems lose:
- Reasoning stays attached to the decision instead of disappearing after the choice is made.
- Expectations can be compared with Outcomes later.
- Disagreement can remain part of the record instead of being flattened away.
- History is preserved so the past is not silently rewritten after results are known.
Next Steps⚓︎
- Read the Vision for the product thesis and long-term direction.
- Read the Domain Model for the core concepts.
- Read the Behavior & Lifecycle for Topic stages and transitions.
- Read the Collaboration for participation and disagreement handling.