A Conversation That Stuck With Me
Recently, I was in a conversation with an expert about AI, Models, and Maths. At one point, he said something that made me pause:
I don’t need to know the math in detail. I just focus on the business: why AI matters, what problems it can solve, and why it will change industries.
It struck me: the belief that problems could be solved by framing purpose alone, without understanding the basics of what happens under the hood.
In AI, Linear algebra, probability, and optimization, these aren’t side details; they are the engine itself. Ignoring them while talking about why AI matters is like running a business review without knowing how systems behave, or how customers and supply chains actually work.
In my experience, whether in IT architecture, AI, or business design, the how never figures itself out. It has to be engineered, tested, and executed.
When systems go down, customers churn, or supply chains collapse, you can’t fix it with a deck about why we exist. You fix it with the hard work of knowing how things function, and the discipline to make them work better.
That conversation made the divide crystal clear: those who obsess over why or what without wrestling with how often drift into nonsense and pretending. Those who master the how actually build.
That conversation stayed with me. It reminded me of something simple but uncomfortable: focusing on why or what without knowing how isn’t a strategy. It’s pretending.
We’ve been told for years: Start with why. Sometimes, we’re also told to define the what. But without the how, both stall at the level of talk. And over time, that advice has quietly crippled both careers and companies.
The reality? Businesses don’t fail because they lack a why or what. They fail because they never figured out how.
Careers don’t stall because of a missing purpose. They stall because people get trapped in endless loops of why, never moving into action.
I’ve seen this up close as an IT architect.
The Architect’s Lesson
As an IT architect, you can always draft a beautiful vision. A future-ready enterprise. A digital-first ecosystem. A platform to change the world.
That’s the why. And sometimes you can even frame the what, the specific problem to be solved, the pain point to address, and the constraints to navigate.
But none of it means anything if you don’t solve the how:
-
How do you migrate legacy systems without breaking operations?
-
How do you ensure APIs, data, and security layers actually talk to each other?
-
How do you scale the architecture without collapsing under cost or complexity?
The why sets the direction. The how builds the bridge.
Without the how, the why is just a PowerPoint slide.
Too often in architecture, I’ve seen the focus shift to business value decks, glossy charts about ROI, customer experience, and strategic alignment.
Take cloud adoption as an example: the deck sells the business value of agility and cost savings. But unless you know what systems need migration, what data flows are impacted, and how integration will work with legacy ERP, how security controls will be enforced, how data egress costs spiral, the business value pitch is hollow.
I still remember sitting in a meeting where the room buzzed with slides about accelerating transformation through cloud. Everyone nodded. But when I asked, How will we migrate our legacy batch jobs without breaking overnight reconciliation?, silence. The business value story was strong, but without the how, it was theater.
The same is true in business. Startups don’t collapse because their mission wasn’t inspiring enough. They collapse because they didn’t figure out how to ship product on time, how to acquire users, how to monetize, or how to scale infrastructure.
The Fluff Problem
Too many leaders get lost in fluff.
Endless vision decks. Purpose workshops. Inspirational off-sites.
It feels profound. It sounds inspiring. But it doesn’t move the needle.
Because the real problems: what breaks in integration, what drives cash flow gaps, what causes distribution delays, what triggers customer churn, and how supply chains falter, are how problems in disguise. They’re not solved by slogans, nor by merely defining what needs to change. They’re solved by execution.
When folks drift into fluffy why talk, they mistake talking about business for solving business. It creates a halo of meaning but doesn’t answer the hard, technical questions that keep companies alive.
This is where nonsense becomes an industry. Consultants, leaders, and teams spend millions on abstract narratives instead of concrete solutions.
It also fuels a culture of pretending; the theater of progress, where everyone claps for vision statements while the hard how questions stay unanswered.
And it’s one reason behind the slow death of the corporate job. Too many roles today are built on circulating decks and crafting stories of value, while the real builders, the ones solving the how, carry the actual weight of progress.
In IT, you don’t fix an outage with a manifesto about why uptime matters.
You fix it by knowing how to trace logs, reroute traffic, and patch systems under pressure.
Likewise, companies don’t fail for lack of mission.
They fail because they don’t know how to make their mission real.
What Science Tells Us
This isn’t just my frustration as an architect; science and management research confirm it.
🔹 The Brain and Action
Excessive focus on why activates the brain’s default mode network, the seat of rumination and self-criticism. Psychologists call this analysis paralysis.
Shifting focus to how engages the executive function in the prefrontal cortex: planning, sequencing, and execution. That’s what drives progress.
🔹 Organizations in Motion
Karl Weick, one of the giants of organizational theory, argued that companies don’t really know their purpose in advance. They enact it. They take small actions, learn, and only then stitch a narrative of why.
Strategy emerges from how, not handed down from why.
🔹 Motivation Research
Deci & Ryan’s Self-Determination Theory shows that motivation comes not from abstract purpose but from a sense of competence, the belief that you can act effectively. And competence only grows through doing the how.
Lessons from IT, Business, and History
-
WeWork had one of the loftiest whys of the last decade: to elevate the world’s consciousness. But no customer signed a lease because of consciousness. The what was clear: flexible office spaces for the modern workforce. Yet WeWork failed because it never solved the how of unit economics, governance, or sustainable scaling.
-
Amazon, on the other hand, never obsessed over lofty purpose. The what was straightforward: sell books online. Jeff Bezos drilled the company on the how, lowering delivery costs, perfecting logistics, and scaling cloud infrastructure. That obsession with execution turned a scrappy online bookstore into one of history’s most powerful companies.
-
In IT history, Google didn’t win search because it had a better mission statement. Yahoo’s why was inspiring too, and it’s what, being the front page of the internet, was bold. Google won because it figured out the how: PageRank, scalable indexing, data centers that ran faster and cheaper than anyone else’s.
-
Zoom out to civilizations, and the pattern holds.
The Romans didn’t dominate the Mediterranean because their why was nobler, or their what more precise. They lasted because they mastered the how of engineering: aqueducts, roads, logistics for armies.
In contrast, the Library of Alexandria carried a magnificent why: to preserve all human knowledge, but without a sustainable how, it burned and vanished into history.
Why Is Not Enough
Don’t get me wrong: why has value. It can inspire, align, and give direction.
But over-glorify it, and it becomes a trap. It gives the illusion of depth while postponing the hard work of execution.
IT architects don’t build resilient systems by endlessly asking, Why do we need resilience. They build them by figuring out how to design redundancy, automate recovery, and handle peak loads.
Careers don’t advance because someone finally found their grand purpose. They advance because people have mastered how to code, present, negotiate, deliver, and lead.
Why, What, and How
There’s another layer here: the what.
The what is the problem statement. What exactly are we solving? What’s broken? What needs to change?
The why gives motivation. The what frames the problem. But neither actually delivers results.
History is full of examples where people had a compelling why and a clear what — but failed because they never cracked the how.
-
Kodak knew what: digital cameras were the future. It even had the technology. But it never solved how to pivot its business model.
-
Countless governments knew why railways mattered and what routes to build, but only nations that mastered how to lay track, maintain engines, and finance infrastructure unlocked real progress.
-
In IT, teams can articulate why agility matters and what needs to be modernized, but unless they solve how to decouple systems, refactor code, and migrate data, they stay stuck.
Why is inspiration. What is definition.
But how is transformation.
Without how, why and what are empty shells.
The Shift We Need
The future belongs to those who master the how:
-
How to break a big problem into solvable parts.
-
How to experiment, learn, and adapt.
-
How to act even when the why feels fuzzy.
Because clarity comes from action.
Meaning comes from progress.
And systems, whether of software, careers, or civilizations, run not on why but on how.
How is movement. How is action. How is growth.
Stop worshipping why.
Start building with how.
The Builder’s Law
Why inspires. What defines. How builds. Builders change the world
And if my years as an architect taught me anything, it’s this: a blueprint without engineering is fantasy. In business and in life, a why and what without how is the same.