The Catalyst of the Flawed First Move; or, The Freedom of the Sacrificial Draft

Some time ago I realized that my quirk of starting with the wrong answer to get a conversation going wasn’t just fun for everyone, it has broad applications. Some people think I’m being antagonistic at first, but I’m gentle—it’s just an efficient way to find the signal in the noise. I first observed this in my personal life, and have been testing it in my professional life for years. Here are my findings.

The Mechanical Utility of Being Wrong

In technical discussions and social planning alike, we often get stuck in analysis paralysis because everyone is waiting for the “perfect” architecture or plan to emerge from the void. But when you’re dealing with a system full of unknown unknowns, you can’t just wait for clarity. You have to force it to the surface.

People explain this in different ways. It’s a Forcing Function, or Cunningham’s Law: The best way to get the right answer on the internet is not to ask a question; it’s to post the wrong answer. Dark forces like shitty politicians pervert the Strawman Proposal by rhetorically using the logical Strawman Fallacy, but I use it as a tool for discovery—a tool for good. Colloquially, you might know it as playing Devil’s Advocate, setting up an Aunt Sally, or leaving a Queen’s Duck in the design just to give a stakeholder something to “fix”.

The Prerequisite: Security

Before you try this, a disclaimer: this requires a layer of security—either professional or social. You can’t do this with every new acquaintance. There is a real social risk in sounding “dumb,” and you need enough established trust or competency that people know you’re being a catalyst, not just incompetent. It works best when the “paved road” of the relationship is already built.

Why This Works in a Team, Group, or Pair

By intentionally starting with a flawed but concrete starting point, you change the dynamic from “brainstorming” to “debugging”:

It flushes out hidden constraints: People often forget to mention a requirement until they see it being violated.
- If I suggest we drive three hours to that “meh” bakery, someone will immediately remember they have plans at 4pm. Alternately, it will activate their “opinion” layer. If they say “yes” to a plan that’s obviously terrible, I’ll usually laugh and tell them it’s a horrible idea—and they can defend and own that choice should they so choose.
- Similarly, if I propose a simple Cron job for a high-volume pipeline, a peer will suddenly remember that the upstream source has a 500ms TTL.
- In both cases, the requirement is surfaced because I gave it something to push against.
It grants ownership: When you provide the “wrong” answer, you’re giving others the power to fix it. When a friend corrects my bad dinner suggestion or an engineer corrects my flawed tech spec, they aren’t following my lead. They’ve improved the plan, and it becomes their plan as much as mine.
It lowers the activation energy: Staring at a blank whiteboard (or a silent group chat) is intimidating. If I provide a sacrificial “bad” proposal, the stakes disappear. People don’t have to be geniuses to contribute; they just have to be correctors.

Protocol Summary

Don’t wait for the perfect tech spec or the perfect social plan. Start with the wrong answer. Propose the “wrong” thing and watch how fast the actual requirements reveal themselves. These are just two areas for potential application—conduct your own experiments!

So who wants to go to that overpriced restaurant with terrible food unironically?

Published in the Lab Notebook at cyberrhizome.ca