A research sprint tests one meaningful product change with the people it affects: in moderated sessions, I watch how they use it and ask why. In 2–3 weeks you learn what they adopt, question, trust or struggle with – and what your team should improve or test next. I plan the study, run the sessions and present the findings to your team.
Sessions
6–9, moderated
Timeline
2–3 weeks
Investment
From €2,700

Test before you commit
What is a research sprint?
A research sprint, sometimes called a user research sprint, is a short, fixed-scope study around one product change: a new feature, a redesigned flow or a concept you are about to build. People from your target group work with it in moderated sessions while I observe and ask follow-up questions. Sessions are a small sample, so the results show where and why people struggle, not how many. I mark this boundary in every report.
What people adopt
Which parts they understand and use without help: observed, not assumed.
What they question
Where wording, logic or trust makes them hesitate, and why.
What to fix first
Each issue rated by how much it blocks the user’s goal and yours.
Is a research sprint right for you?
A good fit if
A product change is coming and you want to see how people respond before launch.
You redesigned something and want to check it does what it should.
Conversion drops or users abandon a key flow and analytics can’t tell you why.
You’re launching a new feature or a complex user flow and need to know people can complete it.
Your team disagrees about what is “intuitive”.
Not the right fit if
You don’t know yet what to build. Start with discovery research.
You need to know how many users do something. Use analytics or an A/B test.
The decision is already made and you only need approval.
You need research continuously, not for one question. That’s the embedded partnership.
Need a quick expert opinion instead? A UX audit reviews your flow without recruiting participants and delivers within days.
How it compares
How does a research sprint compare?
Research sprint, usability test, UX audit and design sprint overlap in name. Here is what each one is and when it is the better choice.
Research sprint
A fixed-scope study around one product change: 6 to 9 moderated sessions, analysis and a live readout in 2–3 weeks. Choose it when a decision depends on how people respond.
Usability test
The method most sprints use: people work through realistic tasks while I observe. A sprint wraps it in scoping, recruitment, prioritized findings and a readout.
UX audit
An expert review without participants, delivered within days from €690. It points to likely problems; a sprint shows what people actually do and why.
Design sprint
A five-day workshop in which a team designs, prototypes and tests a solution with a handful of users. A research sprint doesn’t design the solution: it tests the one you have, with more sessions and deeper analysis.
What a sprint can cover
What can a sprint test?
A sprint works for any change people can click through: on a website, in an app or in a prototype. Sessions run remotely with people from your target group, in German, English or Polish.
Websites and web apps
A new or redesigned flow such as sign-up, onboarding, search, product pages, checkout, payment or settings.
Mobile apps
A new feature or reworked screen, tested on real devices in the context people actually use them.
Clickable prototypes
Figma prototypes from mid-fidelity onwards: a concept you are about to build, tested while changing direction is still cheap.
Comparative testing
Two versions of the same change, or your flow next to a competitor’s, to see which decision logic works better.
Accessibility
Whether people with different needs can find, understand and complete the key tasks in the new flow.
SaaS, B2B and decision tools
Specialist tools, calculators and dashboards where people must understand a result before they act on it, like the scenario calculator in the case study below.
How a research sprint works, week by week
WEEK 1
Agree on one question
In a kickoff call we pin down the decision behind the sprint: which change you are about to ship, what you need to know before you do and what result would change your plans.
WEEK 1
Plan and recruit
I write the test plan and tasks, we agree on participant criteria and recruitment starts: from your customers, a research panel or both.
WEEK 2
Run 6 to 9 sessions
I moderate every session live over video, in German, English or Polish. Participants work through realistic tasks with your change and think aloud while I follow up on what they do and say.
WEEK 2–3
Analyze and prioritize
After the last session I group the observations into patterns across participants and rate each issue by how much it blocks the user’s goal and yours.
WEEK 2–3
Readout with your team
The sprint ends with a live readout: we walk through the findings and the evidence together and agree what to fix now, what to test further and what to leave.
What you’ll receive
Everything from the sprint is yours to keep: the plan, the session material and a report that rates every finding by its impact on the user’s goal and on yours, with a clear line between what was observed and what is interpretation.
A sprint plan
Research question, tasks and participant criteria, agreed before recruitment starts.
Recordings and notes
Recordings and notes from every session, where participants have agreed to recording.
Prioritized findings
Each finding with what happened, where, how many participants it affected and why it likely matters.
Concrete recommendations
What to fix now, what to test further and what can wait, in an order your team can plan with.
A live readout
A session with your team to go through the evidence, answer questions and agree next steps.
Ready to see how people respond to your change?
A research sprint in practice
Example: an agritech team had built a complex scenario calculator. Seven remote usability sessions in Polish turned the observations into clear requirements for the next version. Each case study below shows the problem, the research approach and the product decision it led to.
Research sprint cost and timeline
Start with a Focused UX audit: book a Research Sprint within 30 days and the €690 is credited toward it. Prices are net; VAT is added based on your country and tax status.
Independent UX consultant
Why work with me?
I’m a UX researcher and psychologist (M.Sc.) working independently with product teams. You work with me directly, from the first question to the final readout.
Psychology meets product work
I know how people perceive, decide and hesitate. I translate that into findings your team can act on.
25+ usability studies
Websites, apps, prototypes and complex B2B tools, including the Urlaubsguru product detail page and an agritech scenario calculator.
German, English and Polish
I moderate sessions in all three languages, so you can test with your real target groups.
FAQ
What you might want to know.
Have a product change coming up?
Tell me which change, flow or prototype you want to test. In a free 20-minute call we clarify the question, the participants and what it takes to get evidence you can act on.

Diana Szczepanik
UX Researcher & CRO Consultant, Psychologist (M.Sc.)









