← Item page
← Read queue

HTML explainer artifact

Founders Fund: Choose Good Quests

Source: https://foundersfund.com/2023/06/choose-good-quests/
Generated: 2026-05-22T06:48:30Z

Choose Good Quests — Founders Fund / Pirate Wires

Type: strategy essay / founder-mindset piece

Source: Founders Fund, originally Pirate Wires, by Trae Stephens and Markie Wagner; intro by Mike Solana. Published 2023-06-22, modified 2024-12-16.

Core question: if a capable person has unusually strong “player stats” — talent, network, money, credibility, energy — what quest should they spend a life on?

Thesis

The essay argues that Silicon Valley has a “crisis of nonsense”: many of the most capable builders and operators are using rare leverage on low-consequence work — investing, posting, safe SaaS, lifestyle retirement, derivative consumer products — instead of hard problems that could materially improve the future.

Its moral claim is sharper than generic ambition advice:

> If you are exceptionally capable, choosing a low-consequence quest is not neutral. It is an opportunity cost imposed on everyone else.

The quest framework

The piece uses a simple two-axis model:

                         Good for the future
                               ↑
             hard + good       │       easy + good
        fusion, cancer, AGI,   │       rare, usually already solved
        space, defense, energy │
Hard / risky / complex ────────┼──────── Easy / legible / playbooked
        hard + bad             │       easy + bad
        status games,          │       lifestyle flexing, hot-deal VC,
        overbuilt markets      │       shallow posting, copycat apps
                               ↓
                       Low consequence / harmful

Definitions:

The important nuance: a quest can be wrong for one person and right for another. Someone with no nuclear background skipping fusion is fine; a talented nuclear physicist with capital and network choosing a tiki bar is a waste.

What the authors criticize

The essay’s “bad quest” examples are mostly second-act Silicon Valley traps:

The Facebook Mafia is used as a negative case study: after a major IPO, many alumni had capital and reputation, but the essay argues the ecosystem produced mostly venture funds and derivative software rather than a PayPal-Mafia-style generation of paradigm-shifting companies.

Positive examples

The essay praises second-act founders/operators who used accumulated leverage on consequential problems:

The authors emphasize that these projects often require non-financial motivation: obsession, calling, revenge, or compulsion to build. The point is not “be impressive”; it is “spend rare leverage where it can unlock something others cannot.”

Consequential domains named

The closing list is useful as a raw research/idea seed list:

Tradeoffs and caveats

How Ananth can use this

Use it as a decision filter for Mission Control and personal project selection:

1. Name the quest, not just the task. “Build Daily Podcast Creator” is a task; “make Dab convert scattered interests into recurring high-signal audio briefings” is closer to a quest.

2. Score fit from the player card. What does Ananth/Dab uniquely have: always-on capture stream, Raspberry Pi/home environment, coding agents, personal context, taste, curiosity, willingness to iterate?

3. Reject easy-bad loops. More dashboards, more feeds, more bookmarking, or more agent demos are bad quests unless they reduce friction or create a compounding capability.

4. Prefer hard-good wedges. Small systems that make Dab more autonomous, trustworthy, or useful in Ananth’s real life are better than shiny but isolated experiments.

5. Set an anti-status rule. If a project is mainly impressive to describe but does not change Ananth’s day/week, it is probably a bad quest for Mission Control.

Fit with current Mission Control threads

Suggested next step

Create a lightweight “Good Quest filter” inside Mission Control’s idea-review process: every serious new idea gets one line for quest, future upside, why Ananth/Dab are a fit, and easy-bad trap to avoid. Do not turn this into a heavy framework; keep it as a pre-build sanity check.