The sprint nobody runs: using design thinking to fix internal adoption, not just products

I watched a brilliant innovation team at a major bank spend six months perfecting a customer onboarding tool. User research, prototype testing, stakeholder interviews. Textbook design thinking process. The tool was genuinely good.

Then they handed it to the branches and waited for adoption.

Eighteen months later, usage sat at 12%. The same team that had obsessed over customer friction completely ignored the friction facing their internal users. They designed for customers but deployed to colleagues like it was 1995.

This is the sprint nobody runs. The one where you apply design thinking to the hardest user journey of all: getting your own organisation to change.

Your internal users are still users

When we design for customers, we start with empathy. We map their current journey, identify pain points, understand their jobs to be done. We prototype solutions and test them with real people.

When we deploy internally, we send an email and book a training session.

The branch managers trying to use that onboarding tool were users too. They had existing workflows, competing priorities, and about thirty seconds to decide whether this new thing was worth their attention. The innovation team never mapped that journey.

At Disney, we learned this the expensive way. A brilliant new guest experience platform sat unused for months because we had not designed the adoption experience for cast members. We had built something customers would love, but we had not built something employees could easily integrate into their existing routines.

The three stages of internal adoption design

The fix is not complicated. It is the same process you already know, applied to your internal challenge.

Stage 1: Discovery with internal users

Before you build anything, spend time with the people who will actually use it. Not their managers. Them. Shadow a branch advisor for a morning. Sit with a customer service agent during peak hours. Watch how they currently solve the problem your innovation addresses.

You are looking for the same things you would with external customers: pain points, workarounds, competing priorities, and moments of truth. The difference is that internal users are often more honest about friction because they live with bad tools every day.

Stage 2: Design the adoption journey

Map the path from "never heard of this tool" to "using it naturally." This is not a training plan. It is a behaviour change journey.

What triggers will prompt first use? What support do people need when they hit obstacles? How do you build confidence through early wins? How does the tool fit into their existing workflow, not replace it?

At NatWest, we designed adoption moments into the tool itself. Instead of training people on everything upfront, the interface guided users through progressive disclosure. Each feature unlocked based on confidence with the previous one.

Stage 3: Test and iterate the adoption experience

Run the same tests you would with customers. Pilot with a small group. Watch what happens when people try to use your innovation in real conditions, not training conditions.

The feedback will be different from customer testing. Internal users will tell you about system integration issues, process conflicts, and political friction you never considered. Use this insight to iterate both the product and the adoption approach.

The toolkit you already have

You do not need new frameworks for this. Jobs to Be Done works as well for internal users as external ones. Journey mapping reveals internal friction just like customer friction. Prototyping and testing work the same way.

The mindset shift is what matters. Your colleagues are not just stakeholders to manage or audiences to inform. They are users with their own needs, constraints, and jobs to be done.

When American Express rolled out a new expense management system, they treated finance teams like customers. User research revealed that the biggest barrier was not the complexity of the tool but the timing of when people were asked to use it. The solution was not better training but different triggers aligned with natural workflow patterns.

Start this week

Pick one internal initiative that is struggling with adoption. Spend an hour with someone who should be using it but is not. Do not pitch or train. Just observe and listen.

Ask them to show you their current process. Where does your innovation fit? Where does it conflict? What would make it easier to try?

Then design the adoption experience with the same care you would design the customer experience.

The best innovation team designs twice: once for the customer who will love it, and once for the colleague who will use it.

We've been helping big brands for over 28 years. Book a call and see how we can help you too!