The strategy / execution paradox

It’s a fine line, balancing strategy and execution.

There are so many variables relevant for both. Because if you think for too long, probably execution will be too late or at least a missed opportunity. Velocity matters.

At the same time, if you execute for too long without strategizing, you might be rowing in the wrong way. Strategy is darn important.

Finding the right balance between execution and strategy is one of the most important things we can do if we desire and scale output.

And 9 out of 10 times you should bias towards execution.

Execution is the ultimate form of input for strategy. But it doesn’t work the other way around.

If you think for an hour or a week, or a year, you will still only have feedback if you have tested your strategy in the real world. That’s what makes execution so important.

My conclusion here would be to fail fast, and strategize accordingly.

More often than not we doubt, because we think there’s no way back if we execute. And that we should think and strategize longer.

But that’s a trap.

It’s where emotions, procrastination and doubt comes in. Telling us that we could be wrong. And all the rejection we will have to endure if we’ve started executing too soon.

It’s a great excuse to procrastinate the execution.

That’s always the safe option.

But it rarely moves you closer.

It’s so much more valuable to try in the field to prove you’re wrong, than to think of more reasons that you’re wrong.

That’s why I have a bias towards action, execution.

For me, that has been the right decision more often than not.

Geef een antwoord

Het e-mailadres wordt niet gepubliceerd.