Key Executive Takeaways
- What leadership thinks happens is rarely what actually occurs on the shop floor or in customer support.
- Focus first on capturing the authentic As-Is reality before proposing future-state optimizations.
- Ask open-ended questions like "What do you do when the ERP rejects this record?" to find hidden workarounds.
- Always conduct collaborative validation sessions to ensure team ownership and buy-in.
1. Why Process Discovery Fails Most Companies
Most process mapping projects stumble because they map the idealized process documented in corporate policy binders instead of observing ground-level reality. When employees deviate from official rules, they usually do so not out of malice, but because official processes are clunky, incomplete, or broken.
Discovery is the systematic forensic investigation of how daily work actually gets completed. Its objective is to capture the authentic "As-Is" state, identify bottlenecks, and build trust with front-line teams before proposing optimizations.
2. Phase 1: Scoping & Stakeholder Identification
Do not attempt to map the entire company at once. Define clean process boundaries using a high-level SIPOC (Suppliers, Inputs, Process, Outputs, Customers) diagram:
- Identify the specific trigger that starts the process.
- Identify the final deliverable and end state.
- Create a stakeholder map including front-line executors, team leads, system administrators, and downstream recipients.
3. Phase 2: Conducting Effective As-Is Interviews
Avoid asking leading questions such as "Do you always follow the CRM handbook?". Instead, apply structured behavioral interviewing:
- "Walk me through the last time you completed this task yesterday."
- "What pieces of information were missing when you received the request?"
- "Who did you have to ask or message in Slack to get clarification?"
- "What is the most frustrating part of this process?"
4. Phase 3: Uncovering Shadow IT & Hidden Workarounds
Almost every team maintains unofficial Excel spreadsheets, personal email templates, or private Google Sheets to bypass cumbersome enterprise systems. These shadow operations contain the most critical insights into operational friction. Documenting them without judgment transforms hidden vulnerabilities into formal improvement opportunities.
5. Phase 4: Validation & Building Consensus
Once a draft BPMN diagram is created, gather stakeholders for a walkthrough session. Review the diagram step-by-step: "If step 3 fails, does this match what really happens?". When employees see their real pain points represented accurately on screen, resistance to change dissolves into active collaboration.