Product design from Nairobi

UI/UX Design for
digital products

We turn complex workflows into clear user journeys, wireframes, prototypes, and design systems for web and mobile products. The work helps teams make decisions before implementation becomes expensive.

Design for clear decisions

Good UX makes the next step easier to understand. We use familiar interaction patterns, clear hierarchy, useful feedback, and testing with the people who will use the product.

01

Hick's Law

We group and prioritise choices so people can decide without scanning an unnecessarily crowded screen.

02

Fitts's Law

We place important actions where they are easy to reach and use, especially on smaller screens and in field conditions.

03

Gestalt Laws

We use spacing, grouping, hierarchy, and consistent language so users can see what belongs together and what needs attention.

A practical design process

We move from understanding the workflow to mapping user journeys, testing prototypes, and preparing design material that an engineering team can use.

ยป

Understand the work

We speak with the people involved, review existing screens and processes, and identify the decisions the product must support.

ยป

Map the journeys

We define users, steps, content, states, permissions, and edge cases before settling on visual treatment.

ยป

Prototype and test

We use wireframes and clickable Figma prototypes to review the flow with stakeholders and representative users.

ยป

Prepare the handover

We provide agreed design files, components, states, and notes that the engineering team can estimate and implement.

// A design handover
const DesignSpec = {
prototyping: ["Figma", "Framer"],
tokens: ["JSON", "Sass"],
accessibility: "Considered early",
review: () => "Representative journeys"
}

What You Receive

We provide the design material needed to review the product, make decisions, and support implementation.

๐ŸŽจ

Core Design System

Complete library of reusable components, typography, and color tokens.

๐Ÿ“ฑ

Interactive Prototype

A clickable, high-fidelity Figma prototype for user testing and stakeholder buy-in.

๐Ÿ›ค๏ธ

User Journey Flow

Detailed mapping of all possible user paths and edge-case handling.

๐Ÿ“„

Developer Documentation

Comprehensive hand-off specs including CSS variables and asset exports.

Scalability

Design systems for consistent products

We create reusable components, patterns, content guidance, and design tokens where they will help a product remain consistent across screens, teams, and future releases.

  • โœ“
    Atomic Design Methodology
  • โœ“
    Figma Variables & Tokens
  • โœ“
    Dark Mode Architecture
  • โœ“
    Multi-Brand theming
Colors
Aa
Typography
Components
8px
Spacing

Designing for different needs.

We consider keyboard use, readable contrast, screen readers, touch targets, language, device conditions, and the accessibility requirements that apply to the product. A formal WCAG review can be included when needed.

Screen Readers Haptic Feedback Dynamic Type
Aa
Accessibility-first review

UX FAQ

A discovery research sprint typically spans 2 to 3 weeks. This includes stakeholder interviews, user persona mapping, and competitive analysis. For complex enterprise systems, we might extend this to include on-field observation.
Yes. We deliver clickable Figma Prototypes that simulate the final product's UX. This allows you to test user flows and get executive buy-in before writing production code.
We use Success Metrics (KPIs) such as Task Completion Rate, Time-on-Task, and Error Rate. Post-launch, we track conversion lift and support ticket reduction.
How we work

Give delivery a clear, testable starting point.

We turn research, flows, and prototypes into implementable design systems that engineering teams can estimate and ship with fewer rewrites.

Start with

The decisions users need to make and the information they need at each point.

Plan for

Research, accessibility, content, edge cases, and the engineering effort behind the interface.

Review with

Product owners, operational users, and the team that will build the product.

Handover includes

Flows, prototypes, design rules, and implementation-ready detail.

A useful first conversation

Bring the workflow, decision, or technical constraint that is creating the most friction. We can then decide whether discovery, a focused delivery phase, or a different next step makes sense.

Discuss a project with Statum

Make the product
easier to use.

Align research, interaction design, and implementation before your product roadmap gets more expensive.

Book Design Workshop