How we set out to support a complex ecosystem

No single initiative can connect the built environment's data ecosystem alone. So we work in repeating cycles of probe, sense and respond. Each cycle sends a ripple further out, and every response drops the stone that starts the next.

Probe Sense Respond Output
Scroll to begin↓
Cycle 0

Where it began

ambition · failure · success
Probe

Three separate journeys started us off: an ambition that academics should support industry, a failure in an unsuccessful proposal, and a success in a collaborative report, each asking the same question: how should interoperability in the built environment actually be approached?

Sense

Interoperability cannot be treated in silos or as neat layers. The layers connect and influence one another, behaving as a system of systems.

Respond

So we challenged the layered view and saw interoperability as a Venn diagram, where the layers overlap and feed into each other. We founded CBEDS to connect these aspects.

Output

A reframed problem

The realisation that set the direction for everything that followed.

Interoperability as overlapping domains
this response drops the next stone ↓
Cycle 1

Interoperability in practice

April 2025 · 52 experts
Probe

With CBEDS established, the reframing had to be tested in the real world. In April 2025 we convened 52 experts to put interoperability to the test in practice.

Sense

Across the conversations the same gaps and frictions surfaced again and again. We captured them as 30 recommendations spanning the full data lifecycle.

Respond

Rather than leave them in a report, we published everything openly and turned the evidence into a live dashboard others could reuse.

Output

30 recommendations & an open dashboard

A report and a live dataset for other researchers to build on.

30 recommendations across five themes
this response drops the next stone ↓
Cycle 2

Collective impact

January 2026 · 46 leaders
Probe

The open evidence drew in the people who set direction. In January 2026 we brought 46 working group leaders together to ask what was holding the sector back.

Sense

A pattern emerged that no single initiative could see alone: a fragmentation loop. Effort was duplicated and energy lost because the sector shared no common vision.

Respond

We responded by co-creating the missing piece, a shared vision and direction the community could align around.

Output

A shared vision & direction

A common reference point the community can align around.

System of systems framework
this response drops the next stone ↓
Cycle 3

Collaboration to scale

June 2026 · 27 collaborators
Probe

A shared vision only matters if people can act on it together. In June 2026 we gathered 27 collaborators to work through collaboration and coordination, treating CBEDSynergy not as a single tool, but as a system to be designed.

Sense

Mapped with the Seven Samurai systems framework, the pattern was clear: collaboration sits inside a fragmented context, competes with go-it-alone alternatives, and only endures if governance and incentives sustain it. Connection does not scale on goodwill alone.

Respond

So we designed the intervention as a system of systems and built the infrastructure to hold it together: the CBEDSync knowledge graph and the CBEDSynergy network that keep existing efforts connected and in sync, rather than competing with them.

Output

CBEDSynergy mapped as a system of systems

The Seven Samurai systems framework applied to collaboration: what the network must connect, compete with and sustain, from the fragmented context and its competitors to the partners and governance that keep it alive.

The Seven Samurai systems framework applied to CBEDSynergy: seven interacting systems (S1 Context, S2 Intervention, S3 Realization, S4 Deployed, S5 Collaborating, S6 Sustainment, S7 Competing) with problems P1 and P2 and their relationships.
and these cycles now power the three roles ↓
enlarged