Twenty-five years, four waves of disruption, and the pattern I stopped translating

A founder tells me her pipeline isn't converting. She wants help with sales methodology. Inside two minutes I'm tracking something else. The way she described her ideal customer last month is different from how she describes it today. The prospect she just lost was hired into a function her positioning doesn't address. The pilot she keeps mentioning ended without a documented success criterion. I'm not deciding any of this is true. I'm noticing the shape these facts make together. The sales question is downstream of three conversations that never happened.

I do this all the time. In coaching sessions. In commercial diligence. In product reviews. In board meetings where I sit at the edge. I track several systems at once and read the dependencies between them. I have done it for as long as I can remember.

It took me twenty years to stop thinking this was a problem. My path through life has not been linear. Not even close.

I started in 1998, at Agency.com, the first internet agency. We were building eCommerce for Kingfisher and digital media for Elle.com when most companies didn't yet have a website. From there: WPP, Microsoft, Publicis, Kantar, frog/Capgemini. Then Aieutics.
My clients: Kingfisher, Hachette Filippacchi, P&G, Warner, Audi, Ferrero, Unilever (from Dove to DollarShaveClub). L'Oréal. Google. Burberry. Lego...

Four waves of technology disruption, and I was inside each one before it had a name. eCommerce. Digital marketing and the analytics revolution. Digital experience and customer data platforms. AI and advanced applied analytics. Each time, I arrived early, built the practice, and moved on when the field matured into something teachable.

From the outside, this looked like a resume that couldn't settle down. Strategy. Analytics. Product. Corporate innovation. Agency. Consultancy. In-house. Fractional. The sectors kept changing too. Consumer goods. Retail. Technology. Energy. Beauty. Automotive.

But for me these were never separate. They were different systems describing the same underlying reality. Each one internally consistent. Each one explaining a different aspect of how organisations create value, how customers behave, how technology shifts the ground underneath both. I was always less interested in what any single system could explain than in what lived in the connections between them.

Because that's where the truth was. Not in the system itself, but in how the systems related to and illuminated one another.

What I didn't have language for until recently was why. It wasn't restlessness. It wasn't inability to commit. It was that my mind was running multiple streams simultaneously. Tracking each system in parallel. Watching how they moved in relation to each other. Following what happened at the intersections.

I wasn't moving from one field to the next. I was holding them all at once and bouncing between them.

Multi-stream thinking is what it feels like from the inside. Dependencies are what I see when I look at a situation. Not a sales problem. Not a product problem. Not a positioning problem. The dependency chain that connects all three, and the point in that chain where the constraint actually sits.

I spent twenty years in environments that couldn't see what I was doing.

Not silenced. Just not followed. The meeting that moved on before the connection landed. The room that wanted the recommendation, not the diagnosis underneath it. The sense, repeated across two decades and four technology waves, that the full shape of the thing was visible to me and invisible to everyone else in the room.

So I learned to translate. To flatten the parallel into something sequential enough for others to follow. To hand over the twenty-line version of the three-line thought. To arrive at the conclusion and present it as if I had reasoned linearly to it, when what I'd actually done was see the whole shape at once and work backwards to the point that mattered.

It worked. People could follow the translated version. Decisions got made. Revenue grew. Call centres got restructured. Products launched. TV spend cut by 20% across fifteen brand portfolios while baseline sales held. An 85% reduction in customer service calls by solving systemic data flow issues nobody had connected.

But something was always lost. The translated version was legible. It was never quite true.

The thinking wasn't wrong. The environments were too narrow.

The cost was real. Not just the energy of constant translation, but the diagnostic power that got stripped out every time I compressed the full picture into a single-stream recommendation. The conclusion arrived without the diagnosis attached, which meant it could be argued with on the wrong axis. People would push back on the sales methodology when the real issue was upstream, in the positioning. They'd debate the tactic when the strategy layer underneath it hadn't been resolved. I could see it. The translated version didn't carry it.

All of this would be a personal footnote if the world hadn't shifted.

The environments my clients operate in have changed in two ways.

• The cadence at which the binding constraint moves has accelerated. A founder who had six months to iterate on positioning now has six weeks. An operating partner who could plan a transformation roadmap over a quarter now finds the assumptions underneath it invalidated before the plan is approved.

• The number of dependencies a team has to hold in mind at once has multiplied. Whatever you specialise in is now downstream of something you don't specialise in, and the upstream layer changed last week.

Sequential thinking was built for a slower world. This moment is not that world.

People who think in single streams need a framework to manage this. People who think in multiple streams already manage it. They need a framework so the rest of the room can follow along.

The pattern I've been seeing for twenty-five years has a shape. That shape became a framework. I call it Critical Path Layers.

It took longer to build than the cognition did. The hard part wasn't seeing the pattern. The hard part was rendering it in a form someone who doesn't see in dependencies could pick up and use. The framework is the translation, made durable. A system of artefacts that carries the diagnosis the translated recommendation always lost.

I don't need to be in the room for the seeing to happen anymore. That was the point.

For most of my career I thought I needed to get better at translating. Better at compressing. Better at making the multi-stream picture fit into the single-stream slot the room was built for.

I don't think that anymore. The room needs to change. Not because I say so. Because the problems have outgrown the thinking that created them.

The honest answer to why Critical Path Layers looks the way it does is simpler than any framework document can make it sound. This is what the inside of my head looks like when I've spent long enough on a problem to render it operational.

The rest is the rendering.

*Alexandra Najdanovic is the founder of Aieutics. She works with founders, operating partners, and corporate transformation leads on sequencing the work that actually moves the system.