Two Companies, One Phrase
I've sat in kickoff meetings at a four-person seed-stage company and at a three-hundred-person Series D company, and heard the exact same sentence in both rooms: "That's just how we operate — we're a startup, we move fast."
At the first company, it was true, and it was earned. There was no roadmap because there was no product yet. There was no formal ticket process because three engineers could talk through a decision in the time it would take to write it down. The informality was proportional to the size of the problem.
At the second company, it was a cover story. There were three hundred employees, a real customer base, real revenue, real compliance obligations — and also no clear owner for half the codebase, no documented reason for half the architecture decisions, and a habit of shipping features nobody had actually agreed on the requirements for. When something broke, "we're scrappy" was the explanation offered instead of an actual post-mortem.
Those are not the same phenomenon wearing the same words. One is a genuine operating mode suited to genuine constraints. The other is disorganization wearing a costume it stopped fitting a long time ago.
What Startup Culture Actually Means
Real startup culture, the kind that built the companies people study, was never about the absence of process. It was about a specific set of tradeoffs made deliberately, under real constraints, by people who could tell you exactly why they were making them.
Speed came from small surface area, not from skipped thinking. A five-person team can make a decision in a Slack thread because five people can hold the whole system in their heads at once. That's not a lack of rigor — it's rigor happening at conversational speed instead of documentation speed.
Ownership was total, not diffuse. In a real early-stage company, if you touched it, you owned it — end to end, including the consequences. "Scrappy" companies with genuine culture don't have less accountability than mature ones. They have accountability concentrated in fewer people, which is a different thing entirely.
Informality was a means, not an identity. Nobody who built something real was attached to the absence of process as a personality trait. They dropped process that wasn't earning its keep and kept the process that was. The goal was building the right thing quickly — not performing a vibe.
What the Excuse Version Looks Like
The weaponized version of "startup culture" has a recognizable shape, and it shows up disproportionately at companies well past the stage where the excuse should still apply.
No one can tell you why a system was built the way it was. Not because the decision was undocumented on purpose to move fast — because nobody thought to ask the question in the first place, and now the person who could answer it left eighteen months ago.
Onboarding is "just ask around." New engineers spend their first month reconstructing tribal knowledge through Slack archaeology instead of reading anything, and leadership calls this agility instead of what it actually is: an absence of institutional memory.
Ownership is everywhere and nowhere. Ask who owns the billing service and you'll get three names, none of whom feel fully responsible, all of whom assumed someone else was watching it. That's not startup energy. That's a bus factor of zero dressed up as flat hierarchy.
Postmortems don't happen, or happen without follow-through. Incidents get patched, not understood. The same category of outage recurs every few months because nobody was ever tasked with fixing the root cause — just the fire.
Feedback gets deflected with the culture, not addressed on the merits. Someone raises a legitimate concern about test coverage or documentation, and the response is some version of "we're not that kind of company" — as if rigor were a lifestyle brand instead of a response to actual risk.
| Real Startup Culture | The Excuse Version |
|---|---|
| Small team, small surface area, fast decisions | Large team, sprawling surface area, same fast decisions |
| Total ownership by whoever's building it | Diffuse ownership, nobody fully accountable |
| Process dropped because it doesn't pay for itself yet | Process avoided because nobody wants to do it |
| Tribal knowledge because there's no time to write it down yet | Tribal knowledge because nobody was ever asked to write it down |
| Speed as a byproduct of clarity | Speed as an excuse for the absence of clarity |
Why This Happens
Companies don't usually decide to become disorganized. It creeps in, and "startup culture" becomes the retroactive justification for whatever the organization already is, rather than a deliberate operating choice.
Part of it is nostalgia. Founders and early employees remember when the informal approach worked — because at the time, it matched the company's actual size and risk profile — and they keep reaching for it long after the company has outgrown it. Part of it is convenience. Process is genuinely more work to build and maintain than the absence of process, and "that's not who we are" is a much easier sentence than admitting the team never got around to it. And part of it is that disorganization is invisible until it's expensive. Nobody notices the missing runbook until the outage happens at 2am. Nobody notices the undocumented decision until the person who made it is gone and someone else has to guess.
By the time the cost shows up, it's usually wearing a name tag that says "culture," which makes it much harder to challenge than if it were just called what it is.
The Tell
There's a simple diagnostic question that cuts through most of this: would this company's current level of process be appropriate if a brand-new employee had to operate inside it with zero tribal knowledge?
A five-person company where nothing is written down passes that test — there's so little surface area that a new hire can absorb it all in conversation within days. A three-hundred-person company where nothing is written down fails it badly, and no amount of "we move fast here" changes that math. The size of the problem has to justify the size of the process gap. When it doesn't, what you're looking at isn't culture. It's debt that hasn't been named yet.
Another tell: ask what happens when someone raises a concern about the informality. A healthy team says "you're right, let's fix that" and does. An unhealthy one gets defensive, treats the observation as an attack on identity, and doubles down on the phrase instead of the fix.
What Doesn't Have to Go Away
None of this is an argument for bureaucracy. Plenty of genuinely fast, genuinely well-run companies stay light on process by design, and that's a real and valuable thing to protect. Quick decisions, minimal ceremony, high trust, low friction — those are good. They just have to be earned by the actual constraints of the business, not asserted as a permanent identity regardless of how much the business has changed underneath it.
The healthiest version of this I've seen keeps the speed and adds the minimum viable amount of structure to make that speed sustainable: a short written rationale for decisions that will outlive the person making them, one clear owner per system even when the team is small, a real five-minute postmortem after incidents instead of a shrug. None of that slows a team down in any way that matters. It just means the speed doesn't quietly become someone else's problem six months from now.
The Standard Worth Holding
"We're a startup" is a description of a company's stage and constraints. It is not a permanent exemption from the basic disciplines that keep organizations functional as they grow — knowing who owns what, knowing why decisions were made, and being able to explain your systems to the next person who has to work inside them.
If your company has outgrown the constraints that made the informality legitimate, the informality should have outgrown itself along with it. Holding onto the language after the reality underneath it has changed isn't scrappy. It's just disorganization that hasn't been asked to justify itself yet.
Ask it to.
