Theme

Text size

Font

Line spacing

MODULE 1.3

🧱 Productive pessimism

Productive pessimism means honestly imagining everything that could go wrong, not to give up, but to prepare. This module turns that attitude into a method: reasons against, reasons for, a small bet, and an AI-assisted premortem.

6
Topics
45
Minutes
Intermediate
Level
Practical
Type
0 of 60%
1

🌧️ Productive pessimism isn’t defeatism

Entrepreneurs tend to be optimistic, and that’s necessary to get started. The problem is that optimism can also hide risks. Productive pessimism is the antidote: you deliberately and carefully imagine all the ways the plan could fail.

DEFEATIST Lists the risksConcludes: it won’t workStops thereLearns nothing PRODUCTIVE Lists the risksAsks: how can I reduce it?Makes a small betLearns quickly same list, different use
What to look for: Both start the same way: listing what could go wrong. The difference is in the second line. The productive approach turns each risk into an action question.

✓ Productive mindset

  • ✓"If no one knows it exists, how do I get the first 10 users to find it?"
  • ✓"If someone copies it in a week, what would still be mine?"
  • ✓"If I’m wrong, how much will I lose?"

✗ Defeatist mindset

  • ✗"I don’t have an audience, so there’s no point."
  • ✗"They’ll copy it anyway, so why try?"
  • ✗"Something similar already exists, so I’m giving up."

💡 One-line test

For every risk you list, write an action next to it that takes less than a day. If there isn’t one, that risk is serious and deserves your attention first.

2

📓 The contingency journal

Some entrepreneurs keep a notebook for years with just one question: "if I lost everything tomorrow, how would I feed my family legally?". Their answers become more concrete and creative over time: sleeping near universities, buying a suit at a thrift store to get into events with free food, shaving to look like any other attendee.

🧗 Why such an extreme exercise helps

Thinking about the worst-case scenario takes fear out of the abstract and turns it into a list of actions. After a few years, you discover that there’s almost always a way out, as long as you look creatively at the resources available to you.

Applying that same mindset to products leads to useful questions: "if I had no ad budget, how would I get my first users?".

1 Extreme scenario what ifeverything goes 2 wrong? Real resourceswhat I still 3 have on hand Creative ways outnon-obvious 4 Product plan same logic,different target How a contingency exercise becomes a product strategy
What to look for: The personal exercise and the product exercise use the same four steps. Practicing the first makes the second faster and less intimidating.

Copy and run

Create your product version of the contingency journal with help from an AI assistant (Claude, ChatGPT, or Codex).

I want to practice productive pessimism about my product.

Product: <describe it in one sentence>
Audience: <who uses it>
Resources I have today: <time per week, money, contacts, skills>

Imagine the three worst realistic scenarios for the next 90 days
(e.g., no one signs up, a large competitor launches the same thing, I run out of time).
For each scenario, list 3 creative ways out using ONLY the resources I already have.
Nothing that requires new investment. Be specific: action, timeline, cost.
How to check: You should get 3 scenarios × 3 ways out. If any option requires money you don’t have, ask the assistant to replace it. Save the result in a note and review it in 30 days.

💡 Start small

It doesn’t have to be a journal you keep for years. Open a note called "contingency" and add one line each week. The value comes from repetition.

3

👎 The five reasons it WON’T work

Take your idea and answer without mercy: what are the five strongest reasons this won’t work? The list below shows the reasons that come up most often. Use it as a starting point, not an answer.

The most common reasons

1

I don’t have distribution

The problem most people face

No one will know the product exists. Without an audience, partners, or a channel, even the best product dies in silence.

2

It can be copied by screen recording

The clone test

Someone records a video using your product, gives it to a coding assistant, and says "make the same thing." If that’s enough, you don’t have a product; you have a demo.

3

The pain might be unique to me

Unknown market

The problem exists in the way you work, but you don’t know whether hundreds, thousands, or millions of people feel the same way.

4

I don’t know the market size

Uncertain TAM

There could be five potential customers in the world, or five million. Without an estimate, you don’t know whether it’s worth the effort.

5

It may be local only

Geographic scope

The need may exist in your city or region and not make sense anywhere else.

5reasonsNo distributionmost frequentEasy to copythe clone testUncertain pain or marketjust me? how many?
What to look for: The proportions are illustrative. The point is that distribution stands out as the largest share: if you solve only the product and ignore the channel, you’ve solved the smallest part of the problem.

⚠️ Don’t skip this exercise

It’s uncomfortable to write down why your idea will fail. That’s exactly why almost no one does it, and almost everyone discovers these reasons too late, after months of work.

4

👍 The five reasons it will work

Now do the reverse exercise. What are the five strongest reasons this could work? The same rule applies: no wishful thinking, just facts and resources you have today.

🤝

Partners who would promote it

People you know with an audience on social media who would talk about the product in exchange for a commission on each sale.

📺

A channel of your own

Even a small one: an email list, a profile, a group of former customers.

👥

Test groups

Forums and groups where your audience already gathers and is open to useful tools.

🔁

