Generative vs. Extractive Thinking: Yes, And...

March 12, 2026
Generative vs. Extractive Thinking: Yes, And...

My name is Ben and I naturally tend towards negative thinking.

I'm solidly Gen X, and — well — our reputation for being somewhat nihilistic purveyors of gloomy thinking isn't entirely unearned. If you could pick a spirit animal for my generation, it'd be Eeyore. "Thanks for noticing me." "It's not much of a tail, but I'm sort of attached to it." That's pretty much us at every all-hands meeting since 1997.

Before I go any further, I want to say: we've kind of earned it.

The short version (TLDR): There are two kinds of thinking — generative (what could we build?) and extractive (how do we get more from what we have?). Both are essential. But after 25 years of compounding crises — 9/11, the 2008 crash, the pandemic, AI anxiety — many organizations have drifted so far toward extractive thinking that they've forgotten how to be ambitious. Nobody raises their hand anymore. We've gotten world-class at "No, but" and forgotten how to say "Yes, and." This essay is about naming that pattern. The next ones are about what to do about it — starting with how this frame changes the way you lead and the words you use to do it.


The Last 25 Years Have Been a Lot

In 2001, the world became dangerous. The response was protection. Defense. We created a Department of Homeland Security. The organizational posture — at a national scale — shifted from "what can we build?" to "what can we protect?"

In 2008, the economy became dangerous. The response was austerity. Efficiency. Do more with less. Cut the fat. And then the downturn sort of never ended as a mindset. The "lean" mandate became permanent. Organizations learned that the smart move is to contract, and they never unlearned it.

In 2020, everything became dangerous. The pandemic. The response was freeze. Hold. Preserve what you have. And for many leaders, it worked — they were frankly stunned by how well it worked. But the cost was invisible: they stopped starting new things. On top of that, the pandemic left us with probably quite literally PTSD — people operating from a nervous system that learned "the world can shut down overnight." That's in their bodies, not just their business plans.

In 2023, the future became dangerous. AI arrived and instead of being exciting — which it genuinely is — the dominant narrative was fear. Will it take my job? Will it replace my team? Should I wait to see what happens before I commit to anything?

If you're into generational theory — Strauss and Howe's "Fourth Turning" stuff — this pattern won't surprise you. Crisis eras compress. The shocks come faster. Each one reinforces the lesson from the last: the smart move is to defend, not build. To optimize, not invest. To count what you have, not imagine what you could create. If you know the theory, you also know what comes next: the first turning. Springtime.

The pandemic put us into a holding pattern where we tried to preserve what we had and simply do our best to maintain. Now with AI, there's this other fear that AI is going to take all our jobs — or worse. The pandemic was "wait it out." AI is "wait and see."

And here we sit. Waiting.


The Two Voices

I've been a software consultant for 28 years. I walk into companies, figure out what's broken, and help them fix it. And I've noticed something over the last five or six years that I want to try to put into words.

There are two kinds of thinking. Two orientations. I've started calling them generative and extractive.

The extractive mindset asks: "How do I get more from what I have?" It measures. It optimizes. It defends. It manages. It is essential — you absolutely need this thinking — but it has a ceiling. It can only see what is. It doesn't see what could be.

The generative mindset asks: "What are we building? What could this become?" It invests. It creates. It invites. It builds. It's the audacity to believe that the next idea exists. That improvement is possible. That risks are worth taking and you haven't already seen the best version of this thing.

Most organizations I walk into have drifted extractive without realizing it. And the insidious part is that every metric still looks fine while the soul of the place kind of shrivels and dies. People show up. They do the work. They go home. Nobody raises their hand anymore. Nobody suggests improvements. And it's not because they're lazy or disengaged. It's because they learned, through a thousand small moments, that raising your hand costs social capital and produces nothing.

You know that moment. Someone speaks up in a retro and says "what if we did X differently?" and the room fills with tired reasons why not. "We tried that." "That won't get approved." "You don't understand the politics."

The person who raised their hand learns the lesson. So they stop. And now they're the person giving the tired reasons to the next person who raises their hand. It's contagious.


The Accountant Problem

Let me be clear: extractive thinking is essential. The world's greatest, amazing, at-the-top-of-their-game accountant can help you save a lot of money. They might find the rogue expense. They might optimize your budget.

That's genuinely valuable.

But it's worth remembering that that person doesn't — and won't ever — create new revenue for you.

