‘Organisational knowledge protection’ means making sure the quotes, specifications, artwork, and supplier history behind your product development do not live only in one person's inbox or on one person's laptop. It matters because most small and medium businesses discover the gap only after a key staff member has already walked out the door with it.

Designing a product versus designing a system is the difference between building a single item and building a foundation that can expand into a range without a full redesign. The choice between the two costs almost nothing to consider at concept stage, but can be much more expensive later on.

A visual overlay is a sampling review method where required changes to a prototype are marked directly onto photos of the physical sample. It uses CAD markups, reference images, and physical swatches, instead of written instructions. It matters because a written list of changes gets lost across language, culture, and distance, and every misunderstood instruction costs another two-week round of resampling. 

The Iron Triangle of product development is the balance between specifications, cost, and time, and the principle that you can usually optimise for two of the three, but rarely all three at once. Understanding how the pressure between them shifts across a project is one of the most useful, and most overlooked, skills a product developer can have.

A prototype (confirming a design) is not the same as mass production. The gap between the two depends heavily on how the sample was made, who made it, and the production method. That gap can widen if a proper design for manufacturing review was never done in the beginning.

Checking commerciality at the idea stage means confirming a product can be manufactured, priced, and sold before any real design work begins. It matters because a brilliant solution to a real problem can still fail completely if nobody checked whether it could be built and sold at a price the market will pay.

‘Expertise without the overhead’ means accessing decades of specialist product development experience only when you need it, rather than carrying the cost of a full-time hire or an overseas office all year round. For a growing SME, that difference is often what decides whether new product ideas actually happen… or quietly stalls. 

A realistic product development timeline accounts for supplier reliability, product complexity, and review cycles, not just the best-case number on a factory quote. It sits closer to an art built from experience than a fixed formula, and getting it wrong is one of the most common ways a launch date is blown out.

A realistic product development timeline accounts for supplier reliability, product complexity, and review cycles, not just the best-case number on a factory quote. It sits closer to an art built from experience than a fixed formula, and getting it wrong is one of the most common ways a launch date is blown out.