Product discovery and definition

A discovery and definition phase builds a detailed level of shared understanding between Devbridge and the client. Business outcomes are aligned with product goals, funding justified.

D&D helps navigate complexity.

The need for discovery and definition surfaces during highly complex engagements. It can be identified from pre-workshop meetings, or it can be an outcome from the workshop itself. There are three types of discovery engagements, each unique in the de-risking it seeks to accomplish.

Icon - 1

Prototype and validate the product idea.

Icon - 2

Roll out system design and change management.

Icon - 3

Assess the technical feasibility of legacy or greenfield products.

Types of discovery and definition

Discovery and definition creates value by demystifying opportunities that would otherwise be too large and ambiguous to take on. We break the problem down into essential components, prototype and validate assumptions, and prove out business outcomes before significant investment is made in development.

icon Prototype paper airplane

Product viability

Use product research and prototyping to validate assumptions and build internal consensus. It's key to unlock the definition of the problem space and the features required. The goal is to validate that the product will fit the need, to identify the best place to start development, or potentially to generate approval internally for the product to move forward.

icon Ecosystem or model

System design and change management

New products often force a significant shift in the way a company does business. Anticipating these changes, the process of change management should begin prior to development. The development of the solution and the business systems design must go hand-in-hand throughout the delivery process. When a product shifts the way a customer does business, it also has unforeseen upstream and downstream consequences. Service design activities, like a service blueprint, should be used regularly to map how these changes will impact the business.

icon Design

Technical feasibility

When taking over existing products, legacy systems, products rich with integrations and lateral dependencies, technical feasibility sprints are designed to move a project to a place where an engineering team can start writing code. Technical spikes aim to de-risk, de-couple, establish a predictable plan, data, and technical design, and deliver clarity for all involved.

Have an opportunity in mind? Let's workshop it.

Build alignment around an identified digital opportunity, establish a go-to-market roadmap, and prioritize features necessary to achieve business goals in less than two days.

White paper

Define product excellence with service design

How to deliver high-quality experiences for people where they are and when they need them

Download