Running a 5-Day Design Thinking Discovery Sprint for B2B SaaS

B2B SaaS teams rarely fail because they cannot build. They fail because they build the wrong thing well. A feature requested loudly by one enterprise customer ships after three months of engineering, and adoption stalls because the people who use the product every day were never asked.

A design thinking discovery sprint compresses the riskiest learning into five days. You end the week with a tested prototype and evidence for a go, pivot or stop decision, before committing a roadmap quarter. Here is the format we run with clients at Qodequay.

Before the sprint: set it up to succeed

• One sharp question. "Improve onboarding" is too broad. "Why do 40% of new admin users stall before inviting their team?" is a sprint question.
• A decider. Someone with authority over the roadmap must attend key sessions, or the outcome becomes a slide nobody acts on.
• A cross-functional core team of five to seven: product, design, engineering, customer success and sales.
• Five to six users booked for Day 5, recruited before the sprint starts. In B2B, include both economic buyers and daily users; they want different things.

Day 1 — Understand

Map the end-to-end journey for the problem area, from the trigger that brings a user in to the outcome they want. Pull in evidence: support tickets, churn reasons, product analytics, sales call notes. Invite two or three internal experts for short lightning talks. Close the day by writing "How might we" questions on the journey map and voting on the moment that matters most.

Day 2 — Empathise

Spend the morning talking to real users about their current workflow, not your feature ideas. Ask them to share their screen and walk through the task. Watch for workarounds: exported spreadsheets, sticky notes, WhatsApp groups. Workarounds are where the value hides.

In the afternoon, synthesise findings into an empathy map for each persona and agree on a crisp problem statement: [User] needs a way to [need] because [insight].

Day 3 — Ideate and decide

Generate widely, then converge hard. Each person sketches solutions individually (groups brainstorming out loud converge too early). Review sketches silently, heat-map the strongest parts, and let the decider pick one direction, or two to test head-to-head. End the day with a storyboard of the exact flow you will prototype, screen by screen.

Day 4 — Prototype

Build a realistic facade, not a product. A clickable Figma prototype with believable data is enough for most B2B flows. Use real field names, realistic record counts and your customer's industry language; enterprise users disengage the moment a demo feels generic. Assign one person to write the interview script and a checklist of what you need to learn.

Day 5 — Test and decide

Run five or six one-hour sessions. One facilitator, everyone else watching remotely and noting observations against the checklist. After roughly five sessions patterns become obvious. Close the week with the decider: what worked, what failed, and whether to build, iterate or stop.

B2B-specific adjustments

• Test permissions and roles. Admin, manager and end-user experiences differ. Prototype the handoffs between them.
• Include integration moments. Many B2B journeys break where your product meets the customer's ERP, CRM or identity provider.
• Separate buyer value from user value. A dashboard that delights a CXO but adds data entry for frontline staff will not survive renewal.
• Check compliance early. If the feature touches personal data, bring privacy requirements into Day 3, not after launch.

What you walk away with

• A validated (or invalidated) solution direction backed by user evidence
• A tested prototype engineering can estimate against
• Recorded user sessions to align stakeholders
• A shortlist of follow-up questions for the next sprint

Five days is a small investment compared with a quarter of engineering spent on the wrong feature.

Run your sprint with Qodequay

Qodequay's design thinking consulting team facilitates discovery sprints end to end, from framing the question and recruiting users to prototyping and synthesis, for product teams across SaaS, enterprise and public-sector programmes. Book a 30-minute consultation to scope yours.