Here's a truth most audits miss:
The org chart lies.
It tells you who's supposed to make decisions. Who's supposed to own processes. Who's supposed to know how things work.
But the org chart doesn't tell you who actually does the work, who really makes decisions when things break, or where the bottlenecks actually live.
This step is about finding those people—the ones who know the truth.
If you talk to the wrong people, you'll get a polished version of how the business is supposed to run. If you talk to the right people, you'll see how it actually runs.
That's where the real opportunities are.
Why Stakeholder Selection Matters
You can't audit what you can't see.
And you can't see the real problems unless you talk to the people who live with them every day.
If you only interview executives, you'll get strategy—but no ground truth.
If you only interview frontline workers, you'll get complaints—but no context for priorities.
If you skip system owners, you'll miss critical data flows and integration points.
You need all three perspectives: strategy, execution, and systems.
The Three Types of Stakeholders You Need
Every audit should include at least:
1. Executive decision-makers
These are the people who control strategy and budget. They set goals, approve spending, and decide what gets prioritized.
2. Department heads and process owners
These are the people who own processes day-to-day. They know where work slows down, where handoffs break, and where time gets wasted.
3. Frontline operators
These are the people doing the actual work. They know what's manual, what's redundant, and what workarounds exist because the "official" process doesn't work.
Bonus: System owners
These are the people who manage the tools and data. They know what's connected, what's broken, and what data lives where.
How to Map Stakeholders to Processes
Start with your in-scope processes from the last step.
For each process, identify:
- 1 decision owner: Who approves changes or makes final calls?
- 1 system owner: Who manages the tools or data involved?
- 1 frontline user: Who actually does the work every day?
Sometimes one person fills multiple roles. That's fine—just note it.
Why this matters: If you're missing any of these perspectives, you'll have blind spots. You might understand the strategy but not the execution. Or you might see the symptoms but not the root cause.
How to Prioritize Who You Talk To
Not all stakeholders are equally valuable.
Rank them based on:
- Number of decisions they influence: Do they approve budgets, projects, or changes?
- Volume of work they touch: Do they handle hundreds of tasks a week or just a few?
- Number of handoffs they control: Are they a bottleneck between teams?
- Exposure to failure or rework: Do they see where things break most often?
The people who rank highest in these areas should be your top interview priorities.
How Many Interviews Should You Conduct?
It depends on the size of your audit.
Here's a rough guide:
- Small company audit: 5–10 interviews
- Standard company audit: 10–20 interviews
- Large company audit: 20–30 interviews
Never exceed your capacity to synthesize the information. If you conduct 40 interviews, you won't have time to process what you learned. Quality beats quantity.
Who You Should NOT Interview
Some interviews are a waste of time.
Don't interview:
- People with no decision power and no execution role
- People who only report metrics but don't act on them
- People included "for politics" who don't actually touch the work
Why this matters: Every interview takes time—yours and theirs. If someone can't give you useful insight, skip them.
Confirm Availability and Authority
Before you lock in your list, make sure each person:
- Can speak authoritatively about their area
- Understands day-to-day reality (not just the ideal state)
- Can approve or influence change
If someone doesn't meet these criteria, replace them with someone who does.
Create Your Stakeholder Interview List
Pull it all together into one document.
For each person, record:
- Name
- Role
- Department
- Systems they touch
- Processes they own or execute
- Interview priority (High or Medium)
This becomes your interview schedule.
Validate with Your Project Owner
Before you finalize the list, run it by the person leading the project internally.
Ask them one question:
"Who on this list would break things if we missed them?"
If they name someone not on the list, add them. If they say everyone's covered, you're good.
Adjust once. Then lock it.
What You Should Have Now
By the end of this step, you should have:
✅ A complete stakeholder interview list
✅ A locked interview count that matches your capacity
✅ Clear role coverage across strategy, execution, and systems
✅ Priority labels for scheduling (High vs. Medium)
✅ Written confirmation from your project owner that the list is complete
Quality Check: Did You Do This Right?
Before you move on, make sure:
- Every in-scope process has at least one decision voice and one execution voice
- No interview exists without a clear purpose
- Your interview count matches your audit capacity (you can realistically synthesize the insights)
- No stakeholder was added for political reasons
- Your client confirmed the list is complete in writing
Next Step: Once you have your stakeholders selected, you're ready to request the data and documentation you'll need before interviews start.