Speed as the new essential David Giraourd, former President of Google Enterprise Apps and CEO of startup Upstart argues that speed is the key competitive advantage of to-day [and not just in Accelerators].
His top points are:
* Think first of all about the importance and the timing of each decision.
* Next about the inputs and perspectives of your team that you need.
* Make sure that all plans come with assigned completion dates.
* Prioritise mission critical items.
* Make sure that people are not waiting for one another, and can work in parallel.
* Firm up on doubtful assumptions eg legal or regulatory.
* Confront uncertain lines of authority eg CEO vs Founders vs Managers.
* Use your competition as your incentive.
* Help the members of your team to help you: what inspires them. And tell them why your objective is so vital.
I’ve long believed that speed is the ultimate weapon in business. All else being equal, the fastest company in any market will win.
Speed is a defining characteristic — if not the defining characteristic — of the leader in virtually every industry you look at. In tech, speed is seen primarily as an asset in product development. Many people would agree that speed and agility are how you win when it comes to product.
What they fail to grasp is that speed matters to the rest of the business too — not just product. Google is fast. General Motors is slow. Startups are fast. Big companies are slow.
The building blocks of speed are in making decisions and executing on decisions.
A good plan violently executed now is better than a perfect plan next week. The process of making and remaking decisions wastes an insane amount of time at companies. When a decision is made is much more important than what decision is made.
You should consistently begin every decision-making process by considering how much time and effort that decision is worth, who needs to have input, and when you’ll have an answer. Some decisions are more complicated or critical than others: more information might be essential; some decisions can’t be easily reversed or would be too damaging if you choose poorly. Most importantly, some decisions don’t need to be made immediately to maintain downstream velocity.
Eric Schmidt at Google knew he stalled a lot of things, but Eric made sure that decisions were made on a specific timeframe — a realistic one — but a firm one. The art of good decision making requires that you gather input and perspective from your team, and then push toward a final decision in a way that makes it clear that all voices were heard. You don’t want consensus to hold you hostage — but input from others will help you get to the right decision faster, and with buy-in from the team.
There’s an art to knowing when to end debate and make a decision. We intuitively want the team to come to the right decision on their own. But people are enormously relieved when they hear that you’re grabbing the baton and accepting responsibility for a decision.
Executing decisions A lot of people spend a whole lot of time refining their productivity systems and to-do lists. But within the context of a team and a business, executing a plan as quickly as possible is an entirely different concept.
Many plans and action items come out of meetings without being assigned due dates. Even when dates are assigned, they’re often based on half-baked intuition about how long the task should take. Completion dates and times follow a tribal notion of the sun setting and rising, and too often “tomorrow” is the default answer. For items on your critical path, it’s always useful to challenge the due date. All it takes is asking the simplest question: “Why can’t this be done sooner?”
Just as important as assigning a deadline, you need to tease out any dependencies around an action item. Mission critical items should be tackled head-on by your team in order to accelerate all downstream activities. Things that can wait till later need to wait.
A big part of this is making sure people aren’t waiting on one another to take next steps. The untrained mind has a weird way of defaulting to serial activities — i.e. I’ll do this after you do that after X, Y, Z happens. You want people working in parallel instead.
Projects can be so complicated that it can seem you have to go back over the thinking so much that everything else grinds to a halt too. For example, our business at Upstart has to comply with a lot of regulations. There’s not a lot we can do until we know we’ll have legal approval, so we used to spend a lot of time dancing around whether something was going to be legal or not. Then we thought, why don’t we just get a brain dump from our lawyers saying, “Do this, this and this and not this, and you’ll be fine.” Having that type of simple understanding of the problem drastically reduced the cognitive overhead of every decision we made.
If you can assess, pull out and stomp on the complicating pieces of the puzzle, everyone’s life gets easier. The one I see the most — and this includes at Google too — is that people hem and haw over what the founder or CEO will think every step of the way. Just get their input first. Don’t get your work reversed later on. What a founder might think is classic cognitive overhead.
Talking about your competition is a good way to add urgency. At Upstart, we constantly say that while we’re working hard on this one thing, our competitors are probably working just as hard on something we don’t even know about. So we have to be vigilant. A lot of people say you should ignore competition, but by acknowledging it, you’re incentivizing yourself to set the pace in your market.
When we were launching Google Apps, we were coming out against Microsoft Office, which had this dominant, monopolistic ownership of the business. We thought about what we could do differently and better, and the simplicity of our pricing was part of it — I think we decided that in a half hour. We just wanted to be able to tell people, “We may not be free, but we’ll be the simplest decision you ever made.”
Once you’ve made a decision, you’ll need to convince others that you’re right and get them to prioritize what you need from them over the other things on their plate. You need to understand this person, what their job is, how their success is measured, what they care about, what all of their other priorities are, etc. Then ask: “How can you help them get what they want while helping you get what you want?”
I’ve seen this done by appealing to people’s pride. Maybe you tell them that you used to work with a competitor who was quite speedy so that they have incentive to go even faster. I’ve also seen this done by appealing to human decency and being honest. You might say something like, “Hey we’re really betting heavily on this, and we really need you guys to deliver.”
Whichever route you choose, you want to back up your argument with logic. You should gently seek to understand what’s happening. I tend to ask a lot of questions like: “Can you help me understand why something would take so long? Is there any way we can help or make it go faster?”
To keep things moving along at Upstart, I ask a lot of hard questions very quickly, and most of them are time related. I know that we execute well and are generally working on the right things at the right time, but I will always challenge why something takes a certain amount of time. Are we working as smartly as we can?
Too many people believe that speed is the enemy of quality. To an extent they’re right — you can’t force innovation and sometimes genius needs time and freedom to bloom. But in my experience, that’s the rare case. There’s not always a stark tradeoff between something done fast and done well. Don’t let you or your organization use that as a false shield or excuse to lose momentum. The moment you do, you lose your competitive advantage.