Thread 05 · Kattha · cutch
Product Design
User research, UX strategy, interface design and design systems for digital products, designed alongside engineering so what we draw is what ships.
Swatch · product-designBasket 2×2
Who it’s for
New products finding their shape
You know the problem. You need flows and interfaces that make the solution feel inevitable to your users.
Products that have grown messy
Years of features have left inconsistent screens and confused users. You need a system, not another redesign.
Complex, data-heavy tools
Dashboards, back offices and workflows where clarity directly saves your users time and mistakes.
What you get
- 01Decisions grounded in how your users actually work
- 02Clickable prototypes tested before engineering starts
- 03A design system shared by designers and developers, in code
- 04Accessible interfaces that meet WCAG 2.2 AA by design
Deliverables
- User research & interviews
- UX flows & information architecture
- Interactive prototypes
- UI design
- Design systems & tokens
- Usability testing
Materials
Tools we reach for first, chosen per project and never by habit.
- Figma
- Design tokens
- Storybook
- Maze
- Rive
How we weave it
- Pass 01
Listen first
Interviews, support tickets and analytics tell us where users struggle. We design against evidence, not taste alone.
- Pass 02
Sketch the whole cloth
End-to-end flows before polished screens, so the product makes sense as a whole, not just page by page.
- Pass 03
Prototype and test
Realistic prototypes put in front of real users. What confuses them gets fixed while it is still cheap.
- Pass 04
Systematize
Tokens, components and patterns documented and built in code, so the design survives contact with the next feature.
Questions, answered
Do you only design, or also build?
Both. Designers and engineers work in the same team, which is why our designs are buildable and our builds match the designs. We are also happy to design for your in-house engineers.
What is a design system and do we need one?
A shared library of design decisions (colors, type, components and patterns) kept in sync between design files and code. If more than one person designs or builds your product, it pays for itself quickly.
How do you handle accessibility?
From the start: color contrast, focus states, keyboard flows, screen-reader semantics and motion preferences are part of the design, then verified in the build.
Can you redesign without disrupting our users?
Yes. We favor incremental redesigns behind feature flags, measured against usage data, over big-bang launches that surprise loyal users.