lead-product-by-leading-company — quality + safety report

---
name: lead-product-by-leading-company
description: Force a brutal role-clarity reckoning whenever a technical founder is trying to "stay CTO/CPO and hire a CEO" so they can keep doing the fun engineering work. Use this skill aggressively when the user is debating founder roles, planning a CEO search, asking "should I hire a CEO and stay CTO", "I just want to focus on product", "I'll be Chief Product Officer and let someone else run the business", "my product VP keeps losing fights with finance", "I want to be the technical visionary, not the operator", "should I step down as CEO to focus on engineering", "we need an adult in the room", "I hate the business stuff", "the board wants a real CEO", or any moment a founder is romanticizing a non-CEO technical seat at a company whose competitive edge is technology. Also fires when a product or engineering leader is being structurally outvoted by finance, sales, or a hired-gun CEO on calls that determine the product itself. Trigger eagerly even when the user does not name Musk or the framework.
---

# Lead Product By Leading Company

> "I never wanted to be a CEO, but I learned you could not truly be the chief technology or product officer unless you were the CEO."
> — Elon Musk, *The Book of Elon* (Chapter: Becoming Tesla's CEO)

## What this skill captures

Musk's hardest-won lesson from early Tesla: the title "CTO" or "CPO" is a lie at a tech company unless you also sit in the CEO seat. He tried to have his cake and eat it too — "I just wanted to work on the technology and the product. I thought someone else could be the CEO and run the business" — and called it "a huge mistake and fundamentally a moral error." In a company whose competitive edge is technology, the CEO is the product officer whether they want to be or not. Every call about hiring, capital allocation, supplier choice, factory layout, schedule, and pricing IS a product call. If you're not the CEO, you don't make those calls — somebody else does, and your "product vision" becomes a series of losing fights with finance.

The value you get: a hard structural test for whether you can actually deliver the product you say you want to build from the seat you're proposing to occupy, or whether you're optimizing for personal comfort while handing the steering wheel to someone with different priorities.

## When to use this skill

- A technical founder is planning to hire an outside CEO so they can "stay focused on the technology and product"
- A founder is considering stepping down from CEO into a CTO/CPO/Chief Architect role at their own company
- A CTO or VP of Product reports their hardest battles are losing fights with finance, sales, or the CEO over product-defining tradeoffs
- The board is pushing a founder to bring in "adult supervision" at a company whose moat is engineering
- A co-founder is being slotted into a non-CEO technical title while a non-technical co-founder takes the CEO seat
- A founder is justifying the split by saying "I hate the business stuff, the legal stuff, the personnel stuff"

## The how-to

1. **Name the actual motive — comfort, not strategy.** Force the user to say out loud why they want the CTO/CPO seat instead of CEO. Almost always the honest answer is "because I like engineering and hate chores," not "because the company wins more with this structure."
   > "The actual error was me trying to have my cake and eat it too: I just wanted to work on the technology and the product. I thought someone else could be the CEO and run the business, because I just like working on technology, product, and design."
   > — *The Book of Elon*

   The dodge is universal among technical founders. Naming it kills 80% of the rationalization.

2. **Test whether the company's edge is technology. If yes, the CEO IS the product officer.** Ask: does this company win because of its technology and product, or because of distribution, brand, regulation, or capital? If technology, the CEO cannot delegate product. The CTO/CPO seat does not have the authority to make the calls that determine the product.
   > "I never wanted to be a CEO, but I learned you could not truly be the chief technology or product officer unless you were the CEO."
   > — *The Book of Elon*

3. **Identify the calls a non-CEO product/tech officer will lose.** Capital allocation, supplier selection, hiring/firing of senior engineers, factory location, schedule vs. quality tradeoffs, pricing, partnerships. Each of these IS a product decision. List the next five such calls the company faces. Ask who decides each one if the user is CTO and someone else is CEO.
   > "I do the business stuff because you have to do the business stuff. If you don't do the business stuff, somebody else could do it for you and then you could be in trouble."
   > — *The Book of Elon*

4. **Be honest about the chore tax.** The CEO seat is mostly chores — personnel, legal, finance, board management — and Musk admits he hates them. The question is not "do I enjoy chores" but "am I willing to do chores I hate so that the product I care about actually ships."
   > "If you're a CEO of a company, the chore level is high, and if you don't do your chores then the company goes to hell. Frankly, I hate doing chores—who doesn't?"
   > — *The Book of Elon*

   If the answer is no, the user is not actually committed to the product — they are committed to the fun parts of building it.

5. **If you refuse the CEO seat, pick a CEO who is structurally a product/engineering CEO — and accept the consequences.** If the founder genuinely cannot or will not take the CEO seat, the only survivable substitute is a CEO whose own deepest instinct is product and engineering, with explicit authority handed back to the founder on the calls that determine the product. Anything less and the company drifts.
   > "I had provided about 95 percent of the money for Tesla, so I could become CEO anytime I wanted. And in the end, I had to frickin' become CEO of Tesla. I didn't want to be, but it was either that or the company was going to die."
   > — *The Book of Elon*

6. **Accept that taking the seat is the price of the product mattering.** This is not a career-optimization question. It is a "do I want this thing to exist" question. If the user genuinely wants the product to exist, they take the seat. If they want a job they enjoy, they hire a CEO and accept they will not get to make the product they imagine.
   > "I never wanted to be a CEO, but I learned you could not truly be the chief technology or product officer unless you were the CEO."
   > — *The Book of Elon*

## Common failure modes

- **"I'll just be Chief Product Officer and we'll hire a strong operator CEO."** This is the exact mistake Musk names as "fundamentally a moral error." At a tech-edge company, the operator CEO will out-vote the CPO on every product-defining call because the CPO does not control capital, hiring, or schedule.
- **"I hate the business stuff, so I shouldn't be CEO."** Musk hates it too. The point is not preference; it is that whoever does the business stuff makes the product decisions, so it must be you.
- **Hiring a "real CEO" to satisfy the board.** Boards want the comfort of a credentialed CEO; the product suffers when that CEO's instincts are finance, sales, or process rather than engineering.
- **Splitting co-founder titles by who's "more business-y."** This is comfort-driven, not strategy-driven. The CEO seat should go to whoever has the deepest conviction about and ownership of the product.
- **Staying CTO and complaining the CPO/CEO "doesn't get it."** If they don't get it and they have the seat, they win. You are now a complainer with a title.

## When NOT to use this skill

- The company's edge is genuinely not technology — e.g., a distribution-arbitrage business, a regulated licensing play, or a brand/media business. Then a non-technical CEO may be correct.
- The technical founder is genuinely unfit to be CEO and self-aware about it — has tried and failed, or has documented inability to do personnel and capital work even badly. Sometimes the right answer is to step aside entirely, not to split the seat.
- The company is already at scale (thousands of employees) and the founder-CEO is the bottleneck on execution; bringing in an operator CEO with the founder as Executive Chair / Chief Engineer can be the right move (and is itself a CEO-level decision the founder must make).
- The user is a junior IC weighing a CTO offer at someone else's startup — different question entirely.

## Source

The Book of Elon by Eric Jorgenson (2026, Scribe Media). Chapter: "Becoming Tesla's CEO" (in "Building Tesla").