The moment everything gets questioned I worked with a business last year where the operations director left after seven years. Within three weeks, the new person had questioned every system, paused two supplier contracts, and proposed restructuring the team. Some of those questions were valid. Most were not. The problem was nobody could tell the difference. This happens constantly. A leadership change arrives and suddenly everything is up for debate. Priorities shift. Projects stall. People start second-guessing decisions that were settled months ago. You can see it playing out right now with John Lewis. Peter Ruis exits, and immediately the conversation turns to "strategic change" and which nettles need grasping. The implication is always that the previous direction was somehow wrong. Sometimes it was. Often it was simply unfinished. A decision matrix does not solve politics. But it does give you a way to separate genuine strategic choices from the noise that leadership transitions create. What a decision matrix actually does A decision matrix is a scoring system. You list your options down one side, your criteria across the top, and you score each option against each criterion. Then you weight the criteria by importance and calculate totals. That is the mechanical description. The actual value is different. It forces you to name what matters. Not in vague terms like "growth" or "efficiency", but in specific, weighted priorities. Does cost matter more than speed? By how much? Does team capacity outweigh customer impact? You have to say. When leadership changes, those weights often shift. A new person brings different priorities. That is fine. But the shift should be visible and deliberate, not hidden inside a dozen separate conversations. Why leadership transitions break decision-making I have seen three patterns repeat. First, the new leader questions everything to establish authority. This is often unconscious. They want to put their stamp on things. The result is that decisions which were 80% complete get reopened, costing time and momentum. Second, the team hedges. Nobody wants to commit to a direction that might get reversed next month. So projects slow down while people wait to see which way the wind blows. Third, institutional knowledge walks out the door. The previous leader knew why certain choices were made. The reasons were never documented. Now those decisions look arbitrary, even when they were sound. A decision matrix addresses all three. It makes the reasoning visible. It creates a record that survives personnel changes. And it gives the new leader a framework to work within rather than a blank slate to fill with preferences. How to build one during a transition Start with the decisions that are genuinely open. Not the ones that were settled last quarter. Not the ones that are just being questioned because someone new arrived. The ones where you actually have options. I typically limit this to three or four decisions maximum. More than that and you are probably trying to re-examine the entire business strategy, which is a different exercise. For each decision, list the realistic options. Not the fantasy scenarios. If you do not have budget for option three, do not include it. Then define your criteria. This is where leadership alignment matters most. The new leader and the existing team need to agree on what factors matter and how much weight each carries. I worked with a client in February where we spent 45 minutes just on the criteria. The new managing director wanted to weight "market positioning" at 30%. The sales lead thought it should be 15% because short-term revenue was more pressing. That disagreement was the real conversation. The matrix just made it visible. Once you have criteria and weights, scoring is straightforward. Use a simple scale. I prefer 1 to 5. Anything more granular creates false precision. The Decision Matrix tool on alira.london automates the maths, which helps when you are comparing multiple options. But the real work is in the conversation that builds the matrix, not the calculation. When to ignore the numbers The matrix gives you a ranking. It does not make the decision. If option A scores 78 and option B scores 76, that is a tie. Do not pretend the numbers are more precise than they are. If the highest-scoring option feels wrong, interrogate that feeling. Either you have missed a criterion, or you have weighted something incorrectly, or there is information you have not articulated. The discomfort is data. I had a client last autumn where the matrix clearly pointed toward outsourcing a function. The numbers were not close. But the business owner kept hesitating. We dug into it and realised she had not weighted "team morale" at all. Once we added it, the calculation shifted. She chose a hybrid model instead. The matrix did its job. It surfaced the hidden factor. The 72-hour rule When a new leader arrives, I recommend a 72-hour pause on any decision that was already in progress. Not a freeze. Just a pause. Use that time to document the current state. What options are on the table? What criteria have been applied? What does the existing team think? Then bring the new leader into the matrix. Let them adjust the weights if they want. But make them do it explicitly, in a way everyone can see. This prevents the pattern where new leadership quietly shifts priorities and the team only discovers it weeks later when their work gets rejected. What to do this week Identify one decision that has stalled or been reopened since your last leadership change. Write down the options and the criteria that should govern the choice. Do not score yet. Just get it on paper. Have a 20-minute conversation with whoever is now responsible for that decision. Ask them to weight the criteria from most to least important. Compare their weights to what the previous approach implied. Note where they differ. Run the numbers using the Decision Matrix tool at alira.london. See what the calculation says. Then decide whether to follow it or override it. Either choice is valid. But make it deliberately.