How we build products

A product is a solution to a problem in the market that should bring more benefit to the company developing the product than what it costs to develop.

Bringing a product idea to market

We understand the risks in taking a new product to market.

A large part of the risk is the fact that a Product Idea contains many assumptions around both the Problem and the Solution.

Wrong assumptions can mean taking longer to bring the right product with the right features to market. Lean Product Development investigates the need first, before coming up with the best solution to fulfil that need. First Validate the Problem, then Validate the Solution.

It is a process of rapid validation, allowing us to test assumptions and learn faster which assumptions are wrong. Then we can adapt our strategy and tactics quickly. Developing a product this way means we can help you launch the right product to meet your customers’ needs sooner and at a lower risk.

Validate the Problem – the building of the business

Product development starts with a vision of what the world would look like with a solution to a specific problem.

We focus on understanding this solution and the benefit it has to both the user and the business.

Some solutions assist companies in creating better products, opening up a new market or gaining a unique perspective that leads to new services or products. Each product will have a variety of stakeholders, including the Product Owner, Marketer, Sales Representative, Service Representative, UX designer, UI Designer and Software Engineer.

The following tools will assist the team in creating a deeper understanding of the market:

Business Model Canvas

Vision Canvas

Lean Canvas

User Interviews

Paper Prototypes

Competitor Analysis

The solution process

You as the entrepreneur focus on validating the problem and building the business. We’ll work together with you, in parallel, to build the right solution.

We work to find the answer to questions like what is the desired user experience, what functionality should the product provide and how should the product be built.

For this exercise, the team shrinks down to the Product Owner, Designer and Developer. Coming onboard will be additional developers and testers as well as any additional members that can add to creating a great product. The focus turns to the user, with the team capturing their assumptions about the product, including user interaction, user interface design and functionality.

Tools used to capture this information are:

Product Canvas

User Journeys

Rapid Prototyping

User Stories

Design Sketches

Incremental Product Releases

These assumptions are then tested using prototypes, mock-ups and MVP’s and feedback is gathered with product demos, user tests and releases to a small and selected group of users.