Key Takeaway: Systems thinkers with business background are the highest-leverage people in the current AI ecosystem.
AI didn't create a new superpower. It revealed one that's been undervalued for decades. Not data scientists. Not prompt engineers. Not the executive who tells a great story in a room. The people who see how components fit together, who decompose problems into structures, who design for change -- and who also understand unit economics, customer behavior, and why organizations actually behave the way they do. This is a specific and rare combination. Most technical people lack business intuition. Most business people lack structural thinking. The intersection has been undervalued for decades because institutions couldn't tell the difference between someone who sees the system and someone who tells a good story about it.
I'm one of them. Twenty years in environments that reward narrative thinking -- McKinsey, sovereign wealth, venture capital, enterprise consulting. Every one of those institutions promotes the person who tells the best story, not the person who builds the best structure.
The two modes
Narrative thinkers reason by analogy. They communicate through stories. They're persuasive in rooms. Systems thinkers reason by decomposition -- components, dependencies, leverage points. They communicate through structures.
Both matter. But institutions weighted narrative heavily because story scales faster through an organization. A compelling narrative aligns a hundred people in an hour. A well-designed system can't be explained in an hour -- it has to be experienced through its outputs.
Narrative-strong people get promoted, then select for skills they recognize. Within a decade, leadership believes structural analysis is an input, not the work itself.
The email test
Systems thinkers write: "Three things: (1) X depends on Y, (2) if Y delayed, Z shifts, (3) decision needed." Narrative thinkers write: "Hey -- wanted to loop you in. Great progress on X, team is energized. One thing that's come up..."
Same information. Institutions reward the second. I ran this against twenty years of email. Two people matched my style. Two.
What AI changed
For twenty years, systems thinkers had a gap: the technical execution of their ideas required either teams they couldn't access or skills they didn't have at production depth. AI collapsed that gap.
A systems thinker with AI tools builds directly. Not toy prototypes -- actual production systems. I run a platform with 13 dependencies, 200+ automated tests, and a RAG system processing thousands of documents. Before AI: identify bottleneck, build presentation, convince stakeholders through narrative, hire team. Now: identify, design, build prototype in days. The architecture diagram becomes the working system.
AI can write the implementation. It cannot see the architecture. It cannot decide what to build. It cannot evaluate whether the structure matches the problem. Context engineering is structural work.
And here's what actually changed: systems thinkers can now create narrative by building working systems. The system IS the story. A running platform with 18,000 RAG chunks and sub-millisecond search communicates more than any deck ever could. For twenty years, we had to translate structural insights into stories to get anything done. Now the systems speak for themselves.
Why business background matters
Business experience means you know which problems are worth solving -- not just technically interesting but economically meaningful. You grok incentive structures, organizational dynamics, sales cycles, unit economics.
At McKinsey, I spent three years building analytical structures that partners used to tell stories. At ATIC, I built frameworks for evaluating semiconductor investments. At Staircase, I built the product and learned the hard way that building isn't enough without go-to-market muscle. Each experience deposited pattern recognition that's now deployable through AI tools at a speed that wasn't possible before.
The leverage equation
The minimum viable team size has collapsed. A three-person pod can now do what used to require fifteen people. The cost of technical ownership dropped by an order of magnitude. The barrier between "I see the right architecture" and "it's running in production" effectively disappeared for people who think in systems.
Stop apologizing for how you think. The structural insight is the value. The communication is packaging. Don't confuse the two. Systems thinkers with business context who spent twenty years feeling out of place in narrative-driven institutions are holding the better hand -- building got fast enough that the systems speak for themselves, and the business judgment to know what to build is the scarce input.