Skip to content

People-centered Design

  • People
  • Design
  • Business
  • More …
    • Thinking about AI
    • Prototyping UX
  • People
  • Design
  • Business
  • More …
    • Thinking about AI
    • Prototyping UX

Business and technology

How do all these other constraints fit in with people centered design?

Product design is a complex balancing of conflicting constraints and what works for a product idea in one company might be very different than would work for the same idea in a different company. Given that – does it really make sense to say the design is centred on anything?

The answer to this goes hand-in-hand with the use of ‘people’ as the representative of that centre. The purpose of good design is to make something that fits well into its world and at the centre of that world are all the people that might use, interact or be affected by it. By saying ‘people-centred’ we are avoiding a declaration of which people are at the centre, but fully embracing the idea that the needs of some people need to explicitly drive the design.

A startup might have limited funds and therefore pressure to be earning revenue sooner than a well-established company with deep pockets. In this context one wants an experience strategy that is about delivering an experience quickly and then growing it over time; which in turn makes it critical to identify the fundamental core value of the product concept and the people who will most embrace that value, and that can define the starting point for the growth to mass market.

Alternatively a technological breakthrough may be the core fundamental idea (and IP that must be protected) and a product needs to be launched to claim the idea and the IP.  

We can think of these different possibilities as different starting points for the people-centred design process – starting in commerce or technology, but then rapidly progressing repeatedly through technical, experiential and commercial explorations until something is defined enough to be the first release.

Sometimes it is easier to see where quality goes astray – it is common in medical domains for a product to start out being built for one hospital, or even for one team at one hospital. I these cases the very existence of the product is all that matters – the product is being built for themselves to use and it is in many cases following a good user-centred, or people-centred approach. The complex interactions between this new product and existing products is easily understood and addressed since all the users are in the same context. However, the next step is when someone decides that the product should be commercialised and then, when it looks like a finished product exists, there are suddenly numerous other workflows and tools that the product must accommodate in order to be successful.

A map of whose journey?

Journey maps, experience roadmaps, customer experience journeys are all common tools nowadays, but a key question that needs to be asked is "whose journey are we mapping?" and is that the right person?

Motion management in Radiotherapy

This is another good example of how having the data is only the starting point. Presenting the user with the relevant data in a way which is safe and usable is a much deeper design problem that is usually appreciated.

Racing data

Kevin Richardson (Infragistics) gave a talk at UCDUK15 about the design of data presentation for motor bike racing, which provided a great example of how having the data is only the starting point of the design process.

The Compelling Touchscreen

THE HAZARDS OF USER DATA AND FEEDBACK …

It seems almost sacrilegious to say it, but I think it is really important to maintain significant caution around data obtained from user feedback, testing or group discussions. Too often I hear people proudly say that all their design decisions are based on feedback from users, or one hears leadership asking that all the design decisions be based on documented data from user feedback. These attitudes are, of course, well-founded, but at the same time they are seriously misguided – and for a number of different reasons …

GE Digital Power

In creating digital HMI for a power plant, it is easy to find constraints pulling in different directions – towards simplification of the HMI and the use of fewer, smaller screens, versus the presentation of more data across more, larger screens. Either is a possible experience that can be designed for, but the whole team needs to know which experience they are aiming for.

What is the role for data and AI?

Making things better?

Design?

Experience is infinite

Which People?

  • Welcome
  • What’s New?
  • About
  • Welcome
  • What’s New?
  • About

info@peoplecentereddesign.org

© 2026 David Gilmore