Kosmos core
Kosmos
We didn’t have a design problem, we had a scalability problem.

Role
Design lead
Timeline:
11 months
Tools used:
Mural / Figma /Illustrator /Photoshop
Context...
Background
Kosmos operated in the financial sector, helping banks and financial institutions create validation and onboarding flows for their customers. As the company grew, the demand for more customized and flexible implementations increased, requiring close collaboration between sales, design, and development teams for every new client.
Which was the
Problem...?
The process depended on:
-
Multiple meetings (sales, design, development)
-
Constant translation of requirements
-
Long cycles
-
Constant rework
-
Loss of business opportunities
What were the
Product goals?
-
Create a scalable platform that reduced dependency on manual processes
-
Enable financial institutions to configure and launch validation flows autonomously
-
Standardize components and workflows to minimize rework
-
Reduce implementation and onboarding times
-
Improve collaboration between sales, design, and development teams
-
Build a consistent and flexible design system to support product scalability
-
Increase operational efficiency and support business growth.
Process
Empower users to build, not depend.
Emphatize
Define
Ideate
Prototype
We researched client and team frustrations to understand the inefficiencies behind the implementation process.
We identified the core issue: rebuilding the same flows repeatedly instead of creating scalable systems.
We explored self-service solutions focused on flexibility, autonomy, and reusable components.
We validated flows and interactions through iterative feedback with users and teams.
User persona
The persona development process helped align product, design, and business decisions around real user pain points instead of assumptions. We focused on understanding how implementation managers and operational teams interacted with the onboarding process, where delays happened, and what prevented them from working autonomously.
This work allowed us to define key motivations, goals, frustrations, and expectations that later informed the platform structure, user flows, feature prioritization, and overall self-service experience.
How might we...
-
How might we enable financial institutions to configure validation flows without depending on technical teams?
-
How might we reduce repetitive implementation work and create a scalable process?
-
How might we simplify complex workflows into an intuitive self-service experience?
-
How might we give users more visibility and control throughout the implementation process?
-
How might we reduce onboarding and launch times while maintaining flexibility and customization?

Ideation Stage
OVERVIEW
-
Ideation
-
Storyboarding
-
User Flow
During the ideation stage, we explored different ways to transform a repetitive, service-based process into a scalable self-service platform. Through workshops, collaborative sessions, flow explorations, and rapid wireframing, we focused on simplifying complex workflows into modular and reusable experiences.
The main goal was to create a system that empowered users to independently configure validation flows, customize experiences, and launch solutions without relying heavily on internal teams.
This phase helped define the platform structure, reusable components, interaction patterns, and the foundations of the design system.



Final design
Empower users to build, not depend.
The final design delivered a scalable and intuitive self-service platform that enabled financial institutions to independently create, configure, and launch validation flows. Built through a modular design system, the experience focused on simplicity, flexibility, and efficiency, reducing operational friction while maintaining consistency across the product.


Updated
Outcome: A faster, clearer and autonomous way to build and launch validation flows.
The updated user flow simplified a previously fragmented and manual process into a streamlined self-service experience. By reducing dependencies between teams and organizing the journey into clear, intuitive steps, users could independently configure, validate, and launch flows faster and with greater confidence.
