Stakeholder Discovery Question Bank by Persona

Use the right section for whoever is in the room. The questions are ordered open-to-probing. You don't need to ask all of them. Stop when you know what you need.

---

1. End-User

What they care about: Day-to-day ease, not being made to look incompetent, keeping their current workflow from breaking.

What they fear: A new tool that creates more work, a rollout that ignores how the job actually gets done, being blamed when it goes wrong.

When to skip or shorten: If the end-user has no formal input into the decision, keep it to 2-3 questions. Don't over-invest, but don't ignore them; they surface blockers that champions often miss.

1. "Walk me through a normal [day/week] when [the problem we're discussing] comes up. What does that actually look like?"
2. "Where does the current process slow you down the most?"
3. "When [the current tool/approach] doesn't work, what do you end up doing instead?"
4. "If you could change one thing about how [this task] works today, what would it be?"
5. "What would make a new solution harder to use than what you've got now?"
6. "Has anything like this been rolled out to your team before? How did that go?"
7. "Who else on your team would have a strong view on whether this works or not?"
8. "If a new solution made your role easier but required you to change how you log/track/report [X], would that be an issue?"

---

2. Champion

What they care about: Looking good internally, building credibility with their leadership, getting a win they can own.

What they fear: Staking their reputation on a vendor who underdelivers, losing internal sponsorship mid-process, being outflanked by a colleague who prefers a competitor.

When to skip or shorten: Never skip. The champion is your internal salesperson. If you don't have one, stop here and work out why.

1. "What made you decide to bring this problem forward now?"
2. "When you picture this going well, what does success look like for you personally, not just for the business?"
3. "Who else in the business has a strong opinion about this decision, and where do they stand?"
4. "If we get to the end of this process and the answer is yes, who needs to have been part of that journey?"
5. "What would make it hard for you to get internal support for moving forward?"
6. "Have you bought something like this before? What happened?"
7. "If the final decision came down to two equally good options, what would tip it?"
8. "What does your [manager/CFO/board] need to see to feel comfortable with this?"
9. "Is there anyone in the business who would prefer you didn't solve this, or who'd prefer a different solution?"
10. "What would make you look back on this and wish you'd gone a different way?"

---

3. IT / Technical Evaluator

What they care about: Security, integration, maintenance burden, not inheriting a support nightmare.

What they fear: Creating a dependency on a vendor who can't deliver, being held responsible for a breach or an outage, adding complexity to an already stretched infrastructure.

When to skip or shorten: Shorten if IT is advisory only and has no veto. Lengthen if they can block the deal, which is more common than most reps expect.

1. "What does your current tech stack look like in the area we're talking about?"
2. "What integration requirements would any new solution have to meet from day one?"
3. "What's your security review process, and what are the hard requirements we'd need to meet?"
4. "Who owns the decision on whether a new tool gets added to your approved vendor list?"
5. "What's your typical implementation timeline expectation for something like this?"
6. "What have you seen go wrong in past rollouts that we should know about?"
7. "Do you have a preference on [cloud vs on-premise / API vs native integration / SSO requirements]?"
8. "If something went wrong post-implementation, who's on the hook internally?"
9. "What would make you comfortable recommending this to whoever makes the final call?"

---

4. Finance / CFO

What they care about: Payback period, total cost of ownership, risk to budget, whether this is a cost or a revenue driver.

What they fear: Approving spend that doesn't deliver a measurable return, being caught out by hidden costs, committing to multi-year contracts in an uncertain environment.

When to skip or shorten: Never skip if they're in the room. Even if they say "I'm just here to understand the numbers", they often hold informal veto power.

1. "How does your business case approval process work for something in this budget range?"
2. "What ROI or payback period would make this a straightforward approval?"
3. "Are you looking at this as a cost reduction, a revenue enablement, or something else entirely?"
4. "What's the cost of doing nothing over the next 12 months? Has anyone modelled that?"
5. "What other budget commitments is this competing against right now?"
6. "Are there any constraints on payment structure that I should be aware of, annual vs monthly, multi-year, and so on?"
7. "What would need to be true about the numbers for you to feel confident recommending this?"
8. "If the headline number works but there are implementation costs on top, how does that change the conversation?"
9. "Who else looks at the financials before a decision like this gets signed off?"

