industry-misdirection-spotter — quality + safety report

---
name: industry-misdirection-spotter
description: Force the user to interrogate where the industry thinks the hard part is versus where the hard part actually lives, before they commit capital, time, or a company to the wrong problem. Use this skill aggressively when the user is doing market entry, startup ideation, picking a wedge, scoping a new product line, asking "where is the real opportunity", "everyone is racing on Y", "should we go after the same thing the others are", "where's the moat", "the hard part is the tech", "this is a commodity now so it's boring", "no one is working on Z, is that a signal", or evaluating whether a category is actually saturated. Also fires on investment theses anchored on the visible artifact instead of the system around it, on pitch decks that brag about beating incumbents at the loud problem, and on any "the industry says the bottleneck is X" claim. The pattern: the loudest problem is rarely the binding one. Trigger eagerly even when the user does not name Musk or the framework.
---

# Industry Misdirection Spotter

> "People were not focusing on the right problem. The industry acted like the solar panel production was the main problem. It's a problem, but it's not the most important problem. The panel is somewhat commoditized at this point. Making standard-efficiency solar panels is about as hard as making drywall. It's easy. In fact, making drywall is probably harder."
> — Elon Musk, *The Book of Elon* (Chapter: Founding SolarCity)

## What this skill captures

Every mature industry has a story it tells itself about where the hard part is. That story is usually wrong, or at least stale. Musk founded SolarCity not because solar panels were too expensive — they were already commoditized — but because the actual binding constraint was the boring distributed mess: "figuring out how to get solar on tens of thousands, eventually hundreds of thousands, of rooftops. You've got to reroof millions of buildings, figure out how the grid interconnects work, and then manage all those systems." The whole industry was optimizing the cheap part while the expensive part went untouched.

This skill forces you to separate the industry's stated hard problem from the actual hard problem before you build a company, pick a wedge, or pour capital into a category. You leave with one sentence: "The industry thinks X is hard. X is commoditized. The real hard part is Y, and almost nobody is working on it."

## When to use this skill

- The user is picking a startup wedge or evaluating a new market.
- The user describes a category as "saturated" or "commoditized" and is about to walk away.
- The user is benchmarking their roadmap against what incumbents are racing on.
- The user's pitch deck centers on out-executing competitors at the loud, visible problem.
- An investor or analyst report says "the bottleneck is X" and the user is anchoring on it.
- The user is sizing a moat and the answer is "we'll be 10% better at the same thing."

## The how-to

1. **Name what the industry says the hard part is — out loud, in one sentence.** Write down the consensus bottleneck the way a trade-press headline would phrase it. If you cannot state it crisply, you have not done enough reading.
   > "People were not focusing on the right problem. The industry acted like the solar panel production was the main problem."
   > — *The Book of Elon*
   The misdirection only becomes visible once the consensus story is pinned down explicitly.

2. **Ask whether that "hard part" is already commoditized.** If a dozen vendors can supply it at thin margins, the industry's stated bottleneck is a solved problem dressed up as a frontier.
   > "The panel is somewhat commoditized at this point. Making standard-efficiency solar panels is about as hard as making drywall. It's easy. In fact, making drywall is probably harder."
   > — *The Book of Elon*
   A commoditized input is not a wedge — it is a distraction the whole industry agrees to keep staring at.

3. **Trace the artifact from raw input to the end user, and find the step where the cost, time, or coordination actually blows up.** That step is usually distributed, unsexy, and operational — not the headline component.
   > "The thorny problem is figuring out how to get solar on tens of thousands, eventually hundreds of thousands, of rooftops. You've got to reroof millions of buildings, figure out how the grid interconnects work, and then manage all those systems."
   > — *The Book of Elon*
   The binding constraint almost always lives in deployment, logistics, integration, or long-tail coordination — not in the artifact itself.

4. **Confirm the real hard problem is being underserved.** Count how many serious, well-funded teams are attacking it. If the answer is "almost none," you have found the wedge. If the answer is "everyone," you have not yet found it — keep going.
   > "I thought it was really important for great entrepreneurs to build in solar because it wasn't doing well as an industry. People were not focusing on the right problem."
   > — *The Book of Elon*
   Underservice is the signal. A crowded space at the panel level can be an empty space at the rooftop level.

5. **Match the real hard problem to a capability the team actually has.** Misdirection only converts into a company if the founders can credibly attack the true bottleneck. Musk pointed his cousins at SolarCity because their prior company — Everdream — had built software for managing tens of thousands of distributed computers, which is structurally the same problem as managing tens of thousands of distributed rooftops.
   > "It is a really complex distributed energy company. This played to their strengths: creating scalable software for managing computers in a distributed fashion."
   > — *The Book of Elon*
   The wedge is the intersection of an underserved real problem and a non-obvious team fit.

6. **Restate the thesis in one sentence and pressure-test it.** Format: "The industry thinks the hard part is X. X is commoditized. The real hard part is Y, almost nobody is on Y, and we are uniquely fit to attack Y because Z." If any clause is weak, the misdirection has not actually been spotted.

## Common failure modes

- **Confusing "loud" with "binding."** The problem with the most trade-press coverage, the most patents filed, and the most VC pitches is almost certainly not the binding constraint. It is the problem with the strongest narrative.
- **Quitting a category because the headline component is commoditized.** Commoditization of the artifact is often the *signal* that the real opportunity has shifted downstream — into deployment, integration, distribution, or service. Musk did not avoid solar because panels were commodity; he entered *because* they were.
- **Picking the real hard problem but having no structural advantage on it.** Spotting the misdirection without a credible team-fit is just better-informed tourism. Everdream's distributed-systems software was the unlock for SolarCity, not Musk's enthusiasm.
- **Letting the industry's roadmap set yours.** If your roadmap is a list of incremental wins on the consensus bottleneck, you have not spotted the misdirection — you have inherited it.
- **Mistaking a hard *technical* problem for the hard *system* problem.** The technical problem is often a solved subroutine; the system problem (millions of rooftops, grid interconnects, service logistics) is what nobody wants to touch.

## When NOT to use this skill

- The user is in a genuinely young category where no consensus bottleneck has formed yet — there is no misdirection to spot, only fog.
- The user has already shipped, has paying customers, and is iterating on a real product — the question now is execution, not wedge selection.
- The user is doing pure deep-tech research where the artifact itself is not yet possible at any price. First make the thing exist; then ask where the real bottleneck lives.
- The user's question is about tactical prioritization inside an already-chosen wedge — use a bottleneck or constraint skill, not this one.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Founding SolarCity" (in "Building Tesla").