Overview

Kito helps parents in Kenya understand their child's symptoms and what to do next.

When I joined the project, the team already had a working MVP they were testing with users. But the experience was messy. Inconsistent components, confusing interaction patterns, and accessibility issues made an already sensitive journey harder to navigate.

I worked with the team to rethink the assessment experience and establish the product's first design system, collaborating closely with frontend developers to bring consistency to the interface.

Role & Context
Solo Product Designer · 8 months · 2022

Impact

75%
Less development time
4 months
Full product rework shipped
1st Design System
Tokens, components and guidance

Solution

Establish consistent controls

I developed the system alongside the MVP, using recurring needs in the product to shape its components.

Buttons were an early priority because testing had exposed accessibility issues across them. I consolidated their treatments into a shared family with defined hierarchy, sizing, and interaction states. The library documented default, hover, focus, and disabled behavior, alongside full-width and icon-only variations.

This gave each variation a defined purpose and provided a common reference for addressing the issues identified during testing.

Give feedback a clear meaning

In the original assessment, answering “Yes” to certain questions turned the selected radio button red. Parents then had to tap Continue to view the emergency guidance. User testing showed that the red selection made parents feel they had answered incorrectly, even though it was intended to communicate urgency.

I separated those messages. Selection used a consistent interaction state, while distinct guidance communicated urgency and the next action. This made the distinction between confirming an answer and responding to its meaning explicit in the design.

Build reusable foundations

I established named colors, typography styles, spacing values, borders, and layout guidance, then applied those foundations to reusable components.

The system covered behavior as well as appearance. Inputs included focus, filled, error, and disabled states. Selection controls defined sizing and icon placement. Accordions specified spacing, optional icons, and expanded content.

Developing these rules alongside real screens kept the system connected to the assessment experience it needed to support.

Beyond the Design

I worked with frontend developers to define how components should behave when implemented.

The documentation translated visual decisions into explicit rules: which controls filled their container, how elements were spaced, when icons were optional, and how states changed. Shared token names connected those specifications to the foundations of the system.

Both the product and library files also used a simple workflow: Finishing touches → Ready for Development → Implemented. This made the status of the work visible and gave design and development a shared reference as the MVP progressed.

Reflections

Building Kito’s first design system alongside the MVP taught me to connect reusable rules to specific user problems.

Working through states and layout behavior with frontend developers also made those decisions more explicit. The system became a place to document the reasoning needed to carry an interaction from a design into the product.

The delivered work established that foundation. Follow-up testing and an accessibility audit would be needed to demonstrate how effectively the redesigned controls resolved the original findings.