When to bring in external help!
In our experience, most organisations bring in agencies, CX resources and external help too late. By the time the call gets made, they're already a long way down a path, and the impact an outside perspective can make has shrunk to the margins.
Here's what we keep seeing, and what we explored in our last article on AI and design decision making: all that output isn't making decisions easier. It's making them harder.
So when is the right time? Here are five signals we've noticed.
1. The same problems keep coming back
You've seen this issue before. You put a band-aid on it, fixed a feature, patched a flow, and six months later it's back, wearing a slightly different outfit.
Recurring problems are rarely about the feature. They're usually about something structural underneath it that nobody's been positioned to see, or empowered to fix. When the same issue resurfaces for the third time, that's not a delivery problem. It's a signal.
2. No one owns the end-to-end experience
Someone owns the front. Someone else owns the back. Someone owns the app, someone owns the call centre, someone owns the onboarding emails. But nobody owns the complete experience, which means every problem gets looked at in isolation, and the whole thing never actually gets fixed.
The question that keeps getting lost is the simplest one: what does the user actually need? When every conversation starts from technical constraints instead, an external perspective can help a team step back over the org chart and see the journey the way a customer does.
3. There's data everywhere and decisions nowhere
NPS. Website analytics. Internal surveys. Customer feedback. Most organisations aren't short on data. They're drowning in it.
Some of it is useless. Some of it is useful but nobody's using it. And much of it gets interpreted through the lens of whoever's presenting it, which means the loudest stakeholder's reading tends to win.
This is where external help earns its keep: rising above the internal subjectivity to say, with confidence, this is what your users are actually telling you. Not what each stakeholder hopes they're saying. Objectivity is the product.
4. Design is an afterthought
We've all been in this scenario. Something big has been built, it's nearly done, and design gets brought in at the end, where the only thing left to fix is the colour of a button.
The opportunity isn't at the end. It's at the beginning, when the decisions that actually shape the experience are still open. If design keeps arriving after the important choices are made, that's not a design problem. It's a sequencing problem, and it's fixable.
5. The team is too close to it
This one's counterintuitive, because closeness is usually a strength. Your team knows the detail, the history, the constraints.
But teams that have been working on something for a long time, across too many objectives, too many business units, and too many moving parts, often lose the ability to step back. Decisions don't get made, or they stall. Projects lose momentum when people move on. Being in the detail is good. Being unable to get out of it isn't.
An outside perspective doesn't replace that internal knowledge. It complements it, bringing the big picture of the user back into a room that's been staring at the small one.
When you do seek external help, keep this in mind
A few things worth looking for. Pick people who've done it before, who are evidence-based, and who have context in your industry. Look for a partner who builds capability in your team rather than just filling a discrete role. The goal is that you're stronger after they leave, not dependent while they're there.
Meet them first. You'll learn more about how an agency operates from one conversation than from any capability deck.
And think about size. With a smaller agency, you're often their main focus. A big fish in a small pond rather than the other way around. That tends to show up in the work.
The takeaway
None of these five signals is a crisis on its own. That's exactly why they persist. They feel like normal organisational friction. But if more than one of them feels familiar, that's usually the moment to act: early enough that an outside perspective can still shape the direction, not just polish the edges of it.
Sound familiar? Let's chat.
In our experience, most organisations bring in agencies, CX resources and external help too late. By the time the call gets made, they're already a long way down a path, and the impact an outside perspective can make has shrunk to the margins.
Here's what we keep seeing, and what we explored in our last article on AI and design decision making: all that output isn't making decisions easier. It's making them harder.
So when is the right time? Here are five signals we've noticed.
1. The same problems keep coming back
You've seen this issue before. You put a band-aid on it, fixed a feature, patched a flow, and six months later it's back, wearing a slightly different outfit.
Recurring problems are rarely about the feature. They're usually about something structural underneath it that nobody's been positioned to see, or empowered to fix. When the same issue resurfaces for the third time, that's not a delivery problem. It's a signal.
2. No one owns the end-to-end experience
Someone owns the front. Someone else owns the back. Someone owns the app, someone owns the call centre, someone owns the onboarding emails. But nobody owns the complete experience, which means every problem gets looked at in isolation, and the whole thing never actually gets fixed.
The question that keeps getting lost is the simplest one: what does the user actually need? When every conversation starts from technical constraints instead, an external perspective can help a team step back over the org chart and see the journey the way a customer does.
3. There's data everywhere and decisions nowhere
NPS. Website analytics. Internal surveys. Customer feedback. Most organisations aren't short on data. They're drowning in it.
Some of it is useless. Some of it is useful but nobody's using it. And much of it gets interpreted through the lens of whoever's presenting it, which means the loudest stakeholder's reading tends to win.
This is where external help earns its keep: rising above the internal subjectivity to say, with confidence, this is what your users are actually telling you. Not what each stakeholder hopes they're saying. Objectivity is the product.
4. Design is an afterthought
We've all been in this scenario. Something big has been built, it's nearly done, and design gets brought in at the end, where the only thing left to fix is the colour of a button.
The opportunity isn't at the end. It's at the beginning, when the decisions that actually shape the experience are still open. If design keeps arriving after the important choices are made, that's not a design problem. It's a sequencing problem, and it's fixable.
5. The team is too close to it
This one's counterintuitive, because closeness is usually a strength. Your team knows the detail, the history, the constraints.
But teams that have been working on something for a long time, across too many objectives, too many business units, and too many moving parts, often lose the ability to step back. Decisions don't get made, or they stall. Projects lose momentum when people move on. Being in the detail is good. Being unable to get out of it isn't.
An outside perspective doesn't replace that internal knowledge. It complements it, bringing the big picture of the user back into a room that's been staring at the small one.
When you do seek external help, keep this in mind
A few things worth looking for. Pick people who've done it before, who are evidence-based, and who have context in your industry. Look for a partner who builds capability in your team rather than just filling a discrete role. The goal is that you're stronger after they leave, not dependent while they're there.
Meet them first. You'll learn more about how an agency operates from one conversation than from any capability deck.
And think about size. With a smaller agency, you're often their main focus. A big fish in a small pond rather than the other way around. That tends to show up in the work.
The takeaway
None of these five signals is a crisis on its own. That's exactly why they persist. They feel like normal organisational friction. But if more than one of them feels familiar, that's usually the moment to act: early enough that an outside perspective can still shape the direction, not just polish the edges of it.
Sound familiar? Let's chat.