Architect Tomorrow

← Articles

Whatever Next? Why Transformation Needs to Get More Human

· 11 min read

Recorded live at Chief Architect Network London 2026 in April, Oliver brought together Lisa Woodall (Enterprise Architect, Transformation Strategist and Author of Whatever Next? Making Transformation Stick) and Whynde Kuehn (Founder of S2E Transformation Inc. and Author of Strategy to Reality) for a conversation about what makes transformation actually stick, why the human dimension keeps getting sidelined, and how ecosystem thinking changes everything.

There was a nice bit of symmetry to this recording. Back in February 2023, we had Whynde on the podcast with Lisa on the panel, discussing Whynde’s book Strategy to Reality. Three years later, the tables have turned and we are asking Lisa about her book instead!

Embedded LinkedIn content: view it on the original article

Blog to Book and Corridors to Chapters

Lisa’s book didn’t start as a book. It started as a decade of blogging, 156 posts, over 100,000 words, driven by a simple instinct to make sense of what she was seeing inside transformation programmes:

“That blog came pre-AI. It was just my responses to what I was seeing happening either at work or on LinkedIn. Stuff that Whynde was posting about was triggering me to think about what do I really think about that. And I just was blogging, getting my thoughts down, publishing it on the internet and seeing what conversations came as a result.”

What emerged from that body of work was a pattern. The conversations that mattered, the ones that determined whether transformation would succeed or quietly fade, were happening in corridors not in technical design sessions:

“I thought there is something in all this lived experience which I can bring together and maybe help everybody in the technology world of enterprise architecture think a bit differently, think about being more human and more honest. Because that was conversations I was hearing in the corridors but I wasn’t hearing in the technical discussions.”

That observation alone should give any architect pause. How much of the signal that matters to our work is being picked up in the formal forums, and how much is being lost because we’re not in the right conversations?

The Five Lenses: Permission to Step Back

The heart of the book is the Five Lenses of Transformation: Reflect, Reimagine, Reframe, Rewire and Reconnect. Lisa was emphatic that these are not another framework to follow:

“It’s not a framework. It’s not a process. It’s stepping back sometimes as architects. Stepping back from the technical diagrams, stepping back from the technical conversations and reflecting on why we are where we are. We’ve got a legacy estate for a reason. People that came before us have made decisions based on the context of the time.”

That last point is worth sitting with. We spend a great deal of time complaining about legacy estates without acknowledging that someone, probably someone quite smart, made those choices with the best information available at the time. Reflection means understanding the context before reaching for the solution.

Of the five lenses, Lisa identifies Rewire as the core: “That’s where we all spend most of our time. We are rewiring people. We’re rewiring processes. We’re rewiring technology.” But it is Reconnect that she considers the most important, and the one most often left unread:

“We can talk about AI, we can talk about cloud, we can talk about blockchain. I remember we’ve all forgotten that, but that was a hype thing. But why are we doing all of this stuff? We’re doing it for people. And it’s actually what shows up in that technology and how we reconnect with the people we’re serving.”

Whynde distilled the book’s contribution sharply: “This book brings us back to two things: intent and human.”

Don’t Learn Everything. Bring People In.

One of the most practical challenges to come out of the conversation was Lisa’s pushback on the assumption that architects need to develop human-centred skills themselves. Instead, she argued for broadening who sits at the table:

“I’m not saying we need to all develop the skills to be more human-centred. I’m saying make sure you’re opening your ears and your eyes to people that can bring that specialism into your teams.”

She spoke about a behavioural researcher she worked with at WPP who transformed her own thinking about technology deployment:

“She wasn’t a researcher of the business or technology. It was very much about human behaviours. She really demonstrated for me the power of a day in the life, actually getting out into the organisation, watching what people are doing, listening to what people are saying, what they were thinking before they open their laptop. You can’t capture that in your requirements document.”

This echoes Jenny Wilson’s point from a previous Architect Tomorrow episode about architects being enablers, not gatekeepers. The question is not whether architects need to become behavioural scientists. It is whether architecture teams are diverse enough to include the perspectives that matter. Lisa’s answer is direct: “Even if you just do that once a year, just get out there and see what people are experiencing in their work. I think you think about your technology challenges differently. I know I did.”

The Unsaid: What Lurks Below the Surface

Whynde picked up on a line from the book that deserves to become a design principle in its own right: “Lisa says, ‘How change feels to people matters as much as what it does.’ I don’t think we spend nearly enough time, and also too late, focusing on that change.”

She identified two structural failures that let the emotional and political dimensions of transformation derail progress. The first is the absence of genuine spaces for dialogue:

“When we don’t create real authentic forums and spaces for people to dialogue and ask questions and voice what they’re thinking, all that stuff is lurking below the surface. Sometimes change management even when we do it, it feels very mechanical.”

The second is more systemic: “The organisational structures and motivations of leaders, which can create really siloed political decision-making.”

That word “mechanical” is telling. We have got quite good at the theatre of change management: the communications plan, the stakeholder map, the readiness assessment. But if the forums are not authentic, if people cannot say what they actually think, then it is all surface.

Designing for the Ecosystem, Not Just the Enterprise

The conversation took a significant turn when we moved beyond the enterprise boundary. Lisa made an observation that connects to something I have been working on with Pragmatic Ecosystems and Dynamic Ecosystem Architecture:

