Scenario overview
Scenarios are Orgonaut's core planning feature.
A scenario is a safe modeling space where you can change structure, placements, and role design without affecting Live.
Why scenarios matter
Scenarios let you separate thinking from committing.
That means you can evaluate alternatives, compare outcomes, and make better decisions before changing your Live organisation.
Live vs scenario
| Context | Purpose | Typical action |
|---|---|---|
| Live | Current operating state | Run operations and reporting |
| Scenario | Proposed future state | Model changes and compare deltas |
Scenario lifecycle
- Create a scenario from Live (or another source where supported).
- Enter edit mode and model proposed changes.
- Review scenario deltas (cost, capacity, velocity).
- Share and discuss with stakeholders.
- Promote to Live when approved.
What you can model
Common scenario edits include:
- moving teams between departments
- changing actor placements and allocation
- adding or removing roles and positions
- adjusting team composition
These edits remain isolated until promotion.
Reading deltas
Scenario deltas help you quantify impact:
- monthly cost change
- headcount and FTE shifts
- velocity changes where data is available
- direct reporting-line changes
- added, removed, or changed organisation records
The delta page is intentionally filtered to changed records only and reads like a compact diff review.
When a scenario was cloned from another scenario, the default delta compares it with that immediate source scenario. Use the Live View comparison option only when you specifically want to review the proposed state against Live View; records inherited unchanged from the clone source stay hidden so the view still focuses on changes made in the current scenario.
The left side lists changed records grouped by model family. The main panel shows only the changed fields: green rows were added, red rows were removed, and blue headers mark changed records. Unchanged records stay hidden so larger restructures read like a focused review instead of a full org listing.
Deltas can include people, agents, robots, teams, departments, positions, allocations, compensation, agent profiles, team agent budgets, and scenario metrics. Structural hierarchy changes are shown on their owning department or team record rather than as separate org-unit plumbing. Reporting changes appear as report-line diffs based on manager changes and direct-report impact.
Cost, budget, compensation, and velocity details follow your permissions. If those permissions are unavailable, the diff remains visible but sensitive cost or metric lines are omitted.
Use deltas to compare options, not just to confirm assumptions.
Related scenario concepts
- Snapshots: point-in-time captures for traceability
- Archived scenarios: read-only historical scenarios
- Lineage: how scenarios branch and relate
- Activity log: exact event-level change history
Smaller screens
On smaller screens, the secondary actions in the Scenarios and Snapshots list headers collapse to icon buttons to preserve width.
In the Scenarios list, the row-level Edit action switches to a filled pencil icon on small screens and returns to text-only on larger screens.
When to create a new scenario
Create a scenario when you need to answer one of these:
- What if we move this team under another department?
- What if we rebalance allocation across critical initiatives?
- What is the cost and capacity impact of adding agents?