Startup vs Big-Company: The Leadership You Trained May Be a Liability on the Other Side
Topic: Startup vs Big-Company Leadership·4 Principles
"Peacetime CEO knows that proper protocol leads to winning. Wartime CEO violates protocol in order to win." — Ben Horowitz
This issue's thesis: the same leadership capability often carries the opposite sign in a startup versus a big company. The process, coordination, and stakeholder alignment you mastered at a big company are fatal premature optimization at a startup; the hands-on heroics and rule-bending that work at a startup are unscalable single points of failure at a big company. Capability has no absolute good or bad — only fit with stage. BigCat is a tech lead manager at a big company who also wants to be a "super-individual," so this difference has to be read both ways: which big-company skills become liabilities when you move to a startup, and how to preserve the 0→1 muscle inside a big company without letting bureaucracy atrophy it. Four steps: stage is the first variable, creating vs scaling are two muscles, the intrapreneur's trap, and what to unload and rebuild when you switch.
PRINCIPLE 01
Stage Is the First Variable: Wartime Leader vs Peacetime Leader
Wartime vs Peacetime — Stage Is the First Variable
Stage FitWartime/PeacetimeSituational
The Principle in One Line
A leadership style has no absolute right or wrong — only fit with stage. The same act — rewriting critical code yourself, calling the shot around process — saves the day at a startup but manufactures single points of failure and breaks scalability at a mature company. Before judging good or bad, judge which stage you're in.
In Their Words
"Peacetime CEO knows that proper protocol leads to winning. Wartime CEO violates protocol in order to win."— Ben Horowitz, The Hard Thing About Hard Things, "Peacetime CEO/Wartime CEO"
Stage → Leadership Mode
Scene
Context: a staff engineer who joined a big company from a startup hits a production P1 and instinctively wants to charge in, hotfix it himself, and bypass review.
✗ Wartime move dropped into peacetime
"Forget review — I'll push a patch directly, five minutes, I'll backfill the process later." At a startup this is heroism; at a big company that one cut bypasses change control, the rollback plan, and the right-to-know of three dependent teams. You fix this one, plant a bigger landmine, and the team learns "when it's urgent, you can just bypass."
✓ The move after recognizing the stage
"Spin up a war room per the incident process, name an IC, and push the fix through the emergency review channel — a big company has that channel precisely for moments like this. Then run a blameless postmortem and distill the hotfix into a reusable runbook." Personal heroism is converted into a reusable system.
Self-Check: Which Mode Should I Be In?
Are we searching for the answer (PMF) or replicating a known answer (scaling)? Former leans wartime, latter peacetime.
If this decision is wrong, is it fatal or reversible? Fatal and time-pressed → call it fast; reversible → delegate and run the process.
The process I'm bypassing — am I fighting a fire or taking a shortcut? The latter builds technical and organizational debt.
Am I jumping in because only I can do it, or because I can't let go? The latter is a signal to delegate.
Common Mistakes
Treating style as personality, not tool. "I'm just a hands-on leader" — you've simply failed to notice the stage changed.
Faking wartime at a big company. A daily "wartime" mindset with no real existential threat manufactures anxiety and overreach.
Faking peacetime at a startup. Building heavy process and six-page memos before PMF is even in sight — optimizing away the speed that keeps you alive.
Knowing only one mode. What's truly scarce is a leader who can switch between wartime and peacetime.
Key References
Ben Horowitz, The Hard Thing About Hard Things (chapter "Peacetime CEO/Wartime CEO") — the origin of the wartime/peacetime frame. Larry Greiner, "Evolution and Revolution as Organizations Grow" (HBR, 1972/1998) — five stages of organizational growth, each with a different crisis and leadership demand.
PRINCIPLE 02
Zero-to-One vs One-to-Hundred: Creating and Scaling Are Two Different Muscles
Zero-to-One vs One-to-Hundred — Two Different Muscles
Create vs ScaleDelegationSystematize
The Principle in One Line
Taking something from 0 to 1 (making a new thing amid uncertainty) and from 1 to 100 (scaling a validated thing) are nearly opposite capabilities. Creating runs on hands-on work and speed; scaling runs on systems and delegation. Many get stuck trying to scale the way they create — and become the bottleneck.
In Their Words
"Doing what we already know how to do takes the world from 1 to n... But every time we create something new, we go from 0 to 1."— Peter Thiel, Zero to One, Ch.1
The Two Muscles, Side by Side
Scene
Context: BigCat's team grew from 3 to 12. The most critical service is one he wrote by hand, and he's used to reviewing and approving every core change himself.
✗ Scaling the way you create
"The core path is too important — I'd better review it myself; you all take the periphery." Three months later he's the bottleneck on every key PR, and his strongest engineers — locked out of the core, unable to grow — start looking elsewhere. He's doing a 3-person job inside a 12-person team.
✓ Switching to the scale muscle
"Write the judgment criteria for the core service into a design-principles doc and a review checklist, name two owners, and I step back to a guardrail role — only watching for red lines." To the person taking over: "This used to be my baby; now it's yours. I give you the boundaries, not the answers — I'll stop you at a red line, but inside it I don't interfere."
Self-Check: Am I Still Using Create-Phase Moves While Scaling?
Are the things only I can do growing or shrinking? (Shrinking is the sign of healthy scaling.)
Have I turned "my judgment" into "a standard others can use", instead of leaving it only in my head?
If I'm gone for two weeks, do the team's key decisions stall or continue as usual?
Common Mistakes
Mistaking non-delegation for high standards. "Only I can guarantee quality" — right short-term, but long-term you seal off the team's growth and your own rise.
Premature systematization. Writing heavy process docs in the 0→1 phase freezes unvalidated things and kills exploration.
Assuming skill in one is skill in the other. Many great 0→1 founders get replaced during scaling — not failure, just a muscle mismatch.
Still using the hero narrative while scaling. Praising "who saved the fire tonight" makes people start fires to put out — rewarding the wrong behavior.
Key References
Peter Thiel, Zero to One — the essential distinction between 0→1 and 1→n. Reid Hoffman, Blitzscaling — why the scaling phase deliberately sacrifices efficiency for speed. Will Larson, An Elegant Puzzle — turning judgment into systems, delegation, and team topology.
PRINCIPLE 03
The "Entrepreneur" Trap Inside a Big Company: Keeping the 0→1 Muscle from Atrophying
The Intrapreneur's Trap
IntrapreneurshipInfluenceSuper-Individual
The Principle in One Line
A big company rewards "wait for permission, write the deck, align until everyone agrees" — a set of behaviors that is slow death at a startup. To be a super-individual inside a big company, selectively keep the entrepreneur's reflexes amid bureaucracy — but tell apart which "bypasses" advance you and which get you labeled.
In Their Words
"The hallmark of originality is rejecting the default and exploring whether a better option exists."— Adam Grant, Originals, Ch.1
Scene: Request Resources vs Just Build It
Context: BigCat spots an obvious improvement to an internal tool, but it isn't in this quarter's OKRs.
✗ Pure big-company reflex
"First write a proposal, slot it into next quarter's planning, wait for the org to approve resources and three teams to align." Half a year later the window has closed, or the proposal has been sanded down to something toothless by its fourth review.
✗ Pure startup reflex (gets you labeled at a big company)
"Just pull two people, quietly build and ship it, ask forgiveness later." The thing might be good, but you've touched someone else's system, gotten tagged "uncontrollable, doesn't respect process," and someone holds a grudge at promotion calibration.
✓ The intrapreneur's middle path
Use a prototype small enough to need no approval, touch only what's within your own permissions, and prove value with real data. Then bring something you can demo — not a deck — to the owner: "I built a prototype that validates X; I'd like to talk about getting it onto your roadmap, under your team's name." Lower the decision cost with the work, and expand through collaboration rather than bypass.
Self-Check: Which Big-Company Habits Are Startup Liabilities / Which Reflexes to Keep
Permission culture: safe at a big company, slow death at a startup — practice "do first, report after" on reversible, low-risk things.
Deck-driven: a prototype you can demo beats slides — keep the "build it, then talk" muscle.
Align until everyone's happy: often equals mediocrity — tell apart which decisions truly need broad alignment and which only need one or two key nods.
Sense of boundaries: this is the real skill a big company teaches — don't drop it at a startup; before bypassing process, be clear whose turf you're touching.
Common Mistakes
Treating "entrepreneurial spirit" as a license to ignore process. Half of big-company process is bureaucracy, half is protection others bought with incidents — confuse them and you step on a mine.
Using the demo to humiliate, not invite. "Look, I alone built what you didn't in half a year" — you win the prototype and lose all future collaboration.
Mistaking visibility for influence. Flashing presence everywhere isn't being irreplaceable; the leverage is work others can't route around.
Female Leader's Note
Female Leader's Note
"Ask-forgiveness" intrapreneurship has a lower margin of error for women at a big company: the same "bypassing process" is often read as "has ownership, bold" for men but more easily as "doesn't follow rules, hard to work with" for women (the likability penalty). A counter: turn the solo prototype into collaboration with co-signers as early as possible — bring the relevant owners on as joint authors — rewriting "she acted on her own" into "she drove a cross-team collaboration." Not retreat — a non-backfiring wrapper for the same nerve.
Key References
Adam Grant, Originals — strategies for pushing new ideas within an institution, and the timing of "earn status first, then take the risk." Gifford Pinchot, Intrapreneuring — the origin of the word "intrapreneur" and the classic treatise on building inside a large organization.
PRINCIPLE 04
What to Unload, What to Build When You Switch: A Two-Way Conversion Map
What to Unload & What to Build When You Switch
Career MoveSkill ConversionSelf-Diagnosis
The Principle in One Line
The biggest risk in switching stages isn't lacking skill — it's carrying the previous stage's muscle memory without unloading it. Big-company-to-startup most often dies of "over-structuring"; startup-to-big-company most often hits the wall of "ignoring systems." First figure out which abilities transfer, which are liabilities, and which you must build new.
In Their Words
"The higher you go, the more your problems are behavioral. What got you here won't get you there."— Marshall Goldsmith, What Got You Here Won't Get You There
Skill Conversion Map
Scene: A Self-Diagnosis Conversation Before Switching
Context: BigCat is weighing whether to leave the big company to be head of engineering at a Series-B startup.
✓ Three questions to be honest with yourself about
1. Where does my sense of achievement come from? "Making something from nothing" or "making the existing thing steadier and bigger"? The former suits early stage, the latter scaling. The cost of self-deception is years of mismatch.
2. How much of my advantage comes from the big-company platform? Brand, resources, network — honestly separate "my ability" from "the ability the platform lends me," and note what zeroes out when you leave.
3. How much structurelessness can I tolerate? A startup has no clear ladder, no ready-made systems, and pay may drop — that's its nature, not a flaw; the question is whether your psychological and financial buffer is enough.
Switching Checklist
Have I listed the 2 old habits I need to actively unload? (Not what to learn — what to stop doing.)
Have I separated "my ability" from "the ability the platform lends me" — which zeroes out when I leave?
Do I have a financial buffer (FU money / runway) to ride out the swings of the adaptation period?
Is my first-90-days goal to understand before remaking, or to rush to prove myself? (Switchers most often die of the second.)
Have I asked people who've walked this path what's easiest to step on?
Common Mistakes
Walking a new road with the old map. Bring a full big-company process to a 5-person startup and you get bureaucracy before you even have a product.
Underestimating the zeroing of platform dividends. Much of "my influence" was borrowed from the company brand; switch and you find the doors no longer open by themselves.
Remaking everything on arrival. Overturning it all in the first 90 days turns the "understanding period" into an "enemy-making period."
Treating a job change as escape. First be clear whether you're fleeing a stage mismatch or something else — otherwise you just jump into another mismatch.
Key References
Marshall Goldsmith, What Got You Here Won't Get You There — why old success patterns become obstacles in a transition. Michael Watkins, The First 90 Days — the "diagnose before remaking" cadence of the first 90 days. Marty Cagan, EMPOWERED — the leadership differences teams need at different stages.
Deeper Questions · Pushed to the Edge
1. Can "stage fit" become an excuse not to grow or improve?
Yes — that's its abuse boundary. "We're a startup so we don't need process" can be an honest judgment or a fig leaf for dodging engineering discipline. The test: is what you're sacrificing making way for the single most critical constraint right now? Sacrificing process for speed is a real trade-off; sacrificing to the point of no tests, no review, and all critical knowledge inside one person's head is not stage fit — it's planting landmines. Ask: "Is this simplification to move fast, or just because doing it right is annoying?"
2. From a senior big-company role to a startup, can the halo become a burden?
Often yes. A big-company title brings not just expectations but a platform-spoiled way of working: someone handles hiring, legal, cross-team coordination — all gone at a startup. The subtler trap is identity inertia: you're used to exercising influence through rank, but a startup only recognizes what you solved with your own hands this week. Healthy switchers "level down" on purpose — doing grunt work for the first months to rebuild the "I can create value directly" muscle and the team's trust. Take the halo off yourself, or it refuses growth on your behalf.
3. Are "super-individual" and "scaling leader" contradictory?
There's real tension. The super-individual's leverage comes from being irreplaceable, while a scaling leader's value comes precisely from making yourself replaceable. The more you want to build something dazzling with your own hands, the harder it is to delegate. One integration: move "irreplaceable" from the execution layer to the judgment layer — it shouldn't be "only I can write this code" but "only I can define the direction, see the trap, spot the talent." Delegate execution; make judgment and taste scarce. That scales the team and keeps your personal leverage.
4. Does this stage frame hold the same in hardtech vs pure software?
The frame holds, but the parameters differ enormously. Pure-software 0→1 can prototype in weeks and iterate fast, so "scale first, fix later" is often viable; but for biotech, aerospace, and chips, 0→1 itself takes years and huge capital — "fail fast" means the company goes to zero, so it actually needs substantial engineering discipline early. Heavily regulated industries (finance, healthcare) are the same: the cost of bypassing process is legal liability. Don't copy the Silicon Valley software narrative — first ask what the unit cost and irreversibility of a mistake are in your industry, then set the ratio of speed to structure.
This Issue's Exercise · Your Day 41 Action
Do two concrete things this issue — not reflection, not reading:
Step 1 (stage diagnosis): Use Card 1's four self-check questions to locate your team now — overall in 0→1, 1→100, or peacetime mode? Then answer honestly: do my own default moves right now (jumping in vs delegating and building systems) match that stage? Write down the one that doesn't.
Step 2 (unload one move): Pick one thing "only you can do," and this week write its judgment criteria into a one-page doc or checklist, hand it to one person to own, and step back to the guardrail role. It's the smallest step in converting the create muscle into the scale muscle.
One reflection question: If you jumped to a 5-person startup next week, of the abilities you rely on today, how much is "yours" and how much is "lent to you by the big-company platform"? That ratio decides your real starting point when you switch.