Choose the right entry point
A team starts with a concrete choice: which market to prioritise, which commercial scenario to engage, how much budget to commit or when to review a strategy.
The scope remains proportional to the decision. A three-segment prioritisation needs a lighter file than a three-to-five-year financial trajectory.
A common discipline across different decisions
Each case separates evidence from assumptions, compares options on a shared basis and keeps the reasons for the final choice readable. The workspaces are selected only after the question and expected decision deliverable are clear.
| Situation | Dominant question | Decision deliverable |
|---|---|---|
| Prioritisation | Where should effort be focused? | Ranked options and conditions |
| Commitment | What resources should be mobilized? | Costed scenario and assumptions |
| Governance | When should the choice be reviewed? | Risks, deviations and review points |
Nexus for a bounded web investigation
When the decision requires a view of external actors, sources or co-citations, Nexus can map a bounded corpus and preserve the provenance of the relationships observed.
Nexus remains outside Decision Suite. Its findings complement the decision analysis when collection rules, corpus limits and interpretation remain explicit.
Frequently asked questions
Which workspace should a team start with?
Start with the decision question and expected deliverable. Atlas anchors the file; the relevant specialist workspaces depend on the market, commercial, operational, quantitative or financial questions to examine.
Can one use case require several workspaces?
Yes, but only the useful workspaces should be selected. Each keeps its role, and the results are brought together and checked in the decision file.