Stakeholder & Customer Interviews
Good digital decisions depend on understanding both the people inside the organisation and the people using its products, services and platforms.
Stakeholder and customer interviews help bring those perspectives into the project early. They give teams a clearer view of business priorities, customer expectations, operational constraints and the issues that may not be visible through analytics or internal discussion alone.
At Bright Labs, interviews are often used at the beginning of strategy, research and design engagements to build a stronger evidence base before key decisions are made.
Understand stakeholder perspectives
Stakeholders often see the same digital experience from very different angles.
Leadership may be focused on growth and efficiency. Marketing may care about lead generation and content. Customer service teams may see recurring issues that are not visible elsewhere. Technology teams may be managing legacy systems or integration constraints that affect what is possible.
Stakeholder interviews help bring those perspectives together.
We typically use them to explore:
- business objectives and priorities
- known customer or user issues
- internal processes and operational pain points
- platform limitations
- content challenges
- technical constraints
- stakeholder expectations
- previous project learnings
- measures of success
This can be particularly useful in larger organisations where important knowledge is spread across different departments.
The aim is to identify where there is alignment, where views differ and which assumptions need to be tested further.
Hear directly from customers and users
Customer interviews add another layer of evidence. They help uncover how people actually experience a service, website, product or process, including the points where expectations are not being met.
Interviews can explore areas such as:
- what customers are trying to achieve
- how they currently complete key tasks
- where they experience friction or confusion
- what influences their decisions
- what information they need
- how they move between channels
- what they value most
- where current experiences fall short
The format depends on the research question.
Some projects need broad exploratory interviews to understand behaviours and motivations. Others are more focused, such as exploring a particular journey, testing a proposition or understanding issues within an existing platform.
The value comes from hearing the language customers use and understanding the context behind their behaviour.
Turn interview findings into useful direction
Interviews generate a lot of information, but the value comes from how that information is interpreted and applied. We look for recurring themes, points of tension, unmet needs and areas where internal perceptions differ from customer experience.
The findings can help inform:
- website or digital strategy
- audience priorities
- customer journey mapping
- information architecture
- content requirements
- feature prioritisation
- service design
- user experience decisions
- digital roadmaps
Where appropriate, interview findings can also be combined with analytics, usability testing or broader research to give a more complete picture.
For example, analytics may show that users are abandoning a particular journey. Interviews can help explain why. Stakeholders may believe one audience is most important, while customer research may suggest another group has greater unmet needs.
This type of evidence helps teams make decisions with greater confidence.
Create a more grounded brief
Stakeholder and customer interviews are most useful when they influence the work that follows. We use the findings to help shape priorities, clarify requirements and identify the questions that still need to be answered.
For a website project, that might mean refining audience needs, identifying important content gaps or understanding where the current experience is creating frustration.
For a broader digital initiative, it may mean identifying operational issues, service gaps or opportunities for improvement across several touchpoints.
Interview findings also help create a clearer shared brief across internal teams and project partners. Instead of relying on assumptions or the loudest opinion in the room, decisions can be linked back to what stakeholders and customers have actually said.
That gives strategy, design and technology teams a stronger foundation for the next stage of work.