ORGONAUT
Login Signup
Docs
Scenarios
Create a scenario

Create a scenario

Create a scenario when you need to test organisational change without affecting Live.

Plan availability: creating new planning scenarios is available on every current paid plan. The team plan supports up to 3 active planning scenarios, business supports up to 10, and enterprise plus agency are unlimited.

A good scenario starts with a clear question and explicit scope.

Use this before creating one

Define the planning question in one sentence.

Examples:

  • What is the impact of moving Platform under Core Engineering?
  • What cost change do we get if we rebalance shared staffing across Product teams?
  • What is the velocity effect of adding two agents to support incident triage?

If the question is vague, the scenario will be hard to evaluate.

Naming convention

Use names that encode purpose and time.

Pattern: YYYY-MM purpose scope

Examples:

  • 2026-03 platform-realignment
  • 2026-03 support-agent-pilot

This improves search, lineage review, and stakeholder communication.

Scenario creation workflow

  1. Open scenarios and create a new scenario.
  2. Choose source context (typically Live).
  3. Set a clear name and brief description.
  4. Confirm creation.
  5. Enter scenario context and begin edits.

If your plan also enforces an active planning-scenario cap, archive or apply an existing planning scenario before starting another one.

Scope discipline

Keep each scenario focused.

  • Prefer one change theme per scenario.
  • Avoid mixing unrelated restructures.
  • Use separate scenarios for competing options.

Focused scenarios are easier to review and safer to promote.

First edits to make

Start with the minimum meaningful change:

  • move a target team
  • update placements for the affected actors
  • adjust positions if role structure changes

Then review deltas before additional edits.

Review readiness checklist

Before sharing a scenario for decision:

  • primary placements are correct for affected actors
  • edited teams/departments are structurally valid
  • cost and velocity deltas are understandable
  • scenario purpose is clear to non-authors