61.2970°N 23.5025°E
© Sami Surakka 2026
Problem
The previous app was not designed for mobile, making onboarding and KYC flows clunky and error-prone.
Solution
Design sprints with user-tested prototypes that became the foundation for the launched app.
I facilitated a short, high-intensity design sprint for a fintech business developing a mobile app for investment management and know-your-customer processes. Working closely with stakeholders, I mapped out the core user journeys, led ideation sessions, and conducted user testing with a high-fidelity prototype for validation. The sprint helped clarify the product direction, align the team, and set a solid foundation for development. The app launched in early 2026.
Loading…
In collaboration with Heikki Salo.
The client wanted to overhaul the mobile experience of their investment service. The previous app was not really designed for mobile at all, which made key tasks like onboarding, managing investments, and completing KYC flows feel clunky and error‑prone. They commissioned a design sprint to create momentum, clarify direction, and unblock the broader overhaul effort.
I facilitated a short but intense design sprint focused on the full mobile experience, from core investment journeys to the supporting flows. Together with the team, I mapped out key journeys, led ideation sessions, helped shape a high‑fidelity prototype that covered the main screens and interactions, and led the testing process with users. Because of the regulatory importance and complexity of KYC, we later ran a separate sprint focused specifically on the KYC flow, again prototyping and testing with users to make sure the experience was both smooth and compliant.
The sprints gave the team a clear, shared picture of what the new mobile app could be, and a tested prototype to build from. The app has since launched, although I don’t have visibility into current metrics around conversion or compliance. The client was very happy with the sprint outcomes and used the prototype and user‑test insights as a foundation for the implementation.
I acted as the sprint facilitator and was responsible for planning and running the week, leading user testing, and synthesizing the results. My colleague, Heikki Salo, produced the high‑fidelity UI design; we collaborated closely to make sure the flows and visuals worked together.
One thing I’d adjust next time would be either resourcing, or schedule. A lot of the UI design weight sat on Heikki’s shoulders while I focused on facilitation and research, and splitting that work under tight timelines was challenging. With a bit more design capacity or more room schedule-wise, we could have shared some of the detailed UI load more evenly without compromising the depth of the sprint.