I have just returned from the ATN Summit in London, a two-day event bringing together some of the most forward-thinking architects, technologists, and founders working in the built environment today.

For those who were not in the room, this is a concise briefing on what was actually discussed, what is working in practice, and where the industry is heading next. This is not a summary of talks. It is a distillation of the underlying patterns that emerged across the event, supported by both my own notes and observations from attendees.

The focus is on three things:

-/ what leading practitioners are doing differently
-/ where technology is genuinely delivering value
-/ what this means for architecture practices today

If you are reviewing how your workflows operate across projects, I am happy to share how other practices are approaching this.

Book a call here: 30 min with Allister Lewis

The clearest takeaway from the ATN Summit is that the industry conversation has moved beyond tools.

For the past decade, much of the focus has been on identifying and adopting new software. That conversation is now maturing. The leading practices are no longer asking which tools to use, but how those tools operate together across a project lifecycle.

This shift towards workflow thinking is significant. It reframes technology from a collection of isolated applications into a connected system that supports decision-making, design development, and delivery.

In practice, this is where the real gains are being realised. Not through individual tools, but through how information flows between them, how tasks are automated, and how teams operate across stages.

A number of talks stood out, not just for their content, but for what they reveal about the direction of the industry.

Aaron Perry opened the conference with a clear articulation of the structural challenges facing the AEC industry, particularly around fragmented workflows and disconnected data. He then demonstrated how Qonic is evolving to address these issues, showing significant product development over the past nine months.

The platform has moved beyond a high-performance browser-based model viewer into an environment where users can model, manipulate geometry, and manage data within a single interface.

Implications: There is a clear move towards unified, web-based environments that reduce fragmentation across tools and workflows. This is where meaningful efficiency gains are likely to be realised.

Sanne presented MVRDV’s work through the lens of sustainability, focusing on how the practice has embedded embodied carbon tracking across its projects. A centralised dashboard enables comparison, monitoring, and informed decision-making throughout the design process.

Importantly, the presentation demonstrated that high-quality architectural design and sustainability are not competing priorities, but can be balanced within a structured system.

Implications: Sustainability is becoming a measurable and integrated part of design workflows, particularly at early stages where decisions have the greatest impact.

Gary McLuskey shared how Greystar is using data from tenants to inform and improve future developments. The presentation highlighted a commitment to integrated workflows, combining user data, design processes, and technology such as Giraffe to refine outcomes over time.

This reflects a developer-led approach that prioritises feedback loops and continuous improvement.

Implications: The centre of decision-making is increasingly shifting towards developers who are leveraging data to drive design outcomes. Architects need to align with this reality.

Pamela and Jesper presented the evolution of Finch, from an early parametric concept into a multi-platform tool for generating and optimising layouts across Rhino, Revit, and Archicad.

Recent developments include expanded modelling capabilities and application across additional sectors such as commercial and healthcare. The decision to remain platform-agnostic is particularly notable.

Implications: Tools that integrate across existing architectural workflows, rather than replacing them, are more likely to achieve widespread adoption.

Harlan Miller presented a series of projects spanning several decades, illustrating the continuity between design intent and final delivery. A key example was a large-scale tower project in Dubai, where the original concept was maintained through a complex and extended delivery process.

The presentation emphasised rigour, consistency, and long-term design stewardship.

Implications: While technology is evolving, the fundamentals of architectural quality, control, and intent remain central. Workflow improvements must support, not replace, these principles.

Mollie Claypool presented AUAR’s approach to automated timber construction, combining digital design, robotic fabrication, and on-site manufacturing. The use of container-based robotic systems to produce building components represents a significant shift in how housing can be delivered. The ambition to scale this model, particularly in the US market, was clear.

Implications: Construction innovation is becoming increasingly integrated with design and technology. This has the potential to reshape delivery models, particularly in housing.

Across these talks, the common thread was clear. The industry is moving towards more connected, data-driven workflows where design, analysis, and delivery are increasingly integrated.

