The hardest part of process improvement is not drawing the diagram. It is getting the people who need to change their work to agree that the change is worth making.
Why most process changes stall
You run a discovery workshop. You produce a clear as-is model. You design an improved to-be state that saves the team hours every week. You present it to leadership. They nod, say "looks great," and nothing happens.
Three months later, everyone is still running the old process.
This is not a modeling problem. It is an alignment problem.
Step 1: Map your stakeholders before you map the process
Before you touch a modeling tool, list every person or group that will be affected by the process change. For each stakeholder, answer three questions:
- What do they care about?
- What do they stand to gain or lose?
- What level of involvement do they need?
Use a simple 2x2 grid: influence on one axis, impact on the other. High influence + high impact stakeholders need co-design. It takes ten minutes and saves weeks of politics.
Step 2: Frame the change in their language
The number one mistake: explaining the process change in process language.
- For executives: Focus on outcomes and numbers.
- For team leads: Focus on workload and clarity.
- For frontline workers: Focus on daily experience. Be honest about what gets harder.
- For IT teams: Focus on integration and system impact.
Step 3: Align at the right moments
Alignment is not a single meeting. It is a series of touchpoints:
- Before discovery: Set expectations
- After discovery: Share the as-is model in plain language
- During design: Co-create the to-be state
- Before implementation: Get explicit sign-off in writing
- After implementation: Close the loop with results
How to handle resistance
Resistance is information about what you missed.
- "We tried this before" - Ask what specifically failed. Usually it was the rollout, not the design.
- "This will create more work" - Quantify current vs projected workload.
- "My team was not consulted" - Own it. Late involvement beats no involvement.
- "The current process works fine" - Show the data if it does not.
- "I do not understand the diagram" - Translate into narrative. The model is a visual aid, not the deliverable.
Five alignment anti-patterns
- The big reveal - Working in isolation then presenting a finished design
- Consensus theater - Meetings where everyone nods but nobody commits
- The BPMN lecture - Explaining gateway types to people who never asked
- Ignoring the silent objector - The person who says nothing but undermines later
- Alignment without authority - Getting the team excited without securing the decision maker
Checklist
- Stakeholders mapped by influence and impact
- Change framed in stakeholder-specific language
- Alignment touchpoints scheduled at each phase
- Process model translated for non-technical audiences
- Sign-off documented in writing
- Results reported back after implementation
Read the full guide on ProcessCamp with instructor tips, detailed resistance handling, and FAQ.
Top comments (0)