The information overload we're not talking about.

Every meaningful advancement in the MEP trades has been met with resistance. PVC solvent cement was going to ruin plumbing. ProPress fittings were a shortcut that couldn't be trusted. BIM coordination was an expensive distraction from real work. Robotic layout was a gimmick.

In every case, the skeptics were doing what skilled people do: protecting quality, protecting craft, protecting what they knew worked. And in every case, the tools eventually proved themselves, not by replacing skill, but by removing unnecessary burden so the skill could be applied where it mattered most.

There is another burden building on projects right now, and we are not measuring it.

The problem no one is quantifying.

On a mid-sized commercial or critical infrastructure MEP project, a project manager, superintendent, or foreman is expected to hold an extraordinary volume of information in their head at any given moment. Spec requirements, RFI responses, submittal statuses, schedule predecessors, budget variances, change order impacts, coordination conflicts, inspection results, delivery dates, punch list items, manpower counts, all of it shifting, all of it interdependent, all of it consequential.

The people doing this work are remarkably good at it. They have to be. But consider how their days actually unfold: toggling between four or five software platforms, searching email threads for a decision that was made three weeks ago, refreshing dashboards that may or may not reflect reality, cross-referencing a pay application against a schedule against a change order log. Hours spent hunting for information rather than acting on it. Hours spent reconstructing context rather than leading crews or solving problems on the ground.

This is not a technology complaint. It is an observation about what happens when the volume of decision-making information exceeds what any person can reasonably hold and process at one time.

The cost shows up everywhere: delayed decisions that push schedule, escalated issues that could have been caught earlier, rework driven by missed coordination, and a slow, compounding fatigue that wears down even the most experienced project leaders. We measure labor hours, material costs, productivity rates, and safety incidents in meticulous detail. We rarely measure, or even discuss, the cognitive load placed on the people making the decisions that drive all of those outcomes.

A framework for understanding it.

If we want to understand this problem clearly enough to do something about it, we need a way to describe it without exaggeration.

Start with the total inventory of structured information on a project. Every spec clause, every submittal data field, every schedule activity attribute, every RFI response, every cost code line, each one a discrete, addressable, value-bearing unit of project data. Call these Structured Data Elements. They represent the full informational mass of the job.

Not all of that information is active at any given time. A pipe diameter that has been specified, submitted, approved, and installed is settled. It no longer demands attention. But a subset of those elements remains unsettled, carrying uncertainty, subject to change, capable of affecting cost, schedule, safety, or contractual position. These are Decision-Relevant Variables: the information that still matters to an open decision.

Now narrow further. Of all the Decision-Relevant Variables on a project, only some are concurrently active, requiring monitoring, evaluation, or action within the current time window. This is the Active Decision Surface: the set of independent variables competing for a project leader's attention right now, today, this week.

The question becomes straightforward. Compare the Active Decision Surface against what cognitive science tells us about human working memory, the number of independent variables a person can actively hold, evaluate, and compare at the same time. Research consistently places that capacity in the range of four to seven items.

When the Active Decision Surface routinely exceeds that capacity, overload is not a personal failing. It is a structural condition.

The people are not the problem.

This matters because of who it affects. The men and women running MEP projects, the foremen coordinating twenty tradespeople across three floors, the superintendents sequencing work around live building systems, the project managers balancing owner expectations against subcontractor realities, these people bring decades of hard-earned judgment to the job every day. Their skill, dedication, and resilience are what hold projects together.

They deserve better than being asked to manage an information load that has quietly grown beyond what any human mind was designed to carry.

What comes next.

The goal is not to replace judgment. It is to understand the problem deeply enough to build better cognitive supports, tools that function like cognitive forklifts, handling the heavy mental lifting of tracking, filtering, and surfacing the right information at the right time, so that experienced professionals can focus on what they do best: leading people, solving problems, and building the work.

The trades have always found ways to make hard things more manageable without diminishing the craft. Thoughtful cognitive support is the next natural step in that tradition, not a disruption, but a continuation.

The real question is whether we will resist it, or lead it.