Street Fashion, Style and Life – Friday May 15 – Jason Hargrove + Here’s a little look at what Toronto is wearing. This week a bunch of Torontonians in Manhattan, New York, NY! <a href=" http://jasonstreetstyle.tumblr.com " rel="noreferrer nofollow">jasonstreetstyle.tumblr.com</a> + Onta. Are founder readiness mistakes really just good practice in disguise?
Photo by Jason Hargrove from Toronto on Wikimedia Commons, CC BY 2.0

Rules

Part of Founder readiness: a written stop rule, three jobs covered, commitments postponed

Are founder readiness mistakes really just good practice in disguise?

Founder readiness mistakes that all feel like good practice: nine ways of removing the possibility of a bad answer, each with the correction that restores it.

These are not mistakes of effort. Every one of them is committed by people working hard, and every one of them feels like good practice at the time. That is what makes them durable: each has a respectable-sounding reason attached, and the reason is usually true in some other situation.

What to take away

  • Every mistake here is committed by people working hard, and each has a respectable reason attached.
  • Eight of the nine are the same moveremoving the possibility of a bad answer, one defensible decision at a time.
  • The ninth contains the rest, because any of them survives indefinitely when nothing forces a verdict.

1. Treating agreement as evidence

You describe the idea, people nod, you write down that the conversation went well.

Before the conversation

  • Write the sentence that would disappoint you
  • Check no answer could produce it
  • If none could, you are collecting encouragement

It felt like research because it was a conversation with a real customer. But nothing in it could have come out badly. Agreement is what a polite person produces when they are shown something a stranger is clearly proud of, and it costs nothing to give.

The correction: before a conversation, write the sentence that would disappoint you. If no answer could produce it, you are collecting encouragement.

2. Running a test with no failing outcome

The threshold gets set after the numbers arrive. Whatever happened is interpreted as directional, worth iterating on, early days.

Set thresholds before the test

  1. Write the stop number
  2. Write the go number
  3. Put them somewhere you cannot quietly edit
  4. Run the test

This is not dishonesty. Ambiguous results are the normal case, and human judgment resolves ambiguity in whichever direction lets the work continue. The defense has to be procedural, not moral.

The correction: write the stop number and the go number before the test runs, and put them somewhere you cannot quietly edit.

3. Validating the idea but never the delivery

Demand gets tested to death. Whether you can actually produce the result, repeatedly, for people you do not know, gets assumed.

Deliver once by hand

  1. Do the whole job yourself, end to end
  2. Time it
  3. Deliver it once by hand, fully
  4. Then sell the tenth one

The gap shows up at the worst moment: the first week where more than one customer needs something at once. Until you have done the whole job yourself, end to end, timing it, the plan contains an estimate where a measurement should be.

The correction: deliver it once by hand, fully, before you sell the tenth one. See minimum viable offers for how to keep that small without making it dishonest.

4. Asking about the future

"Would you use this?" "How much would you pay?" "Would that be useful?"

Future questions vs past events

Ask

Would you use this?
Guess dressed as fact
How much would you pay?
Generous, undetectable
Would that be useful?
Not withholding, they don't know
What happened last time?
Recoverable, reliable

Answer quality

Would you use this?
How much would you pay?
Would that be useful?
What happened last time?

People cannot answer these about themselves. They are not withholding; they genuinely do not know, and the question invites a guess dressed as a fact.

How much a question's wording shapes the answer that comes back is documented at length in the guidance on writing survey questions, and a question you wrote about your own idea is the hardest case there is. The answers are consistently more generous than behavior, in a direction you will not detect until you have spent money on it.

The correction: ask what happened last time. Past events are recoverable; intentions are not. The interview mechanics are worth getting right before you book anything.

5. Testing only where it is easy to test

Friends, former colleagues, your own following, the industry you just left. They answer quickly and they are kind.

Two columns in your notes

Problem

Friends and colleagues
Can fill
Own following
Can fill
Former industry
Can fill
Bias direction
Known

