Containment and Flow: BIM Coordination for Scarcity

1. The Taste of Water

In Dune, Frank Herbert imagined a desert planet called Arrakis, a world so arid that water itself becomes sacred. On its burning sands, the nomadic Fremen survive by recovering every possible drop of moisture from their bodies, air, and even the dead. Their entire culture is built around preservation: the economy, the rituals, the architecture are all organised around the understanding that water is life, and that to waste it is a moral offence.

What Herbert described was more than an ecological condition, though it’s often downplayed as such. On Arrakis, value is born from scarcity. The Fremen’s most emblematic invention, the stillsuit, is both a feat of engineering — a suit that captures and recycles bodily moisture — and a narrative device to make it even clearer that every loss matters, and the way grandeur is expressed in the Duke’s palace is through the absence of such parsimony. Through this part of the narrative, Herbert invites us to consider how material limits can cultivate cultural meaning, how a community must turn necessity into ethics in order to survive.

Our own deserts aren’t different, but I’m no ecologist and I’m not here to talk about famine. My realm is that of the digital, and here’s where we stay. In that context, we live in an age of apparent abundance — of data, content, and computational power — and yet we suffer from a kind of drought as attention has become our most finite resource. In digital design environments such as BIM coordination, we see the paradox clearly: limitless storage, endless revisions, constant updates, and a growing sense of exhaustion. The more we produce, the less we seem to understand what truly holds value.

To design a process for scarcity in today’s digital landscape means to design for significance. It means to treat time, focus, and energy as the Fremen treated water: as elements to be gathered, conserved, and shared with intention. It asks us to build digital systems that honour limits rather than conceal them, that respect the human cost of coordination, and that make clarity itself a design goal. This week’s thought experiment is organised around this idea.

2. The Fremen Ethic: Rituals of Preservation

To survive in the desert, the Fremen had to turn survival itself into culture and their very gesture — from how they drank to how they buried their dead — became a ritual of preservation. Their architecture is carved into stone, hidden from the sun, their settlements designed for endurance.

In Herbert’s story, these choices were both drawing from his understanding of anthropology — customs are survival tools — and a pragmatic of conveying characters and their mindset: the stillsuit, the sietch, the water discipline encode a shared framework in which you are responsible for the system that keeps you alive. Scarcity forces collaboration, trust, and precision. Every action weights because every mistake carries a cost. There’s more about the urbanism lessons we can draw from Dune at this address.

Digital practice, at its best, demands the same kind of approach. BIM management, despite its promise of automation and its apparent abundance in tools and storage space, is also a culture of preservation: not of water, which our datacentres pour about both endlessly and carelessly, but of information integrity. A well-structured Common Data Environment is a stillsuit of data: it recycles, conserves, and protects meaning from evaporation through confusion or redundancy. The naming conventions, metadata standards, and version controls we so often treat as bureaucratic constraints are, in fact way to ensure that nothing essential is lost in translation, and that information survives the journey across teams and time.

Yet the Fremen’s approach to water also warns us: systems of preservation can easily become systems of control, and the line between discipline and dogma is thin. When a ritual forgets its origin — when the act of naming replaces the act of understanding, as we have seen a few weeks ago — the practice hollows out, and many digital standards face this risk: they are followed, audited, and certified, but no longer lived.

To recover meaning, we might return to the Fremen lesson that to preserve is not to hoard; it is to sustain a cycle. Water circulates. Information must, too. A healthy digital ecosystem does not trap data but moves it with care through open standards, thoughtful coordination, and humility toward what cannot be automated.

Preservation, then, is not the opposite of innovation. It is its condition. Only by recognising the fragility of what we manage can we design systems that endure because they are kept alive to the cost of every drop.

3. Designing a Digital Ecology

Let’s approach scarcity not as a curse, in this exercise, but rather as a design condition. Every system — social, architectural, or ritual — is structured around an economy of limitation, in one way or another, and to live in the desert only means the price of abundance becomes much more apparent: excess water might rot, abundance would weaken discipline, and comfort would dissolve the collective ethic that keeps you alive.

