Entry · Test before you commit
Design & Validate
Validate your direction in days, not months. Get real user feedback on real prototypes before you commit development resources.
The problem this solves
You've got a team, a roadmap, and pressure to ship. But somewhere in the back of your mind, there's a question: are we building the right thing?
I've seen teams spend two years building something, launch it, and watch users struggle to understand what it does. The product worked. The problem was nobody validated the concept with real users first.
Sprints compress months of uncertainty into days of clarity. You don't get a deck of recommendations. You get tested answers.
Three formats
1-Day Sprint
Focused question, fast answer
You have one specific thing to validate. A feature concept, a positioning hypothesis, a UI direction. We build a prototype in the morning, test with users in the afternoon.
Good for: decisions that are blocking progress, features that need quick validation, teams that can't spare a full week.
Most common
3-Day Sprint
Full methodology, validated direction
Day 1: Map the problem, identify the target. Day 2: Sketch solutions, build prototypes. Day 3: Test with 5 users, document findings.
Good for: new products, significant pivots, features that affect multiple teams, strategic decisions with real stakes.
2-Week Sprint
Complex, multi-stakeholder
For problems that span departments. Week 1: Research and mapping across teams. Week 2: Prototype and test multiple concepts. More iterations, more user sessions.
Good for: enterprise transformations, service redesigns, products with multiple user types.
What you leave with
Validated prototype
Not wireframes. A clickable prototype that looks and feels real. Detailed enough that users react to it honestly.
User test recordings
Video of 5 users interacting with your prototype. Their reactions, hesitations, and exact feedback. Evidence your team can watch.
Clear next steps
A prioritized list of what to build, what to skip, and what to explore further. Based on evidence, not opinions.
Team alignment
Everyone who participated saw the same thing. The debates about direction often stop because the answers become obvious.
Sprint outcomes
"Two years of building, then users couldn't understand the product. A one-week sprint gave us the clarity we should have had from day one."
"We saved €120-160K in development by validating the concept before writing code. The prototype tested well. We built exactly what users needed."
How it works
1. Before the sprint
30-minute call to understand the problem. I'll help you frame the right question to answer. You recruit 5 users for the test sessions (I can help with criteria).
2. During the sprint
Your team participates. Not spectators. Everyone sketches, everyone decides. I facilitate. The prototype gets built in real-time. Users test it while it's fresh.
3. After the sprint
You get the prototype files, test recordings, and a summary document within 48 hours. Follow-up call a week later to discuss implementation.
This works if
You have a specific question to answer, not just "make our product better"
Decision-makers can participate for the full sprint
You can recruit 5 users for testing (customers, prospects, or target users)
You're ready to act on what you learn, even if it's uncomfortable
This doesn't work if
You already know what to build and just need execution
The real decision-maker won't be in the room
Next step
Ready to sustain the momentum?
Many teams start with a validation sprint, then continue with fractional leadership to maintain strategic direction and build on what they learned.
Learn about Fractional CDO →