Most employee experience initiatives don’t fail because people didn’t try hard enough. They fail because they were built on the wrong understanding of the problem.
That might sound like a bold statement, but it is something we see time and time again. Teams invest time, energy and budget into improving onboarding, recognition, communication or development. The thinking is sound. The intent is right. The execution is often strong.
And yet the impact falls short.
Following our recent webinar on EX design sprints , we wanted to share a couple of the real life examples we discussed in the session. Not theory. Not frameworks. Just a clear look at what happens when organisations design from assumptions compared to when they design with people.
Case study one: onboarding
An organisation identified a clear issue. A high percentage of new starters were leaving within the first three months. It was affecting performance, morale and cost, so understandably, it became a priority to fix.
Without EX design
The team moved quickly into solution mode. They focused on improving the parts of onboarding that felt most visible and tangible. A new welcome pack was created for day one. Investment was made in an employee app to keep people informed. There were multiple workstreams, all aimed at improving the early experience.
On paper, it looked like progress. And to a degree, it was. There was a slight improvement in retention, but nowhere near what the team had hoped for. The results felt underwhelming given the level of effort that had gone in.
The challenge was not that these ideas were wrong. It was that they were built on assumptions about what mattered most.
With EX design
Rather than continuing to iterate on the same approach, the organisation took a step back and ran a design sprint. They brought together a mix of stakeholders, including line managers, people involved in the onboarding process, and employees who had recently joined, so the experience was still fresh.
Instead of starting with solutions, they focused on understanding the real experience. They mapped the journey, explored what people actually went through, and identified the moments that made the biggest difference.
What emerged was a very different picture.
The real issues were not about welcome packs or access to information. They were about clarity and connection. New recruits did not have a clear sense of direction in their first 90 days. Training felt too long and too generic to be useful. Job descriptions often did not reflect the reality of the role, which created a disconnect from the start.
Once the problem was properly defined, the solutions naturally shifted. Line managers were given practical tools to set clear goals and direction in those early months. Training was redesigned to be more relevant and tailored. Recruitment processes were reviewed so that expectations were more aligned from the outset.
Within a year, early attrition reduced significantly. The difference was not in how much effort went in, but in how well the problem was understood before action was taken.
Case study two: recognition
A second organisation faced a different challenge, but a very similar pattern.
Employee feedback suggested that people did not feel recognised. It came through clearly in their survey results, so the team set out to address it.
Without EX design
The response was to launch a new recognition programme. It included a digital platform with gamified “kudos”, a nomination process and a large end-of-year awards ceremony. It was visible, engaging and, in many ways, well received…. but only by a small proportion of the organisation.
Engagement with the platform remained low, at around five percent, and the impact was uneven. Some people loved it, but many did not engage at all. And worst of all, the next survey saw barely any shift in questions around recognition.
Again, the issue was not a lack of effort or creativity. It was that the solution had been designed based on what recognition was assumed to look like, rather than how it was actually experienced day to day.
With EX design
The following year, the team approached things differently. They ran a design sprint, bringing together a mix of employees, including those who had engaged with the programme and those who had not, alongside line managers.
They started by exploring what recognition really meant to people in their context. Through journey mapping and discussion, they uncovered a gap between the formal programme and the everyday experience of work.
What people really valued was timely, meaningful feedback from their manager. They wanted consistency across teams, so recognition did not feel dependent on where you worked or who you worked for. And importantly, they wanted it to feel fair. Some employees had actually felt disengaged by the previous approach, as it seemed to amplify visibility for the same individuals.
With that understanding, the team co-created and tested new ideas. The focus shifted away from large, centralised initiatives towards more local, consistent and human ways of recognising contribution. Managers were supported to build better habits around feedback, and approaches were tested and refined before being rolled out more widely.
The result was not just a different solution, but a more relevant one. One that reflected the reality of people’s experiences and built buy-in along the way.
So what is actually different?
When you look at these examples side by side, the difference is not the type of problem being solved. It is not even the level of investment or intent.
It is the approach.
Without a design-led approach, organisations tend to move quickly from insight to action, often skipping over the step that matters most. They define the problem based on data, assumptions or past experience, and then build solutions that feel logical from that perspective.
With a design approach, the process slows down just enough to get clarity. Time is spent understanding the lived experience, involving the people who are closest to it, and testing ideas before committing to them at scale.
That shift changes everything. It leads to better problem definition, more relevant solutions and stronger adoption, because people have been part of shaping what is created.
Why this matters now
This is not just about doing better projects. It is about responding to a changing world of work.
Expectations are higher. Experiences outside of work are setting a new benchmark. AI is making it easier than ever to create and deliver solutions quickly. But speed without understanding only amplifies the problem.
If anything, the ability to move fast makes it even more important to design well.
Taking a human-centred, design-led approach helps organisations focus their effort where it will make the biggest difference. It reduces wasted investment and increases the likelihood that what is created will actually land in practice.
A more practical way forward
This is why we use EX design sprints in our work.
They are not about adding another layer of process. They are about creating space to properly understand a challenge, involve the right people, and test ideas before scaling them. In a matter of days, teams can move from a broad problem statement to something much more focused, practical and evidence-based.
More importantly, they help build capability. Teams start to think differently about how they approach challenges, moving away from assumptions and towards curiosity, empathy and experimentation.
Because ultimately, the goal is not just to fix one issue. It is to create a way of working that consistently leads to better outcomes.
If this feels familiar, you’re not alone. Most organisations aren’t short on ideas, they’re just missing the space to properly design them. If you’re working through a challenge and want to take a more structured, human-centred approach, we’d love to help. Get in touch and let’s explore how we can turn insight into something that actually works in practice.
