How the work runs today
Everything below is yours. Rename it, delete it, add what you actually run.
- Process and sub-process names come from a reference taxonomy, not from an observation of your organization — rename, add and delete freely.
- Nothing quantitative is seeded. Every volume, role, disposition and baseline in this studio is yours from the moment you type it.
- Sub-processes are supplied for the flows the reference model covers; the rest start empty on purpose. Add what you actually run.
Current → future
What the redesign does to the work, and where that lands in the organization
Nothing is sized yet, so there is nothing to bridge. Open an activity, give it a volume and a minutes-per-unit, and decide what happens to it — the moment two numbers exist, every figure below starts moving. 7 activities and tasks are available to analyse.
0 of 7 activities and tasks are being analysed; 0 carry numbers.
Data lineage
Where each data object is born, changed, and depended on — derived from the work, not drawn separately
No data objects declared yet. On any activity, record what it creates, changes and consumes. An object changed in three places and consumed in eight is where reconciliation breaks — and where a control belongs.
Limits
What this is, and what it is not
- Not an observation of your organization
- Not an assessed control
- Not a benchmark or peer comparison
- Not a headcount or a cost case
- Not a professional review
Effort figures are yours from the moment you type a volume, and modeled before that. Turning effort into headcount or cost needs utilization and rate assumptions this studio does not own — that is the Org Design Studio’s job, and it states its own.