We live in a golden age of design innovation. The artifacts and environments we create have never been more advanced. Yet, if you look at how most Architecture, Engineering, and Construction (AEC) firms are managed, you’ll see a relic from the past: the Organization Chart. It is neat, hierarchical, and creates a comforting sense of order. It is also imprecise, at best, and wrong, at worst. It cannot capture the ways in which work actually gets done.

In reality, your projects don't run on lines of authority. They run on a fluid network of informal chats, quick emails, and shared problem-solving that defies formal structures. As research into complex adaptive systems suggests, teams are not static entities but dynamic, evolving networks (Ramos-Villagrasa et al., 2017). To truly optimize how we work, we need to stop looking at the static chart and start looking at this dynamic reality. This aligns with recent calls in the construction IT sector for a ‘no-model’ approach that embraces the messy reality of project information rather than idealized data structures (El-Diraby, 2023).

This is where Adaptive Coordination Networks (ACN) come in. Think of ACN as an X-ray for your project's body, which enables you to see beyond its skin.

Seeing the Invisible

You don't need a PhD in data science to start thinking like a network analyst. Building a map of your organization's actual workflow starts by identifying the ‘digital hum’ of your project. Every team generates a massive amount of passive data, but we often treat emails, Slack messages, and BIM log entries as mere storage. In reality, they are signals. Real coordination rarely happens in the formal RFI process; it happens in the 30-message Teams thread where the actual problem-solving occurs.

Once you begin to view communication as data, you can start to identify the ‘Knowledge Brokers.’ These are the individuals who act as bridges in your network. They might not be Project Managers on paper, but they are the ones everyone goes to for answers. The knowledge brokers, along with other sources of information, are then organized in a Adaptive Coordination Network (ACN), which can be used to understand, monitor and change your organizational practices. An example for such a network is shown in the figure below. 

You will likely find that a junior architect or a specific engineer is the central hub quietly holding the project together. If that person leaves or gets overloaded, your project creates a bottleneck that the Organization Chart would never predict.

Furthermore, this approach allows you to detect ‘Mode Shifts.’ Teams work differently when they are cruising through routine tasks versus when they are solving a crisis. By observing the volume and speed of connections, you can see these shifts in real-time. A sudden spike in cross-department communication usually signals a shift from ‘Routine Mode’ to ‘Problem-Solving Mode.’ Recognizing such shifts early allows you to allocate resources before the team burns out.

The Value of Operational Intelligence

Why go through the trouble of mapping this? Because you can't manage what you can't see. By making these invisible networks visible, you gain true Operational Intelligence. You can spot bottlenecks before they cause delays and protect your key connectors from burnout. Most importantly, it allows you to design your teams as thoughtfully as you design your buildings, ensuring the right flow of information.

Mapping the network is just the first step in modernizing your practice. Once you know how people are connecting, you need to understand the quality of those connections. In the next article of this series, we will look at the ‘soft’ side of data, team culture and health, and how to measure it like a heartbeat using Multi-Level Resonance Capture (MLRC).