Reach

Friends and colleagues
Never fills
Own following
Never fills
Former industry
Never fills
Bias direction
Too optimistic

Two problems. They are biased in a known direction. And the channel that reached them cannot be repeated at any scale, so even a genuine yes tells you nothing about whether the audience is reachable. Both errors point the same way: too optimistic.

The correction: keep two columns in your notes, what you learned about the problem and what you learned about reach. The easy audience can fill the first column and never the second, which is the distinction market validation is built around.

6. Moving several things at once

The headline, the price, and the audience all change in the same week, because there is never enough traffic and it feels efficient.

One variable per test

  1. Change one variable only
  2. If you can afford one, pick the killer
  3. Spend it on what would kill the idea
  4. Avoid one number meaning six things

The result is one number that could mean six things. You have spent the week and bought no information. This is the most common way that a founder ends up with months of activity and no accumulated knowledge.

The correction: one variable per test. If you can only afford one, spend it on the thing that would kill the idea if it were wrong.

7. Leaving price until later

Price gets treated as a detail to settle once the product is right. Meanwhile every plan quietly assumes a number nobody has ever said out loud to a customer.

Name a price early

  1. Name a real number in a real conversation
  2. Let the silence sit
  3. Refuse to produce anything
  4. Do not defer to later

For most ideas the price is the largest single unknown, and the rest of the business is downstream of it. Guessing at it is not free.

The floor it has to clear is built from your own delivery and acquisition costs, and the SBA's breakdown of one-time against recurring startup costs is the cleanest statement of which of those actually bind. Deferring it does not reduce the risk. It just moves the discovery to a point where changing course costs more.

The correction: name a real number in a real conversation early, and let the silence sit. Pricing work needs a refusal to produce anything.

8. Mistaking the enthusiast for the buyer

Someone inside an organization loves it. They ask good questions, they want it, they say they will make it happen.

They may not be able to. The person who feels the problem and the person who releases the money are often different, and the enthusiast is frequently guessing about what their own organization will approve. Their sincerity is not the obstacle; their authority is.

The correction: ask who signed off the last thing they bought like this, and get a quote in front of that person.

9. Continuing by default

There was never a date or a condition at which the answer could be no. So the question is never asked, and the time already spent becomes the reason to spend more.

This is the mistake that contains all the others, because any of the first eight can survive indefinitely if nothing forces a verdict. It is also the only one that gets harder to correct the longer it runs.

The correction: set, in advance, a date and a specific observable condition. Write down what you will do if it is not met, including who you would tell. Then keep it somewhere a second person can see it.

The pattern underneath

Eight of these nine are the same move: removing the possibility of a bad answer, one small reasonable decision at a time. Nobody chooses to avoid the truth. They choose the easier audience, the softer question, the deferred number, the test with no threshold, and each choice is defensible on its own.

The check is short. For whatever you are doing this week, name the result that would make you stop. If you cannot, that is the finding, and it is available before you spend anything. The pillar on founder readiness describes the arrangements that make that check hold when you stop wanting it to.

Common questions

Which of the nine is most expensive?

The ninth, continuing by default, because it is the one that lets the other eight run for years. It is also the only one that gets harder to correct the longer it goes on.

Is agreement from a customer ever evidence?

Agreement attached to a cost is. Somebody who agrees and then sends the file, books the half hour, or pays a deposit has told you something. Agreement on its own is a social response.

How do I test one variable when I have almost no traffic?

Spend the one test you can afford on the thing that would end the idea if it were wrong, and accept a slower sequence. Two clean readings a month beat six unattributable ones.

What if the enthusiast really can get it approved?

Then it costs nothing to find out: ask who signed the last purchase of that size and what they needed to see. If the answer comes back specific, the enthusiast was right.

Who should hold my stop rule?

Somebody with nothing at stake and no reluctance to be blunt. A co-founder shares your incentive to reinterpret it, which is exactly the failure the rule exists to prevent.

More in Rules

Latest from Field Desk