The Stakeholder Interview (The 30,000-Foot View)

This is where the audit really begins.

You've gathered data and identified stakeholders. Now it's time to talk to the people running the business and get their view from the top.

This interview is about understanding:

What leadership thinks the problems are
What goals they're trying to hit
What's keeping them up at night
Where they see the biggest opportunities

You're looking for the 30,000-foot view—the strategic context that shapes everything else.

Why Start with Leadership?

Because strategy defines what matters.

If you dive into process details without understanding business goals, you'll waste time mapping things that don't matter. Leadership tells you what success looks like, what constraints exist, and what problems are worth solving.

What You're Trying to Learn

1. Role & Team Overview

Ask questions like:

"Can you describe your role and your team's primary responsibilities?"
"What are the main goals or KPIs your team is responsible for?"
"Could you walk me through your team's structure?"

Why this matters: You're mapping accountability. When something breaks, who owns fixing it?

2. Core Processes & Workflow

Ask questions like:

"What are the most critical processes your team manages?"
"Where do you see the biggest bottlenecks or delays?"
"Which tasks consume the most time or resources?"

Why this matters: If leadership already knows a process is a problem, that's a signal.

3. Tools & Technology

Ask questions like:

"What are the main systems or tools your team relies on?"
"What are your biggest frustrations with your current tech stack?"
"Are there important processes happening outside your main software—in spreadsheets, email, or manual documents?"

Why this matters: The tools people complain about are where AI can help. Processes in spreadsheets are automation gold mines.

4. Pain Points & Strategic Challenges

Ask questions like:

"What are the biggest challenges your team is facing right now?"
"If you had a magic wand, what's the one problem you would solve overnight?"
"What's preventing your team from being more efficient?"

Why this matters: This is where you hear the real frustrations—not the sanitized annual report version.

5. Future Vision

Ask questions like:

"Where do you see the biggest opportunities for improvement?"
"How does your team respond to new technology? What makes a new tool successful versus resisted?"

Why this matters: If the team rejects new tools, you need to know why. If there's political resistance to change, you need to navigate that.

What You Should Walk Away With

By the end of this interview:

✅ Clear understanding of goals and KPIs

✅ List of most critical processes

✅ Documented tools and pain points

✅ Insight into how they respond to change

✅ Baseline for comparing leadership's view versus ground reality

Next Step: Once you have the leadership perspective, talk to the people actually doing the work.

Rather have experts handle this? Learn how we work → OpsSystem.ai

This is where the audit really begins.

You've gathered data and identified stakeholders. Now it's time to talk to the people running the business and get their view from the top.

This interview is about understanding:

What leadership thinks the problems are
What goals they're trying to hit
What's keeping them up at night
Where they see the biggest opportunities

You're looking for the 30,000-foot view—the strategic context that shapes everything else.

Why Start with Leadership?

Because strategy defines what matters.

What You're Trying to Learn

1. Role & Team Overview

Ask questions like:

"Can you describe your role and your team's primary responsibilities?"
"What are the main goals or KPIs your team is responsible for?"
"Could you walk me through your team's structure?"

Why this matters: You're mapping accountability. When something breaks, who owns fixing it?

2. Core Processes & Workflow

Ask questions like:

"What are the most critical processes your team manages?"
"Where do you see the biggest bottlenecks or delays?"
"Which tasks consume the most time or resources?"

Why this matters: If leadership already knows a process is a problem, that's a signal.

3. Tools & Technology

Ask questions like:

"What are the main systems or tools your team relies on?"
"What are your biggest frustrations with your current tech stack?"
"Are there important processes happening outside your main software—in spreadsheets, email, or manual documents?"

Why this matters: The tools people complain about are where AI can help. Processes in spreadsheets are automation gold mines.

4. Pain Points & Strategic Challenges

Ask questions like:

"What are the biggest challenges your team is facing right now?"
"If you had a magic wand, what's the one problem you would solve overnight?"
"What's preventing your team from being more efficient?"

Why this matters: This is where you hear the real frustrations—not the sanitized annual report version.

5. Future Vision

Ask questions like:

"Where do you see the biggest opportunities for improvement?"
"How does your team respond to new technology? What makes a new tool successful versus resisted?"

Why this matters: If the team rejects new tools, you need to know why. If there's political resistance to change, you need to navigate that.

What You Should Walk Away With

By the end of this interview:

✅ Clear understanding of goals and KPIs

✅ List of most critical processes

✅ Documented tools and pain points

✅ Insight into how they respond to change

✅ Baseline for comparing leadership's view versus ground reality

Next Step: Once you have the leadership perspective, talk to the people actually doing the work.

Rather have experts handle this? Learn how we work → OpsSystem.ai