Studio notes
Good ideas are cheap. Good execution is rare.
Every week someone tells us an idea and asks us not to share it. We get it. But here is the uncomfortable truth: somewhere, several other people have had a similar idea this year. What almost none of them will do is execute it well. That is the scarce part, and that is where the value lives.
Why are good ideas cheap?
Because problems are visible to everyone. Thousands of Nairobi residents have been frustrated by the same queue, the same paperwork, the same unreliable service. Many will think, 'someone should build an app for this'. The idea is the easy part. It costs nothing but a matatu ride and a moment of irritation.
That does not make ideas worthless. It means the idea is the ticket to the game, not the win.
What does good execution actually mean?
| Execution is... | Not... |
|---|---|
| Choosing one user to serve first | Building for everyone |
| Shipping a focused first version | Waiting until it is perfect |
| Saying no to good ideas that do not fit now | Adding every suggestion |
| Watching what users do | Trusting what they say they would do |
| Polishing the core journey | Polishing features nobody uses |
| Showing up after the launch excitement | Moving on to the next idea |
Why is prioritisation the heart of execution?
Every product has more possible work than time and money. Execution is mostly the skill of choosing what matters most right now, and having the discipline to leave the rest. Teams that try to do everything do everything badly.
For a practical method, read why your first product does not need every feature.
Why do product decisions matter more than the original idea?
The original idea is one decision. A product is thousands: which screen comes first, what happens when payment fails, what the error message says, what to build next month, which customer request to decline. Each small decision compounds. Get most of them right and the product feels effortless. Get many wrong and even a great concept feels clumsy.
Why does execution fail?
- Scope grows faster than the budget.
- The team falls in love with the idea and stops listening to users.
- Launch keeps getting delayed because it is not 'ready'.
- Quality is spread thin across too many features.
- Nobody owns the decisions, so nothing is decided.
- Energy disappears after launch, when the real work begins.
How do you execute an idea well?
- Write the problem and the user in one sentence each.
- Test whether people care before building much. See before you build it, question it.
- Define the smallest version that solves the core problem.
- Set a launch date and protect it.
- Launch to a small group, measure, and improve the core first.
- Decide regularly what to stop doing, not just what to start.
This is the thinking behind our product-minded execution work, and the step-by-step path is in from idea to MVP.
So should you still protect your idea?
Be sensible: share with people you trust, and sign agreements where it matters. But do not let secrecy stop you from talking to customers, advisers and builders. The feedback you gain is worth far more than the small risk of someone copying an idea they would then have to execute themselves. Got an idea worth executing? Start a project inquiry.
Quick answers about ideas and execution
Is execution more important than the idea?
In most cases, yes. Many people have similar ideas, but few make the disciplined decisions about scope, users, quality and follow-through needed to turn an idea into a working product or business.
What does good execution mean in business?
Good execution means prioritising clearly, shipping a focused version early, learning from real users, maintaining quality on what matters most and following through consistently after launch.
Why do good ideas fail?
Common reasons include growing scope, delayed launches, ignoring user feedback, spreading quality too thin, unclear decision ownership and losing momentum after launch.
Should I keep my business idea secret?
Share it sensibly with people you trust and use agreements where appropriate, but avoid secrecy that stops you from getting feedback from customers and advisers.
How do I start executing my business idea?
Define the problem and the user, test demand cheaply, scope the smallest useful version, set a launch date, launch to a small group and improve based on real usage.