Skip to content
← Transform overview

TRANSFORM / DIGITAL TWIN

See the whole.
Follow the detail.

Connect the work, people, systems and goals. Explore what a change touches—and open the evidence behind each connection.

Interactive examples. Fictional data. No sign-up.
Digital Twin workflowStrategy · Processes · Systems · People · Value. An authored illustration of a fictional handoff project. Client handoff StrategyProcessesSystemsPeople & sitesValue FOLLOW A CONNECTION. OPEN ITS EVIDENCE.
Strategy · Processes · Systems · People · Value
Transform workflow illustration · Fictional Northstar example
01Five business layers
02Evidence & unknowns
03Connected impact

SEE THE WORK / MAKE A CHOICE

A connected picture.
A better question.

Inspect the model, follow a relationship and test the shape of a proposed change. Keep useful context for the next decision.

Working demo screens · Fictional examples

TRANSFORM / INSIDE THE DEMO

A business question has connections.

Open a process alongside its goal, systems, people and measures. Follow a relationship into its supporting evidence.

Each object keeps its evidence and open questions in view.

Explore the connected modelInteractive example · No sign-up
ProcessScout / Digital TwinDEMO WORKSPACE
Northstar working demo: Open a process alongside its goal, systems, people and measures. Follow a relationship into its supporting evidence.

TRANSFORM / INSIDE THE DEMO

What else does the proposal touch?

Change the volume, adoption and time assumptions for a readiness check. Inspect the resulting range and calculation.

The range is a planning model with explicit assumptions. The demo keeps cash savings unknown.

Try the Digital Twin demoInteractive example · No sign-up
ProcessScout / Digital TwinDEMO WORKSPACE
Northstar working demo: Change the volume, adoption and time assumptions for a readiness check. Inspect the resulting range and calculation.
01

ORIENT YOURSELF

Five layers. One connected picture.

Start with Strategy, Processes, Systems, People & sites and Value. Each layer opens the objects behind it: goals, problems, steps, business rules, systems, roles, outcomes and more.

The Twin draws from the project records your organization already holds. Counts, evidence status, disputed items and gaps help you see where the picture is stronger and where it still needs work. Narrow the view to the project or program relevant to the question.

Start with
Project evidence and the business records produced or confirmed from it.
Work toward
A connected view of the business with a path into the underlying detail.
Detail of the Transform demo with fictional example data
ProcessScout / Transformfive connected layers · fictional data
02

FOLLOW THE EXPLANATION

Open an object. See what it rests on.

Select a problem, process step, system or goal to inspect its properties, source references and relationships. Object 360 keeps the supporting detail close to the question you are investigating.

Explore nearby objects or trace a path between two points in the model. The path names its weakest link, helping you distinguish a supported explanation from a relationship that still needs confirmation.

Start with
A specific business question and an object or relationship to investigate.
Work toward
A traceable explanation with supporting evidence and visible gaps.
Detail of the Transform demo with fictional example data
ProcessScout / Transformone step, its owner and its rule · fictional data

NORTHSTAR / THE WORKED EXAMPLE

A delayed handoff touches more than a queue.

Follow client onboarding to the readiness review, the delivery owner, the queue and the proposed owner check. The demo shows how those relationships help frame a question; its authored data is not a customer outcome.

Walk through this example

A BETTER QUESTION AT EVERY LAYER.

  1. 01 / GoalWhat needs to improve?
  2. 02 / ProcessWhere does the problem arise?
  3. 03 / People & systemsWho and what does the work depend on?
  4. 04 / DecisionWhat should change, and what is still unknown?
Move from an outcome to the work behind it, then back to a decision the team can explain.
03

TEST THE SHAPE OF A CHANGE

See what else the proposal touches.

Open a proposed option to inspect its connected changes and the objects around them. The scenario view shows affected systems, people and measures, as well as possible collisions with other delivery waves.

Explore a what-if by adding or removing changes. Figures carry their basis and uncertainty; missing information becomes a named question. Exploring a variant does not silently commit a change to the underlying business records.

Start with
An option or a selected set of proposed changes, with their modeled relationships.
Work toward
An impact view, affected people, potential collisions and questions to resolve.
Detail of the Transform demo with fictional example data
ProcessScout / Transforma change and what it touches · fictional data
04

MAKE IT USEFUL TO A DECISION-MAKER

The detail and the brief share a basis.

Executive mode brings the conversation back to where things stand, the most pressing problems, available options and decisions that need attention. Measures appear with their evidence rather than as disconnected headline numbers.

Analysts can keep investigating while a sponsor reads a concise brief from the same model. When an option is ready, the approval request goes through Decide so the accountable person’s decision and its basis are recorded together.

Start with
The connected model, current options and relevant measures.
Work toward
An executive brief and a reviewable route into a decision.
Detail of the Transform demo with fictional example data
ProcessScout / Transformoptions a decision-maker can compare · fictional data
05

KEEP THE INVESTIGATION

Save the view. Revisit the question.

Pin objects, object sets, paths and Sarah answers to a board. Keep the perspective that helped the team understand a problem, so the next conversation can begin with the reasoning already in place.

Live viewpoints refresh against the model when the board opens, under the viewer’s own access. Frozen answers remain distinct from those refreshed views. The time lens can compare modeled states and make proposed changes easier to inspect.

Start with
An investigation worth returning to, with its objects and questions.
Work toward
A saved board that preserves context and reopens the relevant model views.

Keep the investigation

  1. Saved viewLayers and filters kept
  2. Open questionStays with the view
  3. Next reviewSame basis, new evidence
Illustration · fictional example

THE PRACTICAL DETAILS

Know where
you stand.

Talk through your workflow
Does the Twin need every system connected?

Start with a project and relevant sources. The model grows as evidence and business records are added and reviewed. Connections can add useful inputs, but the first useful question can be much smaller than a company-wide integration project.

Are the scenario figures predictions?

They are modeled figures with a stated basis. Explicit bounds can flow through the calculations; missing bounds stay unknown. A confirmed fact and a guaranteed future outcome are different things.

Who can see the model?

The Twin follows organization entitlements, subject access and project permissions. Private evidence is filtered for the viewer. Ask about the roles and sharing scope appropriate to your organization.

YOUR NEXT CHANGE

See the workflow.
Make it your own.

Try the workflow, or bring one question from your business.

Product view

ProcessScout interactive demo · Fictional Northstar data