CIO Case Study: Gather, Process, Decide

Decision making gets harder as leaders move up.

Earlier in a career, a capable leader can often create value by being thoughtful, thorough, and technically strong. They gather the facts. They study the issue. They involve the right people.

They work hard to avoid mistakes.

Those habits are valuable.

But at the executive level, the same habits can become a source of friction if they are not paired with decisiveness.

I saw this clearly in coaching work with a leader who had been moved from a business unit role into the CIO seat of a billion-dollar organization. He was smart, capable, respected, and deeply committed to doing the right thing for the business.

The challenge was not effort.

The challenge was decision friction.

He needed to focus on the right priorities, make tough calls with imperfect information, bring stakeholders along without allowing every decision to slow down, and follow through until the work was complete.

That became the coaching work.

Over time, he built more confidence in his decision making by using a simple structure:

Gather.Process.Decide.

That structure helped him slow down where alignment mattered, speed up where consensus was not required, and stay engaged long enough to get more wins on the board.

The leadership problem behind decision friction

Decision friction rarely shows up as one dramatic failure.

It usually shows up as a pattern.

Decisions take too long. Issues circle back repeatedly. Stakeholders are consulted, but the leader still hesitates. The team is active, but progress feels slower than it should. Peers experience too much ambiguity. Executives start to wonder whether the leader can make the hard call.

In this case, the CIO was not avoiding responsibility. He cared about the business. He cared about the quality of the decision. He wanted his peers to feel heard. He wanted to avoid moving too quickly and creating resistance or rework.

Those instincts were good.

But the role required a different level of decision leadership.

As CIO, he could not allow every significant issue to become a slow consensus process. He had to learn which decisions required broad stakeholder buy-in and which decisions needed a clear point of view, a reasonable process, and forward motion.

That is a common executive challenge.

The higher the role, the more often leaders have to decide with incomplete information. They may not have perfect data. They may not have full alignment. They may not have certainty that the path will work exactly as planned.

But the business still needs movement.

Decision friction becomes a leadership problem when it affects the team, peers, and enterprise. People begin waiting. Priorities blur. Energy gets consumed by repeated discussion rather than execution. The leader’s credibility can suffer, even when the leader is trying to be careful.

This is where executive coaching can create real value.

The work is not to turn a thoughtful leader into a reckless one. The work is to help a thoughtful leader make better decisions faster, with enough stakeholder input, enough structure, and enough confidence to keep the business moving.

Why high-capability leaders still get stuck

High-capability leaders get stuck for understandable reasons.

They often have a strong sense of responsibility. They know their decisions affect people, budgets, customers, systems, and future performance. They have seen poor decisions create problems downstream, so they want to be careful.

In technical and functional leadership roles, this can be especially pronounced.

A CIO, CFO, engineering leader, or operations executive may be trained to see risk. They know what can break. They understand the dependencies. They know one missed detail can create real consequences.

So they gather more information.

They seek another point of view.

They wait for more certainty.

They revisit the decision.

At some point, diligence turns into analysis paralysis.

Fear of failure is often underneath the surface. The leader may not say, “I am afraid to decide.” Instead, they say, “We need more information.” Sometimes that is true. But sometimes more information becomes a way to delay ownership.

That is the trap.

The leader wants the decision to become safe before making it. At the executive level, many decisions never become fully safe.

They become clear enough.

That is a different standard.

A high-capability leader can also get stuck because they are trying to keep everyone aligned. Stakeholder buy-in matters. But when buy-in becomes informal veto power, the leader slows the organization down.

This is where leaders need to distinguish between input, alignment, and consensus.

Input means, “I need your perspective before deciding.”

Alignment means, “I need you to understand and support the direction.”

Consensus means, “I need everyone to agree before we move.”

Those are not the same.

A leader who treats every decision as if it requires consensus will frustrate the business. A leader who ignores stakeholder input will create resistance and blind spots. The art is knowing what the decision requires.

That was a major part of the CIO’s development.

He needed to gather enough input to make a sound decision, process the tradeoffs clearly, then decide and follow through.

The gather, process, decide framework

The gather, process, decide framework is simple by design.

Leaders do not need a complicated model in the middle of a hard decision. They need a structure they can use under pressure.

The first step is gather.

Gathering means collecting the information and perspectives required to understand the decision well enough. It does not mean collecting all available information. That distinction matters.

Useful gathering includes questions like:

What decision are we actually making?

What information is essential?

Whose input do we need?

What risk are we trying to understand?

What are the consequences of waiting?

What information would change the recommendation?

Those questions help prevent endless analysis.

The second step is process.

Processing means stepping back from the raw information and making sense of it. What are the options? What tradeoff does each option create? What matters most for the business? Where is the risk acceptable? Where is it not? Who will be affected by the decision?

