North Star Framework

Process design

We design how work actually flows, from the truth of how it runs today to a future that reaches the outcome.

Start the diagnostic See all five services
Where this sits
Direction and measures Operating model Information management Process design Adoption (Adopt360)

What this service covers

Every business has two versions of its processes: the one in the handbook and the one people actually do. They’re never the same. We map the real one, then design the one that reaches the outcome.

Not this service
  • Building, configuring or choosing the systems. That’s implementation, a separate phase.
  • The taxonomy and standard underneath. That is information management, Service 3.
  • Getting people to work the new way. That is Adopt360, Service 5.
You’re probably here if
Work takes far too long and no one can point to where the time goes.
Ask three people how a process runs and you get three different answers.
A new system is going in and you need the process right before it does, not after.

Three outputs, mapped to what you need.

The current state, the future state, the detail to run it. Which of them you need is matched to what you need to change.

Take it at the depth you need: the map of how work flows today, the map plus the future design, or both with the operating detail to run it. Detail on its own rarely stands up without the design above it.

Current state mapping

How the work really flows today: every handoff, delay and workaround, from evidence not the handbook.

Future state design

The flow that reaches the outcome, designed with the people who run it.

Operating detail

SOPs, work instructions and who does what. Enough to run it.

Either way: open across systems or built around the platform you already have. Designed for it, not configured in it.

How we do it

The same discipline whichever pieces you take.

From evidence, not policy

We map what people do, from watching the work and the trail it leaves. The written process is usually fiction.

With the people who do it

The future flow is designed with the people who run it, so it’s one they will use.

AI only where it earns it

We flag where AI could take the load, design it in where it pays and say so plainly where it doesn’t.

Handed over, not shelved

Maps and detail go to the build and to the people working the new way, so nothing is lost between design and doing.

What you walk away with

The time black holes, found

The delays and handoffs nobody could point to, mapped and designed out.

One process, not three versions

Everyone running it the same way and able to describe it the same way.

Fit before the tool

The process designed before the platform, so the system serves the work.

Work and writing from this service

See everything from this service →
Case study
From nothing to business as usual: a shared identity service
A new identity service had the technology but no way for anyone to adopt it. We built the front door.
Read →
Case study
An ERP choice the board could defend
A PE-backed manufacturer needed a new ERP its board would back. Picking the software turned out to be the easy part.
Read →
Founder insight
Ask why before you start
Jumping to solutions before agreeing why the project exists is the fastest way to deliver the wrong thing on time.
Read →

Not sure this is where you should start?

That’s what the Diagnostic is for. Fifteen minutes and you leave knowing your next step. Or just talk to us.

Take the diagnosticReady to chat