Skip to content

People-centered Design

  • People?
  • Centered?
  • Design?
  • Experience
  • Quality?
  • Data
  • People?
  • Centered?
  • Design?
  • Experience
  • Quality?
  • Data

Writing a good conversation guide

The trick to creating a good conversation is having a good conversation guide and then being prepared to be authentic and allow the conversation to wander wherever it goes. One way to assess the authenticity of a conversation would be in terms of the number of times you (and your conversationalist) are surprised by it, or find new ideas in it.

In an authentic conversation the participants are equally able to lead (or block) any avenue of exploration. Your conversation guide must then provide you with a good idea of the avenues you want to go down and why.

To get there you need to move away from your product / commercial / technical focus and reframe your goals in terms that make sense to your user or customer.

Some Principles

  1. Think like a detective. Solicit spontaneous, unprompted comments first. Plan out how you are going to gradually move from open-ended to explicit, direct questions.
  2. Focus on specifics. “What did you do yesterday?” will get better conversation than “What do you do on a typical day?”
  3. Take the person to the relevant context (at the very least in their imagination) – “tell me about the best gaming experience you’ve ever had?”
  4. Like an identity parade, ensure you have multiple alternatives for them to consider – not just your product concept of interest.

The steps to getting there

  1. List out the decisions that you need to be able to make from a product / business / technical perspective.
  2. For each of these decisions consider what  questions you would need to know the answer to in order to make the right decision.
  3. These questions are almost certainly not meaningful to your users / customers and so the next step is to work out what there is in their perspective that might help you work out the answers to your questions.  In effect, you need to treat the conversation as data gathering that enables you to answer your questions, and not a chance to ask them what the answers are.
  4. This should lead you to a list of areas to explore and the final step is to capture ways to frame these topics so that they seem spontaneous. 

Some tactics

  1. If you have a question that you really need to ask, then find a number of paths that might produce a spontaneous “answer” before you ask the explicit question – once you ask the explicit question, you only know their answer, but you have little data to help you decide if they consider it important.
  2. If you have multiple people (users or customers, or other) in the conversation, then make the conversation happen between them, rather then through you. Maybe even find an excuse to leave the room for a few moments (assuming you are recording the conversations).
  3. If you need to offer two possibilities for their consideration, distance your self from the ideas with lines such as “In other conversations I have heard people state that they would like <x> – does that make sense to you?” “Can you explain what you think they might have meant?”

Examples

Loading...

ROLM: The digital PBX

End of content

No more pages to load

Opinions

Loading...

Don’t write interview guides

If you are going to meet with users and do some qualitative research then I hope you have had it drilled in to you to carefully construct an interview guide. Now, I ask you to remember that lesson, but throw away the interview guide!

End of content

No more pages to load

Themes

Loading...

Making better things, or making things better?

Are we (UX, design and product management professionals) expending enough energy on reflecting on what works and what doesn't. Today it still seems to be the case that people argue for the financial (commercial) benefits of UX or of design, without addressing the question about the quality of that design

What is the role for data, analytics and AI?

Increasingly the experiences we are designing products for entail the collection and sharing of lots of data. As well as the broader questions about who owns the data, there is also the need for the presentation of data to be designed and it isn't obvious that traditional design methods address

End of content

No more pages to load

People-centered Design
  • People?
  • Centered?
  • Design?
  • Experience
  • Quality?
  • Data
  • People?
  • Centered?
  • Design?
  • Experience
  • Quality?
  • Data

info@peoplecentereddesign.org

© 2025 David Gilmore