The function is essential. The problem is when accounting logic becomes the only logic or the dominant logic. When the measuring-and-optimizing mindset colonizes territory that should belong to a different kind of thinking.

The accountant can tell you what you spent. They can tell you what you saved.

They cannot tell you what you failed to create.

There's no line item for "idea nobody had because we made it too exhausting to suggest things." There's no audit that catches "we lost our best architect because the culture went dead and she didn't want to sink with it."

The limits of the extractive mindset aren't that it's wrong. It's that it only looks in one direction. It can see what is. It doesn't see what could be. And that's not a flaw — it's just not the mission. Dreaming about what could be isn't what the accountant is there to do. But somebody has to.


Yes, And

If you've ever watched improv comedy, you know the fundamental rule: "Yes, and."

Someone says "we're on a submarine" and your job is to accept that reality and build on it. "Yes, and the captain just discovered we're out of pickles." You accept what's been established and you add something new. The scene builds. It goes somewhere nobody predicted. It's alive.

The opposite kills the scene instantly. "No, we're not on a submarine." Scene's dead. Nothing to build on. Everybody stares at each other.

Here's the thing about "no" in improv: if you're in on the joke, it's sometimes funnier to watch than "yes, and" — if the performer commits to it hard enough. I've watched improv comics deliberately try to tank scenes and it's hilarious in a deeply meta way. Finding creative ways to completely stonewall every offer? That takes effort and imagination. The audience laughs because it's ridiculous.

But here's the thing: they're laughing because it's the officially wrong approach and everyone can see it.

Now think about your last few meetings at work.

The extractive mindset in an organization sounds a lot like "No, but." Except it's more like "No, but... and furthermore, it'll never work, and it was a waste of time to ever try, and nothing positive will ever happen again, and I can't believe you even brought this up."

That's not a scene partner. That's a scene killer.

And we've been doing it for 25 years. We've gotten really, really good at it. We can kill a scene in three words. "Not in budget." "Too much risk." "We tried that."

We're world-class at "No, but."


The Part Where I Connect This to Your Job

I walk into companies all the time where the "No, but" muscle is so overdeveloped that nobody even tries anymore. The place produces output — it ships code, it hits quarterly numbers, it does the work — but it's running on fumes. The energy is gone. The curiosity is gone.

It's a gray building where people pack gray paperclips into gray boxes. Paperclips that they don't even MAKE. They just pack and ship. Under buzzing fluorescent lights. All day. Every day. Until maybe they're mercifully allowed to retire.

And here's what I've been thinking about lately: we might be running out of road on the extractive approach.

We've optimized everything that can be optimized. We've squeezed every efficiency gain. We've done "more with less" for so long that "less" is all that's left. The next dollar doesn't come from cutting deeper. The next competitive advantage doesn't come from another reorg. The next product idea doesn't come from analyzing last quarter's data harder.

At some point, someone has to walk into the room and say something new. Present new information. "Yes, and."

That's the generative move. And we're out of practice.


Why I'm Writing This

This is the first essay in a series. The next one is about AI — specifically, about why AI is the most powerful extractive tool ever built, and why that's not an insult but a design constraint that every leader needs to understand. After that, I'm going to get practical: the specific patterns I see in struggling organizations, the diagnostic questions I ask, and the leadership and communication skills that actually move teams from "No, but" to "Yes, and."

Some of this will be tactical — flow metrics, architecture decisions, delivery intelligence. Some of it will be philosophical — how you use language to create motion instead of friction, how you make change feel like an opportunity instead of a loss, how you get a room full of tired people to raise their hands again.

All of it comes from 28 years of walking into organizations that are stuck and helping them get unstuck.

I'm writing it because I think we're at an inflection point. The defensive crouch has been the right move for a long time. Maybe it isn't anymore. There's no shortage of capital, talent, or technology. What's missing is the willingness to have an original idea and back it. We've built an entire economy around extracting returns from other people's ideas — and we're running out of other people's ideas to extract from. Maybe it's time to start having our own.

Maybe the organizations that figure out how to start building again — not by ignoring the real dangers, but by refusing to let the dangers be the only thing driving decisions — maybe those are the ones that define what comes next.

Or maybe I'm just a Gen X Eeyore trying to talk himself into optimism.

Either way, the scene needs new information. Let's see what happens.

—Ben

Categories: generative-leadership