Speed as a Habit
firstround.com
firstround.com
The phrase has a very specific meaning in statistics. Any one of us can think of counter-examples where a company which was late to a market ended up dominating it. This article's opening statement allows the author to deflect these repostes, saying "Ah but in that case, company x's execution was much better" or "Company b's marketing push came at a really bad time"; i.e. All else wasn't equal and so your counter-example doesn't detract from the author's point.
This reasoning is problematic. Imagine the equivalent phrase: "If you have two Ferraris, identical in every single way except that one has a higher rate of acceleration than the other, then the faster Ferrari is better". In a vacuum, this statement is so obviously true that it doesn't need to be said.
So the author starts with this statement. As every reader will intuitively agree with it, the author gets them "on side". They then go on to make unsupported claims, which the reader is now happilly innoculated to.
The article's opening is misleading because, effort being a finite resource, all else cannot be equal when it comes to human endeavour. By focusing on speed you inevitably sacrifice time spent on something else such as the rollcage, the breaks, or the looks.
The prediliction for speed and fast execution is systemic in the startup scene right now and it can be very damaging. Don't ignore that risk when pushing to deliver.
We didn't put men on the moon quickly, we did it as safely as we could. Google didn't become the pre-eminent search engine because it was first (it wasn't), but rather because it was the best.
EDIT: It has been pointed out to me that misuse of "All else being equal" in this manner is fairly common. That being the case, it is unlikely that the author was purposefully attempting to support an argument they knew to be weak (why would they do so, afterall). Apologies if the tone of the original comment was taken as aggressive :)
I take offense to idea of speed as a priority, though not necessarily to the whole article.
> All else being equal, the fastest company in any market will win.
All else is never equal when speed is the driving factor. I have never seen a company execute well while pressuring for speed.
It's significantly more important to think about systems. What is the cooperative source of your speed? What are the barriers to making good product quickly? What allows us to make faster decisions?
Invariably, without fail, unequivocally, the answers to these questions—which are sources of speed, quality, and market fit—lie in the systems that compose a company. Not systems as in slow methodical heavy processes, but systems as in a clear understanding of how things are connected and how to continually improve how they work.
Start with systems, then you can go fast. It's ludicrously dangerous to put the cart before the horse. Granted, much of this article dives into detail on how to make things run smoother in order to go fast—that's great, but if you focus primarily on the systemic source, imagine how fast you could go.
Speed... a noble goal, but as W. Edwards Deming said, "By what method?"
That doesn't follow. "All else being equal, best execution in any market will win". Does that mean, that good execution is the ultimate weapon in business?
Off topic: based on the title, I was expecting some drug addict stories.
"All else being equal", if that means all the companies in questions are on the same profitable trajectory, the fastest company probably will win.
The problem of course is that all else is never equal, and speed generally comes at a cost, which means there are plenty of scenarios where opting for a slower approach will be better.
For that reason alone, it's best to ignore the speed motivator and focus on what can actually improve to get you to be faster as a team.
In my experience too much speed poses a much greater risk than too little.
I dont agree with the general point of this article
"Why slow thinking wins"
General George Patton said that, and I definitely subscribe to it. Do you remember the last time you were in a meeting and someone said, “We’re going to make this decision before we leave the room”? How great did that feel? Didn’t you just want to hug that person?"
I, actually, wanted to severely beat that person for depriving me precious silent time alone to think about the decision.
There are different kinds of meetings. You need know what kind one is before you agree to attend. If it's a decision meeting, then you need to do your silent reflection before it begins.
Even thought both articles imply different contexts of 'fast' and 'slow', being caught in the impulsive decision making cycle is very easy, because, as the referenced book "Thinking Fast, Slow" states this is the natural, energy-efficient mode.
A friend of mine went to visit some of the biggest startups in SF (we are from Netherlands) and was shocked with the working culture. Things are going at insanely fast rates, people are irritated and the environment is extremely charged. Comparing to Europe, the work culture is more relaxed, a lot of people work part hours. I wonder what effect it has on productivity, accomplishments and satisfaction with life?
Yes, you can get it done today, but you will have a mess tomorrow. And you might just burn-out all the employees that can fix it.
This article is a perfect example of a hero manager who doesn't get it, imho. If you are too dumb to think, what can you do except make it a strategy not to.
Google is a startup, not a big company? And this dude leads a business?
Personally, speed is a matter of motivation and dedication on how much you want done per unit of time.
If you get your systems right, all three go up at once. The tradeoff is a false dichotomy.
And logically, this makes sense. If you've doubled your workforce, what the hell is preventing them from going quickly and executing well at the same time? Shouldn't you expect a decent bump in efficiency, if not double then at least a moderate increase? What leads to diminishing returns when you grow?
Systems, that's what. The connections between people, between processes, and the methods of management that generate those connections.
Read up on Deming, still the best source of wisdom on the topic.
The best posture for a specific system depends on how far you are from an optimum, and not by mindlessly claiming that "there's not free lunch" or "we can always improve".
Doesn't the fact that a change can worsen all three qualities imply that there must be a change that can also improve all three qualities?
These things are not always mutually exclusive. That's the fallacy.
Read the full phrase, not just half. I didn't say those are mutually exclusive anyway.
I think it all comes back down to motivation. Systems and design-level thinking is core, but there should be proper motivation.
Boyd was a fighter pilot who invented the concept of the "OODA Loop." Observe, Orient, Decide, Act. The competitor who can do this faster generally wins...not just by moving faster, but by disorienting opponents, and thus disrupting their OODA loops.
There's more to it than just pushing for speed. If you're doing a poor job of understanding the situation, for example, pushing ahead with fast decisions won't help you.
A lot of what Richards writes about is building a business capable of fast, effective OODA loops.