What to remember
- One decision per file
- Dated and attributed sources
- Assumptions separated from evidence
- A record of the choice and its conditions
The seven blocks of the file
The summary page should remain short while linking to the evidence. A stable structure prevents each project from reinventing its format and makes decisions easier to compare.
- Question
Precise formulation, owner, date and scope.
- Context
Current situation, constraints and concerned actors.
- Evidence
Sourced data and documents.
- Assumptions
Uncertain elements, values and rationale.
- Scenarios
Coherent options and shared criteria.
- Recommendation
Proposed choice, benefits, costs and risks.
- Record
Decision, participants, commitments and review.
Do not mix evidence, assumptions and estimates
Evidence can be verified in an identified source. An assumption is a working proposition about the future. An estimate is a value produced by a stated method. Mixing them creates an appearance of certainty.
In the file, show the type, source or method, owner, update date and confidence level. A missing value should remain missing: zero is already information.
| Nature | Example | Expected evidence |
|---|---|---|
| Evidence | Last financial year’s revenue | Dated accounting source |
| Assumption | Conversion rate of a new channel | Rationale and owner |
| Estimate | Size of a segment | Method, sources and range |
| Decision | Pilot in two markets | Date, decision-makers and conditions |
Govern access and versions
Some documents are confidential, and not every team edits the same objects. Access should be defined at the useful level without preventing an overall understanding of the file.
Retain a stable identity for every market, segment, offer or scenario. Renaming should not break links between analyses. Material versions should be comparable and connected to the corresponding decision.
- A named file owner
- Explicit read and edit rights
- Supported shared objects with stable identity
- History of material changes
- Decision associated with a specific version
Atlas within Innovatio Decision Suite
Atlas is the foundation of the Innovatio decision file. It organizes context, access, versions, supported shared objects and the record of trade-offs. Specialist modules retain their own working logic.
This architecture avoids turning the file into a universal tool. Atlas carries the shared context; Grid, Plot, Mix, Calc, Map and Pilot each address a category of question.
Frequently asked questions
How long should a decision file be?
The summary can fit on one or two pages when evidence, calculations and appendices remain accessible and connected.
Should rejected scenarios be retained?
Yes. Retaining the reasons for rejection prevents the same debates from reopening without new information.
How should a changed assumption be handled?
Create a new version, assess the impact on scenarios and connect the change to its owner and date.