Home / Method
The small-improvements methodNotice, weigh, make it small
A product rarely gets easier through one big redesign. More often it’s through dozens of careful changes, each removing a little friction.

Notice
We go through the product as a newcomer and as a regular user. We note everything that makes a person stop, reread or guess. Sources: the product itself, reviews, support requests, conversations with the team.
Weigh
Each observation is rated on three axes: how much it helps, how many people it reaches and how much effort it needs. It’s not a formula for truth but a way to discuss priorities concretely.
Make it small
We split a big idea into steps, each of which can ship on its own. Changes reach people sooner and each step carries less risk.
Check
Before release, a change passes our quality criteria: states, copy, accessibility, screen sizes. After release we look at feedback and requests.
Record
Every change has a short note: what changed, why, how to roll it back. Six months later this saves hours.

Notice, weigh, make it small. Repeat next week.
MIKSORA
Why small doesn’t mean unimportant
An unclear basket button, an error with no explanation, a field that clears after a mistake — each seems trivial on its own. But people meet them every day, and they shape the feeling that “this product is hard”.
Small changes are also easier to verify. If something goes wrong after release, it’s clear what, and rolling back is simple.
What if a big change is needed?
How long does a review take?
Do you need access to the code?
How do you report?
Try it yourself
Our improvement sorter is a simplified version of how we weigh observations. Enter a few items from your product and it will split them into three buckets.
Open the sorter