Top-down leadership has its place at startups

I’ll confess something here: team members have told me I’m “too top-down.”
Not just once. Several times.
I won’t say it happens every time, though.
When you become a leader, everyone wants to exercise “republican leadership.”
Even more so when you have trustworthy members, meaningful goals, and aligned expectations from those around you. Everyone cooperates, problems are always discussed openly, and things move forward with mutual understanding. The workplace is happy and everyone gets along. Everyone wants that kind of scene.
And yet, there are times when you notice something is “missing.”
“Driving force.”
Fruitful, constructive discussion. A reasonable development schedule. A budget plan with no strain. The right collaborators at the right milestones. The right technology and the right working environment.
”(…but can we actually win with this?)”
In most cases, startups are aiming at goals that are reckless. Things like “exponential revenue growth,” or “dominating the market in two years,” or “revolutionizing the XX market.”
If you want to stack up the right things in the right amount in the right way, and do what’s reasonable and ordinary, maybe you should stay away from startups. There are times when you need a kind of madness. Turning a plan of 1 into 1.2. Finishing in 10 months what was supposed to take a year. Being prepared for instant death — bankruptcy — if it fails.
You need to muster that level of unyielding greed.
Can you get everyone to share that kind of common understanding?
Does something like that arise spontaneously?
I believe it’s impossible.
Things that are right and reasonable can be arrived at through discussion. Give a team of excellent members enough time, and they will always reach the correct answer. But I know of no way to reach, through republican discussion, “an answer that’s mostly in the right direction but not quite right” — an answer that’s slightly off from correct.
So when I judge that it’s necessary, I use a top-down approach.
In most cases, nobody thanks me for it. Usually the team gets thrown into disorder. On top of that, the risk if it ultimately fails is extremely large. Even so, I use it. The reason is simply that I don’t want to regret later not having done what needed to be done when it needed doing.
I think the worst outcome for a startup isn’t losing the competition and going bankrupt — it’s dragging on without ever challenging anything, never knowing what the result would have been if you had.
Originally published in Japanese at https://clazytech.com/2021/08/490/. Translated with LLM assistance and reviewed before publication.