The Dark S(AI)de of Innovation Automation

AI can generate ideas. It cannot make weak opportunities worth pursuing.

I’m currently reading one of those bestselling books that promises to explain how people should work with AI, and I have to admit that one part of it is hard to argue with. Large language models really are impressive creative partners. They can throw out ideas, variations, objections, concepts, and competitor moves faster than any workshop room full of smart people ever could, and in innovation work that speed is not a small thing.

I’d go further than the book does, honestly. AI is genuinely useful in the divergent phase of a problem, when you’re still trying to frame a situation, generate hypotheses, and figure out what struggles your job performers actually have. It widens the search space in a way a Tuesday afternoon workshop rarely manages, especially once you notice that most workshop rooms are filled with people from the same company, carrying the same incentives, the same vocabulary, and the same unspoken assumptions about what a good idea looks like.

It’s just as useful on the solution side. Ask it for analogies from other industries, prototype directions, business model variants, or the uncomfortable question nobody on the team wants to raise, and it delivers something usable within seconds. And it doesn’t stop at divergence. Feed it a stack of interview notes and it finds patterns you missed. Give it a pile of problem statements and it sorts and compares them. Hand it messy workshop material and it turns it into something structured enough to actually discuss, instead of a wall of sticky notes nobody wants to revisit.

It can even help you build something fast enough to test whether a solution offers real relief, and whether people would switch and pay for it, without pulling your best engineers off their real work or spending a serious budget on something that only exists to test problem-solution fit. Used deliberately, that’s a genuine accelerant.

AI can widen the room, but…

I’ve run experiments like this myself, and the claim holds up. With the right prompting, you can pull a broader, weirder set of ideas out of a model in twenty minutes than a group of well-meaning colleagues produces in an afternoon. You can ask it to argue the case as a skeptical buyer, a tired frontline employee, a regulator, a procurement manager, or a CFO with zero patience for elegant nonsense. You can also ask it a less comfortable question: how would our sharpest competitor attack this idea and make our life difficult? That’s a genuinely useful exercise, and most teams never bother to run it with a human, let alone a machine.

One prompt is not serious thinking

None of that makes it magic, though, and one prompt is not serious thinking. The value doesn’t come from typing a clever instruction and waiting for the model to reveal the future. It comes from pressure and iteration: squeezing out the obvious answers first, then forcing the system into less comfortable territory by changing the role, the constraint, the time horizon, or the failure mode you’re asking it to consider. That isn’t so different from a good ideation workshop. It’s just faster, cheaper, and doesn’t require booking ten calendars and ordering sandwiches.

The research on this is genuinely mixed, which I find reassuring rather than annoying. Some studies show large language models outperforming average human participants on divergent thinking tasks. Other work suggests that while AI assistance can lift an individual’s creative output, it quietly narrows collective diversity, because everyone ends up drawing from similar machine-generated patterns.[1] So the honest conclusion isn’t “AI is creative” or “AI kills creativity.” It’s something less quotable: AI expands ideation when it’s used deliberately, and homogenizes thinking when it’s used lazily.

Synthetic answers are still answers, not decisions

There’s a further point I think gets glossed over too quickly. Even a genuinely useful synthetic answer is still just an answer, not a judgment and not a decision. A model can give you a plausible view on users, jobs, solution directions, channels, pricing, objections, or adoption barriers, and it can do it fast. Sometimes that first answer is surprisingly sharp. Sometimes it only sounds sharp because the language is smooth. Either way, it’s built on probability rather than truth. It predicts what’s likely to fit your prompt and the pattern behind it, and that’s simply a different thing from being real, or relevant, or being decision-grade.

So the judging stays with you. You decide whether the synthetic customer response is plausible or lazy, whether the proposed job is specific enough to act on, whether the solution candidate actually addresses the struggle you set out to solve, whether the channel makes sense, whether the pricing logic deserves a real test, and whether the whole thing is strong enough to justify the next commitment or too thin to trust. None of that responsibility shifts to the machine just because the machine got faster. If anything it gets heavier, because the bottleneck has quietly moved from producing options to judging them. You were never short on answers. The question was always whether you knew what a strong enough answer looked like.

Where the argument breaks

This is where the book, and the argument in general, starts to bother me. Not because it overstates what AI can do, which is common enough by now, but because of the way it quietly treats innovation as though it were mostly about invention, creativity, and idea generation. It isn’t. I’d be far less bothered by this framing coming from a generic technology enthusiast. When it comes from people who teach innovation and entrepreneurship for a living, the shallow definition is harder to let slide. If we keep teaching innovation as creativity and idea generation, we shouldn’t be surprised when companies keep reducing it to workshops, sticky notes, prototypes, pitch decks, and demo days. The misunderstanding starts upstream, long before anyone opens a prompt window.

Ideas are inputs, not the work

Ideas are inputs. They are not the work. Innovation is the disciplined work of turning uncertainty into evidence-backed businesses, and in my experience it rarely fails because nobody had an idea. It fails because teams commit to weak opportunities, because they can’t turn a promising idea into a working business, because they build around a problem they never really understood, and because internal enthusiasm gets mistaken for market evidence. It fails because nobody wants to stop a project once it has a name, a sponsor, a budget line, and a slide template of its own. It fails when users, quite reasonably, don’t want to switch and don’t want to pay, and are perfectly content staying with whatever they already use. And sometimes it simply fails on the numbers, when the opportunity can’t generate enough financial throughput to justify the investment, the team, the sales effort, the marketing spend, the partnerships, or the next funding round. That’s where the easy story ends, and where the real work of innovation begins.

The work nobody wants to own

