Skip to content
← Transform overview

TRANSFORM / EVIDENCE & ASK SARAH

Ask the question.
Open the evidence.

Bring scattered sources into one investigation. Ask Sarah, inspect the answer and follow a finding back to the original.

Interactive examples. Fictional data. No sign-up.
Evidence & Ask Sarah workflowSources → a supported answer → a reviewable decision. An authored illustration of a fictional handoff project.ChecklistThe stated processWorkbookWhat the records showWalkthroughHow the work happens ASK SARAHWhy does thehandoff stall?Inspect the explanationOpen the source FINDING + BASIS
Sources → a supported answer → a reviewable decision
Transform workflow illustration · Fictional Northstar example
01Connected sources
02Cited answers
03Human review

SEE THE WORK / MAKE A CHOICE

The answer matters.
So does its source.

Open the original material, then ask a question about the handoff. A citation gives you somewhere concrete to look next.

Working demo screens · Fictional examples

TRANSFORM / INSIDE THE DEMO

Keep the original within reach.

Inspect the project’s documents, records and walkthroughs. Open a source and follow what it contributes.

A finding remains connected to the material behind it.

Open the evidence demoInteractive example · No sign-up
ProcessScout / TransformDEMO WORKSPACE
Northstar working demo: Inspect the project’s documents, records and walkthroughs. Open a source and follow what it contributes.

TRANSFORM / INSIDE THE DEMO

An answer you can investigate.

Ask why the client handoff gets delayed, then open a citation and check the supporting source.

Authored demo answers show the citation workflow using fictional evidence.

Try Ask SarahInteractive example · No sign-up
ProcessScout / TransformDEMO WORKSPACE
Northstar working demo: Ask why the client handoff gets delayed, then open a citation and check the supporting source.
01

BRING A REPRESENTATIVE PICTURE

Start with the work you already have.

Add relevant documents, spreadsheet extracts, recordings and interview material to a project. Include a normal case and an exception, so the investigation is grounded in the variation your team actually encounters.

Recordings can feed transcripts, screenshots, documentation and process analysis when the corresponding capabilities are available. You can begin with a few useful sources and a clear question rather than an entire system estate.

Start with
A question, a defined process boundary and representative sources.
Work toward
An organized starting point for investigation, with each source available in context.
Detail of the Product demo with fictional example data
ProcessScout / Producta source with its limits stated · fictional data
02

SEE WHAT THE SOURCE CONTRIBUTES

Read the finding and its basis together.

A source’s Insights view connects its reading to the problems, findings, figures, questions, process steps and people it helped identify. Open the relevant object to inspect its detail.

This makes the next review more precise. Check whether a finding matches the passage or observed work, whether another source supports it and what remains unanswered. Keep the original evidence close to the interpretation.

Start with
An analyzed source and the findings or business objects connected to it.
Work toward
A traceable explanation of what the source says and what it contributes to the project.
Detail of the Transform demo with fictional example data
ProcessScout / Transforma step with its evidence · fictional data

NORTHSTAR / THE WORKED EXAMPLE

“Why does the handoff get delayed?”

The prepared answer connects the checklist, sample records and an authored team walkthrough. Open a citation and check its wording. The demo illustrates the interaction; its answer is prepared, not generated live.

Walk through this example

THE ANSWER IS THE BEGINNING OF A REVIEW.

  1. 01 / SourceOpen the handoff checklist.
  2. 02 / FindingInspect the ownership gap.
  3. 03 / QuestionAsk why the handoff is delayed.
  4. 04 / ReviewCheck the citation and decide what needs attention.
The fictional demo lets you follow this chain without uploading business data or making a live AI call.
03

ASK IN CONTEXT

Sarah starts with what you are looking at.

Open Ask Sarah from a source, a project page, a goal or a Digital Twin object. The conversation carries a scope, so you can ask about the work in front of you and inspect the evidence behind an answer.

Use the conversation to investigate a delay, understand a business rule or identify the information needed for the next decision. For spreadsheet questions, supported tools provide cell-cited observations and calculations; an unavailable result stays explicit.

Start with
A question tied to the relevant source, object or project context.
Work toward
A contextual answer to inspect, with a path back to the supporting material.

A question you can check

  1. Your questionAsked where you are working
  2. Cited answerEach claim names a source
  3. The originalOne click away
Illustration · fictional example
04

PUT HUMAN KNOWLEDGE TO WORK

Confirm what the team can stand behind.

People who know the process can confirm or reject a finding and resolve the questions it raises. Keep that review attached to the object rather than losing it in a separate conversation.

The useful next action may be another source, an owner’s explanation or an accepted correction. Review strengthens the shared picture while preserving the distinction between an observed fact and a proposed improvement.

Start with
A finding, its source references and the perspective of someone who knows the work.
Work toward
A reviewed finding or a concrete question to resolve before it is used.

Review by the people who know the work

  1. Process ownerConfirms the boundary
  2. OperatorTests the interpretation
  3. Accepted findingThe team can stand behind it
Illustration · fictional example
05

MAKE THE KNOWLEDGE USEFUL

Keep the source connected to the next step.

Use the growing evidence base to understand a process, inspect the Digital Twin, compare options and prepare documents. The next person should be able to see both the conclusion and how the team reached it.

For a procedure, move from the observed steps into a draft that can be edited, reviewed and shared. For a proposed system change, carry the source-backed requirement into the design and delivery conversation.

Start with
Reviewed findings, explicit questions and the relevant source material.
Work toward
Process knowledge, a stronger decision brief or a draft deliverable with its context intact.
Detail of the Transform demo with fictional example data
ProcessScout / Transformreviewed findings shape the options · fictional data

THE PRACTICAL DETAILS

Know where
you stand.

Talk through your workflow
Do we need to connect all of our systems first?

No. A focused project can start with documents, representative records and a walkthrough. Add connections where they provide relevant evidence, with the required permissions and supported operations confirmed.

Does everyone see the same evidence?

No. Project and source access determine what a viewer can open. A shared project is not a promise that every source is visible to every participant. Plan the membership and source permissions with your team.

Does Sarah make the final decision?

People remain responsible for reviewing findings and approving consequential changes. Sarah helps investigate and prepare work; the relevant review and approval rules still apply.

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