Back in the dim and distant past, when I ran an enterprise architecture team, we spent months building immaculate diagrams that were technically correct, logically coherent, beautifully presented, and largely irrelevant because ultimately, they sat on a shared drive and no one used them.

CX teams are repeating the same mistake, only the artefacts have changed. Today it’s journey maps, platforms, and measurement frameworks standing in for impact.

The commonality of both problems, other than a lot of wasted effort, is that mapping, modelling and describing everything in minute detail doesn’t help the business when it needs to act fact.

Change isn’t the new normal. Unexpected change is.

Since my time in enterprise architecture in the heady days of the late noughties worrying about building mobile apps, the context has shifted. Technology has advanced, sure, but change has changed. Uncertainty is no longer episodic. It’s structural. Change isn’t just faster, it’s less predictable. Executives increasingly see change as a permanent operating condition rather than a time‑bound initiative. But organizations can absorb extraordinary amounts of change when they choose it. What they struggle with is change they can’t control: geopolitical shocks, misinformation, regulatory swings, economic volatility. In that environment, efficiency alone doesn’t create resilience. Culture, decision rights, and ways of working do.

Culture is your resilience superpower

Many CX teams respond to uncertainty by tightening process. More governance. More artefacts. More methodological purity. Structure feels like control. But:

  • Focus on what you enable, not how you work. Teams that define themselves by how they work rather than what they enable, are fragile. The moment the context shifts, the process no longer fits and the team loses relevance at exactly the wrong time. Resilient organizations behave differently. They don’t reinvent how decisions get made every time something goes wrong. They ritualize problem‑solving. Who convenes. Who decides. How trade‑offs get made. What authority actually means in practice. The problem changes; the muscle memory does not.
  • Treat trust as a system, not a sentiment. Trust and empowerment come up frequently in culture conversations, and are just as frequently left vague. In hierarchical organizations, trust does not “emerge.” You have to design it. That means explicitly defining: what decisions teams can make without escalation, what inputs are considered credible, and when executives will not override decisions after the fact.
  • Prioritize outcomes, not tools. CX tools still matter. Research, mapping, measurement are all capabilities, not liabilities. But deploy them opportunistically, not by rote. The teams that thrive in uncertainty lead with business outcomes: revenue protection, cost avoidance, trust recovery, speed to market. Tools follow the problem, not the other way around.

If you want to learn more, myself and Angelina dive into the tension between process rigidity and flexibility in our increasingly volatile world on the CX Cast and explain why many CX teams struggle when change hits, and what resilient leaders do differently.

Listen now to learn how to build a CX team that stays effective when everything else is changing.