The CLEAR Process

A Decision Clarity Process: A structured approach to making organizational decisions with clarity, consistency, and accountability, without replacing leadership judgment or experience.

Organizations make decisions every day. Some are small and affect only a single person or department. Others influence budgets, projects, technology, customers, or the strategic direction of the entire business. While the importance of these decisions varies considerably, the questions surrounding them are consistent.

  • Who owns this decision?
  • Who should have a voice?
  • Who has the authority to approve it?
  • How do we ensure everyone understands the outcome?

Without a consistent approach, decisions often become driven by a few, often consistent, people, and equally as often, the wrong people. Sometimes, decisions are made by whomever happens to be available when the discussion takes place. All too often, the right people aren’t consulted. And sometimes too many people are consulted. Some decisions are even made more than once because nobody is certain who made them in the first place. Have you ever heard these questions in a meeting?

  • Who decided this was a good idea?
  • Why did so-and-so decide to do this? It’s not even their department!
  • Why did someone decide this without including the person affected the most?
  • Who said this was legal?

If you’ve heard those, you’re probably in the right spot for needing a decision-making process.

The CLEAR Process provides a simple way to bring consistency to organizational decision-making. It doesn’t tell an organization what to decide. It just helps ensure that every significant decision is owned, informed by the right people, approved by the appropriate authority, and communicated clearly.

Clarify

Every decision begins by defining exactly what decision is being made.

This sounds obvious, yet it is surprising how often meetings begin with people discussing solutions before everyone agrees on the actual question. Is the organization deciding whether to replace a system, or simply whether the existing system has become a problem? Is the discussion about hiring another employee, or about increasing organizational capacity? Those are different decisions, and each may lead to a different outcome.

The person bringing the idea forward is responsible for clearly defining the decision before asking others to evaluate it.

Label

Once the decision has been clarified, identify and label who owns the area of the business affected by that decision.

Ownership should exist long before a decision is required. Finance should have a financial owner. Customer data should have a business owner. Technology should have a technology owner. Human resources should have an owner. That owner may not make every decision personally, but they should always have a voice because they are accountable for the long-term success of that area. These can often be referred to as stakeholders.

This is a good time to note that on owner does not need to be a person. It can be, but it can also be a group of people with equal voices.

This step prevents decisions from being made without involving the people responsible for living with the outcome.

Engage

No significant decision should be made in isolation.

After identifying the owner, engage the people who bring valuable perspective to the discussion. Depending on the decision, that may include subject matter experts, department leaders, legal counsel, security, operations, finance, or a steering committee. In some organizations, this step may involve a formal vote where multiple perspectives are normalized into a single recommendation. These can be summarized as SMEs—subject matter experts—as this applies to a wide range of people with valuable perspective.

The purpose is to ensure the right voices are heard before a decision is made.

Authorize

Every significant decision deserves a clearly identified authority.

Sometimes that authority belongs to a single executive. Other times it belongs to a project steering committee, a Change Advisory Board, an executive leadership team, or a board of directors. Whatever the governance structure, there should never be uncertainty about who has the authority to make the final decision. This may be defined as the owner, and may or may not be the person who brought the idea forward.

Consultation should be collaborative, but authorization should be clear. This voice is the final authority.

Record

A decision that isn’t documented often becomes a decision that is questioned later.

Record what was decided, why it was decided, when it was decided, who participated, and who authorized it. The documentation doesn’t need to be lengthy. In many cases, a short summary in a decision spreadsheet is all that’s required. The important thing is that the organization has a shared understanding of the decision and can revisit it if circumstances change in the future.

Recording decisions also creates organizational memory. Teams change, leaders move into new roles, and projects evolve over time. Good documentation ensures the reasoning behind important decisions is preserved rather than reconstructed months later.

Note that when leadership changes, because it inevitably will, it doesn’t hurt to have all decisions in a spreadsheet. When a leader is replaced with another leader, it may help to filter the spreadsheet on the previous leader’s “authorized” column, and sorted by date. The new leader can review the most recent major decisions of their predecessor, and if there is any reason to revisit those decisions, it’s much easier to bring them to the table for reassessment.

Recording major business decisions as a habit ensures you never lose track of the relevant details. If it wasn’t written down, it wasn’t said.

Bringing Clarity to Every Decision

The CLEAR Process is intentionally simple because decision-making should be understandable by everyone in the organization.

Every significant decision follows the same sequence.

  • Clarify the decision.
  • Label the owner(s).
  • Engage the right voices.
  • Authorize the outcome.
  • Record the decision.

Whether the discussion involves approving a project, selecting new technology, defining a policy, establishing a budget, assigning ownership of critical data, or setting the organization’s strategic direction, the process remains the same.

Be careful not to over-use this process. Every question doesn’t need to be answered by process. The CLEAR Process should apply when a decision affects one or more of the following:

  • Strategic direction
  • Organizational policy
  • Financial investment
  • Technology or data
  • Customers or products
  • Cross-functional operations
  • Significant organizational risk
  • Multiple departments or business units

You don’t need CLEAR for routine operational decisions, day-to-day management, individual tasks, existing procedures, team schedules, or budgeted purchases.

If a decision creates a lasting organizational effect, use CLEAR.

Be aware that clarity doesn’t guarantee perfect decisions. It does ensure that decisions are made deliberately, consistently, and with the right people involved. Over time, that consistency builds trust throughout the organization because people understand not only what was decided, but how the organization arrived there.