Is standardization pushing AEC forward, or holding it back?

Standardization. The word alone can create strong reactions in the AEC industry. Some see it as a necessary step towards clarity and consistency. Others view it as a barrier to creativity and innovation. So which is it? Does standardization make us more efficient or hold us back? The answer isn’t simple. But it’s worth exploring.

Understanding standarlization in AEC

Standardization in the AEC industry refers to the establishment of uniform protocols, procedures, and guidelines that everyone involved in a project must follow. This includes everything from building codes to project management practices. The goal of standardization is clear: enhance quality, boost safety, and simplify processes to make them easier to follow. On paper, it sounds ideal. But real-world implementation is more nuanced.

The case for standarlization as an enabler

Standardization is often considered the key for efficiency. When project teams follow shared information requirements, naming conventions, standard object libraries, and project management workflows, everything flows more smoothly. There are fewer misunderstandings, fewer delays, and less rework. It becomes easier to meet client expectations and keep everyone accountable. For example, ISO 19650 gives structure to how and when information is exchanged, helping teams stay aligned without reinventing the wheel each time.

Standardization is often considered the key for efficiency. When all parties in the AEC sector embrace the same guidelines, projects tend to run smoother. Miscommunication decreases, resulting in fewer costly delays. Another example is the standardization of materials and construction methods that can reduce quality discrepancies by up to 30%. This predictability helps project teams manage timelines and budgets effectively. Clients often see projects delivered on time and within budget, increasing satisfaction and trust in the process.

In AEC, effective communication among stakeholders, engineers, architects, contractors, and clients is crucial. Standardization helps by ensuring that all team members speak the same "language." Consider a scenario where all partners utilize the same project management software and construction protocols. This clarity eliminates confusion, supports workflows and enhances accountability. As a result, teams work more collaboratively toward shared goals.

Standardization does not have to stifle creativity. In fact, it can create an environment ripe for innovation. When baseline processes are well defined, teams can focus their creative efforts on problem-solving and improving functionality, rather than starting from scratch. For example, a team familiar with standard energy efficiency codes can explore new sustainable building technologies without getting bogged down in procedural uncertainties. The framework provided by standards can actually support innovative ideas that enhance project outcomes.

Is standardization a blocker?

While standardization helps with structure, it can also be perceived as rigid. ISO 19650 defines clear requirements, but if interpreted too narrowly, it may leave little room for alternative approaches. For creative professionals, especially designers, this can feel restrictive. The fear is that creativity might be sacrificed for the sake of ticking compliance boxes. And when standards become too prescriptive, teams may follow them blindly rather than thinking critically about what’s best for a unique project.

Another issue is resistance. Not everyone welcomes change, especially in an industry where individual methods and legacy processes run deep. Introducing new standards, even when they offer long-term benefits, often meets initial pushback. People worry about added complexity, steep learning curves, and losing autonomy over their workflows.

There’s also a risk of focusing too much on uniformity. Projects vary. A standard that works well on a large hospital may be overkill for a small residential build. ISO 19650 itself allows flexibility, but some organizations may adopt it in a way that applies the same level of control to every context, regardless of scale or complexity. That’s when standardization becomes a blocker, when it replaces judgment with templates.

Finding the Right Balance

So how do we navigate this? The key is balance. ISO 19650 should serve as a guide, not a cage. It offers a solid foundation to build on, but teams need to interpret and apply it in a way that makes sense for their specific project, role, and responsibility. That means taking the time to understand the intent behind each requirement, not just copying and pasting from a previous BEP or EIR.

It also means creating feedback loops. Standards aren’t static. They should evolve based on project experience, lessons learned, and user input. The best organizations use ISO 19650 not as a fixed manual, but as a living framework. They tweak, adapt, and improve over time.

Technology helps, too. The right tools can reinforce standard processes without making them feel burdensome. A well-configured CDE aligned with ISO 19650 can guide users through the right steps, automate routine tasks, and ensure consistency, while still allowing room for innovation in design and delivery.

Ultimately, standardization is not the enemy of efficiency. Nor is it a silver bullet. It’s a tool, and like any tool, its impact depends on how it’s used. Used well, ISO 19650 can bring order, clarity, and reliability to complex AEC projects. Used poorly, it can feel like just another bureaucratic hurdle.

The challenge for AEC professionals is to engage with standards, not resist them, and not follow them blindly either. To ask: does this help my project? Does this serve my team? Does this enable us to deliver better? Because that’s what efficiency really means, doing things better, not just doing them the same.

Summary

Standardization in AEC, particularly through frameworks like ISO 19650, can be a powerful enabler of efficiency by improving clarity, reducing rework, and enhancing collaboration across project teams. However, if applied rigidly or without context, it risks limiting creativity, provoking resistance, and prioritizing uniformity over project-specific needs. The key lies in applying standards thoughtfully, using ISO 19650 as a flexible guide rather than a strict rulebook, and combining it with continuous improvement and adaptable technology to strike the right balance between consistency and innovation.

🖊️About the author: Nicoleta Panagiotidou is an architect, ISO 19650 specialist, and the founder of BIM Design Hub. She helps AEC professionals and businesses optimize their projects through effective information management.

Breakwithanarchitect © 2025 by Nicoleta Panagiotidou. Licensed under Attribution-NonCommercial-NoDerivs (CC BY-NC-ND 4.0). Sharing is encouraged with credit and link to the original post, but full reproduction requires prior written consent.