Stakeholder Interview Template for Discovery

Six to ten is typical for a major initiative. Cover each function that will be affected (exec, sales, CS, support, engineering, design). For smaller projects, 4-5 may suffice. The goal is not to interview everyone in the company but to get at least one perspective from each relevant function.

Send them the 3 most important questions by email or Slack and ask for written responses. A 5-minute async reply is better than no input at all. For high-influence stakeholders (VP+), ask their EA to find a 15-minute slot. Frame it as: "I want to make sure your priorities are reflected in our plan."

Yes, always. Send a summary of shared priorities, conflicting assumptions, and proposed next steps. This demonstrates that you took their input seriously and gives them a chance to correct misunderstandings before you act on the findings. It also builds trust for future discovery cycles. The [Stakeholder Management Handbook](/stakeholder-guide) covers communication strategies in detail.

Acknowledge their solution but redirect to the underlying problem. "That is a great idea. Help me understand the problem it solves so I can make sure we address it fully." Often, the specific solution they propose is one of several valid approaches. By understanding their underlying need, you can evaluate all options and may find a better path. Document their proposed solution in your notes and include it as a candidate during ideation.

At the start of each major initiative, or at least once per quarter. Stakeholder priorities shift as the business evolves. Interviews from 6 months ago may no longer reflect current constraints or strategic direction. A quick 15-minute "check-in" interview format works well for recurring alignment. ---