PRODUCT DISCOVERY

Playbook

OVERVIEW

The High Cost of Poor Requirements

As Design Director at an IT consultancy, I led a task force to overhaul our product discovery process. At the time, discovery was largely driven by engineering and centered on feasibility over opportunity. Clients invested weeks in the process, yet often came away with a technical architecture, unresolved questions, and little confidence in what should be built. We set out to create a sharper discovery model—one that surfaced business and user value early, explored solution paths before commitment, and gave teams realistic effort estimates before moving into design.

OVERVIEW

The High Cost of Poor Requirements

MY APPROACH

Designing the Discovery Process

I approached this challenge as a process-design problem. By combining stakeholder research, best-practice analysis, co-design, pilot testing, and implementation support, I worked to rebuild product discovery into a clearer, more collaborative, and more scalable way of working.

MY APPROACH

Designing the Discovery Process

ACTIVITY BREAKDOWN

BEST PRACTICE RESEARCH

35%

EMPATHY LISTENING SESSIONS

25%

PILOT TESTING

20%

DOCUMENTATION AND SUPPORT

15%

DESIGN SESSIONS

UNDERSTAND

Empathy Listening Sessions with Stakeholders

I met with stakeholders across product, design, and engineering to understand their goals and challenges during discovery. These conversations revealed siloed thinking, misalignment between outputs and outcomes, and gaps in validating assumptions with real users.

DEFINE

Researched Product Discovery Best Practices

I reviewed best practices in product discovery and conceptual design to draft an initial process, outlining activities, deliverables, and effort estimates with tradeoffs. This helped the organization align on objectives and move toward a tailored discovery approach

EXPLORE

Facilitated Co-Design Sessions

I led whiteboard sessions with product, design, and engineering to co-create a discovery process, mapping phases and tasks from initial idea to fully scoped roadmap and project plan.

VALIDATE

Piloted the New Discovery Process

I selected a few projects as pilots for the new discovery process, closely observing outcomes and identifying what worked and what didn’t. These learnings refined the approach and helped build broader team confidence and adoption.

BUILD

Documented Process and Built Estimation Tools

I created a comprehensive process map and supporting materials to train project managers, and built an Excel-based estimation tool to model discovery effort, sequencing, and timelines based on key inputs like research scope and design complexity.

UNDERSTAND

Empathy Listening Sessions with Stakeholders

DEFINE

Researched Product Discovery Best Practices

EXPLORE

Facilitated Co-Design Sessions

I led whiteboard sessions with product, design, and engineering to co-create a discovery process, mapping phases and tasks from initial idea to fully scoped roadmap and project plan.

VALIDATE

Piloted the New Discovery Process

BUILD

Documented Process and Built Estimation Tools

UNDERSTAND

Empathy Listening Sessions with Stakeholders

DEFINE

Researched Product Discovery Best Practices

EXPLORE

Facilitated Co-Design Sessions

I led whiteboard sessions with product, design, and engineering to co-create a discovery process, mapping phases and tasks from initial idea to fully scoped roadmap and project plan.

VALIDATE

Piloted the New Discovery Process

BUILD

Documented Process and Built Estimation Tools

UNDERSTAND

Empathy Listening Sessions with Stakeholders

DEFINE

Researched Product Discovery Best Practices

EXPLORE

Facilitated Co-Design Sessions

I led whiteboard sessions with product, design, and engineering to co-create a discovery process, mapping phases and tasks from initial idea to fully scoped roadmap and project plan.

VALIDATE

Piloted the New Discovery Process

BUILD

Documented Process and Built Estimation Tools

Problems to Solve

This work surfaced four issues the new discovery process needed to address

This work surfaced four issues the new discovery process
needed to address

This work surfaced four issues the new discovery process needed to address

01 / OWNERSHIP

Passing the Buck

Ownership and accountability for success were unclear across product, design, and engineering.

01 / OWNERSHIP

Passing the Buck

Ownership and accountability for success were unclear across product, design, and engineering.

O2 / PROCESS

One Size Fits None