What was presented on stage does not reflect the industry average. It reflects what is possible when workflows are intentionally designed and consistently applied. There is a clear level of integration, control, and clarity in how leading teams operate that is not yet widespread.

What this means: A performance gap is emerging between practices that are actively designing their workflows and those that are not.

AI was present across the event, but it was rarely positioned as the primary focus. Most teams are still concentrating on improving delivery, coordination, and reliability. The emphasis remains on getting core processes right.

What this means: The industry is still addressing foundational workflow challenges before AI can be applied at scale.

The most practical examples focused on automation rather than AI. This included reducing repetitive tasks, improving data flow, and connecting systems across different stages. These changes are incremental, but highly effective.

What this means: Real value is currently being delivered through operational efficiency, not speculative transformation.

The strongest presentations did not focus on individual tools. They demonstrated how tools operate together across a project lifecycle. This is where productivity, consistency, and quality are being improved.

What this means: Software selection alone is not enough. Competitive advantage comes from how systems are structured and used in practice.

There is clear progress in the development of next-generation BIM tools and approaches. However, adoption and maturity vary significantly across the ecosystem. Some tools are well integrated into workflows, while others remain experimental.

What this means: Practices need to be selective and pragmatic. Not all innovation is ready to support live project delivery.

Sustainability was consistently present in discussions, often linked to data, analysis, and early-stage decision-making. It is no longer treated as an isolated requirement.

What this means: Environmental performance is increasingly being addressed at the feasibility stage, where it has the greatest impact.

The presence of younger architects was notable. They are more open to new tools, more collaborative in how they work, and less constrained by legacy processes. Their expectations of how practice should operate are different.

What this means: Adoption of new workflows and technologies is likely to accelerate as this group moves into more influential roles.

The way attendees documented, shared, and discussed the event highlighted a shift towards a more visible and connected industry. Content, communication, and audience are becoming part of professional practice.

What this means: Practices that engage with this will build stronger networks and greater visibility.

The level of organisation, curation, and delivery was high. Bringing together this range of perspectives in a coherent way is not straightforward. It reflects a deliberate effort to create value for the community.

What this means: Curated environments like this are becoming important platforms for knowledge exchange and industry alignment.

Many younger attendees are being exposed to advanced workflows and tools early in their careers. They are not bound by the assumptions or limitations that have shaped current practice.

What this means: Future practices will be built on different foundations, with fewer constraints and a greater emphasis on integration and efficiency.

The consistent theme across the ATN Summit is that the industry is not constrained by a lack of tools. It is constrained by how those tools are used.

Most practices are operating with:

-/ disconnected systems across project stages
-/ unclear handovers between teams
-/ limited visibility of how information flows through a project

This creates friction, duplication, and inefficiency, particularly as projects move from early design into delivery. By contrast, the practices operating at a higher level have taken a different approach. They are not focused solely on adopting new software. They are designing how their workflows operate across the full project lifecycle, from feasibility through to construction.

This includes:

-/ defining how data is created, structured, and shared
-/ integrating tools so that information flows without manual intervention
-/ automating repeatable tasks where appropriate
-/ aligning design, analysis, and delivery processes

The result is not just increased efficiency. It is better decision-making, earlier clarity, and more consistent outcomes. This is where the real opportunity now sits. Not in identifying the next tool, but in defining how practice operates as a system.

This is an area I am increasingly focused on in my work with practices:

Helping teams define how their systems operate in practice, where value is created, and how technology supports better outcomes across a project lifecycle. This is the work I am increasingly focused on through workshops and advisory engagements.

If you are reviewing how your workflows operate across projects, I am happy to share how other practices are approaching this.

Book a call here: 30 min with Allister Lewis

This newsletter exists to help architects navigate technology with confidence, not hype by focusing on workflows, decisions, and real practice constraints.

Thanks for reading!

Allister