top of page

Waves, not tides

Jul 29
2 min read

The question your enterprise was built to answer is dead.


For most of the twentieth century, that question was: can we produce it efficiently? Build a product, scale production, win. Hierarchies, planning cycles, annual risk models, governance: every part of the corporate machine was tuned to answer it.


Look at your last three strategy cycles honestly and tell me it still decides anything.


What changed is the shape of demand. It no longer arrives as one long, steady tide that lifts every boat. It arrives in waves: stirred by fashion, a technology, a disruption, a shock. Forming on an otherwise still surface. Fading on no calendar anyone can plan around.


What's scarce now isn't production capacity.


It's perception and response speed: seeing a wave as it forms, judging whether it's real and worth catching given your own constraints, and moving before the window closes.


The winning strategy is no longer "build and scale". It's "sense and respond".

The ambition isn't new. Haeckel described the sense-and-respond enterprise in the nineties; Teece's dynamic capabilities have anchored the strategy literature for two decades. What's new is that it stopped being optional and became structural. Sense-and-respond isn't a strategy you adopt. It's a structural demand the twentieth-century enterprise was never built to meet, and no offsite, no reorg, no two-week sprints will retrofit it into a hierarchy designed for the tide.


What must an enterprise become to meet it?

That's the architecture I published in full this week: "Perception, Design, Execution". It's the heart of Chapter 12 of Architecture of Intellect, and the framework the rest of this campaign builds on.


Which waves has your firm caught in the last five years? And which did it watch from the beach?

Related Posts

See All
The Ferrari engine in the horse cart

There is a standard recipe for enterprise AI adoption. Your organisation is probably following it right now. Take an existing process. Find the step where a human does something repetitive. Replace th

 
 
 
Why I wrote this book

This week, a board will approve an eight-figure AI budget. The evidence: a vendor deck and a thirty-minute demo. I've watched companies buy AI twice. In the nineties it was called expert systems.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating

Get the next argument first. Articles, campaign posts and book news. No more than one email a week.

bottom of page