When to use this
You're scoping a complex engagement
You need to understand the real process before you price the work. Run process discovery before the proposal so your scope is based on truth, not assumptions.
The documented process isn't the real process
Teams describe the official process, but workarounds, exceptions, and handoffs are with the people doing the work. You need their input before you commit.
You're competing on credibility
The firm that understands the client's process before the proposal wins. Show up with process maps, pain points, and evidence your competitors don't have.
How it works
Configure around the process
Set up interviews around the workflow, system, handoffs, exceptions, data, and decisions your team needs to understand.
Reach the people who do the work
Deploy to every stakeholder group the change touches - not just team leads, but the people who actually run the process.
Capture requirements and risks
Surface requirements, process variations, adoption risks, edge cases, and current-state evidence before delivery starts.
Export the process evidence base
Evidence-linked requirements, process maps, risks, and stakeholder input structured for your team's downstream deliverables.
Impact
Process truth captured
What people actually do, not just what the process document says
Requirements earlier
Requirements and edge cases surfaced before they become change requests
Risks visible
Adoption risks, handoff issues, and process variations found before delivery starts
Client trusts it
Evidence-linked process data the client can verify and stand behind
