Osys
Overview
Osys is a digital B2B platform built to modernize optical store management by replacing fragmented, manual processes with structured, efficient, and scalable workflows. The project was born out of my firsthand industry experience and the continuous identification of recurring operational bottlenecks, such as data loss, systematic rework, and critical communication gaps.
Project
B2B / SaaS
Year
2025/2026
Role
Product Designer
My Role
As a personal product project, I led the process end to end, from research and problem definition to product strategy, UX flows, interface design, MVP definition, validation, and iteration.
My responsibilities included:
User research and field observation
Journey mapping
Problem framing
MVP prioritization
UX/UI design
Product flow definition
Client meetings and feedback collection
Iteration based on real usage insights
Process
The first step was to understand how the work actually happened in the store, not how the process was supposed to happen in theory.
I observed the routine of professionals, mapped the main tasks, and identified where information was created, transferred, lost, or corrected. This helped me understand that the biggest opportunity was to reduce fragmentation and create a clearer operational flow.
From there, I organized the process around three key questions:
What information needs to be captured first to avoid errors later?
Which tasks are most critical in the daily workflow?
What should be included in the MVP to create value without making the product too complex?
This helped define the first version of the product with a practical scope: centralizing customer data, orders, prescriptions, and service tracking in a single digital flow.
Decisions
MVP
Instead of trying to build a complete management platform from the beginning, I focused the MVP on the most critical parts of the workflow: customer registration, prescription/order information, and order tracking.
This decision helped reduce scope and allowed the product to solve the most painful operational problems first.
Design
Because users were dealing with a fast-paced operational environment, the interface needed to be simple and direct. I prioritized clear labels, organized sections, and predictable flows to reduce cognitive load.
The goal was to make the product easy to adopt, especially for users transitioning from paper to a digital system.
Learning using the MVP
The first version was not designed to be final.
It was created to validate the core workflow, collect feedback, and understand what should evolve in version 2.
This allowed the product to grow based on real needs.
Solutions
The MVP introduced a digital workflow for managing optical store operations, replacing fragmented paper records with a structured system.
The solution focused on:
Customer registration
Prescription and order records
Order/service tracking
Centralized operational information
Clearer workflows for daily tasks
A foundation for future features
By organizing the main information in one place, the system helped reduce manual errors and gave users more control over the operation..
The project helped transform a manual and error-prone workflow into a more organized digital process.
Key outcomes include:
Reduced dependency on paper records
Better organization of customer, prescription, and order information
Lower risk of lost or inconsistent data
Reduced rework caused by manual errors
Improved visibility over the service workflow
A scalable foundation for future product evolution
