Change in Practice: Decision Clarity During Change
Why Every Implementation Needs a Guiding Force
When Everything Feels Like a Decision
Throughout this series, we have explored what makes change sustainable. We have looked at the gap between awareness and execution, the habits that help new ways of working become routine, and the systems that either support people or make their jobs unnecessarily difficult.
Now we arrive at something every implementation team knows very well: decisions.
There are so many of them. Some are significant. Others seem relatively small until three months later when everyone realizes that one little decision somehow affected payroll, integrations, reporting, security, and a process no one remembered existed. That is the nature of implementation work.
Projects move quickly, and there is often tremendous pressure to make decisions just as quickly. There are design sessions to complete, configurations waiting to be built, testing deadlines approaching, and a project plan reminding everyone that we were technically supposed to decide this last Tuesday. Speed is sometimes necessary. But speed and clarity are not the same thing.
The challenge is not simply that organizations make decisions too quickly. It is that sometimes we make them before we understand enough about the problem, the downstream impact, or what we are ultimately trying to accomplish. That is where a project needs something bigger than the decision in front of it. It needs a guiding force.
Before We Ask “What,” We Need to Understand “Why”
I was recently reminded of this while thinking about Brendon Baker's Valuable Change. One of the ideas that has stayed with me from the book is the importance of understanding the value behind a change rather than becoming consumed by the activity of delivering it. It seems obvious.
Of course we know why we are implementing a new system.
But do we? “We are implementing Workday” is not a why.
Neither is “we are replacing our legacy payroll system.”
Those statements tell us what we are doing. They do not tell us what should be different because we did it.
Maybe the organization wants to reduce manual payroll processes. Perhaps it needs greater global consistency, stronger controls, better data, or a simpler employee experience. Maybe the current operating model simply cannot support where the organization is going next. That distinction matters because once implementation begins, the why becomes incredibly easy to lose beneath the work .
A Guiding Force Creates Decision Clarity
Early in an implementation, we spend enormous amounts of time defining what we are going to build. I wonder if we sometimes spend too little time defining what should guide us while we build it. Because decisions will come quickly. We will not have perfect information for all of them, and waiting until every unknown disappears is not realistic either.
What teams need is a shared framework they can return to.
For me, that begins with three questions:
Why are we doing this? What organizational problem or opportunity is important enough to justify this transformation?
What should be different when we are finished? What does success actually look like beyond completing the implementation?
Does this decision move us toward that destination? Are we making a choice because it supports the future we defined, or because it is simply the fastest answer available today?
Those questions will not make every decision easy. But they give decisions context. And context is often what is missing when teams are asked to move quickly.
Sometimes We Simply Don't Know Enough Yet
There is another part of decision clarity that I think is equally important: knowing when you do not have enough information to make a sound decision. I have watched decisions get made in design sessions that seemed perfectly reasonable at the time.
Then someone closer to the day to day operation asks a question.
What happens with an off cycle payroll?
How does this work when an employee transfers?
What about this population?
Who handles the exception?
And suddenly, the simple decision is not quite so simple anymore.
This is why having the right people involved matters so much. The person closest to the work often knows the exception that never made it onto the process diagram.
How to Improve Decision-Making During Organizational Change
Effective decision-making during organizational change requires more than speed; it requires a clear understanding of purpose, outcomes, and downstream impact. Before making an important implementation decision, teams should be comfortable asking:
Do we understand the actual problem?
Do we have the right people in the conversation?
Do we understand the downstream impacts?
What information are we still missing?
Could that missing information materially change our decision?
There is a difference between thoughtfully slowing down a decision and avoiding one. Mature organizations learn to recognize both.
The Cost of Deciding Too Soon
There is also a human cost when decisions are repeatedly made too quickly and then reversed. Teams begin to stop trusting decisions. They keep the old process nearby, just in case. They hesitate to build around the new direction. They ask whether something is really final before moving forward. And somewhere, inevitably, another spreadsheet survives a little longer than anyone intended.
What started as an attempt to create speed actually creates uncertainty. This connects directly to the cognitive load we have explored throughout this series. When people cannot trust that today's direction will still be tomorrow's direction , they spend more energy preparing for multiple possibilities.
Good decision making creates stability. Not because every decision will be correct, but because people understand how and why the organization arrived there.
AI Makes Decision Clarity More Important Than Ever
This becomes especially interesting as organizations introduce more artificial intelligence and automation into their operations. AI can help organizations analyze information, identify patterns, surface recommendations, and make better information available faster. That is incredibly valuable.
But more information does not automatically create better organizational judgment.
Technology can tell us what we could do. The organization still has to understand why it is doing it.
As I have been reading more about AI and the future of work, I keep noticing that the conversation eventually returns to organizational capability: leadership, adaptability, decision making, and the ability to translate information into action.
I see the same thing in payroll and HR transformations. The technology matters enormously. But technology cannot give an organization its guiding force.
What Mature Organizations Do Differently
Organizations that navigate transformation well are not necessarily the ones that make decisions the fastest. They create enough clarity around the transformation that teams can make decisions thoughtfully, even when circumstances require them to move quickly.
That often means:
Establishing a clear purpose for the transformation before becoming consumed by delivery
Defining what success looks like beyond simply reaching go live
Bringing operational voices into decisions early enough to identify real world implications
Understanding which decisions can be made quickly and which require deeper exploration
Returning to the project's guiding purpose when competing options seem equally reasonable
Most importantly, they remain willing to learn.
Because sometimes new information should change the decision. That is not failure. That is responsible adaptation.
Decision clarity is not about having every answer. It is about giving teams a shared framework for making decisions when information is incomplete. During organizational change, that framework should clarify why the organization is changing, what success looks like, and whether a decision supports that outcome.
Frequently Asked Questions
-
Decision clarity is the ability to make change and transformation decisions using a shared understanding of the organization's purpose, desired outcomes, and the impact of available options.
-
Implementation projects involve interconnected decisions that can affect processes, people, systems, reporting, and the employee experience. Clear decision-making helps teams move forward without losing sight of the transformation's purpose.
-
Leaders can improve decision-making by clarifying the purpose of the transformation, defining what success looks like, involving operational voices early, considering downstream impacts, and creating a framework for evaluating competing choices.
-
AI can make information, patterns, and recommendations available faster, but it does not replace organizational judgment. Leaders still need to understand why a change is being made and what outcomes should guide decisions.
Clarity Isn't Having All the Answers
Implementations will always require decisions.
Some will be made with plenty of information. Others will happen quickly because the project simply needs to move. The goal is not to eliminate uncertainty or to wait until we know everything. The goal is to know what should guide us when we don't.
That is why I believe every transformation needs something larger than its project plan. It needs a shared understanding of why the organization is changing , what it hopes will be different, and what principles should guide the choices made along the way.
Because clarity isn't having all the answers. It is knowing what should guide you when you don't.
Transition to Part 5
In the next article, we will explore what happens once that direction has been established.
Because defining what matters is only the beginning.
Leaders also have to protect it.
New requests will emerge. Priorities will compete. Scope will expand. And there will almost certainly be at least one, “Since we're already changing the system, could we also...?”
Part 5 will explore why sustainable change requires leaders to protect focus, not just create it.