We're all from Missouri now.

Missouri's state motto is "Show Me", and it captures something that has become increasingly true in software and idea-driven work more broadly: people are far better at reacting to something they can see than imagining something they can't.

I've always felt this instinctively. I don't particularly like asking people for their opinions on an idea before it exists. Not because I don't value feedback, but because asking someone to imagine something is a poor way of learning anything useful. They never see what you see. They fill in the gaps with their own assumptions, anxieties, and preferences. And more often than not, you end up discussing ten things that are incidental rather than the one thing that actually matters.

Showing beats asking. Every time.

For a long time, this wasn't how we worked — and for good reason. If it took a year and a team of ten to find out whether something was viable, you did as much thinking upfront as possible. Entire software development methodologies grew out of that reality. Rational Unified Process, heavyweight waterfall approaches, and later Agile itself were all rational attempts to manage risk when building software was slow, expensive, and hard to undo.

They weren't wrong. They were responses to real constraints.

The problem is that many organisations kept the rituals long after the constraints disappeared. The ceremonies survived. The economics didn't.

With modern AI coding assistance — call it "vibe coding" if you like — the cost of turning an idea into a working artefact has collapsed. One person can now go from a half-formed idea to something that runs, clicks, and responds in hours or days. It might be rough. It might be ugly. It might fall over at the edges. But it exists. And that alone makes it more valuable than weeks of conversation about what could exist.

This flips the traditional logic on its head. The expensive part used to be execution; now it's deliberation. Time spent discussing imaginary products is time spent amplifying noise.

When you ask someone what they think of an idea, you don't get a verdict on the idea itself. You get a performance. People speculate. They hedge. They surface edge cases to sound thoughtful. They optimise for being helpful rather than being right. None of this is malicious — it's just what humans do in the absence of something concrete.

Show someone a working prototype and everything changes. Feedback becomes grounded. Reactions become honest. The conversation shifts from "what if" to "this works" and "this doesn't". Signal replaces speculation.

This is why "just build it" isn't anti-feedback. It's anti-premature feedback.

I've felt this shift personally. In the last couple of years I've built side projects that I simply wouldn't have attempted before: a machine-learning-driven horse-racing analysis platform, an investment analysis tool, systems that use AI to categorise and reason over large collections of documents. Not demos — working software. None of these required a team. None required a formal discovery phase. What they required was the ability to build something quickly, see what worked, and adjust.

That's the real change. It's not that ideas have become better. It's that the cost of testing them has collapsed.

There's a deeper point hiding here too: building is a form of thinking. Writing code — even assisted code, even messy code — forces clarity. The moment you try to make something actually function, vague ideas disappear. Assumptions get exposed. You can no longer hide behind language. A product that runs is an argument you can't hand-wave.

AI doesn't remove the need for judgement; it raises the premium on it. Someone still has to decide what to build, what to ignore, what "good enough" looks like, and when to stop. But that judgement is far more effective when exercised in the presence of something real.

There's a management lesson here as well. Many organisations confuse consensus with correctness. They treat alignment as a prerequisite for action rather than something that emerges from it. Building first flips that around. It's easier to align around a thing than around a theory.

So if you have an idea today — for a tool, a product, a workflow, a service — the barrier to entry has never been lower. You don't need permission. You don't need a committee. You don't need a research phase to justify curiosity. You can build something small, show it to someone, and see what happens.

Why not?

In a world where building is cheap, imagination is expensive. If you want people to understand your idea, stop asking them to picture it. Show them.