What is scenario modeling?
In organizational design, scenario modeling means building a hypothetical version of your org structure — a reorganization, a cost-reduction target, a post-merger integration, a new operating model — and seeing what it would actually cost, in headcount and dollars, before you commit to it. It's the "what-if" step between an idea and a decision.
What it typically looks like
Practically, this usually means starting from a current, accurate model of the organization (who reports to whom, at what cost), then moving people and roles around in a hypothetical version of it — removing a layer of management, merging two teams, centralizing a function — and having the cost, headcount, and span-of-control numbers recalculate automatically as you do. Multiple scenarios can be built side by side and compared, so a decision-maker is choosing between real, costed options rather than a single proposal.
Where it gets used
- Restructuring and cost-reduction programs
- M&A integration — combining two organizations' structures
- Centralizing functions into shared services (sometimes called GBS, for "global business services")
- Location strategy — deciding where work should sit geographically
How BlissPoint Organization Viewer approaches this
Clone your live org chart into a named scenario, then drag people onto new managers, add or remove roles, and change titles, teams and costs freely — headcount, cost and span of control recalculate as you go, and a line-by-line diff shows exactly what changed against what's live, down to a person's role. Promote the scenario when you're ready or discard it without a trace. See it on the live demo or start with your own org.