The discovery process was too rigid to adapt to different project needs.

O2 / PROCESS

One Size Fits None

The discovery process was too rigid to adapt to different project needs.

03 / DELIVERABLES

Nothing to Show for It

Discovery lacked clear deliverables, making it hard to justify the time and effort invested.

03 / DELIVERABLES

Nothing to Show for It

Discovery lacked clear deliverables, making it hard to justify the time and effort invested.

04 / ESTIMATION

Guesswork Estimates

Teams lacked the information needed to produce credible effort estimates.

04 / ESTIMATION

Guesswork Estimates

Teams lacked the information needed to produce credible effort estimates.

Playbook Overview

Product discovery is often the most ambiguous phase of delivery, where possibility collides with business constraints. To bring more clarity and momentum to that uncertainty, I developed a structured framework for turning early ideas into actionable plans. The model breaks discovery into three phases—establishing goals, defining solutions, and planning delivery—to help teams align priorities and move from vague concepts to a credible delivery roadmap.

PRODUCT DISCOVERY PROCESS

Establish Goals and Objectives

Understand the landscape and align priorities

Establish Goals and Objectives

Understand the landscape and align priorities

Define Business Goals

Understand Target Users

Assess Existing Product*

Research Competitors

Define the Solution

Explore solutions and shape the product

Define the Solution

Explore solutions and shape the product

Explore Solutions

Define Workflows

Establish Visual Direction

Build Roadmap

Plan for Delivery

Define scope and align stakeholders

Plan for Delivery

Define scope and align stakeholders

Document Requirements

Estimate Effort

Sequence Sprints

Present Project Plan

PLANNING FRAMEWORK

Right-Sizing the Discovery Effort

The playbook helped teams choose the right methods, estimate the work realistically, and clarify ownership before delivery began. By scaling research and design activities to fit each project’s constraints, using historical data to forecast timelines and costs, and defining RACI-based responsibilities across product, design, and engineering, the team could create a practical discovery plan that was structured without being overly rigid.

HOW IT WORKS

Method

Effort

Owner

Select Method(s)

The team can choose one or more research methods based on the insight needed and effort required, tailoring the approach to project constraints.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Method

Effort

Owner

Select Method(s)

The team can choose one or more research methods based on the insight needed and effort required, tailoring the approach to project constraints.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Method

Effort

Owner

Select Method(s)

The team can choose one or more research methods based on the insight needed and effort required, tailoring the approach to project constraints.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Select Method(s)

The team can choose one or more research methods based on the insight needed and effort required, tailoring the approach to project constraints.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

Estimate Effort

The team estimates timelines and costs using historical data, key variables, and expected deliverables for each selected task.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

DELIVERABLES

Key Finding Report

EFFORT ESTIMATE

4 to 6 hours per participant (includes recruiting and data analysis)

Conduct one-on-one conversations to uncover user needs, behaviors, and motivations

Stakeholder Interviews

GOOD

Assign Owner

The team assigns ownership for each task and identifies who should be consulted, informed, or involved—keeping leads aligned without requiring everyone in every task.

Stakeholder Interviews

GOOD

Stakeholder Interviews

GOOD

DELIVERABLES

Key Finding Report

EFFORT ESTIMATE

4 to 6 hours per participant (includes recruiting and data analysis)

Conduct one-on-one conversations to uncover user needs, behaviors, and motivations

PRODUCT

DESIGN

Stakeholder Interviews

GOOD

Key Results

The Product Discovery Playbook brought product, design, and engineering together early to define the customer problem, explore solutions, identify dependencies, and plan delivery. On every project that followed the process, actual design effort came in at or below its original estimate. Some teams used that capacity to deliver additional work within the same budget. The work taught me that discovery needs to answer more than whether a solution is technically feasible. Teams also need a shared understanding of the user need, business opportunity, and work ahead. I built the playbook with clear phases, responsibilities, deliverables, and estimation tools, while leaving teams room to adapt it to each project’s complexity and risk. That balance made discovery useful (and adaptable) for decision-making and delivery planning.