No Early-Stage Startup Team Can Truly Be Equal

That can happen. But depending on the situation, an “equal team” is clearly not preferable.
Early-stage startups are one such case.
To sum up the image of an equal team briefly,
- the whole team decides together
- the whole team acts together
- the whole team helps each other It’s a bit abstract, but that’s roughly what it means.
For an early-stage startup, having “the whole team decide together” is extremely difficult to begin with. Suppose the initial team has five members: a CEO, a CTO, two engineers who used to report to the CTO (one veteran and one junior), and a junior salesperson handling marketing. This is a fairly common setup, with three people building the product while two go out to pitch clients and raise funding. Suppose that midway through building the prototype, a technical difficulty surfaces, forcing a change to specs that have already been pitched to clients. The team now has to decide: do they stop selling until it’s resolved, or change the specs and restart the sales pitch? The CTO is completely convinced the specs need to change. The veteran engineer agrees with the CTO, but the junior engineer thinks a different approach might be worth trying. Still, among the three engineers, the junior was overruled earlier, so they come into the discussion already resigned to the idea that changing the specs is unavoidable. The salesperson is furious that all their hard work would be wasted, but honestly doesn’t really understand the technical constraints no matter how many times someone explains them. The CEO isn’t an engineer but knows the industry well, and is thinking: “I’ve run into situations like this many times before, so let’s see what happens here.”
At this point, the team’s perceptions and feelings are already all over the place. The salesperson doesn’t really understand the reasons but insists, “Seriously, please don’t do this to me.” The CTO says, “Even so, what can’t be done can’t be done,” and when the CEO asks how long a fix would take, answers, “A month at the most optimistic. Depending on how it goes, there might be no clear path to a solution at all.” The junior engineer had been wondering whether it was really worth bringing up “that approach” again, but since the CEO happens to be in the room, decides to propose it once more and adds a technical explanation on the spot. The veteran engineer flatly says, “No way.” The CTO backs off slightly: “It might be possible, but I don’t think we have an engineer here who could pull it off.” But the salesperson pushes back assertively: “If there’s a chance, let’s try it.”
So, will they reach an agreement!?
If there were plenty of time, a decision like this might work: set a deadline, try plans A, B, and C, and if none of them pan out, give up and go with the spec change, while sales works on getting the client to wait.
But a startup doesn’t have that kind of time, and if they don’t land this customer, there might not be a next chance.
A decision is needed right now.
In a moment like that, if there’s a founder CEO, that person should decide. At early-stage startups, a founder CEO holding a majority of the shares is extremely common. In some cases, that person may have put up nearly all of the company’s founding capital.
You often hear lines like:
“Let him decide. It’s his company, after all.”
It’s a particular kind of situation, but in this situation, insisting on “equality” accomplishes nothing. It only slows down decision-making needlessly, and in some cases that delay can be fatal.
That said, having one person decide alone carries an undeniable risk of its own. “Ikkun-banmin” was a doctrine of the old Japanese military: the idea that everyone except the top is equal. In the short term, this can make decisions clear, keep command unified, and produce results, but history tells us how it ends. For that reason, having multiple co-founders is generally considered preferable.
Originally published in Japanese at https://clazytech.com/2021/08/540/. Translated with LLM assistance and reviewed before publication.