A separately ordered report does not require a separate product, because the views share one evidence model.
Why it matters when the plan changes
When each report is produced by its own process, the same organisation ends up described three ways, and reconciling them becomes the reader's job. Sull, Homkes and Sull found that only 9% of managers say they can rely on colleagues in other functions and units all the time, a gap that widens whenever descriptions of the same organisation are built by separate methods rather than read from one case. Drawing every view from one case removes the reconciliation: two reports that disagree are disagreeing about the evidence, which is a real finding, rather than about how they were assembled.
The tension is commercial. Buyers want to order a single report without committing to anything larger, and that is a legitimate way in. The view has to be genuinely useful on its own while still being a window onto one model, which is harder to build than either a standalone report or a platform alone.
In practice
A leadership team orders a Team Map for one function and a Contribution Map for a single role in it. Both are drawn from the same case, so the role-level reading and the team-level reading rest on the same roles, dependencies and plan. Where they differ, the difference is informative rather than an artefact of two methods.
Evidence
Where several views of the same organisation come from separate processes, the reader is left to reconcile descriptions that were never built to agree.
Donald Sull, Rebecca Homkes and Charles Sull, Why Strategy Execution Unravels and What to Do About It, Harvard Business Review (2015)
What it cannot tell you
An evidence view cannot answer a question the underlying case holds no evidence for, and it cannot substitute for the case itself. Reading one view in isolation risks treating a partial account as complete; it describes what the evidence shows about role, team or fit against a plan, not a general judgement of a person or organisation.
How Atlas reads it
The views are Contribution Map, Team Map and Your Atlas. They share the model and the evidence of the case they belong to, and their commercial packaging is defined separately from the product.
Questions
Contribution Map, covering role, team, manager and culture fit against the plan. Team Map, covering team dynamics, friction and complementary strengths. Your Atlas, the individual playbook delivered with an assessment. Research such as Sull, Homkes and Sull's 2015 Harvard Business Review study found only 9% of managers trust cross-functional colleagues fully, showing why one shared case matters.
Yes. A single report can be ordered without a wider commitment, and it still draws on the same model underneath. What it cannot do is answer a question the case has no evidence for, which is why the scope of the view and the scope of the case are agreed together.
Because delivery, contracts and the platform have to use one word for one thing. Each view has one name, Contribution Map, Team Map and Your Atlas, and the same name is used in the proposal, the delivered report and the platform, so a buyer never has to work out whether two documents are the same thing.
They describe the work and the arrangement around a person: the role, the team, the dependencies, the plan. Nobody is ranked out. A behavioural assessment feeds the evidence, and the output is a reading of fit against a demand rather than a statement of a person's worth.
That is treated as a finding rather than an error. Because both draw on the same case and the same evidence, disagreement points at something real, similar to the gap Sull, Homkes and Sull described in 2015, where only 9% of managers said they could rely fully on colleagues elsewhere. It is investigated, not reconciled away.