Stage 2: The Process Assessment

Every company has two versions of its processes: the one written in the playbook, and the one that actually happens on a Tuesday afternoon when someone's out sick and a deal is stuck. The Process Assessment is about the second one, because that's the one your system has to support.

In this stage we map how work really flows through your team, step by step, handoff by handoff. Where a lead gets qualified. Who touches a quote before it goes out. What happens when a customer emails support. Where the sticky notes and the "just ping me" shortcuts live. Those informal shortcuts aren't bad, they're often where the real knowledge is, but they can't be scaled or built into a system until they're visible.

How we do it

We work from how your people actually operate, not from assumptions. That means talking to the people doing the work, watching where things slow down, and documenting the real path a piece of work takes. The output is a clear, honest map of your key processes: what happens, in what order, who owns each step, and where the friction is.

Core vs. Comprehensive

The Process Assessment comes in two depths, and the difference is about how far we carry the work:

• Core delivers the documentation, a clear map of your processes as they are, with the friction points called out.
• Comprehensive adds the enablement layer on top: training and job aids that help your team actually adopt the improved process, not just read about it.

Which one is right depends on whether your team mostly needs clarity or needs clarity plus the materials to change how they work day to day.

Why this stage matters so much

This is the stage that keeps your future build honest. When a system is designed on top of a real process map, the fields, stages, and automations have a reason to exist, they mirror how work actually happens. When it's designed on top of guesses, you get software that fights your team instead of helping them. Mapping the process first is how we make sure the eventual system fits the business, not the other way around.

It also credits toward the Build, like every diagnostic stage, so the clarity you buy here isn't a detour. It's the foundation everything above it is built on.

<- Stage 1  |  Stage 3 ->