That is a provocative title for a field I have spent years learning. I do not mean that understanding people is simple, or that any product can be fixed by following a checklist. I mean that we often make UX sound more mysterious than the work needs to be.
We already know a lot about what helps. Learn what people are trying to do. Understand their context. Involve them before the solution is fixed. Test the thing you are building. Measure whether it works. Change what does not.
That is not a new framework I invented for this article. ISO 9241-210 describes the principles and activities of human-centred design. ISO 9241-11 gives us a way to think about usability through effectiveness, efficiency, and satisfaction in a specified context of use. The basics have been around for a while.
Knowing the method is not the difficult part
Take an application form. Before redesigning it, talk to people who need to use it. Find out what they are trying to achieve, what they need to prepare, and where they get stuck. Look at the path through the live service. Choose a clear measure of success, such as complete applications, and watch for errors or rework. Test a change with people, release it, and check what happened.
None of that requires a 60-slide strategy deck. It requires a team willing to ask a question before drawing a screen and to look at the result after shipping.
If more teams did those things consistently, I think they would already do most of the valuable UX work well. I sometimes call it 80% of the job. That is my shorthand, not a measured industry figure. The remaining work can be difficult: conflicting needs, accessibility, organisational constraints, long journeys across channels, and decisions where there is no clean answer. The fundamentals do not make those problems disappear. They give us a better way to approach them.
The metrics are there to help us learn
“Make it usable” is hard to act on. “Can people complete the application correctly?” is something we can observe. “Do they have to ask for help?” gives us another clue. “What share of started applications become complete submissions?” connects the experience to an outcome the product team cares about.
We do not need to measure everything. We need to know what success looks like, how people are doing today, and whether a change made things better. A metric without a conversation with users can hide the reason behind a problem. A good interview without a way to see its scale can leave us unsure where to invest. The two belong together.
That is the argument behind my Think End to End series: connect personas, journeys, interviews, feedback, and analytics to a hypothesis and an activity. The artefacts become useful when they help us make a decision.
Simple does not mean effortless
Why do teams skip these steps if they are so clear? Sometimes there is pressure to ship. Sometimes recruiting people takes time. Sometimes the data is unreliable, ownership is unclear, or a decision has already been made. And sometimes we prefer the exciting part of the work to the uncomfortable moment when a real person shows us our idea does not work.
That is where the skill lies. Ask the useful question anyway. Choose a method that fits the decision. Make the evidence visible. Be honest about what we know and what we only assume. Help the team act on it, then return to see whether it helped.
UX is rather easy to explain. Doing it well, repeatedly, with real people and real constraints takes practice. The good news is that we do not need to invent the basics again each time. We need to use them.