01
Capture
The current state, from real evidence.
ProcessScout Team
Keep transformation work connected after the workshop ends.
Create a living evidence base for processes, systems, people, opportunities, changes and outcomes — so the team can see what changed and why, with finance, operations and stakeholders in one governed workspace.
Best for
Teams that need traceability, not another folder of slides.
- Operations and finance teams with recurring cross-system work
- Transformation offices coordinating several initiatives
- Continuous-improvement teams that need traceability and governance
- Leaders who need outcomes, not a collection of project files
The loop that keeps running
Capture the current state → measure the result.
The same evidence standard the analyst uses, kept alive by the team — so a decision made in one quarter still carries its reasoning in the next.
02
Decide
What matters, ranked and owned.
03
Design
The first move against real constraints.
04
Launch
Change with approvals and control.
05
Measure
The outcome against the baseline.
An improvement loop, not a project
Same loop, seen from inside one initiative.
Picture your own operations team running the loop Northstar Services ran on invoice approvals — owned start to finish by the people who live with the result.
The loop opens with a workspace for the initiative: the stakeholders, the evidence policy, who signs off. Sarah runs guided intake in the evidence room while the process owner records a walkthrough of how the work actually runs today — not how the org chart says it runs.
Northstar
Finance's own analyst records an 18-minute walkthrough that stays in the team's workspace once the meeting ends, ready for whoever inherits the initiative next quarter.
The team builds the current-state map together from that evidence. Process mapping runs by scope today, and the unified Evidence Ledger view is limited availability — but the problem register is generally available, so every problem logged already carries its source, plus a read on risk and feasibility, back to the walkthrough or system record it came from.
That register becomes a ranked opportunity list with a skip list attached, each reason stated and owned — a record anyone on the team can open and check, not a slide the operations lead has to defend from memory at the next steering meeting.
Where a change goes live, a Trail Map style deliverable documents the decision and its evidence. Carrying that evidence base into next quarter's intake, instead of starting from a fresh whiteboard, draws on the Evidence Ledger — limited availability — and Programs & portfolios — pilot; today, keeping the record compounding depends on the team using this workspace as the system of record.
What a week looks like
A standing rhythm, not a workshop that ends.
The same cadence repeats every week, for whichever initiative is live.
| Day | What happens | What does the work |
|---|---|---|
| Monday | Stand-up review of what Sarah flagged as still uncovered from last week's walkthroughs. | Sarah guided intake, Evidence room coverage |
| Wednesday | The process owner records a walkthrough of whatever changed since the last cycle — a new exception, a new system, a new handoff. | Walkthroughs & recordings |
| Thursday | Finance and operations leads rank opportunities together in the team's standing meeting, then sign off the skip list before Friday's review. | Problems & opportunities, ROI, skip list & first move |
| Friday | The current deliverable is reviewed against the evidence, and next cycle's intake gets scheduled. | Deliverables & client-ready outputs |
Before and after
What this replaces
Most teams run this work across status decks, a shared drive of process documentation and a spreadsheet of open initiatives. The point is not that those tools are bad — it is that the evidence goes stale and drifts further from what's true with every cycle nobody revisits it.
- Status decks — a snapshot of the initiative with no link back to the evidence it was built from, rebuilt from scratch for every steering meeting.
- Process documentation on a shared drive — maps that describe how work used to run, with no owner accountable for keeping them current.
- Spreadsheet initiative trackers — a ranked list with no record of why an item was ranked, deferred or closed.
- Screen recordings sent over chat — recordings nobody can trace back to the finding they informed, gone as soon as the channel gets archived.
- Steering-committee slide templates — an outcome stated once, then never checked again against what the team actually measured.
Team access
Give the team one place the evidence lives.
Current availability is confirmed at setup, with roles, approvals and integrations scoped to how your team actually works.