David Monnerat

Product + AI | Systems Thinker | Enterprise Reality

Tag: ai

  • The Question Is the Creativity

    The Question Is the Creativity

    The conversation around AI tends to focus on outputs. This post is about something upstream from that.

    I was in a room with a small group of engineers and product people. We had a standing rule for these sessions: no constraints. Not on money, not on time, not on what the law currently allowed. Laws change, and if we only invented inside existing rules we’d never get ahead of them. The goal was to ask questions nobody had thought to ask yet.

    One of those sessions started with a conversation between me and a colleague. His father had Parkinson’s. My son had ataxia, a neurological condition affecting coordination and balance that causes involuntary movement. We were talking about tremors, how they made it hard for devices to understand intentional gestures, how the technology kept misreading the signal. Somewhere in that conversation someone said: what if we thought about this the way noise-cancelling headphones work? Not filtering out the gesture, but filtering out the tremor. Separating the signal from the noise at the body level.

    That question became a patent.

    The patent room is an extreme version of something that happens every day in less formal settings. The standard for a patent is legal novelty, something that hasn’t existed before in that form. But the same upstream act, two experiences colliding into a question worth asking, happens whenever someone brings their specific life to a problem and asks it differently than anyone else would have. The question doesn’t have to be patentable to matter. It just has to come from somewhere a model can’t go.

    I’ve thought about that moment a lot since AI became the dominant conversation in technology. Because that question could not have come from a model. Not because the model isn’t capable of sophisticated reasoning. It is. But because the question didn’t come from reasoning. It came from two people’s lives colliding in an unconstrained space.

    That’s where creativity actually lives. Not in the execution. In the question.


    What the Room Was Actually Doing

    Those sessions had a specific energy. You removed the practical objections that normally narrow thinking before it has a chance to go anywhere interesting. No one said “that’s too expensive” or “we can’t do that yet.” You created space for people to bring their actual experience, not their professional expertise, but their lives. Their parents. Their kids. Their frustrations. Their observations from places that had nothing to do with the problem on the table.

    And then you let those things collide.

    We did a session focused on aging in place, how to help elderly people live independently longer, especially when their families were far away. Every person in that room had a version of that worry. A parent in another state. A grandparent who had fallen. The anxiety of not knowing. The ideas that came out of that session didn’t come from market research or competitive analysis. They came from people who were living the problem and had been given permission to imagine solutions without limits.

    That combination of unconstrained thinking plus personal stakes is what produces the questions worth asking. Remove the constraints and you get speculation. Add the personal stakes and you get invention.

    The cochlear implant came from a researcher whose child was deaf. He wasn’t analyzing the hearing aid market. He was watching his daughter navigate a world that hadn’t been designed for her and asking whether it had to be that way. The sticky note came from a choir singer who had been frustrated by a bookmark falling out of his hymnal for years before he connected that frustration to an adhesive a colleague had invented that nobody wanted. Neither of those connections was the product of a logical process. They were the product of a life that had been paying attention to a problem long enough to recognize an answer when it appeared from an unexpected direction.

    Personal stakes aren’t the only path to the right question. Plenty of inventors have no direct connection to the problem they’re solving. But stakes create a kind of attention that’s hard to replicate any other way. You notice differently when you care.

    The question came first. The execution came after.


    What AI Actually Does

    AI is extraordinarily good at execution. Given a well-formed question, it can explore the solution space faster and more thoroughly than any human team. It can find patterns across domains that no individual would have the bandwidth to survey. It can synthesize, generate, iterate, and refine at a scale that would have seemed impossible five years ago.

    I use it this way every day. And the back-and-forth of working with a model, the “that’s close but not quite it,” the steering toward something you can sense but not yet fully articulate, has its own creative quality. It reminds me of those patent sessions. The iterative energy of a room where ideas are being shaped in real time, where one person’s response moves another person’s thinking, where the answer emerges through the conversation rather than arriving fully formed.

    But there’s a difference. In that room, every person brought something the others didn’t have. Their specific experience, their specific frustration, their specific version of the problem. The model brings what it was trained on. Which is vast, more than any person in any room could hold, but it is still bounded by what humans have already thought, written, and recorded. It can recombine brilliantly. It cannot bring something from outside its training the way a person brings something from outside their expertise.


    The Constraint That Isn’t a Constraint

    We told those rooms: imagine no constraints. And it worked, because removing the practical filters let thinking go somewhere it couldn’t go otherwise.

    But you could give an AI the same instruction. “Imagine no constraints on money, time, or law. Solve this problem.” And it would produce output. Sophisticated output. Options and combinations and lateral connections across domains it has been trained on. It might even produce something that looks creative.

    What it can’t do is bring something from outside its training into that unconstrained space. The model has no constraints to remove because it has no constraints in the first place, and also no life experience pressing against those constraints, no accumulated frustration waiting for permission to become a question. The removal of constraints only matters if something was being constrained. In a human, what gets constrained is everything they’ve lived and observed and felt and noticed. Remove the filter and that floods in.

    The model has no equivalent. It can go wide within what it knows. It cannot go to the place where my colleague’s father’s tremor and my son’s tremor became the same problem.


    The Most Important Skill

    There’s a version of the AI conversation that focuses on prompting. How to write better prompts. How to get better output. How to work with the tools more effectively. That’s useful, and I’m not dismissing it.

    But I think it understates where the leverage actually is.

    The prompt is downstream of the question. And the question is downstream of the specific collision: your son’s tremor meeting your colleague’s father’s tremor, a choir singer’s bookmark meeting a chemist’s unwanted adhesive, a researcher’s deaf daughter meeting a question about whether the world had to be that way. That’s not experience in the abstract. It’s experience that has been building pressure against a specific problem long enough to recognize an answer when it comes from an unexpected direction.

    That capacity lives in you, not in the tools.


    What the Model Will Never Have

    The model has no son with ataxia. It has no colleague’s father with Parkinson’s. It has no parent far away whose silence worries it. It has no memory of a room where someone said “what if we” and everything shifted. It has no frustration that has been accumulating for years, waiting for the right collision.

    It has no stakes. It notices nothing differently because it cares about nothing. It brings no life to the question because it has no life to bring.

    Those aren’t limitations that will be engineered away. They’re not gaps in the training data or constraints on the context window. They’re the definition of what the tool is.

    And they’re the definition of what you are.

    The question comes from you. The creativity is yours. The execution, extraordinary, useful, genuinely remarkable, is something you can share.

    Don’t confuse the two.

  • The Same Rocket, A Different Ship

    The Same Rocket, A Different Ship

    AI investment is accelerating faster than any technology wave before it. The pattern underneath it is older than most of us realize.

    There is something deeply human about looking up.

    We’ve always done it. We looked at the stars and decided we belonged there. We looked at the horizon and built ships to cross it. We looked at problems that seemed impossible and found ways to make them less so. That instinct, the refusal to accept limits as permanent, is responsible for most of what we’ve built.

    It’s also responsible for a pattern that keeps repeating. And we never seem to learn it.

    Every generation gets a technology that feels like the one. The thing that will finally close the gap between what we can do and what we’ve always wanted to do. Computers. Then software. Then the internet. Then big data. Each one arrived with genuine capability and genuine promise. Each one attracted enormous investment. Each one produced real gains, new industries, new efficiencies, new possibilities that didn’t exist before. And each one, eventually, ran into the distance between what the demo promised and what the real world required.

    That gap never closed the way we expected. So we did what we always do.

    We threw more fuel at it.

    (more…)
  • The Leveler: The Use Cases Nobody Planned For

    The Leveler: The Use Cases Nobody Planned For

    I sat at a table in the gym at my son’s school. Around the room there was a dog groomer, a police detective, someone from the state park maintenance crew, and an archaeologist. We were there for career day. My topic was AI.

    When each group of kids came over, I played them a song. I told them my son made it. He had the idea, shaped the lyrics, and used AI tools to bring it to life. It’s on Spotify and Apple Music. The instruments, the vocals, the production were all generated by AI. But the idea, the story, the words were his.

    Some of the middle school kids had already used ChatGPT. A few had used it for homework. One wanted a training plan for a video game he was trying to get better at. One girl said she used it as someone to talk to.

    That last one stopped me. The adults in the room were thinking about AI in terms of what it might take from these kids. That girl was using it for something none of the adults had thought to offer her.

    (more…)
  • Defining Success Criteria: Do You Know Where You Are Going?

    Defining Success Criteria: Do You Know Where You Are Going?

    It was the tenth call.

    I had been on the first one. A customer data project, matching records across systems to connect outcomes to the right source. It seemed straightforward enough that I handed it off and moved on. What followed was eight more calls between my team and the customer, each one ending with a tweak to the logic, each tweak fixing something and revealing something else.

    The problem wasn’t the code. It wasn’t the team. It was that nobody had defined success criteria before the work started. Nobody had asked: what does done actually look like?

    By the time my team pulled me back in, it was already swirling. The customer’s manager had joined too. I suspect that because the issue still wasn’t resolved, he felt the need to get involved. We had a piece of logic built by people who were no longer on the team, results that were almost always right, and a team that had been grinding on this for weeks.

    I asked a simple question: What do you actually want?

    That was it. Every previous conversation had been about what the code wasn’t doing right, assuming the approach was sound and just needed adjustment. Nobody had stopped to ask whether the approach itself was the right one. The answer to that simpler question was: when this happens, here is what we expect to see. And the solution that followed was far simpler than what we had been building toward. A defined set of conditions, clearly mapped to outcomes. The complexity we had been wrestling with wasn’t a feature of the problem. It was a feature of never having properly defined the problem.

    We left that meeting with a clear destination. We should have had that conversation on call one.

    (more…)
  • The Code Nobody Understands: The Hidden Risk of AI-Generated Code

    The Code Nobody Understands: The Hidden Risk of AI-Generated Code

    The error message appeared at 2:17 a.m. Something about a null reference in a service that hadn’t been touched in weeks. The developer on call pulled up the relevant file, read through it, and felt a familiar but newly uncomfortable sensation.

    She had written this code. Her name was in the commit history. But she hadn’t really written it. She’d accepted it. Reviewed it in the way you review something when you’re moving fast, and the output looks right, and the tests pass. The AI had generated the logic. She had approved the shape of it. And now, at 2:17 a.m., she needed to understand not just what it did but why it did it that way: what assumption it was built on, what edge case it was avoiding, what the author had been thinking.

    There was no author. Not in the sense that mattered.

    (more…)
  • Enterprise AI Implementation: You Were Promised Everything. Here’s What It Took.

    Enterprise AI Implementation: You Were Promised Everything. Here’s What It Took.

    It was, by all appearances, a standard enterprise AI implementation.

    The summaries looked clean.

    At the top of the screen was a concise paragraph capturing a customer interaction: what was requested, what was explained, and what follow-up was required. Action items were listed neatly below. It was the kind of output you could screenshot for a slide deck. Efficient. Polished. Convincing.

    The premise was simple. If employees spent less time documenting interactions, they could spend more time serving customers. Efficiency would increase. Costs would decrease. The model worked in the demo. It summarized transcripts fluently and quickly. The business case felt straightforward.

    It moved forward.

    The strain didn’t appear in the demo. It appeared in real use.

    (more…)
  • The Other Hand: AI, Disability, and the Cost of Progress

    The Other Hand: AI, Disability, and the Cost of Progress

    I’ve spent more than a decade working in AI. I’ve built teams around it, led products powered by it, and spent more hours than I can count thinking about where it creates value and where it doesn’t. I’m not a skeptic. I’ve seen what the technology can do when it’s applied well.

    I’m also the father of a son with epilepsy. He is sixteen, and he will probably never drive. Autonomous vehicles have been part of how I think about his future for a while now — not as a certainty, just as a possibility worth holding onto. So when I came across a Freakonomics podcast about what a driverless world might mean for people who can’t drive, I expected something that confirmed what I’d been quietly hoping. Instead it pulled in two directions at once.

    That tension is what this post is about.

    (more…)
  • The Workbench: A Fictional Exploration of AI, Patents, and Asymmetric Trust

    The Workbench: A Fictional Exploration of AI, Patents, and Asymmetric Trust

    A short work of speculative fiction about mediated cognition and structural asymmetry in AI systems.

    I’ve worked on the same problem for three years. Agricultural runoff — specifically, a low-infrastructure filtration approach practical for small farms that can’t justify the capital cost of existing solutions. I have notebooks. I have a corner of my basement with a workbench and a lamp. I work at night because that’s when the house is quiet, and no one needs anything from me.

    I’m not describing this to be romantic about it. I’m describing it because the habit matters to what happened.

    (more…)
  • Chasing Fool’s Gold

    Chasing Fool’s Gold

    It’s November 2025, nearly three years after ChatGPT became publicly available.1 Three years of hype, three years after the record-breaking user growth2, three years of promises that AI would transform everything, and three years of that transformation always being just around the corner. 

    I’m generally pro-LLM. At my last two companies, I ran user groups to bring people together — technical and non-technical — to educate, connect, and evangelize around the responsible use of AI. I’ve led product teams building models to improve customer experience and home security, seeing measurable impact on satisfaction and adoption.

    Often, these successes came despite headwinds: misunderstanding, fear, and leadership unfamiliarity with AI. We had to educate executives on what AI was, what it wasn’t, and where it could help. We pushed to let data scientists do the data science, rather than forcing them into traditional software development models.

    The Gold Rush Hits

    Then ChatGPT arrived, and it felt like everything we’d built — metrics, prioritization, careful problem selection — could suddenly be replaced by simply ‘throwing an LLM at it.’ Promises flew: search is dead, coding is dead, thinking is dead. AGI is just around the corner.

    Businesses rushed to stake their claims, building wrappers around LLMs. One API call to solve everything. CoPilots for every task. Flashy demos everywhere. Executives saw dollar signs from revenue gains and headcount reductions.

    Projects worldwide were paused, shelved, or converted into LLM initiatives. Funding poured in, often for initiatives that hadn’t even existed weeks earlier. The goal shifted: from solving important business problems to showcasing generative AI quickly.

    The Barons and the Tools

    The “barons” who built the models and hardware were rewarded with massive investments, copyright protection, and enormous data access. Vendors selling platforms and tools gained huge funding and an endless supply of prospectors eager to mine their land.

    And like every gold rush, there were always “better” tools on the horizon. A new API promising 10x productivity. A new model promising “real” multimodality. A new agent framework that would “finally” automate everything. The land just over the ridge was always more fertile than the land you were currently standing on. And teams spent real money and real time chasing it — sure, this time the promise would finally pay.

    The promise of “grab a shovel and get your gold” was marketing, not reality. Easy-to-get gold runs out; mining becomes technical, requiring skill and know-how. The dream of instant wealth fades. Too often, it’s fool’s gold — investments in tools and access are never recouped.

    Reality Hits

    Suddenly, hallucinations become a board-level word. Reliability matters. “Just call the LLM” is no longer enough.

    Hallucinations, integration friction, and workflow complexity appear. Legal briefs with fabricated citations, inconsistent customer support responses, and hallucinated business documents turn reliability into a top concern. A model that works in a demo may fail in production, exposing operational, financial, and reputational risks.

    The illusion of ease, the desire for speed, and the dream of instant ROI never materialized. Rapidly built demos often worked only on the surface. Quick prototypes, bolt-on integrations, and low-discipline AI-generated code created massive technical debt3 — problems no LLM could solve alone. Many early adopters found fast paths to value required extensive rework, refactoring, and governance. Projects stalled or never reached production.

    These failures weren’t a surprise — they echoed the same issues we’d faced when hype outran preparation.

    Mining Real Value

    Three years in, many companies still haven’t figured it out. They’re digging for gold, chasing demos, hoping for a lucky strike. A few got lucky and saw big value — but most only saw modest gains, if any. Articles and studies show the promised ROI often didn’t materialize. The dream of instant impact remains elusive.

    In that scramble, businesses and their customers often suffer. The barons still own the land, controlling the most valuable resources. Vendors who sold the tools have already moved on to the next rush. The cycle repeats.

    The hope is that we finally learn the lesson: generative AI doesn’t deliver value through hype, demos, or shortcuts. True success comes from patience, discipline, and relentless focus on real value — careful engineering, thoughtful product design, high-quality data, and robust workflows. These principles aren’t just for today’s LLM hype; they matter for whatever technology or “next rush” comes next. 

    Shiny demos grab attention, but only foundational work separates the companies that thrive from those still chasing fool’s gold.

    1. https://openai.com/index/chatgpt/ ↩︎
    2. https://www.reuters.com/technology/chatgpt-sets-record-fastest-growing-user-base-analyst-note-2023-02-01/ ↩︎
    3. https://www.techradar.com/pro/from-vibe-to-viable-the-hidden-cost-of-ai-tech-debt ↩︎

  • The Illusion of Intelligence: How We’re Still Missing the Promise of AI

    The Illusion of Intelligence: How We’re Still Missing the Promise of AI

    When I started my first role as a product manager, my portfolio included solutions built with AI. I leveraged my product experience and joined forces with a team of data scientists as we sought to tackle complex problems with data.

    It was a great time to be in the space. Everyone wanted to work with AI, and the promise of an AI-driven future was highlighted at every quarterly meeting and town hall. There were piles of data and just enough maturity in the tools and teams to start developing and deploying powerful algorithms at scale.

    But progress was much slower than most people anticipated.

    We stood in front of the piles of data without a shovel, unable to make efficient use of the resource because it was in the wrong format or inside an inaccessible system. Sometimes, we’d discover too late that our intuition about the relevance of the data in a particular pile was wrong, and the data wasn’t useful to solve a particular problem.

    To overcome those challenges, we’d start by looking for more data by checking other piles or generating additional data by adding telemetry to our systems to close the gaps in coverage.

    If we couldn’t assemble what we needed to solve that particular problem, we’d try to reshape the problem, or we’d move on to the next problem to solve. But if we happened to find what we needed, we ran into our next hurdle: armchair data scientists—people who watched a demo, skimmed an article, and came away convinced they knew how to build the model better than the experts trained to do it.

    When I said that everyone wanted to work with AI, I meant everyone. In some cases, developers would head to Coursera to learn about AI and how to create algorithms. Others went back to school to get an advanced degree in machine learning or statistics. As a proponent of continuing education, I applauded these efforts to level up their knowledge and skills, and, for the most part, these individuals became curious allies, trying to learn about the process from the inside.

    But the armchair data scientists, often in leadership or decision-making positions, were more disruptive. They would watch a video or read an article, then send it to the team with a brief note, stating only, “We should do this.” There would be no context, no knowledge of how the technology worked, or if what they found addressed a problem or challenge we were facing.

    For the most part, we could deflect these suggestions through thoughtful responses, explaining that we were already doing what they suggested, or why it wasn’t relevant to the actual problem we were solving.

    The more draining interactions were from leaders who wanted to prescribe how a model should be built, sometimes implicitly but often explicitly. They wanted the algorithm to reflect a vision of what they felt a system should do based on their intuition, even if their vision wasn’t technically possible—or even relevant—to the problem at hand. They would prescribe what data should be used, what data should be excluded, or how a model should be trained.

    They tried to influence how predictions were interpreted. They challenged results that didn’t feel intuitive, even when the outcomes were reproducible, measurable, and backed by data. This sometimes created another round of training a separate model driven by feelings, followed by a side-by-side comparison that consistently showed the data science approach performed better than one based on intuition and feelings.

    I’ve sat with some of those same executives to review the results of a model, only to be met with their disappointment, especially when they felt there should be a logical, straightforward solution to a problem that was so complex that it couldn’t be solved or even attempted without AI.

    They would question why the predictions weren’t 100% accurate. Even when I pointed out that we were predicting the future from past data, and even if the model was right 60% of the time, and the previous human-driven process was right only 10% of the time, their questions focused only on achieving the impossible 100%. They’d leave value on the table chasing perfection when they could improve a process now and hope to improve it over time. Or they’d go off on tangents and hyperfocus on edge cases for which there was no solution and often no data to even attempt to use to train an algorithm.

    If the performance was impressive, they’d attempt to move the targets by setting an arbitrarily higher bar, or they’d switch from the measurable metric to a different metric or an abstraction like “trust” without providing direction on what that meant or how to measure it. Trust in what? Accuracy? Fairness? Transparency? Nobody could say. When asked for clarification, the response was the classic Justice Potter Stewart response, “I know it when I see it.”

    In the end, it always seemed like AI was a disappointment. Unless it could solve 100% of a problem 100% of the time, no matter how complex or how poorly humans performed before, leaders would keep chasing a unicorn, while ignoring the perfectly capable, faster horse already in the stable.

    Over and over, the pattern was the same: impossible expectations, misunderstanding of the tools, and a tendency to chase magical thinking over measurable progress.

    Here We Go Again

    Fast forward a few years, and we’re back at it. Only this time, the technology looks smarter. LLMs have reignited AI’s promise with a seductive twist: they speak fluently. They write. They reason. They respond. And for many, that’s been enough to assume that LLMs also understand.

    But just like before, we’ve let the illusion get ahead of the reality.

    While LLMs make it easier than ever to demo something impressive, they haven’t made it easier to deliver something useful. Underneath the conversational surface, the same problems persist: inaccessible data, unclear problems, and unrealistic expectations. In fact, the expectations are even worse now, because the technology feels like it’s already “there.”

    I’ve seen teams leap into building generative AI “solutions” without a clear understanding of what problems they’re solving. I’ve seen leadership get swept up in generative demos and approve massive budgets to chase abstract goals like “productivity” or “creativity” without metrics, definitions, or infrastructure.

    The same pattern is playing out again. Impossible expectations, except this time they’re even higher. A misunderstanding of the tools, especially when it comes to differentiating the hype from the reality. And the same magical thinking chasing a hypothetical problem rather than focusing on a real problem with measurable outcomes.

    Two years in, we’re starting to see the same disappointment creep in again, too. The unrealized expectations, longer timelines, and lack of returns on the investments.

    What Useful AI Actually Looks Like

    Useful AI doesn’t always look like magic. In fact, the most valuable AI systems I’ve seen rarely impress anyone in a demo. They don’t write poetry, simulate conversation, or generate pitch decks with a prompt. They just quietly make things better—faster, cheaper, more consistent, more scalable.

    They are, by most standards, boring.

    A model that flags billing anomalies in a healthcare system might save millions. A classifier that routes customer service tickets to the right team might shave minutes off every support interaction. An optimization algorithm that suggests more efficient delivery routes could reduce fuel costs, improve ETAs, and shrink carbon footprints. None of these use generative AI. None of them are headline-worthy. But all of them create real value.

    And unlike a chatbot that sometimes gives the wrong answer with great confidence, these systems are narrow by design. Purpose-built. Measured. Tightly integrated into workflows and optimized over time. They don’t need to sound human. They just need to work.

    We often overlook this kind of AI because it’s not exciting to watch. It doesn’t feel like the future. But that’s exactly the point: the best AI doesn’t draw attention to itself. It dissolves into the process, making things work better than they did before.

    The Opportunity Cost of the Hype

    The hype around LLMs has sparked a renewed interest in AI, but it’s also warped our sense of what progress looks like. Instead of focusing on impact, we’ve become obsessed with spectacle.

    Executives see a demo of a chatbot that answers questions with a human-like cadence and see the realization of the vision that they’ve had for AI all along. Suddenly, every team is greenlit to build a “copilot.”

    LLMs make it easy to show something impressive. A few prompts, a fancy UI, and you’ve got a prototype that feels like innovation. But most of these tools don’t stand up to basic scrutiny. They hallucinate. They break when connected to real systems. They introduce ambiguity into workflows that once relied on clarity. They create new risks—ethical, operational, and technical—that teams are often unprepared to manage.

    We’re pouring talent, time, and money into building AI wrappers around problems we haven’t defined. Meanwhile, the infrastructure work that would actually make AI useful—cleaning data, improving feedback loops, building explainable systems—is neglected.

    This is the code of chasing the hype. Years of expensive effort with little or no realization of value, certainly to the scale that was promised. Real problems that didn’t require generative AI but could have been solved and added real value were ignored or neglected. Two years in, it turns out we’ve been sprinting on a treadmill. We’ve spent the energy, but we’re still in the same place.

    To be clear, there’s nothing wrong with experimentation. But exploration without a clear problem or success metric isn’t innovation—it’s expensive theater. It gives the illusion of progress while distracting from work that actually moves the needle.

    And we should know the difference because we’ve been here before. We let unrealistic expectations undermine the progress of last-generation AI. Now, we’re doing it faster. We’re skipping the discipline that made the old models work and replacing it with a dopamine hit from a prompt that feels smart.

    A Better Mindset: Value Over Novelty

    If the last two waves of AI taught us anything, it’s this: the technology is only as good as the problems we point it at and the people we trust to solve them.

    Too often, we let novelty set the direction. We ask, “What can we build with this?” instead of “What’s worth solving?” But even when we pick the right problems, we don’t always empower the right people to do the work.

    Instead, we’re seeing a return of the same behavior that stalled progress last time: leaders prescribing not just what to solve, but how to solve it. Dictating which data to use. Demanding specific architectures. Redefining outcomes midstream based on intuition instead of evidence. In some cases, they’re building solutions backwards from a flashy demo instead of forward from a real need.

    This isn’t strategy—it’s armchair data science all over again.

    And it’s especially risky now, because LLMs make it even easier to look smart without being right. It’s one thing to brainstorm ideas. It’s another to second-guess trained experts who understand the constraints, trade-offs, and mechanics of building something that works.

    A better mindset means more than just optimizing for usefulness. It means creating space for people with real expertise—data scientists, engineers, researchers, designers—to lead the “how.”

    It means:

    • Letting evidence drive decisions, not gut instinct or LinkedIn hype.
    • Empowering teams to solve, not just execute.
    • Recognizing that success isn’t always intuitive—and being okay with that.

    Adopting this mindset doesn’t mean ignoring new tech. It means respecting the disciplines that make that tech useful. It means pairing vision with humility, ambition with trust.

    Because there’s nothing wrong with being impressed by what’s possible.

    But if we’re serious about delivering real value with AI, we have to get out of our own way—and let the experts do their jobs.