Having a good idea is just the beginning.
The road from concept to product is long, iterative, and full of decisions that can either protect your project or quietly derail it. After years of leading product development at Ferrari and Rimac-Bugatti — and now working with businesses across Singapore, Malaysia and Indonesia — I’ve seen the same pitfalls appear repeatedly.
This is the framework I use to think about product development. It won’t remove the complexity, but it will help you stay in control of it.
Development is an iterative process — not a straight line
The first thing to understand is that product development is not linear. From the initial idea to the final product, you will go through multiple iterations at almost every stage.
Failing to understand this creates two problems. First, it leads to frustration when progress feels slow or non-linear. Second, it causes teams to underestimate the time and budget required — one of the most common reasons early-stage projects fail.
Build iteration into your planning from day one. Expect it. Budget for it.
Stage 1: Concept
Every product starts with an idea. But an idea alone has no operational value until it’s been tested, defined, and structured.
The concept stage has three distinct steps.
The first is the idea itself — identifying something the market needs that doesn’t yet exist, or doesn’t exist in the form your target customer needs it.
The second is research. Before committing time and budget, validate whether the idea makes sense. Talk to potential customers. Gather feedback from outside your immediate circle. This step does two things: it sharpens your thinking by forcing you to explain the idea clearly, and it gives you early proof of concept from people who have no reason to be polite about it.
The third is product definition — building the foundation on which everything else will be developed. This is where standard operating procedures for the project begin to take shape. It covers four areas: target setting, feasibility analysis, preliminary risk assessment, and planning.
Target setting means defining clear, measurable performance goals for the product. Without them, there is no objective way to assess progress.
Feasibility analysis answers the critical questions: Is this technically achievable with current technology? Is it financially viable? Are there regulatory constraints? Does the team have the capability to execute?
Preliminary risk assessment is where most teams underinvest — and where the most expensive problems originate. Identifying risks before development begins allows you to allocate resources to the right areas and build contingency into the plan. Teams that skip this step end up reacting to problems instead of controlling them. This is how business bottlenecks are created.
Planning turns the project into a structured sequence of steps with a realistic timeline. A project without a timeline is a hobby.
Stage 2: Development
This is where budget starts to move — which is exactly why the concept stage matters so much. Entering development with a weak foundation is one of the most reliable ways to run out of money before the product is ready.
The development stage is an iterative loop: engineering and design, prototyping or virtual validation, testing and validation, issue resolution, and release of a minimum viable product. The specific steps vary by product — some can run in parallel, some can be compressed. There is no universal rule. The process must be tailored to the product and refined continuously to improve efficiency.
The difference between a great product developer and an average one is the ability to complete the minimum number of iterations needed to achieve the desired outcome within budget, time, and quality constraints. That ability comes directly from the quality of the risk assessment done in Stage 1.
Stage 3: Launch
Launch is formally outside the development process — but it’s where the development work either pays off or falls apart.
Once the product is reliable, industrialisation begins. This is a fundamentally different mindset. In development, iteration is expected and managed. In launch, iteration is expensive and disruptive. Committing production budget to a product that still requires design changes is one of the fastest ways to destroy a project’s economics.
This stage covers building the supply chain, selecting a manufacturing location, setting up production and logistics, consolidating manufacturing partnerships, initiating marketing, and establishing distribution channels.
Each of these areas benefits from the same structured, documented approach that good standard operating procedures provide — clarity on who does what, in what sequence, and to what standard.
The mindset that holds it all together
Product development is not a straight road. It is an iterative process that demands organisation, adaptability, and a team willing to rebuild the plan when conditions change.
The businesses I work with that execute product development most effectively share one habit: they invest heavily in structure at the start — clear targets, documented risks, defined processes — so that when things change (and they always change), they have a foundation to adapt from rather than chaos to manage through.
That’s not a product development principle. It’s an operational efficiency principle. And it applies to any business building anything.
Want to find where your development or operational processes are creating hidden bottlenecks? Take the free RISE Assessment — 10 minutes, instant results.