Skip to main content

Critical Flow Sprint · One focused week

One critical flow. One focused week.

From US$2,500

We diagnose the problem, explore the strongest directions, test what holds up, and define a clearer flow your team can take forward.

For product problems that are too important to patch, but focused enough to tackle in a week.
Sketches, printed screens and the MovesMethod home screen from one flow, laid out on a desk

The problem

You already know which part of the product needs attention. What’s missing is focused time to understand why it isn’t working and what a better direction could look like.

The question this Sprint answers

We know where the problem is. What is the right fix, and does it hold up?

When a Sprint makes sense

You have one important flow that is creating friction, confusion or drop-off.

A Sprint works best when the problem is focused enough to explore and test within one week.

Typical examples:

  • Onboarding and first value

    Help new users understand what to do and reach value sooner.

  • Checkout or conversion

    Reduce friction around a key decision or transaction.

  • Core product flow

    Rethink an experience people use repeatedly.

  • Trial to paid

    Explore where conversion breaks down and what could improve it.

  • New feature adoption

    Help users understand, discover and start using an important feature.

  • Existing feature redesign

    Take a flow that has grown messy or unclear and define a stronger direction.

If the problem spans several unrelated journeys or requires a full product redesign, a Sprint is probably too small.

Five days, one flow

  • Day 1Diagnose

    A shared diagnosis of the problem

    Review the current flow, existing evidence, product constraints and what the team already knows.

    • Current-flow diagnosis
  • Day 2Explore

    One or two promising directions

    Explore different ways the flow could work, then narrow down the ideas worth taking further.

    • Design hypotheses and direction options
  • Day 3Prototype

    A direction that can be tested

    Turn the strongest idea into a focused prototype with enough detail to make the experience real.

    • Testable prototype
  • Day 4Validate

    What worked, what didn’t, and what changed

    Put the direction in front of users or relevant stakeholders, collect evidence, and identify the weak points.

    • Validation findings
  • Day 5Refine

    A tested direction and clear next steps

    Refine the flow based on what we learned and document the decisions, remaining questions and recommended next move.

    • Refined design direction and next-step guidance
MovesMethod onboarding in Figma: the flow before, above, and after the redesign, below

What comes out of a Sprint

A clearer direction you can make decisions from

The outcome is a focused flow concept, prototype and rationale showing how the experience could work, what has been tested, and what still needs to be resolved.

It gives your team enough clarity to decide what happens next, whether that means further design work, technical exploration, another round of testing, or moving towards implementation.

What is delivered

  • 01

    Current flow diagnosis

    What’s going wrong, where it happens, and the evidence behind it.

  • 02

    Design hypotheses

    The key ideas and assumptions worth exploring.

  • 03

    Proposed critical flow

    A clearer flow direction focused on the problem we agreed to solve.

  • 04

    Testable prototype

    Enough fidelity to put the direction in front of users or stakeholders.

  • 05

    Validation findings

    What worked, what failed, what changed, and what remains uncertain.

  • 06

    Refined design direction

    The strongest version of the flow after testing and feedback.

  • 07

    Final walkthrough and next-step guidance

    The decisions made, remaining questions, and what your team should explore or develop next.

You leave the week with a tested direction, clearer decisions, and a practical next step.

What’s explicitly excluded

A Sprint is designed to resolve one product problem and define a stronger direction. It does not include production-ready design or implementation support.

The Sprint does not include:

  • Multiple unrelated product flows
  • Full product or app redesign
  • Full design system creation
  • Production-ready UI specifications
  • Detailed developer handoff
  • Large-scale usability research
  • Extensive user recruitment
  • Unlimited revisions
  • Extended research outside the agreed scope
  • Ongoing developer support
  • Post-Sprint implementation or design QA

If the work needs to continue beyond the Sprint, we can decide what makes sense once the direction is clear.

“Bear’s contributions to our design sprints, customer journey workshops, and other projects have been invaluable.”

Jana Maia, PhDEx-Xero / Product Design Manager

Price and terms

From US$2,500

One focused week on one agreed critical flow.

Reserve the week

A 50% deposit confirms the Sprint week. The remaining balance is due at the end of the Sprint.

Starting from an Audit?

Continue within 14 days of your Focused Product Audit walkthrough and US$500 of the audit fee is credited towards the Sprint.

Start with an intro

Talk through the flow

Tell me which part of the product is stuck and what you’ve already tried. I’ll tell you whether a Sprint is the right next step.