In our digital ecosystems, we’ve inverted that logic: abundance has become both our pride and our blindness, we hoard data without purpose just because we can, we replicate models instead of refining them, and we produce information faster than we can interpret it. The result is a quieter form of drought: not the absence of resources, but the absence of meaningful flow. We drown in what we create, and still we feel thirsty.

Computation, too, has its invisible but vast deserts. The servers that power our cloud infrastructures consume extraordinary amounts of energy and water to cool their own artificial climates, but the cost of our digital abundance is buried beneath its apparent immateriality. Each revision, each exported model, each automated clash report has a physical footprint, even if it never touches sand. And this is very rarely taken into account when we design Net Carbon Zero buildings. But that would be a different discourse. For now, let’s focus on how BIM management can make legible at least the abundance of data by coordinating, compressing, and giving coherence to complexity. But coordination can only achieve so much. Without deliberate constraints, BIM risks becoming an architecture for this excess: too many files, too many updates, too little synthesis. What we call “integration” often resembles accumulation; what we call “traceability” often hides an inability to let data go.

Designing for scarcity, in this context, is about treating data as a building material rather than a byproduct. It means defining when enough information is enough, and when precision turns into noise. It requires that managers, modellers, and designers act less like busy bees obsessed with producing and more like people living in a potential desert, aware that focus is as finite as water in the desert.

Scarcity, properly understood, is generative. It restores hierarchy to our decisions and reminds us that significance emerges not from the volume of what we produce, but from the clarity of what we preserve. In digital environments, as in ecosystems, abundance without meaning is just another form of decay.

4. Design Strategies: Containment, Flow, and Exchange

Every architecture depends on boundaries. Without walls, there is no room; without thresholds, no passage; without containment, no flow. The same is true for digital space. In the ecology of BIM, structure is what allows information to move with purpose rather than scatter into entropy.

Scarcity as a design approach becomes tangible here, in the ordinary gestures of coordination: deciding what to keep, what to simplify, and what to let go. Models evolve through phases — concept, design development, construction, maintenance — and yet we often carry forward the entire digital sediment of the past, as if data were sacred simply because it exists. But this is a lot of weight.

To design a digital ecology means, as a first rule, to restructure models at each transition. Each phase should begin by purging: parameters that once guided early exploration may now be irrelevant; families once used for flexibility may now introduce risk. Levels of information evolve with purpose, from ambiguity toward precision, but never toward clutter. And a model that cannot forget is not intelligent; it is hoarding.

Naming conventions and classification systems, too, must evolve with the project. A name that works in concept design rarely survives intact through construction. As information deepens, names need to scale, by adding levels of specificity, by embedding classification codes, by reflecting decisions that were once provisional. This incremental enrichment provides continuity. Each new layer of naming makes relationships legible across disciplines and time, turning the model from a static container into a readable narrative of its own making.

This strategy extends beyond the model itself. Purging parameters, cleaning views, and scaling naming conventions build legibility, prevent waste, and give clarity to those who inherit the project. To archive versions is to acknowledge time as part of the design, and to skillfully preserve the trace of decisions without forcing the present to bear their full weight. In this way, archiving is about creating room for the next phase to breathe.

Digital environments that value meaning over volume must be designed as systems of flow rather than repositories, of course: shared parameters, open standards, and federated models allow information to move across disciplines without losing its form. As we’ve said when discussing the Common Data Environment, the goal is not to centralise everything, but to choreograph exchange, to let each participant contribute their drop to the collective reservoir without flooding it.

Containment and flow: these are the twin principles of digital architecture. Containment defines what belongs and what doesn’t; flow ensures that what matters can circulate freely. Between the two lies the real craft of BIM coordination, which is not maintaining order but cultivating meaningful continuity across time, teams, and technologies.

If the desert taught reverence for every drop, our task is to design systems that show the same reverence for every bit: not by keeping all of them, but by ensuring that what remains truly matters.

5. Practice and Management: Culture, Communication, and the Measure of Enough

Digital tools can model precision, and BIM execution plans can explain how to purge and rename parameters, but only culture can sustain clarity. No standard, however refined, will survive a team that communicates in noise. A parsimonious BIM coordination begins not with software but with rhythm: with how often we speak, how we document, and how we decide when something is truly done. In other words, it begins by embracing the good practices of Agile at a deep, meaningful level.

