About me

Clarity before
commitment

Skills

  • Interaction design

  • Visual design

  • Design systems

  • Product strategy

  • Product growth

  • Prototyping

  • Usability research

  • Accessibility

  • Collaboration

  • Sprints and workshops

  • USSD, SMS and IVR flows

Tools

  • Pencil and paper

  • Figma

  • Sketch

  • Adobe Photoshop

  • Adobe Illustrator

Technology

  • HTML

  • CSS

  • JavaScript

  • React

  • Next.js

  • NestJS

  • PostgreSQL

Lawrence Chege

Experience
9 yrs

I’m a product designer with nine years in UX and product design and sixteen years in digital technology. I started as a programmer in 2010 and still write production code in Next.js, NestJS and PostgreSQL.

I translate messy business requirements into interfaces that make sense. Working directly with software engineers and cross-functional teams, I turn complex challenges into solutions that feel obvious once they exist.

My expertise covers UX strategy, user research, interaction design, and prototyping.

Currently based in Nairobi, Kenya, I’m looking for opportunities where I can keep solving complex problems and building products that matter to the people who use them.

Product design

UX strategy

Fintech

Digital health

Mobile and web

Product design

UX strategy

Fintech

Digital health

Mobile and web

Research before the spec is fixed

I start by looking at what already exists: comparable products, competitors, anything solving a near-enough problem, and hold it against what stakeholders have asked for. That comparison usually changes the requirements, so it happens before the specification is written, not after.

Rough sketches, with engineers in the room

The first drawings are by hand and deliberately unfinished. I take them to front-end and back-end engineers to establish feasibility and technical direction while the work is still cheap to throw away. A constraint found at this stage costs a sketch. Found at build, it costs a sprint.

Low fidelity for agreement, high fidelity for build

Structure gets signed off in low fidelity, before any brand is applied. High fidelity comes after, and where the work needs a design system, that comes before the screens rather than being reverse-engineered out of them.

Handover is part of the design

Final files in Figma or PDF, with specs, a prototype and tokens. I stay close to engineering through implementation, because the design is not done when it is delivered. It is done when it is built.