From Uncertainty to Validated Prototype
5-day validation
Friday afternoon, Day 5 of the sprint. A construction-software user is testing a prototype that was built on Tuesday. Halfway through the second task they stop, look up, and say something the room hadn't heard inside the company once in the previous year of debate: which features actually mattered, and which ones the team had been about to over-invest in. The whole sprint is in that 30-second exchange. Everything before was setup. Everything after was execution.
Admicom is a Finnish construction-software company whose product family had grown into a forest. Multiple tools, each with its own interface, dashboard, and way of presenting information. Users lost time and context every switch. Marketing, product, and customer service each had a different story about what mattered most. The default path was to build on assumptions and hope. The cost of being wrong on a year of dashboard work was high enough to make that path scary.
The shape of the week
- 01
Pre-sprint user research interviews with actual software users
- 02
5-day design sprint co-led with Lauri Lännenmäki (UX engineer)
- 03
Cross-functional participation from marketing, product management, and customer service
- 04
Three morning sessions during the sprint for stakeholder input
- 05
Rapid prototyping and user testing by end of sprint
Product Designer, Tocoman/Admicom
“Expectations were high, and they were met. The Design Sprint went really well. We received feedback internally that it was exceptionally well facilitated.”
The moment that surfaced
User testing surfaced things the team hadn't expected. Features they assumed would be valued weren't. Things they had overlooked turned out to be essential. The view transition problem emerged as the critical usability issue.
What the week bought
A user-tested prototype and clear direction. The team adopted design sprint methodology across the organization. Design thinking became embedded in their corporate culture and strategy.
- Validated dashboard concept in 5 days
- Clear product direction based on user feedback, not assumptions
- Sprint methodology adopted company-wide
- Prototype ready for development handoff
Why the sprint earns its week
Five days. That's all it took to resolve a year of internal debate. The sprint format forces decisions. You can't debate forever when you have to test on Friday.
Full case study on Fraktio
Want this kind of result? Start with the version that matches your situation
These pages break the work down by the problem teams usually feel first, before they know what kind of engagement they actually need.
Design & Validate
3-Day AI Design Sprint
Validate a product direction in days, not months. Working prototype, real user feedback, signed 90-day roadmap. Three live days plus delivery.
Design & Validate
Design Sprint for B2B Teams
For teams dealing with long sales cycles, messy workflows, and too many stakeholders to rely on guesswork.
Design & Validate
Product Validation Consultant
Before you spend another quarter building, find out whether the direction makes sense to real users.