BIM management is often mistaken for coordination at scale, yet its real challenge is governance of attention. A well-timed meeting saves more energy than an elaborate clash-detection routine; a single well-curated dashboard prevents a dozen redundant reports. The question is not how much information we can share, but how much we can absorb meaningfully.

Teams that understand this develop what might be called measured abundance: a flow of communication calibrated to purpose and the habit of wondering whether communicating something is appropriate at the precise time. They know when to broadcast and when to pause, when to consolidate instead of update. Weekly syncs replace daily noise; asynchronous notes replace endless calls. Silence, in these cultures, is not absence but trust and confidence that systems and people are aligned enough not to need constant proof. Do you remember what we said about having too many (mental) windows open? It’s amazing how good practices all tie together.

As it often happens, leadership plays a decisive role here. A manager’s task is to create an environment where focus is protected as a collective resource. This means designing rituals of communication such as fixed times for exchange, clear windows for revision, and precise moments of closure. It also means defending boundaries: keeping models from expanding uncontrollably, meetings from multiplying, and tasks from dissolving into notifications.

In this context, the most efficient teams treat coordination as choreography, where each contributor moves with awareness of the others, and the tempo of their work sustains coherence rather than fatigue. Within such rhythm, digital systems cease to feel like machines of control and begin to act as frameworks for trust.

To design flow, then, is to design culture. The Fremen learned to share water because they learned to share purpose. In our digital deserts, meaning depends on the same principle: not constant communication, but deliberate connection; not more data, but more understanding.

Conclusion

On Arrakis, designing for scarcity is called “dealing with the Law of the Minimum,” which states: “Growth is limited by that necessity which is present in the latest amount. And, naturally, the least favourable condition controls the growth rate.”

Designing for scarcity means shaping one’s practice around the awareness that every resource — time, data, energy, attention — is finite, and therefore precious. The BIM Coordinator who embraces this ethic does not seek more control, but deeper coherence. Below are ten principles for practising this discipline, both on the technical and on the non-technical side.

1. Restructure at every phase, and treat each project stage as a moment of renewal. Instead of carrying old models forward untouched, rebuild, distil, rename, and reframe so that each model reflects its phase’s real purpose and doesn’t turn into its history of accumulation.
2. Purge as you progress. Parameters, families, and views that no longer serve a clear function are not heritage but friction. Purging is not loss; it’s design editing. Make it a ritual at every milestone.
3. Evolve naming conventions. A code that works in early design should grow in precision as the project matures: add structure and hierarchy gradually, reflecting the project’s deepening understanding, not just its complexity.
4. Archive deliberately. Save versions with clear intent: what was learned, what changed, why it mattered. Archiving is memory design. It preserves narrative without suffocating the present under its weight.
5. Design for flow, not control. Build digital environments that allow information to move — between disciplines, between phases — without distortion. Federation and linked models are not compromises but acts of humility: a recognition that meaning thrives in exchange.
6. Calibrate communication rhythms. Meetings, reports, and model updates should follow a pulse that supports attention, not fragments it. Define cycles of silence as well as speech; clarity depends as much on what is not said as on what is.
7. Protect focus as a shared resource. Encourage deep work within the team: blocks of uninterrupted time, asynchronous collaboration, fewer notifications. A focused coordinator models scarcity of attention as an ethic of respect.
8. Teach the why behind the rule. Standards only live if their purpose is understood. Whenever you enforce a protocol, explain the meaning it protects — consistency, traceability, clarity. Culture grows through comprehension, not compliance.
9. Balance precision with sufficiency. Know when accuracy serves the project and when it serves ego. Perfection is often waste in disguise. Define “enough” for each deliverable, and let the team move on without guilt.
10. Lead through care, not control. Stewardship begins with tone. A coordinator’s task is to maintain trust in both system and team. Set expectations gently but firmly, celebrate restraint, and remind everyone that what matters most is not how much we model, but how well we understand what we build.

The desert teaches that survival is not about abundance, but about attention. The same is true of our digital landscapes. Be water in the desert — calm, adaptive, deliberate — and let design regain its dignity: a practice of precision guided by care, and of technology in service of understanding.