Website Redesign Stakeholder Interview Questions

Website redesign stakeholder interview questions are the most undervalued tool in a project manager's discovery kit.

The quality of a redesign is largely determined before design begins, by the quality of the questions asked and the honesty of the answers they surface.

Bad discovery produces beautiful sites that solve the wrong problems. Good discovery ensures that every design decision connects to a real business goal, a real user need, or a real constraint.

This guide gives you the full question set and the process to use it effectively.

Key Takeaways

• Interviews surface alignment gaps: Discovering that decision-makers define success differently is a finding that saves months of rework if caught before design begins.
• Different roles provide different intelligence: Sales knows prospect objections, service knows user struggles, and executives know company direction. Each source is irreplaceable.
• Constraints are as important as goals: Budget, timeline, technical limits, and internal politics must be surfaced in discovery or they become production surprises.
• Good interviews enable good briefs: The creative brief, information architecture, and content strategy are only as strong as the stakeholder input that informed them.
• Record everything verbatim: Stakeholder language about customers and problems is often the best raw material for website copy and should not be lost in summary notes.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

How Stakeholder Interviews Fit into the Redesign Process

Stakeholder interviews are discovery infrastructure, not a formality. They must happen before strategy documents, wireframes, or any design output is produced.

Discovery Phase Positioning

• Phase sequence: Discovery comes first: before strategy, before design, before development, before QA. Interviews are the opening act of discovery.
• Prerequisite to brief: No creative brief, information architecture, or content strategy should be finalized before stakeholder interviews are synthesized.
• Timing matters: Interviews conducted after early wireframes exist will be biased by what stakeholders see rather than what they actually need.

Who Should Be Interviewed

• Executive sponsor: Strategic goals, budget authority, and the success criteria that matter to leadership need direct input from decision-makers.
• Marketing and sales leaders: Brand and audience perspective from marketing, plus prospect objections and customer insights from sales.
• Customer service and IT: Service reveals what users struggle with on the current site. IT surfaces technical constraints that will affect build options.

Interview Format Options: One-on-One vs. Group Sessions

• One-on-one advantages: Individual interviews produce candid, focused responses without the groupthink or hierarchy effects that suppress honest answers in group settings.
• Group session advantages: Workshop-style sessions are more time-efficient and build shared alignment, but may suppress dissenting views from junior stakeholders.
• Best practice: Use one-on-one interviews for executives and stakeholders with strong opinions, and group sessions for alignment and synthesis activities.

Review the kickoff meeting agenda guide for how stakeholder interviews connect to the broader project kickoff structure.

Preparing for Stakeholder Interviews

Thorough preparation is what separates interviews that generate insight from interviews that generate polite noise. The discovery phase in website redesigns is where this preparation pays off.

Pre-Interview Research and Preparation

• Analytics review: Study the current site's analytics before each interview so you can ask informed questions about pages, traffic, and conversions.
• Role-specific preparation: Identify the one or two areas where this specific stakeholder's perspective is most valuable and build your questions around those areas.
• Prior research review: Read any existing strategy documents, brand guidelines, or previous redesign briefs before each session to avoid asking questions that have already been answered.

Setting the Right Interview Framing

• Clear purpose statement: Open with why you're there, how their input will be used, and approximately how long the interview will take.
• No wrong answers framing: Explicitly tell stakeholders there are no wrong answers and that candid input is more valuable than polished input.
• Reduce defensiveness: Framing the interview as a listening exercise, not a performance review of the current site, produces more honest assessments of problems.

Recording and Synthesis Tools

• Transcription tools: Otter.ai and Rev provide automated transcription that preserves the exact language stakeholders use, which is often more valuable than summaries.
• Synthesis approach: Process multiple interview transcripts into patterns and insights, not a collage of quotes. Look for where perspectives converge and where they diverge.

Questions About Goals and Requirements

Capturing redesign requirements completely starts with asking the right questions about what success actually looks like for each stakeholder.

Business Goals and Success Metrics Questions

• 12-month success question: "What does success look like for this project in 12 months?" surfaces concrete, measurable goals that become brief anchors.
• Single improvement question: "If you could only improve one thing about the current site, what would it be?" forces prioritization that reveals what each stakeholder actually cares about.
• Investment justification question: "How will leadership know this redesign was worth the investment?" connects design decisions to the business case from the start.

Audience and Customer Questions

• Ideal customer question: "Who is the ideal customer for this specific service?" produces audience specificity that generic personas miss.
• First visit awareness question: "What does a typical customer know about us when they first visit the site?" reveals the gap between assumed and actual visitor intent.
• Sales intelligence question: "What are the top three questions sales gets from new prospects?" produces the most valuable content direction of any question in the set.

Functional and Technical Requirements

• Must-have features question: "Are there specific features or functions the new site must have?" surfaces requirements that are often assumed rather than stated.
• Integration requirements: "What CRM, booking tool, or ecommerce integrations need to be maintained or added?" prevents integration surprises during development.
• Compliance requirements: "Are there hosting, security, or compliance requirements we need to know?" catches GDPR, HIPAA, or accessibility mandates before architecture is committed.

Questions About Current Site Performance

Preparing for a website redesign requires honest assessment of what the current site is and is not doing well.

Performance and Satisfaction Questions

• Most common complaint: "What's the most common complaint you hear about the current site?" surfaces the issues stakeholders hear repeatedly but may not escalate formally.
• What users can't find: "If a customer couldn't find something on the site, what would it usually be?" reveals navigation and information architecture problems from lived experience.
• Competitive comparison: "What do competitors' sites do better than ours right now?" gets stakeholders to articulate the gap the redesign needs to close.

