The situation
This X-Matrix case study comes from my work earlier this year with the internal agile coaching team of a large pharmaceutical organisation. The team had around 10 to 15 coaches, supporting several areas of the business across multiple sites, mostly in France. The head of agile coaching brought me in, and I worked with them for a little over six months.
The challenge
The coaching team and its leadership kept coming back to the same two questions. What work would have the biggest impact, and what would success look like? The conversation came round again and again, with lots of good ideas and suggestions, but never quite settled on any answer. It’s a pattern I see often, and I’ve written about why leadership teams keep going round in circles on strategic decisions.
How we used the X-Matrix
We put the coaching team’s strategy onto an X-Matrix, using the TASTE elements: True North, Aspirations, Strategies, Tactics and Evidence. We started with one team in one office, then worked across the wider coaching team over several sessions.
I facilitated the conversations and contributed as a coach, giving feedback and guidance, mostly by asking clarifying questions. We aimed to stay method agnostic. It wasn’t about introducing Scrum, Kanban or any other method. Instead, Agendashift’s focus on outcomes was more useful here.
Working with the leadership team
The X-Matrix showed why the conversation kept going round. People were using the same words to mean different things, and weren’t clear on the difference between the TASTE elements.
Flow metrics were the clearest example. Were they Evidence, telling us whether the strategy was working? Or were they a Tactic, something the team would do? There was a similar muddle between Evidence and Aspirations, over which were short-term indicators and which were longer-term results. Until we sorted that out, people were effectively having different conversations while using the same words.
The decisions
The team agreed that flow metrics were Evidence on the X-Matrix (generated using ActionableAgile). That led to a better question: which Tactics did we expect to move them? At the site I was working with, the answer became the coaching team’s main focus: helping pods release work to production and start implementing continuous delivery. Other sites were free to choose their own Tactics. It turned out to be a far more useful conversation than a general one about focus.
What changed with the X-Matrix
At one workshop, I asked the coaches to reflect on the X-Matrix and place a sticky note on a triangle with three corners: “Guides my approach”, “Helps me understand the context” and “Provides tools and tactics”. Where they placed a note showed how strongly each statement applied: the closer to a corner, the more that statement applied. Most notes leaned towards guiding the approach, and a number also towards understanding the context. Some were candid about what was still hard, such as connecting coaching evidence to the strategy, or keeping it in use after the workshop.
For the coaches I worked with directly, the focus shifted, and they dropped some work. It was also easier to tell the story of why they made those changes and what the new priorities were.
The X-Matrix also became a common format across teams. Each site and business area could choose its own Tactics, so the shared format gave consistency while still allowing local freedom.
One coach summed it up on their sticky note:
“I have a clear direction that gives me autonomy of decision and experimentation. I always found it difficult to measure success and show coaching impact. It’s now clearer how I can do it!”
A coach in the team
Lessons from this X-Matrix Case Study
The lesson I’d want other teams to take is that a common language makes for more productive conversations. A debate about focus can look like a disagreement about direction when people are really using the same words for different things.
If your leadership team keeps having the same conversation about priorities or success, the strategy itself may not be the problem. I help leadership teams put their strategy on one page and agree on what each part means, then keep reviewing it together. Find out more about Strategy that evolves, or read how I worked on the X-Matrix at Rally Software.

