HomeNewsHow to understand your clients? Guide to Stakeholder Interview.

How to understand your clients? Guide to Stakeholder Interview.

UX Planet — Medium | Talebook

It is not the only designer’s role to take care of a good user experience. The thing that is just as important is bringing UX and business goals together, striking the right balance between those two, that is a key for the project’s success.

A first step of gathering informations about the product we’re working on should always be a stakeholder interview. No matter if our client is a huge corp, young start-up or just a small business — we can always find someone that is a valuable source of informations on the client side. Informations that will be our starting point for further actions.

Deep interview with your client can save you a lot of time

Client is very often an expert in the field we’re stepping into, therefore he sees a lot of issues and needs in the area of the project. Informations that we can get from that person are priceless for our work and let us to quite quickly familiarize with the topic.

Additional profit of interviewing a client is making a direct contact, getting to know him better and understanding his goals and expectations. It will help us to build a better relationship, which is super important for our project to succeed. If we want to have more independence on the next project’s phases, it is important to make our client sure, at the very beginning, that our main goal is to create the best possible final product.

So, how to prepare yourself for this extremely important interview?

Do a preliminary research

Before an interview you have to get to know the market that the project will operate on. Gain as many informations as possible about your client (or the product), his past, goals, mission. Do a research of similar companies on the market to see what are their advantages and — what is even more important — what are their weaknesses. If the company that you’re working on already have a live product, make sure to spend at least a few hours using it. Write down your thoughts and share them with your client during the interview. It will help you to determine your interview goals and ask the right questions.

You can categorize all informations gathered during the research phase into groups, like: hyphotesis, problems, data. The goals is, of course, not to become an expert in the field, which is impossible in that short time. Focus on the basics, that will enable you to have a natural conversation with the client using a language that is adequate to the industry and asking right questions.

Determine goals

Without clearly established goals, it would be really hard to tell if the interview went well.

Write down the most important objectives. It can be elements such as:

  • Getting to know the area of the project
  • Identifying constraints
  • Discover the most important problems

Having your goals written down you can rephrase them into general, basic questions you need to get answers for during the interview. It will help you to create main, more specific questions for your interview, which I will talk more about later on.

Find interviewees

For an interview to succeed you need… an interviewee. In most cases the choice is simple — it’s normally from 1 to 2 founders that create the product.

In bigger organisations choose up to 5 high-level employees, that represent different areas of the company, so you will have a broad spectrum of the project insights.

Prepare questions

Remember that the interview should have a conversational nature, not checking off bullet points. It doesn’t mean though that we should be spontaneous and just let the discussion flow. Having prepared interview scenario we will be able to stay focus on our goals and get a high-quality feedback. To create such scenario you can use Talebook.io, and its embedded questions list.

Intro questions

Always start an interview with a few — 3 to 5 — basic, overall questions about the person you’re interviewing. It will help you to break the ice and get to know a bit more about your client.

You can find a list of sample intro questions in “Basic” section in Talebook.

Sample basic questions.:

  • What are your favourite apps?
  • In what direction this business area is heading in your opinion?
  • How long are you involved in this business

Main questions

Once you have your goals determined and some general questions, add to each of those a couple of more specific questions that you will ask the client. With a help of this list you will be able to remain in control of the interview, even if the person you’ll talk to will turn out to be an enthusiast of a long and complicated stories, not necessarily related to the question asked.

Remember that your behaviour and attitude will be reflected in a quality of the feedback you will get. When you will be well prepared for an interview, it will be easier for you to stay calm and confident.

Using Talebook you can just open the Question List in “Edit” section and choose those questions that fit your interview. Of course you can — and even you should — add a few more questions prepared specifically for the project you work on.

Goal: Getting to know the area the project will operate on.

Sample questions

  • What is your role in this project?
  • What did you do before this?
  • What is this product going to be?
  • Who is this product made for?
  • When is the version we’re designing going to be released?
  • What worries you about this project? What’s the worst thing that could happen during the project?
  • What should this project accomplish for the business?
  • How will you, personally, define success for this project?
  • Is there anyone you think we should talk to, that isn’t on our list? Who?
  • How would you like to be involved in the rest of the project? What’s the best way to reach you?

A few basic rules for preparing questions for an interview:

  • Ask only open questions — that is questions that require more extensive answers. It will protect you from gaining a feedback that won’t be very useful.
  • Don’t ask obvious questions — do your homework first, and respect the time of your interviewee and your own. Asking obvious questions, or those already answered, can discourage the person you talk to from further discussion.
  • Do not suggest an answer — suggestive questions are very common mistakes in conducting interviews, that has a huge impact on feedback’s quality. Keep it in mind and always check your question list to make sure you avoid that mistake.
  • Questions should be clear — if you want to get a clear answer, your questions should be asked in the same way. Ask one question at a time, don’t confuse or overwhelm the person you’re interviewing.
  • Questions should generate: facts, anecdotes, opinions, attitudes, feelings, perceptions, and values.


When you’re all set with question list and basic rules to conduct an interview, now it’s time use them in practice. Now you should ask yourself how you will collect gathered informations. Not paying attention to the person you talk to because of writing down notes is definitely something to avoid.

Here’s a few ideas on how to manage that:

This is how we did it in Talebook

1. Note-taking person

Invite another person for an interview that will help you making notes. It will let you focus on an interview, having detailed notes in the same time. Just make sure to have at least a sheet of paper for yourself — in case you would like to write down your observations during the interview.

2. Audio/video recording

Another way is to record an interview. It will allow you to keep the whole interview archived and you will be able to get back to it later. Also, while analysing recordings you can notice some non-verbal aspects of answers you get — not only opinions but also your client’s emotions towards particular aspects of the project.

Remember to always ask for the permission to record an interview and inform the person interviewed about its purpose.

3. iPad > Laptop

If you will decide to stick with making notes by yourself, it will be better if you’ll choose a smaller device, such as iPad. That way you will avoid an effect of being separated form the person you’re interviewing, and it will be easier for you to stay focused. Also remember to switch on “do not disturb” mode to keep away any distractors!

You can make notes during an interview directly in Talebook. Then you will be able to share them with your collaborators and get back to them in further steps of the project work.

Conducting interview

Here’s a few tips on conducting an interview:

  • Always let your interviewee finish his answer*
    Never interrupt the person that is answering your questions. When he needs more time to think — hold on, don’t try to guess or suggest what the person is going to say. If anything brought to you some additional questions — write them down, you will be able to ask them later.
  • Make follow-ups
    During the interview, when you get an answer, try to wrap it up shortly. If something was not clear to you — ask about it. If you find any answer especially interesting or valuable — mention that. It will assure the other person that you listen to him/her carefully and make an interview become more conversation-like.
  • Summary
    It’s very important that the person you interviewed will be aware of how important his/her feedback was for your product. Thank your interviewee for his/her time and assure that gathered informations will be very helpful. You can also ask for a feedback on an interview.

A stakeholder interview is just a beginning of a long, bumpy road of project work. Make sure that from the very beginning you conduct this process carefully, and that from the first stage of it your work is well organised, planned and documented. For all that you can use the tool dedicated specifically for those purposes, that is Talebook.io, which will support your work through the whole UX process.


How to understand your clients? Guide to Stakeholder Interview. was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.

Featured articles on Prototypr: