Inside 4:17am: A Q&A with Simon Greenwood

In his upcoming business novel, 4:17am, Simon Greenwood draws on decades of experience across transformation, Lean, technology and organisational change, using fiction to explore some of the biggest questions facing modern organisations. Through the characters of Emma and Fred, the novel brings together ideas around leadership, AI, change and value creation. Seeing the Enterprise Different…

In this Q&A, we speak to Simon about the inspiration behind 4:17am, why he chose storytelling over a traditional business format, the creation of Emma and Fred, and the real-world experiences that helped shape the novel. We also explore some of the key concepts introduced in the book, including the Value Creation System and Enterprise Debt, as well as what Simon hopes readers will take from the story.

What first inspired you to write this book, and why did now feel like the right time to tell this story?

The book began with a question that had been nagging at me for much of my career:

Why do organisations become better at managing change, yet still struggle to change how they create value?

Over nearly forty years, I've worked through successive waves of transformation: business process re-engineering, desktop computing, enterprise applications, Lean, Six Sigma, digital transformation, process automation and now artificial intelligence.

Each promised dramatic improvements, and many delivered them. Yet I kept seeing the same underlying problem. Organisations became more efficient, more digital and more automated, but often remained surprisingly unclear about how the enterprise itself created value.

Certain moments stayed with me.

Early in my career, I stood in a bus factory and realised that the workers were constantly moving, yet the buses barely moved. Years later, I watched organisations automate processes that few people could explain the purpose of. I've worked with transformation programmes where every department understood its own objectives, but almost nobody could describe how the enterprise worked as a system.

Eventually I realised these weren't isolated observations. They were symptoms of the same problem.

AI has made that problem much harder to ignore. The more capability technology gives us, the more important it becomes to understand what we're trying to accomplish, how value is created, where it is lost and how the enterprise needs to adapt.

That's why the timing feels right. Technological possibility is expanding faster than organisational understanding.

Many leaders are asking what AI can do. I think the more important question is what their enterprise needs to become.

AI may be the catalyst for the story, but this isn't really a book about AI.

After too many decades, I learnt that all the methodologies, technologies and transformation programmes had really been pointing me towards the same question:

How does an enterprise actually create value, and why do so many organisations lose sight of it?

In many ways, this book is my attempt to answer that question. Not with a framework or methodology, but through a story. Looking back, I wasn't really learning Lean, Six Sigma, automation or AI in isolation. I was learning how to see the enterprise as a living system.

Once I saw that, I couldn't stop seeing it.

Why did you choose to explore these ideas through Emma and Fred rather than write a traditional business or leadership book?

I could have written a conventional business book full of models, frameworks and management theory. I might still do that.

But most of the things that changed how I think didn't begin with a framework. They began with an experience.

Standing in a factory and noticing that the people were constantly moving but the product wasn't. Mapping a process and discovering nobody could quite explain why some of the work existed. Talking to people doing the job and finding reality was very different from the process we'd designed. And, more than once, discovering that the problem we'd been asked to solve wasn't really the problem at all.

That's the journey I wanted Emma to make.

She starts by looking for answers. Fred keeps giving her questions. Gradually, she begins making the discoveries herself.

I wanted the reader to go through that process with her rather than have me explain the theory in Chapter One.

The story isn't simply a device for making management ideas more entertaining. Discovery is how I learned many of these lessons myself, and it's how I want the reader to encounter them.

Most business books explain. The best mentors help you discover.

Fred represents many of the people who influenced my own thinking. They rarely handed me answers. Instead, they asked awkward questions that forced me to see things differently.

That's what I wanted for Emma and for the reader.

Emma begins the story looking for answers about AI, but soon discovers she may be asking the wrong questions. Why was that an important starting point for you?

Because that's where many leadership teams are today.

They're asking: What should our AI strategy be? What can we automate or augment? Where can we improve productivity? Where can AI create value?

Those are perfectly reasonable questions. But there's a more fundamental one:

What are we trying to make the enterprise better at?

Emma initially sees the challenge through the lens of AI. Then she asks, "If intelligence is becoming abundant, why are we still creating less value than our competitors?"

That changes the conversation.

She begins to understand that AI isn't creating many of the problems she can see. It's exposing what has accumulated over decades: fragmented work, disconnected functions, ageing technology, outdated processes and capabilities that haven't kept pace.

I want the reader to begin with the familiar question:

"What should we do about AI?"

And gradually arrive at a much bigger one:

"What kind of enterprise do we need to become?"

For me, that's the leadership question.

What's interesting is that AI isn't the first technology to promise transformation. I've lived through several waves of that promise. The difference is that AI is arriving at a moment when many organisations are already struggling under the weight of complexity they've accumulated over decades.

AI isn't creating that complexity nor the Enterprise Debt. It's revealing it.

You have spent decades working across transformation, Lean, technology and organisational change. How much of what Emma and Fred encounter is inspired by things you have witnessed in real organisations?

A great deal.

Emma and Fred are fictional, as are the organisations in the story, but many of the situations they encounter have their roots in things I've experienced.

The bus factory, for example, came from a real project. We were trying to double production and discovered that while people were constantly moving, the buses weren't. Changing the system rather than asking people to work harder transformed performance.

Other scenes combine experiences from different organisations and different periods of my career. I've changed circumstances, people and outcomes, but the underlying behaviours and problems are recognisable.

That's one of the advantages of fiction. It allowed me to bring together experiences accumulated over decades without pretending that any single organisation experienced all of them.

In that sense, the story is invented, but the problems aren't.

Fiction gave me the freedom to tell the truth without telling any one organisation's story.

One of the central ideas in the book is the Value Creation System. What does that mean to you, and why do you think organisations can struggle to see it?

The simplest definition is:

It's everything that must work together for a customer to receive value.

People. Processes. Technology. Information. Capabilities. Relationships.

Inside organisations, we tend to manage these things separately. Sales manages sales. Operations manages operations. IT manages technology. Finance manages budgets.

Customers have no interest in any of that.

They experience the result.

That's why an organisation can be extremely well managed internally and still be frustratingly difficult to deal with. Every individual part can appear efficient while the overall system remains fragmented, slow or complicated.

The Value Creation System shifts the unit of attention from the individual parts to the way they work together.

That's the system leadership ultimately has to steward.

If a customer receives the wrong product, waits too long for a response, receives conflicting information, or abandons the journey entirely, they don't care whether the issue sits in Operations, IT, Finance or Customer Service.

They simply experience a failure of the system.

“Enterprise Debt” is another powerful idea within the book. How can decisions that once made sense begin to hold an organisation back?

Enterprise Debt is what happens when yesterday's good decisions quietly become tomorrow's constraints.

Nobody deliberately creates it.

An approval introduced to reduce risk. A temporary workaround. A technology platform that once made perfect sense. A structure designed around yesterday's market.

Each decision can be entirely rational at the time.

The problem is accumulation.

Over years, those decisions become embedded in processes, systems, skills, behaviours and assumptions. Eventually the enterprise finds it harder and harder to adapt, but nobody can point to a single cause.

That's why I think many organisations aren't constrained by a lack of ideas. They're constrained by the weight of decisions they can no longer see.

Enterprise Debt can't be eliminated entirely, nor should it be. The leadership challenge is to make it visible and manage it consciously before yesterday's solutions quietly determine tomorrow's possibilities.

Leaders often assume their biggest challenge is implementing change.

In my experience, it's often overcoming the accumulated consequences of decisions made years earlier for perfectly good reasons.

Enterprise Debt is the hidden inheritance every organisation carries.

Fred rarely gives Emma a straightforward answer. Where did his character come from, and is there any of yourself in him?

There is certainly some of me in Fred, although I hope I'm not quite as irritating.

Earlier in my career, I probably thought experience meant having more answers. These days, I think it often means recognising which questions are worth asking.

Fred comes partly from that, partly from some very good people I've worked with, and partly from the kind of character the story needed.

He understands more than he initially tells Emma, but his job isn't to demonstrate how clever he is. It's to make her think.

A straightforward answer might solve Emma's immediate problem. A good question changes how she sees it.

That's probably the part of Fred I identify with most.

After nearly forty years, I'm less interested in being the person with the answer and much more interested in finding the question that changes the conversation.

Away from writing and the world of business and transformation, what do you enjoy doing – or is there a fun fact about you readers might be surprised to discover?

Away from family, work and writing, three things occupy much of my life: music, genealogy and helping my sister Paula with her event company, Later At.

I’ve always loved music and still go to plenty of gigs. There’s something about seeing a band live that you simply don’t get from listening to an album, and I enjoy everything from discovering new artists to seeing old favourites. I love the small venues.

Genealogy is my other obsession. I’ve spent an unreasonable amount of time tracing the Greenwood family tree through old parish records, census returns and the occasional tantalising clue that may, or may not, lead somewhere. There is something strangely addictive about trying to work out who your ancestors were and how their lives connected to yours.

And more recently, I’ve been supporting my sister Paula with Later At, her event company. It’s been great fun being involved in something completely different from my usual world of business and transformation.

If a CEO or leader finishes the book and changes just one thing about the way they look at their organisation, what would you hope that change would be?

I'd hope they learn to look at their enterprise through the eyes of the customer.

Customers have an inconvenient habit of not caring how we're organised. They don't see departments, organisation charts, transformation programmes or technology platforms.

They experience whether we make their lives better or more difficult.

That sounds obvious, but organisations are remarkably good at becoming absorbed in themselves. We optimise functions, redesign structures, introduce technology and measure performance, while the customer experiences the consequences of how all those things work together.

So I'd hope a leader finishes the book and asks a slightly different question.

Not:

"How do I improve my organisation?"

But:

"How do we continually improve our ability to create value for the people we exist to serve?"

It sounds like a subtle shift in perspective, but I honestly think it changes almost every leadership decision thereafter.

Once you start viewing the organisation as a system for creating value rather than a collection of departments to manage, different questions emerge, different priorities emerge, and often different answers emerge too.

What are you most looking forward to as the book reaches readers, and where can people follow your journey, ideas and future work?

I'm most looking forward to hearing what readers start to see in their own organisations.

These ideas have emerged from decades of observing enterprises work, change and sometimes struggle to adapt. I'm interested in whether other people recognise the same patterns, challenge them, or see things I've missed.

If the book gets a few leaders asking different questions about AI, leadership and how their enterprise really creates value, I'll be very happy.

And if some of them start staring suspiciously at their organisation chart afterwards, even better.

For me, publication isn't the end of the thinking. It's the next stage. I want to continue developing and testing these ideas through writing, speaking, teaching and conversations with people dealing with these challenges in the real world.

People can follow that work through my social media, where I'll continue sharing what I'm learning as the theory of 4:17am develops.

After nearly forty years of studying organisations, I've come to the conclusion that enterprises are far more fascinating, complex and adaptable than we usually give them credit for.

This book captures what I've learned so far.