“We’ve often been at the forefront of designing the new organisations, what we’re going to outsource, which platforms we’re going to bring in. That is all part of an ecosystem. And actually it’s not about designing for our organisation, it’s about designing for the ecosystem that we sit within and being sure of the consequences not just for us, our teams, our processes and our systems, but also for the teams, processes and systems of the organisations that are part of our supply chain. Because they’re often thought of last.”

This is a critical insight. Too much of our architectural thinking stops at the organisation boundary. The decisions we make about platforms, outsourcing, and integration ripple through partner organisations and supply chains in ways we rarely model or consider. As I noted during the discussion, Ron Kersic put it well in our Futuring Architectures episode: “It’s not your ecosystem. You cannot build it. You cannot design it. You can design your position.”

Lisa connected this to the practical realities of post-implementation reviews: “If you really look back over the last 20 or 30 years of the work you’ve been doing, you will recognise those meetings that happened, those post-implementation reviews that would have highlighted the engagement of stakeholders too late. And it’s often those ecosystem stakeholders that we’ve involved too late.”

Whynde extended the ecosystem concept into business architecture constructs, noting that value networks and value streams can readily accommodate sustainability dimensions: “We can use the same construct and map on it materials and energy. Circular economy thinking.” This is exactly the kind of thinking we need more of, reusing architectural tools we already have rather than inventing new ones.

The Natural Ecosystem We Conveniently Ignore

I pushed the conversation further to address the ecosystem we most often overlook. Our worlds are increasingly digitised, virtualised and abstracted from the physical world. But fundamentally, we are all part of the natural ecosystem. We are going to start facing into some hard limits to technological progress: there are only so many data centres we can build, and only so much energy we can distribute to power them.

Ecosystem thinking in its fullest sense means considering not just the business ecosystem but the societal and environmental ecosystems that underpin everything. As architects, we are collectively making choices and decisions that impact sustainability in its broadest sense. The ripple effects of individual projects may seem small, but in aggregate they matter enormously.

The Ironies of Automation: Sleepwalking Risks in Practice

An audience question (from Charles Betz of Forrester, who will appear himself on the podcast when the Twin Cities Business Architecture Forum episode goes live) brought the conversation sharply into the present. Referencing Lisanne Bainbridge’s 1983 paper Ironies of Automation (which inspired a recent newsletter), which argued that humans left “in the loop” to monitor automated systems will inevitably lose the context needed to intervene when those systems fail, the questioner asked whether business architecture has started to address this.

Lisa’s response was characteristically direct:

“Enterprise architects have a role to play in slowing down maybe some of the hype and potential that AI can deliver to allow that human side to catch up. The figures this morning: 1.5 trillion being spent on AI. How much of that is going into the technology side and how much is going into that human capability side? I would say it’s probably 98% on the technology and 2% on the human side. I think we’ve got to correct that.”

This connects directly to the sleepwalking risks we have been exploring on this podcast. Confirmation fatigue. Capability degradation. The quiet erosion of skills and engagement when you take the interesting work out and leave people staring at a production line looking for anomalies. As I noted during the discussion: how interesting are these roles when you take the friction out? There was a recent post about software engineering that captured this perfectly: is it really more fulfilling to debug AI-generated code than to get the dopamine hit from solving the problem yourself?

Whynde brought the macro perspective: “There’s a lot of things we can do and this conversation is so focused at a micro level. We need to come up and say, macro, does this make sense where we’re going?”

That is exactly the right question.

Two Books, One Mission

When asked to compare Whatever Next? and Strategy to Reality, Lisa and Whynde positioned them as companions:

Lisa: “My book is more a lived experience. It’s someone’s reflections on living through the last 30 years of transformation. Whynde’s would be more of the go-to book for business architecture in strategy execution.”

Whynde’s response was simply: “They’re companions.”

They are. And the architecture community is richer for having both.

The Path Forward

Lisa summed up the signal that architects need to tune into:

“We’re enterprise architects. We join the dots. We see things that other people in the organisation don’t see because we have the privilege to work across the silos. We are also in a position where we can go deeper. We can pick up the signals that maybe others aren’t picking up because we’re not as siloed in our thinking. The real message is to turn the volume up on those signals, those hunches, that intuition that you’re getting and pay more attention to that.”

The question for all of us is whether we are listening for the right signals or just the loudest ones. The corridors as much as the ARBs. The supply chain partners as much as the internal stakeholders. The natural ecosystem as much as the business ecosystem.

Lisa’s book gives us five lenses to see more clearly. It is up to us to actually look.

Lisa Woodall is the author of Whatever Next? Making Transformation More Human, More Honest and More Likely to Stick. Find the book, the Five Lenses of Transformation and Lisa’s blog at whatevernextbook.com

Whynde Kuehn is the author of Strategy to Reality and Founder of S2E Transformation. Find her work at strategyintoreality.com and s2etransformation.com and her book interview here.

Oliver Cronk is Founder of Cronk Advisory: cronkadvisory.com a fractional CTO and chief architect consultancy specialising in regenerative and sustainable architecture, innovation and AI. Oliver is also the founder of Architect Tomorrow.

This episode was recorded live at Chief Architect Network London 2026. Find out more about CAN and how to apply to join at chiefarchitectnetwork.com

AI use disclosure: This newsletter was written by Oliver with assistance from a single Claude 4.6 Opus prompt to pull out highlighted parts of the transcript. With human review and editing of the output.

See also related previous editions of the newsletter / podcast:

Originally published on LinkedIn. Comments and discussion live there.