Epilogue: Back to the User
As this series comes to a close, we return to the question of what UX design is, and trace once more where the answer ultimately leads.
This series began with a single question. What is UX design.
In the process of searching for an answer, we traced design’s history back to its roots, explored the headwaters of the river we call experience, and looked beneath the waterline of the iceberg we call cognition. We read clues out of the whirlpool of behavior, and followed a journey built on the scaffolding of frameworks — observing, defining, visualizing, writing scenarios, prototyping, testing.
Looking back, all of this, in the end, has been heading toward one place. The user.
The user is who we observed. The user is who we empathized with. The user is who our designs were meant to serve. Techniques can change, frameworks can evolve, and new tools arrive every year. But the disposition to understand the user and empathize with their experience is the one thing about UX design that does not change — its essence.
So now it is time to return to the question this series first asked. What is UX design.
UX design is a self-declared commitment to address the parameters of the user experience by folding them into the design plan, and it is, in itself, the posture of designing from objectivity and observation rather than from intuition or inspiration.
This is the core thesis of this series. I hope reading this sentence now feels different from reading it the first time. If you have examined how the parameters of experience — cognition, behavior, emotion — actually work, and if you now have the frameworks and tools to work with them, then the weight of this declaration will have shifted.
Please take note of the phrase self-declared. UX design is not a role assigned to you by someone else. It is a proclamation you make to yourself: that you will grasp the user’s experience objectively, and design on that basis. Where that declaration exists, UX design exists. And where it does not, no tool, however impressive, can rightly be called UX design.
This posture matters because UX design is, at its core, a discipline of humility.
The designer does not rely on their own intuition or inspiration, but learns from the user’s behavior. They do not assume they are right, but test through prototypes. They do not try to get it perfect on the first attempt, but refine through iteration. All of this rests on a single premise: that I may not fully understand the user.
And it is precisely that premise which, paradoxically, lets us move closer to the user.
As this series has repeated throughout, I hope you won’t feel bound to any particular technique. You don’t need to build a persona, draw a journey map, or follow the Double Diamond. What matters is only this: standing before the user and trying to see the world through their eyes; trying to read, in their behavior, what they cannot put into words; and trying, on the strength of that understanding, to make the experience even a little better. Hold on to just that, and you are already doing UX design.
The river of experience never stops flowing. And our effort to shape its course cannot end with a single project either — it must continue. Technology changes. Users change. Society changes. The one thing that does not change, through all of it, is the will to make the user’s experience better.
Back to the user, once more.