Organizations spend millions of dollars every year launching new products, services, technologies, policies, and initiatives. But many of these efforts fail to achieve the outcomes they were designed for. The reason is often surprisingly simple: they were designed around assumptions instead of people.
User-centred design is an approach that puts the people who will use, experience, or be impacted by a solution. Rather than starting with what an organization wants to build, user-centred design starts with understanding the needs, motivations, behaviours, and challenges of the people it serves.
At Spring2 Innovation, we often say that the most expensive assumption is the one that goes untested. User-centred design helps organizations move beyond assumptions and make decisions based on real human insights.
What Is User-Centred Design?
User-centred design (UCD) is a problem-solving approach that focuses on understanding users throughout the design and development process. It involves engaging with end users early and often to ensure solutions are useful, usable, and meaningful.
Whether you are designing a new digital service, implementing a CRM, developing a policy, improving an employee experience, or launching a new product, the people who will use the solution should have a voice in shaping it.
The process typically includes:
-
Understanding users and their needs
-
Identifying pain points and challenges
-
Generating ideas based on user insights
-
Creating prototypes
-
Testing solutions with users
-
Iterating based on feedback
Rather than designing for people, organizations design with people.
Why Organizations Struggle
Many organizations believe they understand their customers, employees, or stakeholders. However, understanding often comes from internal perspectives rather than direct engagement.
Imagine ten people are asked to design a bathroom. Each person may picture something completely different. One may imagine a luxury spa-like experience. Another may focus on accessibility. Someone else may prioritize sustainability or cost efficiency.
Without alignment around who the user is and what success looks like, teams can spend significant time and resources building solutions that miss the mark.
This challenge becomes even more pronounced in large organizations where different departments have competing priorities. Marketing may define success one way, operations another, and technology teams yet another. The result is often confusion, rework, delays, and frustrated users.
The Hidden Cost of Ignoring Users
When organizations fail to involve users, the consequences can be significant:
-
Low adoption rates
-
Increased support costs
-
Expensive redesigns
-
Employee resistance to change
-
Customer dissatisfaction
-
Reduced return on investment
Many failed projects are not technology failures. They are human understanding failures.
One of the most famous examples is Google Glass. While the technology was innovative, the broader social and emotional experience of wearing the device was not fully understood before launch. Public concerns around privacy and social acceptance created barriers that technical excellence alone could not overcome.
Organizations often focus heavily on whether something can be built and not enough on whether it should be built or how people will experience it.
User-Centred Design and Innovation
Innovation is often portrayed as a moment of inspiration. In reality, successful innovation is usually the result of curiosity, empathy, experimentation, and learning.
User-centred design provides a structured way to reduce uncertainty before making large investments. Instead of spending months or years building a solution in isolation, organizations can quickly test concepts, gather feedback, and refine their approach.
This creates several advantages:
-
Reduced risk
-
Faster learning cycles
-
Better stakeholder buy-in
-
Increased customer satisfaction
-
Higher likelihood of successful implementation
The goal is not to create the perfect solution immediately. The goal is to learn quickly and continuously improve.
User-Centred Design Is Not Just for Customers
One of the biggest misconceptions about user-centred design is that it only applies to customers.
In reality, every initiative has users. Employees are users of internal systems. Managers are users of reporting tools. Citizens are users of government services. Procurement teams are users of procurement processes. Executives are users of strategic information and decision-making frameworks.
When organizations broaden their understanding of who their users are, opportunities for improvement become much easier to identify.
How user-centered design works in real life
A common example is a CRM implementation.
A company invests significant time and money selecting a new CRM. Leadership focuses on features, reporting capabilities, and dashboards. The system looks great on paper.
The problem? They never involve the sales team in the decision.
After launch, adoption is low. Salespeople continue using spreadsheets and workarounds because the CRM doesn’t fit how they actually work. Data quality suffers, reporting becomes unreliable, and leaders wonder why the investment isn’t delivering results.
The technology itself may not be the problem. The real issue is that the solution was designed around organizational assumptions rather than user needs.
A user-centred approach would have involved employees early, understood their workflows, and tested solutions before implementation. The result would have been higher adoption, better data, and a much greater return on investment.
This is a reminder that successful projects aren’t just about choosing the right technology—they’re about designing for the people who will use it.
The Connection Between User-Centred Design and Alignment
At Spring2 Innovation, we frequently see organizations struggle not because they lack talented people, but because teams have different understandings of the problem they are trying to solve.
User-centred design helps create alignment by grounding discussions in real user needs rather than opinions.
Instead of debating whose idea is best, teams can ask:
-
What did we learn from users?
-
What evidence supports this decision?
-
How does this solution help the people we are serving?
These conversations create clarity, reduce conflict, and help teams move forward together.
Getting Started
Organizations do not need a large innovation team or significant budget to begin applying user-centred design principles.
Start by asking:
-
Who are the users?
-
What are they trying to accomplish?
-
What challenges do they face?
-
What assumptions are we making?
-
How can we test those assumptions quickly?
Small conversations, interviews, observations, and prototypes can reveal insights that dramatically improve outcomes.
The earlier users are involved, the more likely an organization is to build solutions that people actually want, need, and use.
Final Thoughts
The most successful organizations understand that innovation is not about creating more features, processes, or technologies. It is about creating better experiences and better outcomes for people.
User-centred design provides a practical way to achieve this by bringing the voices of customers, employees, and stakeholders into decision-making.
When organizations start with people, they make better decisions, reduce risk, improve adoption, and create solutions that deliver lasting value.
Because in the end, success is not determined by what an organization builds. It is determined by whether the people it serves find it valuable.