This is where executive judgment develops.

The leader is no longer simply collecting data or listening to every stakeholder. The leader is forming a point of view.

Processing also means identifying whether the decision needs more buy-in or more speed.

Some decisions deserve time. A major systems change, a high-risk customer issue, a significant investment, or a decision that affects multiple functions may require stakeholder alignment before action.

Other decisions do not require broad consensus. They require the leader to make the call.

The third step is decide.

Deciding means choosing the path and communicating it clearly.

A strong decision message includes the answer, the rationale, the tradeoff, the risk, and the next steps.

For example:

“Here is the decision. We are moving forward with option two. The reason is that it best protects business continuity while giving us a manageable implementation path. The tradeoff is that we will carry some additional cost this quarter. The risk I want us to watch is adoption in the field. The next step is for the project team to finalize the implementation plan by Friday.”

That is clear.

People may not all agree. But they know what has been decided and why.

This structure helped the CIO build confidence because it gave him a process to stand on. He did not have to wait until he felt completely certain. He could trust the process, make the call, and adjust if new information required it.

How stakeholder buy-in fits without slowing everything down

Stakeholder buy-in is essential in executive leadership.

The mistake is assuming buy-in always means a long process or complete agreement.

Sometimes the leader needs deep involvement before the decision. Sometimes the leader needs to consult a few key people. Sometimes the leader needs to decide quickly and communicate the rationale afterward.

The key is being intentional.

In the CIO case, part of the coaching work was learning when to slow down to speed up.

That phrase matters.

There are moments when taking time on the front end prevents friction later. If a decision will affect multiple senior leaders, disrupt workflows, change priorities, or require people to support implementation, then stakeholder alignment is not optional.

But stakeholder buy-in should not become a place where decisions go to lose momentum.

The leader needs to define what kind of buy-in is required.

Do I need this person’s expertise?

Do I need this person’s support?

Do I need this person to communicate the decision to their team?

Do I need this person to own part of implementation?

Do I need this person to agree, or do I need them to understand and commit?

Those are different needs.

A practical way to handle this is to tell stakeholders what role they are playing.

“I want your input before I decide.”

“I want to pressure test the options with you.”

“I want to make sure you understand the direction because your team will be affected.”

“I need your support in implementation.”

“I am going to make the decision, but I want to hear your concern first.”

That kind of clarity reduces confusion.

It also helps the leader avoid two extremes: deciding in isolation or over-consulting until the decision loses energy.

Stakeholder buy-in and decisiveness can travel together.

The leader can listen well and still decide.

The leader can build alignment and still move.

The leader can acknowledge complexity without letting complexity become paralysis.

That is an executive-level skill.

Lessons from the CIO coaching case

The CIO’s growth offers several lessons for any CEO, COO, CIO, or high-potential leader who wants to improve decision quality and speed.

The first lesson is that prioritization comes before decisiveness.

If a leader does not know what matters most, every decision becomes harder. The CIO had to focus on the right things, not simply the many things competing for attention. Clear priorities made decisions cleaner because they created criteria.

The second lesson is that confidence grows through process.

Confidence did not come from pretending decisions were easy. It came from having a repeatable way to gather information, process tradeoffs, and decide on solid but imperfect information.

The third lesson is that follow-through matters.

A decision is not complete when it is announced. It has to be driven to completion. One piece of feedback in this case was the importance of getting a “touchdown” rather than settling for a “field goal.” That is a useful image. Leaders need to stay engaged long enough to make sure priority work actually gets finished.

The fourth lesson is that stakeholder buy-in is a leadership discipline.

The CIO needed to learn when alignment was essential and when broad consensus was unnecessary. That distinction helped reduce friction with colleagues and improved the speed of execution.

The fifth lesson is that analysis paralysis is coachable.

A leader who over-analyzes may be highly capable. The issue is often not intelligence or commitment. The issue is fear of failure, lack of structure, unclear decision rights, or uncertainty about how much input is enough.

Coaching helps turn those patterns into a practical decision process.

The sixth lesson is that decision making is a readiness signal.

Senior teams notice how leaders make decisions. They notice whether someone can focus priorities, listen well, decide clearly, and follow through. They notice whether a leader stays engaged on hard problems or drifts into hesitation.

For high-potential leaders, this matters.

Decision making is not just an operating skill. It is a signal of readiness for greater responsibility.

Ready to reduce decision friction?

If a leader’s decision process is slowing the team, peers, or enterprise, the issue may not be effort.

It may be structure.

A focused conversation can help identify where the leader is getting stuck, whether the issue is gathering, processing, deciding, stakeholder buy-in, or follow-through.

Book a Call