By Holt Hackney
As AI, cloud computing and digital platforms revolutionize enterprise technology, the role of a chief architect has evolved much more than just technical ability at best as they now represent a relationship between strategy, leadership and cross-organizational cooperation. No one has witnessed the transformational trend as closely or with greater visibility than Mark Clifton, who also helps lead architecture in Adobe’s Digital Experience business.
Clifton, who has worked with companies within Accenture, American Express and Dell Boomi, has worked to create technology systems that adapt to change at each step down in business terms. In today’s fast-moving technology world, he contends, it must be the builders, architects— architects not only who build systems that work today but those systems that can be customized for us today so that tomorrow is on track even though business is chaotic.
Clifton describes the approach as “continuous architecture” because design choices evolve simultaneously with the development and delivery of products. In practice that means architects work closely with product, engineering, security and data personnel that have to figure things out on a long-term technology perspective while supporting business priorities.
Other than his work with large enterprises, Clifton is a member of the Chief Architect Forum, in which top architecture heads share opinions across the world ranging from AI governance to platform strategy. The peer discussion, he says, is increasingly essential as architects navigate the daunting technological and organizational challenges that will drive the future of enterprise systems at a high level.
The full interview follows:
Question: As a chief architect, how do you balance long-term architectural vision with the immediate technical and business needs of the organizations you work with?
Answer: Enterprise architecture exists to help organisations change safely. In the era of AI, cloud platforms, and digital ecosystems, the pace of change has accelerated dramatically — which makes the role of architecture more important than ever.
In many ways, the role of architecture today is to enable continuous change without creating continuous chaos.
Over the course of my career — working across organisations such as Accenture, American Express, Dell Boomi and now Adobe — I’ve seen how architecture only succeeds when it stays closely connected to delivery and real business outcomes.
One concept I often talk about is continuous architecture. Rather than producing large upfront designs that try to predict everything, architecture evolves alongside delivery. Architects work closely with engineering and product teams to shape decisions as systems grow, ensuring that the choices made today don’t create problems tomorrow.
In my current role leading architecture for Adobe’s Digital Experience business — helping shape platforms used by many of the world’s largest brands to deliver digital experiences at global scale — this is particularly important.
AI is also starting to play an important role in how architects manage complexity. Modern enterprises operate hundreds or thousands of interconnected systems, and AI tools are becoming increasingly effective at analysing architectures, identifying dependencies, and highlighting potential risks.
I often describe it as AI becoming a co-pilot for enterprise architecture. It allows architects to spend less time documenting systems and more time focusing on the strategic decisions that shape how technology platforms evolve.
Ultimately, architecture isn’t about predicting the perfect end state. It’s about helping organisations make better technical decisions consistently over time.
Q: What do you see as the most important leadership qualities for a chief architect today, particularly as companies navigate rapid changes in technologies like AI, cloud computing, and distributed systems?
A: The chief architect role has evolved significantly over the past decade. Historically it was often viewed as a deeply technical position. Today it is much more about leadership, influence, and organisational alignment.
Technology is evolving incredibly quickly — AI, cloud platforms, distributed systems — but the real challenge is helping organisations adopt these technologies responsibly and effectively.
There are three qualities I believe are particularly important.
First is technical credibility. Architects still need a deep understanding of modern engineering practices and platforms. If engineering teams don’t believe you understand the technology, they won’t trust your guidance.
Second is judgement. With the pace of innovation today there is always a new platform, framework, or architectural pattern emerging. A chief architect’s role is often deciding what not to adopt just as much as what to adopt.
Third is the ability to align people across the organisation. Architecture sits across engineering, product, security, data, and operations. Success comes from bringing those groups together around a shared direction rather than relying on heavy governance.
The modern chief architect is less of a gatekeeper and more of a connector across the organisation.
Q: How has your involvement with the Chief Architect Forum influenced the way you think about architecture strategy and collaboration across organizations?
A: One of the interesting aspects of enterprise architecture is that many of the challenges we face are shared across organisations.
Whether it’s governance models, platform strategies, scaling architecture teams, or adopting AI responsibly, most organisations are working through very similar issues.
Communities like the Chief Architect Forum are valuable because they create an environment where senior architects can openly exchange ideas and experiences. Through my involvement in communities such as the Chief Architect Forum, the Association of Enterprise Architects, and the Chief Architect Network, I’ve seen how powerful it can be when architects share perspectives across industries.
You quickly realise that many organisations are grappling with the same challenges — from AI adoption to platform strategy — and those discussions often lead to better ideas and better outcomes.
For me personally, those conversations reinforce an important point: architecture should never be developed in isolation. Many of the most effective ideas in enterprise architecture have evolved through shared experience across the profession.
It also highlights how the discipline itself continues to evolve. Architecture is becoming less about static governance frameworks and more about helping organisations shape their long-term technology platforms.
Q: What makes the Chief Architect Forum valuable for experienced architects, and how does the community help members stay ahead of emerging technology and governance challenges?
A: As architects become more senior, the problems they deal with tend to shift away from individual technologies and toward organisational complexity.
You start thinking about how architecture operates within fast-moving engineering organisations, how to influence product strategy, or how to introduce new technologies without creating fragmentation across the platform.
That’s where communities like the Chief Architect Forum are particularly valuable. They bring together people who are dealing with those challenges at scale in real organisations.
Right now, AI is a perfect example. Every organisation is trying to understand how to adopt it responsibly — how to govern models, manage data, and integrate AI capabilities into existing platforms.
No single organisation has fully solved those challenges yet, which makes peer discussions incredibly valuable.
For experienced architects, those conversations often provide insights that you simply don’t get from vendor conferences or technology marketing.
Q: What technology trends are you tracking in 2026 and why?
A: Several trends are converging that I believe will fundamentally reshape enterprise architecture over the next decade.
The most obvious is AI becoming embedded across enterprise platforms. We’re moving beyond standalone AI applications toward a world where AI capabilities are integrated directly into products, workflows, and digital experiences.
This is particularly visible in the digital experience space. Organisations are increasingly using AI to personalise customer journeys, generate content dynamically, and automate interactions in real time. That has significant architectural implications around data, identity, privacy, and platform scalability.
We are also starting to see the emergence of the AI-native enterprise. These are organisations that are not simply adding AI capabilities to existing systems, but redesigning their platforms, processes, and operating models around AI from the ground up. For enterprise architects, this introduces new challenges around data architecture, model governance, trust, and how human decision-making interacts with automated systems.
Another major shift is AI-assisted software development. Engineering teams are already using AI tools to accelerate development, testing, and documentation. Over time this will significantly increase the speed at which organisations can build and evolve software systems.
A third important trend is the growing importance of modern data architectures. AI systems are only as effective as the data behind them, which means organisations are investing heavily in real-time data platforms and stronger governance around enterprise data.
Finally, I’m watching how platform thinking continues to mature. The most successful technology organisations are building reusable digital platforms rather than isolated applications. This approach enables faster innovation and allows teams to scale capabilities across products and services.
Taken together, these trends are pushing enterprise architecture into a new phase — what I often describe as architecture for the AI economy, where the role of architects is not just designing systems but shaping the digital platforms organisations depend on to compete.
Across all of these trends, one thing is clear: the hardest architecture challenges today are rarely technical — they are organisational.
Helping organisations navigate that complexity while still moving quickly is increasingly the real role of enterprise architecture.
Ultimately, the role of enterprise architecture is simple: help organisations move faster, with fewer regrets.