


CASSI
Improving usability across 12 years of healthcare journeys
Company
Unvoid
My Role
Lead Product Designer
Timeline
6 months
Responsabilities
Market Research
Product Strategy
Interaction Design
Visual Design
Design Systems
Prototyping
Overview
For people whose work and personal lives happen mostly online, staying organized often means switching constantly between task managers, calendars and scheduling tools.
Freelancers, remote workers, students and professionals offering online appointments may use one platform for tasks, another for meetings and several calendars connected to different accounts. Beyond the inconvenience, this fragmentation can make it harder to separate work, study and personal time.
Zenika.app was created to bring these parts of the routine into one place. The platform combined task management, calendar organization and meeting scheduling in a customizable experience across responsive web, mobile and desktop applications.
Over approximately six months, we built the product from scratch and released it to beta users. The team reached its initial participant target, but the project depended on securing additional investment. When the required funding was not obtained, Zenika.app was eventually discontinued.
Competitor analysis, interviews and the synthesis of user feedback were made, and the team worked closely to discuss the findings and translate them into product opportunities, feature ideas and visual directions that were relevant to the audience.
These insights were presented to stakeholders and used to define the MVP. Because the team needed to reach beta quickly, most ideas had to be reduced to their most essential version.
The goal was not to create the complete product at once, but to deliver enough value to test the concept with real users and collect initial indicators for potential investors.
Designing at startup speed
The process was fast and intentionally non-linear. Research, design and development happened in parallel, requiring frequent alignment and short decision cycles.
Before investing time in detailed interfaces, I created quick sketches to communicate the concept, validate the direction with stakeholders and estimate the effort required.
Once aligned, I translated these ideas into complete user flows, high-fidelity interfaces, interaction states and detailed documentation for development.
Implementation often started while other parts of the product were still being designed. Clear documentation became essential to reduce ambiguity, support technical decisions and maintain consistency across web, mobile and desktop experiences.
User testing also happened alongside development. Feedback from beta users informed interface adjustments and new iterations while the product continued evolving.
Designing the core experience
The calendar became the center of Zenika.app, bringing together meetings, personal tasks, imported events and user-defined time blocks. The challenge was to organize all this information without making the experience overwhelming, while maintaining consistency across web, mobile and desktop.
Building the product identity
The initial brand provided a visual foundation, but still needed to be translated into a digital product.
I defined the interface language and created a design system with light and dark modes, reusable components, variants and interaction patterns. This helped design and development move faster while maintaining consistency.
The outcome (From idea to beta)
Within approximately six months, we transformed the initial concept into a working product released to beta users across web, mobile, and desktop.
The team reached its beta-user target, allowing us to test the experience with real users and gather early signals for potential investors. My involvement ended shortly after the beta launch, so I was not part of the later funding discussions or the final decision. The Zenika.app faced the challenge of securing investment in a highly competitive market. The venture later decided to discontinue the product and focus its resources on other projects.
Key Learnings
My journey through this project provided several key insights.
1
The project strengthened my ability to prioritize, translate research into product decisions and balance user needs, business goals and technical constraints.
2
It also expanded my experience in design leadership, stakeholder communication and building a scalable product identity from an early-stage brand.
3
The project was developed at a time when generative tools were beginning to enter product workflows. In retrospect, AI could have accelerated operational tasks such as early interface exploration, research synthesis, microcopy, and documentation.
Next Project
A productivity platform from concept to beta
Take me back home.