The Leader's Guide to Winning at Change
How to use a data-driven tool to assess risk, align your team, and ensure your most important initiatives succeed.
These past few days I have been thinking about why big projects or government led interventions fail. We all know that change is constant. But the real problem is that most big change projects fail. They fail quietly, they fail slowly, and they fail expensively. Success today means reacting to new threats and opportunities. It means rethinking strategy and structure to find a temporary advantage. This has made change messy. Projects no longer fit into neat boxes. They stretch across divisions, functions, and entire countries.
This leaves leaders trying to manage a portfolio of competing priorities. They must weigh projects against each other. They must deploy their best people and resources carefully. This requires hard conversations about which projects to modify or stop completely. It is a difficult job. It keeps executives up at night. I have heard many leaders say they lack a simple way to know if a big project will work. They cannot spot the real reasons for success or failure.
My take is that leaders are often flying blind. They rely on gut feelings when they need a simple diagnostic tool. How do you get an honest read on a project’s chances of success before it is too late?
I often use a simple assessment framework called DICE. It was developed by the Boston Consulting Group to predict how likely a project is to succeed. It is a scoring system that helps leaders see the truth early. DICE stands for four key factors in any project:
Duration: The total time of the project. It can also be the time between major check ins. Shorter is always better.
Integrity: The skill of the project team to get the job done on time. This includes the leader’s competence.
Commitment: The support from senior managers. It also includes support from the employees the project affects directly.
Effort: The extra work employees must do on top of their normal jobs.
A project team scores each of these four factors. Team integrity and senior management commitment are weighted more heavily. Low scores are good. High scores show trouble ahead. A project will fall into one of three zones. A low total score puts it in the Win Zone. A middle score puts it in the Worry Zone. A high score puts it in the Woe Zone, where it will likely fail. This system turns arguments into data based conversations. A CEO and a junior team member can use the same language to talk about a project’s health.
Think about a government that wants to open its mineral sector to foreign investment using new technology (blockchain tokens and AI). Before starting, they should evaluate four key risk factors:
Duration (2 years): The project needs new laws, which will take about two years to pass. This long timeline creates risk as political priorities can shift, elections can change leadership, and investors may lose interest.
Integrity (Expertise gaps): Success requires a team with three specialized skills: mining law, blockchain technology, and AI systems. Most governments lack this rare combination of expertise. Without it, the project will likely fail due to poor decisions and implementation.
Commitment (Leadership support): Two groups must stay committed throughout the project. The head of state must champion it despite political pressure and competing priorities. Local mining communities must support it because if they oppose or resist, the project will stall completely.
Effort (Staff workload): Current government employees in mining and finance ministries will need to take on additional responsibilities. If this adds 20% more work to their existing duties, they may burn out and quit, undermining the project.
How this works
Rate each factor on a scale (like 1-10 for risk level). High scores in any area signal major problems ahead. For example, if Duration scores 8/10 (high risk due to the long timeline) and Integrity scores 9/10 (critical expertise gaps), the project should be redesigned or abandoned before wasting resources.
Using a tool like DICE changes how organizations handle big projects. I saw this with a senior policy maker executing a trough of interventions to turnaround an economy. He found his team executing more than 80 different interventions when he started. He knew the administration would not be able to do them all well. He sat with his team. They scored each project using DICE. They found five interventions they had to win. They put their best people on them. They set short term goals to keep the DICE scores low. Initiatives with high scores were paused. Their resources were moved to the top priorities. The leadership team did this review every quarter. The administration was able to finish most of its change projects on time and under budget.
This is the kind of agility that matters. Netflix is successful because it is built to adapt. Its leaders design different structures for different situations. Volkswagen is trying a two speed model for the same reason. Some parts of the business use slower, proven methods. Other parts use faster, more agile structures.
Making this work requires trust and cooperation. Leaders must govern with transparency. Strategic agility is not a single program. It is a mix of a trusting culture, the right delivery skills, and a flexible structure. This is what connects a smart strategy to the messy reality of getting it done. It is especially true at the difficult intersection of policy, technology, and capital. The main question for any leader is this. What simple system are you using to see the truth about your most important projects?