John Lewis

Product Design Leadership

Research-to-strategy executive framework

Research-to-strategy executive framework

Research and Strategy

Turning Research Into Product Strategy

A decision-quality story about using customer and behavioral evidence to separate foundational product problems from later growth bets and change roadmap sequence.

Leadership Question

How do you use research to decide whether the roadmap should fix comprehension, improve usability, or pursue a larger engagement bet?

ResearchDecision QualityRoadmap Strategy

Case at a glance

Leadership scope and evidence

Pair evidence with a clear product implication and recommended sequence so research changes the decision, not only the discussion.

Leadership role
Design leader connecting customer evidence to product choices, sequencing, and executive decisions
Timeframe
Research-led product strategy work
Team
13 designers, 2 researchers, and product, analytics, and executive partners
Scope
Decision signals across usability, understanding, engagement, and perceived generosity

Strategy partners

15

Supported 13 designers and 2 researchers during research-led product strategy work.

Product confidence

Before + after

Used usability, understanding, engagement, and perceived generosity as distinct decision signals.

Decision output

Roadmap

Translated evidence into product implications, sequence, and an explicit recommendation.

Executive summary

The question was whether teams faced foundational usability and comprehension problems or were ready for larger engagement bets. I rebuilt research operations around usability, understanding, engagement, and perceived generosity.

The frame covered 13 designers and 2 researchers. The outcome was a stronger product decision; commercial performance was evaluated separately.

Challenge

The ambiguity was which problem deserved the roadmap.

Teams needed to know whether findings pointed to a foundational fix, a later bet, or another evidence need.

Evaluative, strategic, and behavioral evidence each revealed part of the product picture. Treating every signal as equivalent could lead to the wrong commitment.

I organized outputs around the customer signal, product implication, option tradeoff, and recommended sequence.

Leadership role

What John led

The work connected evidence to a product commitment.

  • Supported 13 designers and 2 researchers during research-led product strategy work.
  • Introduced distinct decision signals for usability, understanding, engagement, and perceived generosity.
  • Connected evidence to product implications, roadmap sequence, and executive recommendations.
  • Kept customer observations separate from unproven business causation.

Approach

Decision approach

Define the uncertainty, compare the right signals, and show how evidence changes the choice.

Frame

Name the product uncertainty

Clarified whether to fix usability and understanding or pursue a larger engagement opportunity.

Distinguish

Give each signal a job

Examined usability, understanding, engagement, and perception as separate questions.

Decide

Change the roadmap sequence

Recommended value visibility and comprehension before deeper gamification.

Decision

Why it mattered

Outcome

Prioritize foundational reward clarity before deeper gamification

New mechanics would add complexity if customers could not see value, understand progress, or recognize the next step.

The roadmap sequence put value visibility, comprehension, and progression first.

Use distinct product-confidence signals

A product can be usable without being understood, engaging, or perceived as valuable.

Teams could discuss which condition the evidence indicated instead of treating research as one verdict.

Present implications instead of a findings recap

Product and executive partners needed to understand what should change and what should wait.

Research reviews ended with an explicit recommendation, tradeoff, and next decision.

Artifacts

Artifacts built for product decisions

Representative and redacted models showing how evidence was organized around choices rather than method summaries.

Research-to-strategy framework

Research-to-strategy framework

Multi-source insight system

Multi-source insight system

Hypothesis mindset model

Hypothesis mindset model

Outcomes

Research changed what happened next

The contribution was a stronger basis for product choice and sequence, not a claim that research caused a business result.

Outcome

Put foundational value visibility and comprehension before deeper gamification in the roadmap sequence.

Outcome

Gave 13 designers and 2 researchers a shared way to discuss usability, understanding, engagement, and perceived generosity.

Outcome

Made the recommendation, tradeoff, and next decision visible in product and executive reviews.

Director Signal

Leadership signal

Pair evidence with a product implication and recommended sequence so research changes what the team does next.

What We Learned

The leadership lessons that carried forward

The strongest case studies leave behind more than shipped work. They sharpen the operating principles behind future decisions.

01

Start with the choice

Research has more influence when the team agrees on the uncertainty and decision before selecting methods.

02

Keep signals distinct

Usability, understanding, engagement, and perception answer different questions about product confidence.

03

What I would do differently

I would establish the decision questions and signal definitions earlier so synthesis could move faster from evidence to product sequence.

Leadership Conversations

Building product ecosystems, stronger teams, and sharper executive alignment.

Open to Product Design Director opportunities across growth, platform, loyalty, and product ecosystem leadership.

Start a conversation

Based in the U.S. and open to product design leadership opportunities.