9
OPINION
Creating a connected tech stack
Solving the silo problem in AEC firms starts with a connected tech stack that boosts collaboration, efficiency, and profit.
Technology update brought to you by
T he architecture, engineering, and construction industry is undergoing a digital transformation, yet many firms still struggle with disconnected workflows and information silos. Let’s dig into the challenges AEC firms face in adopting and integrating technology, and how creating a connected tech stack can revolutionize operations.
Niknaz Aftahi
THE CHALLENGE: DISCONNECTED SYSTEMS, FRAGMENTED TEAMS. 1. Data silos. Many AEC firms still operate in isolated structures, where information is trapped within specific teams, departments, or software tools. These data silos lead to incomplete records, inconsistent documentation, and coordination challenges. According to McKinsey, data silos can increase project costs by up to 25 percent and contribute to significant delays. The root issue is often a lack of interoperability. Tools don’t talk to each other, requiring manual reentry of data or reliance on outdated methods like spreadsheets. As a result, crucial information is either lost or becomes inaccessible at key stages of the project lifecycle. 2. Resource constraints. Digital adoption requires more than just tools, it needs people. However, only about 1 percent of architecture firms have dedicated in-house technologists or R&D teams,
according to a 2023 report by the AIA and the Center for Architecture Science and Ecology. Small and mid-sized firms often rely on peer recommendations, junior staff doing occasional research, or informal exploration of tools, a method that is inefficient and prone to bias. With steep learning curves and limited guidance, many firms fail to integrate technology meaningfully into their workflows. 3. Limited knowledge-sharing culture. Unlike sectors such as software or aerospace, where open-source collaboration and peer-reviewed research are common, the AEC industry often operates with a “closed” mindset. Sharing project data, processes, or lessons learned is the exception, not the rule. Innovative exceptions do exist. ELEMENTAL, for instance, has openly published project documentation and design strategies. Similarly,
See NIKNAZ AFTAHI, page 10
THE ZWEIG LETTER JUNE 16, 2025, ISSUE 1590
Made with FlippingBook flipbook maker