Content and Messaging Feedback Questions

• Accuracy check: "Does the current site accurately reflect what we actually do and who we serve?" often surfaces significant gaps between the site's messaging and the business's current reality.
• Missing information: "Is there important information missing from the current site?" identifies content gaps that stakeholders have noticed but the site team has not addressed.
• Referral test: "When you send someone to the site, what do you hope they find, and do you think they find it?" is one of the highest-value questions in the entire set.

Analytics and Data Awareness Questions

• Traffic awareness: "Do you know what pages get the most traffic?" tests whether data is actually informing stakeholder opinions about the site.
• Conversion awareness: "Do you have any sense of the current conversion rate?" often reveals that decision-makers are making significant investment decisions without baseline data.
• Research history: "Has any user testing or customer research been done on the current site?" identifies existing insights that should inform the redesign rather than be ignored.

Questions About Stakeholder Expectations and Governance

Governance questions are the ones most often skipped and the ones most likely to derail a project mid-execution. The redesign communication planning framework depends on getting clear answers here.

Decision-Making and Approval Process Questions

• Final approval authority: "Who has final approval over design decisions?" is the most important governance question in the entire interview set.
• Hidden stakeholders: "Are there stakeholders not in this conversation who will need to weigh in?" surfaces the decision-makers who will appear at review gates and cause surprises.
• Feedback turnaround: "How quickly can we expect feedback on design deliverables?" sets the realistic timeline for design review cycles before the project even starts.

Budget and Timeline Expectation Questions

• Approved budget: "Has a budget been approved for this project?" distinguishes explorations from committed projects and prevents scoping work against an undefined constraint.
• Hard deadline check: "Is there a conference, campaign, or event that the launch needs to align with?" catches external timeline constraints that will dominate the project schedule.
• Timeline success definition: "What would have to be true for you to consider this project a timeline success?" reveals whether the timeline expectation is realistic before commitment.

Risk and Concern Questions

• Biggest worry: "What keeps you up at night about this project?" surfaces the unstated risks that stakeholders are thinking about but have not yet raised in formal meetings.
• Previous redesign failure: "Have you been through a website redesign before? What went wrong?" produces the most useful project risk intelligence available at the discovery stage.
• Sacred cows: "Is there anything about the current site that must stay exactly as it is?" identifies constraints that will block design directions before those directions are invested in.

Translating Interview Findings into the Creative Brief

Creative brief writing after discovery is only possible when interview synthesis is done rigorously and honestly.

Synthesis: Finding Patterns Across Interviews

• Alignment identification: Where stakeholders converge on goals, problems, or priorities, those points become the safe anchors of the creative brief.
• Divergence identification: Where stakeholders fundamentally disagree, that divergence must be resolved through a facilitated session before strategy is committed to paper.
• Unexpected insights: Patterns that no individual interview would have surfaced become some of the most valuable findings in the synthesis process.

Using Stakeholder Language in the Creative Brief

• Verbatim language preservation: The specific words stakeholders use to describe customers, problems, and value are often the best copy on the brief and eventually the site.
• Voice authenticity: Language sourced directly from stakeholder interviews sounds more authentic in copy than agency-drafted positioning language, because it comes from people who live the business.

Presenting Interview Findings Back to Stakeholders

• Alignment framing: Present areas of convergence as shared foundation, not as unanimous consensus. Acknowledge that individual perspectives contributed to the shared picture.
• Productive divergence: Frame disagreements as productive input that will improve the brief rather than problems to be managed or concealed.
• Resolution before strategy: Do not commit strategy to paper until the divergences identified in interview synthesis have been explicitly resolved by the stakeholder group.

Conclusion

Website redesign stakeholder interviews are the highest-leverage investment in a project's success. An hour of good questions at the start prevents months of misaligned revisions, scope disputes, and rework at the end.

Before your next redesign kickoff, identify the five most important stakeholders and draft three open-ended questions for each based on their specific role.

The interview structure clarifies itself from there, and the findings will shape every design decision that follows.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Starts Every Redesign with a Discovery Process That Gets It Right

LOW/CODE Agency treats discovery as the most important phase of a redesign, not a box to tick before design begins.

Every engagement starts with structured stakeholder interviews, user research, and data analyzis that inform every decision downstream.

We work as a strategic product team, not a dev shop. That means we design against real business goals and real user needs, not assumptions.

Our discovery process surfaces the alignment gaps, constraints, and insights that make the difference between a site that looks good and a site that performs.

• Structured stakeholder interviews: Facilitated one-on-one sessions with each key decision-maker before any strategy or design work begins.
• User research integration: Heatmap analyzis, session recordings, and analytics review combined with stakeholder input for a complete discovery picture.
• Analytics and data analyzis: Baseline traffic, conversion, and SEO data reviewed and synthesized before brief writing begins.
• Discovery synthesis report: All stakeholder interview findings synthesized into a clear summary of alignment, divergence, and priority insights.
• Creative brief development: Discovery findings translated directly into a structured brief that anchors all design decisions to validated business goals.
• Stakeholder alignment facilitation: Group synthesis sessions to resolve stakeholder divergence before strategy is committed, preventing revision cycles later.
• Post-discovery roadmap: A clear project roadmap produced from discovery that reflects the actual scope, priorities, and constraints of the engagement.

We have delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Our process starts with listening.

Partner with a discovery-led website redesign team that treats stakeholder alignment as the foundation of great design. Start with a scoping call to see how our discovery process works in practice.