Think about how Spotify changed the way people listen to music. Instead of buying individual albums or managing a personal music library, listeners could access millions of tracks, discover new artists, and create playlists that matched their preferences.
Or consider Fitbit. It made health and activity tracking part of everyday life by bringing information such as steps, heart rate, and sleep patterns into an experience people could easily access.
These products solve very different problems, but they have something in common: they make complex technology useful in everyday situations.
That thinking sits at the heart of human-centred product design, an approach that starts with understanding people's needs, behaviours, motivations, and circumstances before deciding what to build.
For businesses developing digital products, the challenge is often deciding which problems deserve attention and how to solve them in ways people will actually find useful.
What is human-centred product design?
Human-centred product design is an approach to developing products and services around the people who will use or be affected by them.
It involves understanding real-world needs, exploring possible solutions, testing ideas with people, and improving the experience based on what is learned.
The approach is closely connected to design thinking, where empathy, experimentation, and problem-solving guide decisions throughout the design process.
Consider a digital banking app. A team might begin by identifying the features competitors offer. Human-centred design takes the investigation further.
Why do customers abandon an application midway? Which financial terms are difficult to understand? What makes someone hesitate before transferring money?
These questions reveal problems that interface improvements alone may not solve.
The objective is to create products that people can understand, trust, and use with confidence, while meeting the organisation's business goals.
Why human-centred design matters in product development
A product can be technically sound and still struggle to gain adoption.
Features may work as intended, but customers might find them difficult to discover. A process may seem straightforward to the development team but require too much effort from someone using it for the first time.
Human-centred design helps teams identify these gaps before they become expensive product decisions.
By involving users throughout development, businesses can better understand where friction occurs, which capabilities matter most, and how people respond to proposed solutions.
This can support several business outcomes:
- Better product adoption: People are more likely to use products they can understand and navigate.
- Reduced development risk: Early research and testing help identify assumptions before teams invest heavily in building them.
- Improved customer experience: Products can address the tasks and challenges people encounter in real situations.
- More informed prioritisation: Teams can focus development effort on problems with demonstrated user and business value.
- Stronger product decisions: Customer feedback becomes part of the decision-making process instead of an afterthought.
These benefits depend on how effectively teams apply the research. Human-centred design does not guarantee commercial success, but it gives businesses a more reliable basis for deciding what to build.
Human-centred design vs. user-centred design: What's the difference?
Human-centred design and user-centred design are closely related approaches, and the terms are often used interchangeably.
Both rely on research, usability testing, and iterative development to improve the experience of people interacting with a product.
The distinction is largely one of emphasis.
User-centred design typically focuses on the needs, goals, and tasks of the people directly using a product.
Human-centred design can take a broader view, considering the emotional, social, environmental, and organisational circumstances surrounding an experience, including people indirectly affected by the product.
Take a healthcare application, for example.
A user-centred approach might focus on helping patients book appointments more easily. A broader human-centred approach could also consider caregivers, healthcare professionals, accessibility requirements, and the circumstances that influence how patients access care.
Neither approach is inherently better. The important thing is understanding the people involved and applying that knowledge throughout the design process.
The three phases of the human-centred product design process
Human-centred product design is often explained through three connected phases: inspiration, ideation, and implementation.
Although these phases provide a useful structure, product teams rarely move through them in a perfectly straight line. Testing may reveal a new problem, requiring another round of research or a different solution.
1. Inspiration: Understand people before defining the problem
The inspiration phase begins with understanding who the product is for and what people are trying to achieve.
Product teams conduct user interviews, observe behaviours, study existing journeys, and speak with relevant stakeholders.
The purpose is to understand the problem before committing to a solution.
Imagine a fintech company discovering that customers frequently abandon its loan application.
The immediate assumption might be that the form is too long. But research could reveal something different: customers are uncertain about eligibility, confused by repayment terms, or uncomfortable sharing financial information.
Each finding points towards a different design decision.
Research methods can include contextual interviews, usability assessments, journey mapping, and behavioural analysis.
The findings help teams define a problem statement grounded in user needs.
Instead of asking, "How can we shorten the loan application?" the team might ask, "How can we help customers understand their eligibility and repayment commitments before they apply?"
That change in perspective can influence the entire product experience.
2. Ideation: Explore, prototype, and validate solutions
Once the problem is clearly defined, teams can explore different ways to solve it.
This phase brings together product designers, researchers, business stakeholders, and technical teams to generate and evaluate possible solutions.
Ideas might include changes to information architecture, new product features, simplified user journeys, or different ways of presenting information.
Rather than selecting an idea solely because it looks promising, teams build prototypes and test how people respond.
A prototype could be a simple wireframe, an interactive interface, or a more developed representation of the product.
The level of detail depends on what needs to be learned.
For the fintech example, a team could test whether showing eligibility requirements earlier helps customers feel more confident about starting an application.
Testing might also reveal whether repayment illustrations are easier to understand than lengthy explanatory text.
These observations help teams identify which ideas deserve further investment.
Prototyping is especially useful because it allows businesses to challenge assumptions before committing substantial development resources.
3. Implementation: Turn validated ideas into working products
Implementation is where research findings and tested concepts become a functional product.
Designers work with developers, product managers, and other stakeholders to translate the experience into production-ready interfaces and workflows.
This involves interaction specifications, design systems, accessibility considerations, development collaboration, and quality assurance.
But delivering a product does not mean the design process is finished.
Once people begin using it, businesses gain access to new information about how the experience performs in real situations.
Product teams can examine task completion, feature adoption, user feedback, and points of abandonment to understand what needs improvement.
For example, a redesigned loan application may receive positive feedback during usability testing but still show unexpected drop-offs after launch.
Those findings should inform further investigation.
Human-centred product delivery treats improvement as part of the product lifecycle, allowing the experience to respond to changing needs and behaviours.
How businesses can apply human-centred design effectively
Adopting human-centred design requires more than conducting a few interviews at the beginning of a project.
Research needs to influence decisions across product strategy, design, development, and delivery.
One common challenge is involving users too late, when most product decisions have already been made. At that point, feedback may lead only to minor interface changes rather than addressing the underlying problem.
Another is treating stakeholder assumptions as established user needs.
Business teams often have useful market knowledge, but their understanding should be tested against customer behaviour.
Successful implementation also depends on connecting user needs with commercial and technical realities.
A solution must be desirable to the people using it, feasible for the organisation to deliver, and viable within the business model.
For organisations entering new markets, these considerations become especially important. User behaviours, accessibility expectations, cultural context, and digital maturity can differ substantially between audiences.
Businesses expanding into the United States, for example, may benefit from working with a UI UX design agency in the USA that can help translate market-specific user research into product strategy, intuitive interfaces, and scalable digital experiences.
The aim is to make design decisions based on evidence rather than assumptions about how customers should behave.
How Onething approaches human-centred product design
At Onething, we approach product design by understanding the problem, the people experiencing it, and the business outcomes the product needs to support.
This means examining existing user journeys, identifying sources of friction, and using research to guide design decisions.
Depending on the product's needs, the work may involve experience strategy, information architecture, interface design, prototyping, usability testing, and design systems.
We also believe that research becomes more useful when it directly informs product decisions.
Insights need to translate into clearer journeys, better interaction patterns, and features that address genuine user needs.
Through this approach, Onething helps businesses create digital products that are easier to use, more consistent, and better suited to the people they serve.
Final thoughts
The most useful products often solve problems people have learned to live with.
Human-centred product design helps teams recognise those problems, understand why they exist, and develop solutions grounded in real behaviour.
The process requires ongoing research, experimentation, and the willingness to revisit assumptions when evidence points in a different direction.
For businesses, that discipline can help reduce unnecessary development effort and create products people have a reason to keep using.
Have a digital product challenge worth solving?
Explore Onething's digital product design expertise and discover how research-led design can turn user needs into better product experiences.