Execution & Leadership4 min read

Stop Planning. Start Implementing. A Case for Execution-First Leadership.

by Sean Tay

I've been in business for 17 years. I've been bankrupt once, survived Black Monday twice, and built Malaysia's first Google Cloud Premier Partner from nothing.

If I had to distill everything I've learned into one sentence, it would be this:

The businesses that win are the ones that implement - not the ones that strategize.

The Planning Addiction

I see it constantly. A company identifies an opportunity - AI implementation, market expansion, product development. They assemble a committee. Commission a report. Run a workshop. Build a slide deck.

Three months later, they have a beautiful 47-page strategy document and exactly zero progress.

Meanwhile, their competitor - the one who spent two weeks on planning and started implementing in week three - is already on their third iteration and learning from real-world data.

Why Execution Speed Matters More Than Strategy Quality

Here's what most people miss: a mediocre strategy executed fast beats a perfect strategy executed slowly. Every time.

Why?

1. Learning Only Happens Through Implementation

You don't learn by planning. You learn by doing. Every week of implementation generates data, feedback, and insights that no amount of planning can produce.

The company that implements in month one has 5 months of learning by the time the planning-obsessed company finally launches. That learning gap is almost impossible to close.

2. Speed Compounds

Implementation speed is a compound advantage. Each iteration builds on the last. Each lesson learned accelerates the next decision. The gap between fast implementors and slow planners widens exponentially - not linearly.

3. Market Windows Close

Opportunities don't wait for your strategy document to be finalized. The market moves. Competitors move. Customer needs evolve. By the time your perfect plan is ready, the world has changed.

The Execution-First Framework

I don't mean "act recklessly." I mean "bias toward action within a clear framework."

Here's how I approach it:

Week 1-2: Define the hypothesis. What are we trying to achieve? What's the minimum viable approach? What does "good enough to ship" look like?

Week 3-4: Build and ship. Not perfect. Not polished. Functional. Get it in front of real users, real customers, real data.

Week 5-8: Measure and iterate. What worked? What didn't? What did we learn that we couldn't have predicted? Adjust. Ship again.

Repeat. Permanently.

Real Example: How This Played Out

In 2022, when Google's new partner incentive structure was announced, we had a choice. We could spend 6 months analyzing the impact and building a comprehensive response plan. Or we could start implementing changes immediately.

We chose speed.

Within 4 weeks, we had restructured our customer success program. Within 8 weeks, we had diversified our revenue streams. Within 12 weeks, we had a completely new operating model.

By the time most of our competitors had finished their analysis, we'd already executed three rounds of improvements based on real data.

The result? In 2024, Google named us Partner of the Year for APAC. Not because we had the best strategy. Because we executed the fastest.

The Hard Part

Execution-first leadership is psychologically uncomfortable. It means:

Accepting imperfection. Your first version will be rough. Ship it anyway.

Making decisions with incomplete information. You'll never have all the data. Decide with 70% and adjust.

Being willing to be wrong publicly. When you implement fast, some things will fail visibly. That's the cost of learning speed.

Resisting the urge to over-plan. Planning feels productive. It gives you the illusion of progress without the risk of failure. It's a trap.

The Test

Here's a simple diagnostic:

Look at your current top initiative. How many weeks has it been in the "planning" or "strategy" phase? How many iterations have been shipped?

If the ratio of planning weeks to shipped iterations is greater than 3:1, you have an execution problem.

What I Tell My Team

Every Monday morning, I ask the same question: "What shipped last week?"

Not "what did we discuss." Not "what did we plan." Not "what meetings did we have."

What shipped.

If the answer is "nothing," we have a problem. And the solution is never more planning.


Follow my daily insights on execution-first leadership and AI transformation on LinkedIn.

Sean Tay

Sean Tay

CEO of MatrixC, Malaysia's first Google Cloud Premier Partner. Author of The Execution-First Advantage. Building businesses that bridge the digital divide.

Follow the journey.

I share daily insights on AI transformation, execution-first leadership, and the reality of building businesses.

Follow on LinkedIn