---

5. Legal

What they care about: Contract risk, liability exposure, data handling, compliance with relevant regulation.

What they fear: Signing off on something that creates liability, a data incident traced back to a vendor they approved, terms that don't hold up if things go wrong.

When to skip or shorten: Skip detailed questioning if legal is a rubber-stamp step at the end. Engage early and specifically if data, IP, or regulated information is involved.

1. "What's your standard contract review process and typical timeline?"
2. "Are there specific clauses your team always pushes back on, limitation of liability, IP ownership, data processing terms?"
3. "Do you use your own paper, or are you open to working from ours?"
4. "What data will [our solution] touch, and what compliance frameworks apply, GDPR, ISO 27001, sector-specific regulation?"
5. "Have you had a vendor contract go badly before? What happened, and what did you put in place as a result?"
6. "Who in legal has final sign-off, and do they need to be in any of our conversations directly?"
7. "Are there indemnification or insurance requirements we should know about upfront?"
8. "Is there a procurement or legal checklist I can get early so we're not finding blockers at the finish line?"

---

6. Procurement

What they care about: Process compliance, competitive tension, getting the best commercial terms on record.

What they fear: Being bypassed, being blamed for a bad deal, a vendor relationship that creates problems later.

When to skip or shorten: Shorten to 3-4 questions if procurement is process-only and the economic buyer has already decided. Engage fully if procurement can reopen the vendor shortlist.

1. "What does your formal vendor selection process look like from here?"
2. "Are you running a competitive tender, or is this a directed purchase at this point?"
3. "What criteria are you formally scoring vendors on?"
4. "What's the biggest thing that's slowed down or killed a procurement process like this before?"
5. "Who has final commercial sign-off, you or someone above you?"
6. "Is there a preferred vendor list I need to get onto, and what does that involve?"
7. "What does a good vendor relationship look like to you, not the product, the working relationship?"
8. "What would make this the easiest procurement process you've run this year?"

---

7. COO / Operations

What they care about: Efficiency, scalability, whether this creates or removes operational drag, impact on the team.

What they fear: A solution that breaks existing processes, a rollout that consumes their team's time, a vendor who disappears after go-live.

When to skip or shorten: Don't shorten if they own the process being changed. They're often the most practical gatekeeper in the building.

1. "What does the operational process look like today in the area we're discussing?"
2. "Where are the biggest points of failure or inefficiency right now?"
3. "If this works as intended, what does that free your team up to do?"
4. "What's your biggest concern about the implementation and change management side?"
5. "How does your team typically respond to new tools or process changes?"
6. "What would good post-implementation support look like to you?"
7. "Are there operational dependencies, other teams, systems, third parties, that we'd need to account for?"
8. "What would tell you, 90 days in, that this was the right decision?"
9. "What's the realistic capacity your team has to be involved in implementation right now?"

---

8. CEO / Executive Sponsor

What they care about: Strategic outcomes, competitive position, whether this moves the business forward or just fixes a small problem.

What they fear: Wasting money on something that doesn't shift the needle, being associated with a failed initiative, their team being distracted by a low-value project.

When to skip or shorten: Keep it tight. CEOs tolerate 3-4 sharp questions, not 10 open-ended ones. Get to the strategic frame quickly and let them talk.

1. "What's the strategic priority this sits under for you personally?"
2. "If this works exactly as intended, what changes for the business in 12-24 months?"
3. "What's the cost of this problem staying unsolved for another year?"
4. "How does this rank against the other things competing for your attention and budget right now?"
5. "Is there a version of this that's a small fix, and a version that's a bigger transformation? Which one are you actually trying to do?"
6. "Who do you need to be confident before you're comfortable saying yes?"
7. "What would make you look back in two years and say this was the right call?"
8. "What's your instinct on this so far?"

---

Quick-Reference: Persona Influence Grid