The Art of Saying No to AI

AI makes it incredibly easy to add things.

A new use case here, another pilot there. A training program. A governance committee! Before you can say "acceleration" you're stuck in planning and alignment meetings.

The thing is that each addition seems reasonable on its own.

But taken together, they will turn your AI transformation into a sprawling collection of pending decisions.

And that’s why every good AI strategy now more than ever needs to tackle the "art of saying no" by not just articulating what the organization wants to do with AI.

But giving an explicit answer on what it will deliberately ignore for now.

Want to find out how?

Let's dive in!

A few years ago, finding possible AI use cases was genuinely difficult.

You needed people who understood the technology, people who understood the business, and enough imagination to connect the two.

Today, you can ask ChatGPT to generate 100 AI use cases for an insurance company, manufacturer, retailer, or trade-show organizer before your first coffee gets cold.

I saw this firsthand in a recent engagement: one week of opportunity-mapping workshops at a 500-person company surfaced around 350 problems – and 270 of them looked like a good fit for AI.

This is not a strategy.

Because each of these 270 items will raise questions like:

The cost of producing an idea has literally collapsed to zero.

The cost of evaluating, coordinating, funding, and operating it has not.

That organizational cost is now the real bottleneck.

No management team can meaningfully commit to 270 initiatives. It's just too much.

But the list didn't need 270 decisions. It also did not need deleting 260 use cases and keeping the best top 10.

What was needed was merging and deduplication. So we looked for artificial fragmentation: different departments asking for different variations of the same thing.

Take document extraction for example. For some teams, this might come in the form of contract Q&A. Others might use it for internal decision preparation. They look different because they originate from different teams, processes, and organizational boxes.

Strategically, though, they were often the same request: better knowledge access arriving through different doors.

We also filtered the list through the $10K Threshold (about 110 ideas survived) and deduplicated what remained by underlying problem instead of org chart.

The result was 7 opportunity clusters worth more than $1M per year in untapped potential. The individual use cases still exist underneath.

But the organization now has 7 things to focus on instead of 270.

I'm seeing the same pattern in another engagement right now. The list is smaller (50 use cases instead of 270) but the number of themes that can actually hold management attention is the same. (In this case, we're aiming for four to five.)

Most business cases account for licences, implementation costs and expected savings. Very few account for management attention.

Someone must champion it. Someone must coordinate stakeholders. Someone must review the output. Someone must answer questions when it fails. That cost rarely appears in the proposal.

But attention is the scarcest resource in the building.

This is why saying no is not the opposite of ambition.

Saying no allows you to turn ambition into action.

I found two ways of saying no to be helpful:

Look for use cases that appear different but depend on the same capability, data, workflow, or business outcome.

Instead of funding them separately, cluster them around a central opportunity themes – like the five knowledge-access requests above.

This matters most for Engineered AI: every disconnected initiative drags its own infrastructure, integration, and maintenance along with it.

My rule of thumb: deduplicate by underlying problem, not by org chart.

This is what the $10K Threshold is for.

If a use case can’t generate at least ~$10K per year in recurring impact, it does not deserve engineering, integration, governance, or management attention.

It's the filter that cut our list from 270 ideas to 110 in a single pass.

Not because the ideas were bad. Because they were too small to matter.

"Not now" is a valid strategic decision.

It is in fact often better than leaving an initiative in a permanent state of vague importance.

One warning, because I learned this the hard way.

Present seven themes that span multiple departments for funding and the organization will end up debating the portfolio instead of building the first profitable thing. That is exactly what happened with the $1M AI roadmap I mentioned above.

So treat "Saying No" and ownership as two halves of the same move:

"Saying No" takes you from 270 use cases to seven themes.

Saying Yes to Ownership takes you from five themes to the one opportunity you start with – valuable enough to matter, narrow enough to ship, with a named sponsor. That sponsor needs enough authority to protect the initiative across departmental boundaries and resolve the trade-offs it creates. Spoiler: In many cases, that's the CEO.

To be clear, the goal is not less AI.

“Saying No” is not an argument against ambitious AI investment — broad Productivity AI adoption should absolutely continue.

But to overcome the impact plateau and unlock the real opportunities, you have to say no to a lot of things and assign clear ownership to the right things.

Before adding another initiative to your AI roadmap, ask these 5 questions:

Can’t answer these clearly? You’re adding more possibilities to the pile, but not making your actual AI strategy stronger.

AI has made it easier than ever to create.

Attention concentrated on a handful of themes cannot simultaneously support hundreds of ideas.

A good AI strategy makes those trade-offs explicit instead of hiding them behind a long roadmap.

It combines fragmented use cases into coherent opportunity themes and explicitly answers what the organization will not pursue (for now).

Because merely adding AI will not automatically simplify your organization.

It will simply give your organization more things to manage.

See you next Saturday,
Tobias