A project can have a clear scope, capable people, and a carefully built schedule, yet still lose momentum because no one is sure who gets to make the call. To clarify decision rights is not to create more hierarchy or slow every choice with approvals. It is to give people the confidence to act, raise the right questions, and know when a decision belongs elsewhere.

For AEC leaders, this matters because decisions rarely stay in one lane. A design adjustment can affect cost, constructability, client expectations, permitting, procurement, field conditions, and the relationship between partners. When authority is assumed rather than understood, teams tend to compensate in predictable ways: they wait, escalate everything, revisit settled questions, or make decisions quietly and hope they hold.

The result is not merely inefficiency. It is often erosion of trust. People begin to interpret delays as indecision, involvement as interference, and questions as resistance. Clear decision rights create a healthier alternative: a shared understanding of how choices move through the organization and how people contribute without competing for control.

Why unclear decision rights create friction

Most organizations do not set out to create ambiguity. It develops as teams grow, responsibilities shift, new leaders arrive, or a project becomes more complex than anyone anticipated. An owner may expect the project executive to decide. The project executive may assume the design lead has authority. The design lead may believe the client needs to weigh in first.

Each person can be acting reasonably based on their perspective. Yet the work stalls because the team has not made those perspectives visible.

In AEC environments, decision ambiguity often appears in a few familiar moments: selecting between design alternatives, approving a change order, responding to a field issue, committing to a new technology, or deciding when a risk needs executive attention. The technical question may be manageable. The harder question is often, “Who has the authority to decide, who must be consulted, and who needs to understand the outcome?”

That distinction matters. Consultation is valuable, particularly when a decision affects safety, quality, client relationships, or long-term operations. But consultation is not the same as shared ownership. When everyone is invited to weigh in but no one is clearly accountable for the final call, the team can confuse participation with progress.

Clarify decision rights before the pressure rises

Decision rights are easiest to discuss when a team is not in the middle of a deadline, dispute, or urgent field condition. The goal is not to document every small choice. That would create paperwork without improving judgment. Instead, identify the recurring decisions that carry meaningful consequences for the project, the client, or the organization.

A useful starting point is to ask leaders and project teams where work most frequently gets stuck. Look for decisions that are repeatedly escalated, reopened, or delayed while people wait for direction. Those patterns usually reveal an unclear boundary, competing assumptions, or a lack of confidence in how authority is exercised.

For each significant decision type, make four elements explicit:

• Who makes the final decision and is accountable for its outcome.
• Who provides input before the decision is made.
• Who must approve the decision because of contractual, financial, safety, or governance requirements.
• Who needs to be informed once the decision is complete.

This may resemble a familiar responsibility matrix, but the conversation matters more than the chart. A matrix can assign names. It cannot surface concerns about expertise, trust, risk tolerance, or a leader’s tendency to override others at the last minute. Those are human dynamics, and they deserve direct attention.

Start with the decision, not the job title

Titles can be misleading. A project manager may have broad responsibility but limited authority over a client commitment. A discipline lead may be best positioned to decide a technical issue but need commercial input before committing resources. An executive may retain decision authority for a high-risk matter while deliberately empowering a team to recommend the path forward.

Rather than asking, “What decisions should this role own?” begin with, “What is this decision, what is at stake, and who is closest to the information needed to make it well?” Then consider what level of risk, budget, client impact, and cross-functional consequence warrants additional involvement.

This approach helps avoid two common extremes. In one, senior leaders become the bottleneck for every meaningful choice. In the other, decision-making is pushed downward without enough context, support, or defined boundaries. Empowerment without clarity can feel less like trust and more like exposure.

Use curiosity to uncover competing assumptions

When decision rights are unclear, leaders sometimes respond by issuing a directive. There are moments when that is necessary. In a safety-critical situation or a time-sensitive client issue, a fast decision may be the responsible choice.

But recurring ambiguity calls for curiosity before correction. Leaders can ask: What decision are we actually trying to make? What has made this difficult to resolve? Who believes they have authority here, and why? What risk are we trying to manage by involving more people? What information would help the decision owner move forward?

These questions do more than gather facts. They lower defensiveness and make hidden assumptions discussable. A team member may not be resisting accountability. They may be protecting a client relationship, recalling a previous decision that was reversed, or trying to avoid a financial commitment they do not believe they are authorized to make.

Curiosity also helps leaders distinguish between a decision-rights problem and a capability problem. If a team knows who decides but lacks the data, technical expertise, or commercial judgment to decide well, assigning authority alone will not solve the issue. The appropriate response may be better information, coaching, or a clearer escalation path.

Match authority to the consequences of the decision

Not every decision deserves the same process. Teams need enough structure to protect quality and manage risk, but not so much that routine work requires a committee.

A practical way to think about this is through consequence. Low-impact, reversible decisions should generally sit close to the work. For example, a coordination issue that can be corrected quickly may be best handled by the people directly involved. High-impact or difficult-to-reverse decisions, such as a major scope change, contractual commitment, safety issue, or shift in project strategy, may require broader consultation or formal approval.

The important point is to define the threshold in advance where possible. If a project manager can approve changes up to a certain financial or schedule impact, say so. If client-facing commitments require a specific review, make that expectation visible. When people understand the boundaries, they spend less energy guessing and more energy preparing sound recommendations.

There is a trade-off. More distributed authority can increase speed and ownership, but it requires capable people, shared context, and leaders willing to let others decide differently than they might. More centralized authority can protect consistency and reduce exposure in high-risk decisions, but it can also create bottlenecks and reduce the growth of emerging leaders. The right balance depends on the project, the organization, and the experience of the people involved.

Make the decision visible once it is made

A decision is not complete when one person reaches a conclusion. It is complete when the right people understand the outcome, the reasoning, and what happens next.

This is where many organizations lose momentum. A leadership team decides on a new process, project approach, or technology investment, but the people responsible for implementation hear only the conclusion. Without the context, they fill gaps with assumptions. Some may continue working from the previous direction. Others may comply without commitment because the change feels disconnected from the realities of their work.

A brief decision record can be helpful for consequential choices. It does not need to be elaborate. Capture the decision, the owner, the rationale, the input considered, key risks or assumptions, and the next action. This creates continuity when projects shift hands and gives teams a shared reference point if questions return later.

Visibility also builds trust when the answer is not what everyone preferred. People are more likely to support a decision when they can see that their perspective was heard, the criteria were clear, and someone accepted accountability for the final call.

Revisit decision rights as the work changes

Decision rights should not be treated as permanent simply because they were once written down. A growing firm, a new delivery model, a merger, a leadership transition, or a complex project can all change where decisions need to sit.

Revisit the conversation at natural transition points: project kickoff, phase changes, after a significant conflict, when a new leader joins, or when the team notices repeated escalation. Ask what is working, where decisions are slowing down, and whether the current authority matches the reality of the work.

This is also an opportunity to develop future leaders. Giving an emerging leader ownership of a defined decision category, with appropriate support and boundaries, builds judgment in a way observation cannot. It communicates trust while preserving the safeguards the organization needs.

At Connective Consulting Group, we often see that decision clarity is less about having perfect answers and more about creating the conditions for better conversations. Teams move forward when they know what they own, where to seek input, and how to raise concerns without being seen as obstacles.

The next time a decision lingers in a meeting or reappears for the third time, resist the urge to simply push for a faster answer. Ask what the uncertainty is revealing. A clearer decision right may be the practical change that helps your team act with greater confidence, accountability, and trust.