Why Early Startups Need to Be Quick to Fire

Sometimes founders start off with great friends who make lousy employees

Joe Procopio
Marker

--

Credit: EyeEm/Getty Images

LLast week, one of the founders I’m advising cleaned house. She let almost everyone go and put the few who remained on a different compensation and equity plan. The thing is, her startup wasn’t in trouble — in fact, it was financially sound and growing.

She recognized that her company and her vision had outgrown her initial team, including a co-founder, and it was either toss them overboard or watch the ship go down in a long, slow, painful way.

The wholesale overhaul of an entire team — or even just the booting of one or two early employees — isn’t the kind of thing that’s openly talked about in startup circles. It doesn’t have a catchy name or acronym. But it happens frequently enough that it is its own phenomenon. And while I hate it and most of the time I will disagree with it and recommend against it, I also understand it.

Should you be slow to fire or quick to fire in the early days? It’s a tricky question and the right answer depends on some thorny subjects. So let’s talk through it.

Is it the team or is it you?

The obvious — and correct — counter: Wait a minute, you’re just pissed off and you’re…

--

--

Marker
Marker

Published in Marker

Marker was a publication from Medium about the intersection of business, economics, and culture. Currently inactive and not taking submissions.

Joe Procopio
Joe Procopio

Written by Joe Procopio

I'm a multi-exit, multi-failure entrepreneur. AI pioneer. Technologist. Innovator. I write at Inc.com and BuiltIn.com. More about me at joeprocopio.com