Early feedback

A way to know in days, not months, whether the product is on the right track.

💰

Low cost to test

The ability to find out whether it’s worth pursuing while spending almost nothing.

Againstno distributioneasy to copyuncertain market In favorpartnerschannel of your owncheap test Balance between reasons against and reasons in favor of the idea
What to look for: The balance is useful only if both sides are weighed with the same honesty. If the items "in favor" are wishes and the ones "against" are facts, the result is misleading.

✓ Valid reason in favor

  • ✓"I have three friends in the niche with 20,000 followers who are willing to promote it."
  • ✓"I already have 200 former customers with this problem."
  • ✓"I can test it with a group of 5,000 people this week."

✗ Weak reason in favor

  • ✗"Everyone will want this."
  • ✗"If it goes viral, I’ll make it big."
  • ✗"The product is much better than the others."

💡 Cross-check the two lists

For each reason against, see whether a reason in favor offsets it. "No distribution" is offset by "partners who will promote it." Risks with no match on the other list are the ones that need a plan.

5

🎲 The minimum bet

The final piece of productive pessimism is asking: how can I find out if I’m right while spending as little as possible? Not the minimum needed to build the whole product, but the minimum needed to answer the most dangerous question.

days dollarsComplete product 90 days highWorking prototype 7 days lowPage + waitlist 1 day minimal
What to look for: Each line answers a different question. The page with a waitlist answers "is anyone interested?" The prototype answers "does anyone use it?" The complete product should come only after both.
Examples of minimum bets for different questions
Riskiest questionMinimum betSign of success
Does anyone want this?Simple page with a waitlist, shared in 2 groups30+ sign-ups in one week
Will anyone pay?Pre-order button with a discount3+ actual payments
Can people understand it on their own?Prototype used by 5 people without help4 out of 5 reach the result
Can I reach the audience?A post in a niche forumReplies and direct messages

⚠️ Be careful with a bet that proves nothing

Opinion surveys ("would you use it?") are cheap, but they prove almost nothing. People say yes to be polite. Prefer tests that require them to take action: sign up, pay, or use it.

6

⚰️ AI pre-mortem

You can combine everything in this module into a single AI exercise. The technique is called a pre-mortem: instead of asking "what could go wrong?", you state "it already went wrong" and ask the model to reconstruct the story of the failure. Changing the tense leads to much more concrete criticism.

1 Describe product, audience,resources 2 Declare "it failed in12 months" 3 Reconstruct the likelycauses 4 Mitigate minimum betby cause Steps for an AI pre-mortem
What to look for: The step that makes the difference is the second one: declare the failure as a fact. When the model starts from "it already happened," it stops trying to please you and starts explaining.

Copy and run

Run a complete pre-mortem of your idea in Claude, ChatGPT, or Codex, weighing reasons against it, reasons in favor, and minimum bets.

Act as an experienced, skeptical investor. Run a PRE-MORTEM on my product.

Product: <what it does, in one sentence>
For whom: <specific audience>
How it makes money: <pricing model and price>
Resources I have: <time, money, audience, contacts>

Start from this fact: 12 months from now, the product has FAILED.

1. List the 5 most likely causes of failure, from most to least likely.
   Be sure to consider: distribution, how easy it is to copy (someone records the
   screen and asks an AI to recreate it), the real size of the market, whether the pain is only mine,
   and whether a giant could launch something similar.
2. List the 5 strongest reasons it could have SUCCEEDED, using only the resources I listed.
3. For each cause of failure, propose a minimum bet (less than 7 days and
   less than R$ 200) that would test whether that risk is real.
4. End with a one-sentence verdict: proceed, adjust, or abandon, and why.

Don't sugarcoat it. If the idea is weak, say so.
How to verify: The answer must have all four numbered parts and a clear verdict. If the model praises it too much, reply, "You're being nice; redo this as if your own money were at stake." Save the result: it becomes your testing plan for Track 2.

💡 Run it twice

Run the same prompt in two different models, or twice in the same model in new conversations. Test the causes that appear in both answers first.

✓ Good use of the pre-mortem

  • ✓Run it before writing code.
  • ✓Turn each cause into a cheap test.
  • ✓Repeat when the idea changes.

✗ Bad use of the pre-mortem

  • ✗Keep asking until the model agrees with you.
  • ✗Read it, find it interesting, and carry on as before.
  • ✗Use it as an excuse to never get started.

🧪 Quick module quiz

Three questions. Click an option to see the answer.

1. What distinguishes productive pessimism from defeatism?

2. What is the "clone test"?

3. Why does the pre-mortem declare that the product "has already failed"?

📋 Module summary

✓
Productive pessimism - list risks so you can act, not give up
✓
Contingency journal - practice finding creative ways forward with resources you already have
✓
Five reasons against - distribution, copying, pain only you feel, uncertain market, local scope
✓
Five reasons in favor - only current facts and resources, held to the same standard
✓
Minimum bet - the cheapest test for the riskiest question
✓
AI pre-mortem - declare the failure and reconstruct the causes with a skeptical model