Product Discovery

Custom software development is expensive, and mistakes are costly. Our product discovery process lays a robust foundation for the subsequent design and development stages.

Discovery objectives

Effective product discovery will help refine project requirements in light of the project objectives and success criteria, determine the correct approach and appropriate technology choices and ensure complete alignment between our team and yours. By the end of the discovery process we will have:

Defined the product roadmap

Created a phased, timelined and costed technical backlog

Identified project risks and mitigations

The Product Discovery Process

Nearly a decade of working alongside clients to bring their projects to life has helped us create a best in class discovery process:

01.

Kickoff workshop – Getting to know you

During the kickoff workshop you’ll meet your team. While all projects are unique, we tend to assign a Project Manager, Development lead, and senior developer to each Product Discovery. The process is then overseen by our Head of Engineering. The kickoff workshop is focussed on context gathering. It’s critical that we understand your organisation, your market and your objectives for the project. We may conduct stakeholder interviews, competitor & marketing analysis, and user interviews. Ultimately we’ll do whatever is necessary to ensure we have the insight required to make informed technical recommendations.

02.

Business Requirement Specification – Defining your objectives, and success criteria

The next stage in our Product Discovery Process is the development of your Business Requirement Specification (BRS). The BRS captures everything that we understand about the project objectives and success criteria. We’ll often include a project roadmap at this stage, mapping out project phases and projected timelines. We’ll talk through the BRS with you, and unsure we’re aligned and have a complete and clear understanding of what needs to be accomplished ahead of creating the technical backlog.

03.

Technical backlog – Translating your objectives and success criteria into a technical specification

Once we’re happy that the BRS accurately reflects the project requirements, we’ll convert it in to a technical backlog, detailing development tasks and the effort and costs involved at a granular level. We’ll define the tech stack, 3rd party integrations, and any other dependencies. At this stage we’ll also identify any potential project risks (reliance of third party integrations, for example), the likelihood and impact of them materialising, and the plan to mitigate those risk where possible.

04.

Discovery review workshop – Ensuring alignment on the way forward

What Our Clients Say:

“Coreblue worked closely with us to understand what the business needed to achieve and how best to achieve our requirements through the technical solution. The eventual end point of the technical discovery and planning process was vastly different from the initial concept. We’ve developed and matured the idea together and as a result of Coreblue’s technical and commercial expertise, the specified product is far superior to the initial concept.”

Medidact

Lets talk about your next project

Thank you for your interest in Coreblue! To get started, please fill out the short form – We’ll be in touch soon to set up an informal chat.

If you prefer a more direct approach, give us a call on +(44) 0330 118 0338.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Learn more about Product Discovery

The-5-values
Culture

The 5 ‘Core’ Values that Define Coreblue

Give us a call

+(44) 0330 118 0338