Build only what moves your KPIs: a lean approach to digital products
Most products don’t fail because they do too little. They fail because they try to do everything at once. Here’s how to find the few features that matter and ship them first.
Every new product starts with a long wish list. Dashboards, integrations, settings, notifications, an admin panel, a mobile app. It all feels essential at the start. But every item on that list costs time and money, and most of it won’t change whether your product succeeds.
A lean approach flips the question. Instead of asking “what could we build?”, ask “what is the smallest thing we can build that proves this works?”
Start with the number, not the feature
Before writing a single user story, agree on the one or two metrics that define success. For a store, it might be conversion rate and repeat purchases. For a SaaS product, activation and retention. For an internal tool, hours saved per week.
Once the number is clear, every proposed feature has to answer one question: will this move it? If the answer is “maybe later”, it goes on the later list.
Scope is the cheapest place to save money. Every feature you don’t build is one you never have to test, maintain or explain.
Use a lean canvas to find the core
A lean canvas fits your whole idea on a single page: the problem, the customer, your unique value, the solution, channels, revenue and costs. Filling it in forces hard choices quickly. We often run it as a one-hour workshop with sticky notes, and it routinely cuts a feature list in half.
- Problem: what are the top three problems your customer has today?
- Customer: who has those problems most acutely, and how do you reach them?
- Value: why would they choose you over doing nothing?
- Solution: what is the simplest thing that solves the top problem?
Ship, then listen
An MVP isn’t a worse version of your product. It’s the fastest way to learn what your product should be. Launch the essential features, watch how real users behave, and let that data decide what comes next.
Agile delivery makes this practical. Work in short sprints, demo working software at the end of each one, and re-prioritise based on what you learn. Features that users ask for rise to the top. Features nobody misses quietly disappear.
Lean doesn’t mean cheap
Building less is not the same as building badly. The features you do ship should be fast, accessible, secure and well designed. Lean is about where you spend, not how little you spend. Quality on the essentials is what earns you the right to build more.
- Define success as one or two numbers before you scope anything.
- Use a lean canvas to cut your feature list to the core.
- Launch early, measure, and let real users set priorities.
- Keep quality high on the few things you do build.