Rethinking Construction Hierarchies: A Pilot Program for Open Project Communication

For decades, the Architecture, Engineering, Construction, and Operations (AECO) industry has relied on a hierarchical communication structure. Questions travel up and down the chain of command, Requests for Information (RFIs) are processed through formal channels, and project decisions are made by designated authorities. While this system provides accountability and clear lines of responsibility, it can also create bottlenecks that delay problem-solving and limit the valuable contributions of those closest to the work.

What if there was a better way?

What if licensed professionals, union tradespeople, project managers, facility representatives, and owners could all participate in a structured, open communication environment while preserving the formal processes required for contractual compliance and risk management?

This concept is worth exploring through a pilot project.

The Vision: Open Communication with Structured Accountability

The goal is not to eliminate the RFI process, nor is it to dismantle project leadership. Instead, the objective is to create a collaborative communication framework where everyone involved in the project has a voice.

In this model:

• Anyone can identify a concern.

• Anyone can suggest a solution.

• Anyone can raise a potential risk.

• Authorized parties still make final decisions.

• Formal RFIs remain the official mechanism for contractual clarification.

The result is a project environment that values expertise wherever it exists.

After all, the electrician installing conduit may identify a constructability issue before the design team sees it. The maintenance technician may recognize an operational challenge before equipment is installed. The carpenter may spot a sequencing conflict weeks before it affects the schedule.

Projects succeed when knowledge flows freely.

Why Traditional Hierarchies Can Create Challenges

Traditional project communication often follows a path similar to:

Craft Worker → Foreman → Superintendent → Project Manager → Architect/Engineer → Owner

While this structure offers clear authority, it can also introduce delays and information filtering.

Common challenges include:

• Delayed issue resolution

• Information bottlenecks

• Limited feedback loops

• Missed opportunities for innovation

• Reduced engagement among field personnel

Valuable insights are often lost simply because they never reach the right people at the right time.

A New Model: Flat Communication, Hierarchical Decision-Making

A successful pilot project would embrace a simple principle:

Flat communication. Hierarchical decision-making.

This means everyone is encouraged to communicate openly, but only designated individuals retain authority to:

• Approve design changes

• Submit official RFIs

• Authorize expenditures

• Modify schedules

• Direct work activities

This distinction is critical.

Discussion does not equal direction.

Suggestions do not equal approval.

The chain of accountability remains intact.

Mechanisms for Open Communication

Project Observation Log

One of the simplest and most effective tools is a Project Observation Log.

Think of it as a "Pre-RFI Registry."

Any team member can document:

• Design concerns

• Constructability issues

• Coordination conflicts

• Safety observations

• Cost-saving opportunities

Many issues may be resolved through discussion before becoming formal RFIs.

Weekly Collaboration Meetings

Rather than waiting for problems to escalate, project teams can conduct weekly collaboration sessions involving:

• Trade representatives

• Project managers

• Design professionals

• Owner's Project Managers

• Facility representatives

• End users

These meetings focus on upcoming work, potential risks, and coordination opportunities.

The objective is proactive problem-solving rather than reactive troubleshooting.

Digital Collaboration Platforms

Modern technology provides excellent opportunities for transparent communication.

Platforms such as:

• Procore

• Autodesk Construction Cloud

• Microsoft Teams

can be configured to support open discussion while maintaining document control and audit trails.

Constructability Review Workshops

Monthly constructability workshops can bring together:

• Architects

• Engineers

• General Contractors

• Trade Partners

• Facility Staff

to review upcoming work and identify potential conflicts before they impact the project.

Many RFIs originate from issues that could have been discovered earlier through collaborative planning.

Anonymous Feedback Channels

Not everyone feels comfortable speaking up in meetings.

Providing anonymous feedback options through digital forms or QR code submissions allows concerns to be raised without fear of criticism or retaliation.

Often, the most valuable observations come from those closest to the work.

Potential Benefits

If implemented correctly, an open communication pilot could deliver significant benefits.

Earlier Problem Identification

Field personnel often discover issues before they become costly project impacts.

Reduced Rework

Early coordination leads to fewer surprises during construction.

Improved Constructability

Trade expertise contributes directly to project planning and execution.

Greater Innovation

Open environments encourage creative thinking and problem-solving.

Enhanced Team Morale

People are more engaged when they feel their expertise is respected and valued.

Knowledge Capture

Lessons learned can be documented and applied to future projects.

Challenges to Anticipate

Open communication is not a cure-all.

In many ways, it simply replaces one set of challenges with another.

Information Overload

A project may receive hundreds of observations and suggestions.

Without a structured review process, valuable information can become overwhelming.

Authority Confusion

Participants must clearly understand who has decision-making authority.

A discussion forum is not a source of project direction.

Meeting Fatigue

Too many meetings can reduce productivity.

Communication systems must remain efficient and focused.

Resistance to Change

Some team members may view open communication as a threat to established authority structures.

Strong leadership and clear expectations are essential.

Professional Liability

Licensed professionals remain responsible for design decisions.

Input from the field is valuable, but professional accountability cannot be delegated.

Are Flat Structures Really Better?

The answer may surprise many people.

A completely flat organization can experience just as many challenges as a traditional hierarchy.

Hierarchies tend to struggle with:

• Slow communication

• Bottlenecks

• Limited feedback

Flat structures often struggle with:

• Decision paralysis

• Information overload

• Unclear authority

The most successful organizations often blend the strengths of both approaches.

Open communication encourages participation.

Structured leadership ensures accountability.

A Pilot Program for the Future

Imagine a project collaboration council consisting of:

• Owner's Project Manager

• Project Manager

• Superintendent

• Design Lead

• Trade Representatives

• Facility Representatives

• End Users

The operating principle could be simple:

Anyone can identify a problem. Anyone can suggest a solution. The responsible party makes the decision. Every decision is documented.

As the AECO industry continues to embrace collaboration, technology, and integrated project delivery methods, the opportunity exists to rethink how project teams communicate.

The future may not belong to rigid hierarchies or completely flat organizations.

Instead, it may belong to project teams that combine open communication, shared expertise, and clear accountability to achieve better outcomes for owners, designers, contractors, and end users alike.

In construction, the best ideas do not always come from the top of the organizational chart. Sometimes they come from the people closest to the work. The challenge is creating a system that allows those ideas to be heard.

Blog written by Mel using ChatGPT