This is the part of entrepreneurship nobody particularly wants to own. Someone has to lead when things get uncomfortable. Someone has to push when the evidence is weak but the internal politics are strong. Someone has to spot when a pivot is overdue, and go find the alternative. Someone, eventually, has to kill a project, and has to have already tested the financials, the sales model, the marketing logic, the supply chain, the legal constraints, and the business model sitting underneath the product. None of that is the glamorous part of the job. It is, however, the actual job, and AI doesn’t fix it. If anything it can make it easier to avoid, because once idea generation gets cheap, a company can produce polished uncertainty at scale: concepts, opportunity areas, prototype directions, synthetic customer quotes, strategy language, plenty of activity that looks intelligent from a comfortable distance. None of it answers the harder questions underneath.

The questions ideation cannot answer

Does this opportunity matter enough? Who exactly has the problem, and is it urgent, frequent, expensive, or strategically important to them? What are people doing today instead, and what would actually trigger them to look for something better? Who pays, and why would they? Can you deliver the value at a cost that still makes sense, and can you capture a fair share of the value you create? What has to be true for this to become a real business rather than just an interesting product? Ideation, however good, cannot answer a single one of those questions, and the work of answering them starts well before anyone generates a solution.

Innovation starts before solutions

Before a team starts producing solutions, it has to earn the right to ask about them, which means looking honestly at what’s shifting in the market, the technology, the regulatory environment, cost structures, and competitive pressure, and asking whether there’s a real opening rather than just a fashionable theme. Then comes the user research, and I mean real user research, not a courtesy round of interviews run after the idea is already loved internally. The point of that research is to understand the job performers themselves: their struggles, their context, their constraints, the workarounds they’ve already built, and the outcome they’re actually trying to reach. You aren’t there to ask whether people like your idea. You’re there to understand the progress they’re already trying to make, and where their current options are failing them. Only once you’ve done that can you write a problem prompt that’s grounded in the field rather than in your own enthusiasm. Skip that step, and ideation becomes random noise dressed up as productivity, because a model will always produce something, whether or not you’ve earned the question you asked it. A fluent answer to a weak problem is still a weak answer.

Once the problem is real, AI becomes useful again

Once the problem is real, AI earns its place back in the process. It can explore solution candidates, suggest analogies from other industries, generate business model options, surface hidden assumptions, and play the competitor, the buyer, the skeptic, or the regulator on demand. It can help design tests and expose where a team is quietly hiding risk behind attractive language. What it still cannot do is validate the market for you, or replace real evidence with a convincing simulation of it. Sooner or later the team has to leave the prompt window and confront reality directly, through interviews, observations, smoke tests, landing pages, concierge tests, prototypes, pilots, pricing conversations, channel tests, sales friction, procurement delays, implementation cost, usage data, and churn. Innovation isn’t proven by how elegant the concept sounds. It’s proven by the quality of the evidence sitting behind the next commitment.

The business model is not an appendix

Which is why the business model can never be an appendix, and this is exactly the part that gets lost when innovation is reduced to ideation. A product without a working business model is a shallow answer to a real problem. It might create value for someone, but it doesn’t yet explain how that value gets delivered, paid for, defended, or captured, and that distinction is bigger than most pitch decks admit. A clever product can still be a bad business. A genuinely desirable feature can still be impossible to sell. A real user problem can still sit inside a market that’s too small, too fragmented, too regulated, too slow, or too expensive to serve well. A prototype can impress a room full of people and still tell you almost nothing about willingness to pay.

This, to me, is where the actual work of an innovator sits. Not in being the most inventive person in the room, not in producing the longest list of ideas, and not in running a workshop that makes everyone feel briefly creative. The core job is to connect the opportunity, the customer evidence, the solution design, the business model logic, and the investment decision into one coherent case, and to know what has to be tested before resources scale, what deserves another round of learning, and what should simply stop. If you don’t feel responsible for the business model, you’re not really doing innovation. You’re contributing to an invention pipeline, and that pipeline may still be useful, but it isn’t enough on its own.

What AI should actually be used for

So here’s where I’d position AI more honestly than the book does. It is not an innovation machine. It’s a leverage tool inside innovation work, and a genuinely good one. It can widen the search space, narrow it back down, generate alternatives, build opposing hypotheses, and simulate the perspectives missing from your room. It can translate a vague idea into a testable assumption, compare solution candidates, and draft interview guides, test plans, prototype variants, and business model options faster than any of us could alone. All of that is valuable. None of it should be mistaken for customer evidence, strategic judgment, or commitment quality. AI can help you think, help you see your options, and help you pressure-test a direction before you spend real money on it. It cannot take responsibility for the decision itself, because that was never its job.

The better leadership question

Which is why I think leaders are asking the wrong question. The question isn’t how AI can help a company generate more ideas. It’s where AI can help reduce uncertainty before resources get committed. That single reframe changes what AI is for. It pulls the technology away from brainstorming theater and toward learning discipline, and it quietly raises the bar for every innovation team using it. If idea generation is now fast and cheap, there’s less excuse for lazy opportunity work, weak assumptions, or building something because the concept looked good in a workshop. There’s less excuse for treating a prototype as progress when the business logic behind it is still missing. The loss here is real and worth saying plainly: attractive ideas will sometimes have to be killed before they turn into protected, well-funded projects. That isn’t a failure of innovation work. Done honestly, that is innovation work.

The real implication

AI makes ideation easier, and that’s genuinely useful. But innovation was never short on ideas. It fails when teams commit too early, validate too late, misunderstand the job to be done, ignore the business model underneath the product, and mistake activity for progress. AI doesn’t remove the judgment problem sitting at the center of all this.

It just makes it impossible to hide.