Why “working fine” is not the same as “cannot be better”
When nothing is broken, improvement tends to wait. We think the most useful changes are often found in work that already does its job.
What does “working fine” actually tell you?
“Working fine” tells you that nothing is visibly failing. It doesn’t tell you whether the experience still fits the people using it, the work they do or the goals it was built for, and that gap is where many of the most useful improvements sit.
The phrase usually comes from the absence of signals: no complaints, no outages, no urgent requests. That is worth something. But silence is not the same as satisfaction. People adapt to tools that are slightly awkward. They learn the workaround, keep a spreadsheet on the side, ask a colleague instead of searching. After a while, the workaround feels like part of the job, and nobody thinks to mention it.
Why do good-enough experiences stop improving?
Most teams have more work than time, so attention goes to what is broken or new. That is a reasonable way to prioritize, and it has a side effect: anything that works stays as it is, while everything around it moves.
- The context changes. New products, new markets, new team members, new regulations. An interface designed for one set of conditions slowly drifts away from the next.
- Expectations move. People compare your experience with everything else they use, not only with your competitors.
- Knowledge leaves. The people who knew why something was designed a certain way move on. What remains is the habit, not the reasoning.
- Small costs stay invisible. An extra step, an unclear label, a report that needs explaining. None of them is worth a project on its own, so none of them gets fixed.
None of this means the original work was poor. It means the work was designed for a moment, and the moment has passed.
Where should you look first?
If nothing is failing, you need different signals. We usually start with a handful of questions.
Where do people work around the system?
Workarounds are the clearest evidence that something could be better. Look for exported data reworked elsewhere, notes kept outside the tool, steps people skip, or questions that always go to the same colleague.
What do people have to explain?
If a screen, a report or a process needs a walkthrough every time someone new arrives, the explanation is doing work the design could do.
What has changed since it was designed?
Compare the original brief with today. Different audiences, different volume, different priorities? Each difference is a question worth asking.
What happens where the work happens?
We prefer to go and see. Sitting with the people who use an experience, watching a task from start to finish, shows things no dashboard or interview will. This idea is known as Genchi Genbutsu, “go and see”, and it is one of the principles behind how we work.
How do you improve something that already works?
Carefully, and in steps. A working experience carries the trust and habits of the people who rely on it, so the aim is to improve without disrupting what they already depend on.
- Agree what “better” means. Faster to complete, easier to learn, fewer errors, clearer decisions. Pick what matters for this experience, not in general.
- Choose a few changes worth making. Not everything that could improve should. Weigh the value of each change against its cost and the disruption it brings.
- Make changes people can absorb. Small, well-explained improvements tend to be adopted more easily than one large redesign.
- Look again. Observe how the change is used, then decide the next step.
This is the idea behind Kaizen, continuous improvement: looking for incremental and substantial ways to improve, including in work that already appears satisfactory.
Good is never the end of the story. It is a useful place to start the next one.
Efabrika
How does this fit the way we work?
We work through a continuous loop: Define & Explore, Design & Develop, Optimize. Optimize is not a final stage reserved for problems. It is where we evaluate what is happening, make the evidence understandable and choose what is worth changing next, which leads back to Define & Explore with a clearer view than before.
Not every engagement includes ongoing optimization, and it shouldn’t be presumed. A focused evaluation of an existing experience can be the right first step. A planned programme of improvements suits larger products and services. Continuous design and development support suits work that keeps evolving. What matters is that the question “could this be better?” keeps being asked, whether it is our work or someone else’s.
If something you rely on is working fine and you’d like to know where it could work better, read more about Optimization & Continuity or start a conversation.