This is Part 1 of the complete UI/UX Playbook. Before strategy, before interface craft, before any tool or deliverable, comes the philosophy: a clear understanding of what user experience actually is, and the principles that should guide every decision. Get this foundation right, and everything that follows has something solid to stand on.
Two Perspectives on UX
Good user experience can be understood from two complementary perspectives, and a mature organisation holds both at once.
From the user’s perspective, creating a good experience is always about genuinely caring for the end user — and that requires an organisational culture that supports it. It’s not something a single designer can deliver alone; it needs the whole organisation to value it.
From the organisation’s perspective, UX reflects how well a product meets users’ emotions and expectations, while accounting for different user goals. Strategically and culturally, teams that put user experience first share their cross-disciplinary knowledge with each other and aim to work together to create the best possible experience. The two perspectives reinforce each other: caring about users and building the culture to support that care.
UX, UI, Usability and Interaction: The Core Vocabulary
When building a digital product or service, four terms come up constantly — and they’re all related and work together, but understanding the differences between them is essential.
- User Experience (UX) — how well a product or service meets the user’s emotions and expectations. The fewer difficulties and errors a user encounters, and the more their expectations are met, the better the user experience.
- Usability — the learnability and efficiency of a product. It targets the process of making systems easy and consistent to use, improving the experience by meeting user needs in the easiest, most appropriate way.
- User Interface (UI) — everything the user sees or interacts with: patterns, colours, forms, buttons, the visual design of the product.
- Interaction — how the interface responds when the user provides input: hovering over a link or button, page-loading animations, sounds in response to voice commands, error or success messages.
I’ve explored the UX-versus-UI distinction in more depth, including how the roles are evolving, in the article on what a UI/UX designer is.
The Eight Foundational Principles
These principles span both application (design) and technology, and they form the practical bedrock of the playbook.
- Prioritise the user experience. Understand users’ online and offline needs. Run early UX tests across user groups and continue UX analysis and testing frequently after go-live — never stop iterating. And remember the “fat finger first” principle for touch-friendly design.
- Minimise risk. Break systems into small modules and microservices. Use use cases, user stories, and needs to identify those micro-areas and modules.
- Simplify. Clarity should always be number one — minimise distractions. Keep users in control without making them feel controlled. Use consistent language and design.
- Define your MVP. Don’t compromise on design; aim for a minimum lovable product. Have a clear purpose, focus on building the smallest thing that delivers value, and avoid bloated, distracting, swollen feature sets.
- Stay API-centric. Create content once and make it usable across many channels. Allow content to adapt to different experiences, and ensure APIs support future uses and integrate with external sources.
- Set open, shared standards. Assume resources will be accessed across many channels over long periods. Focus on the whole architecture, with a UX big-picture view, for more extensible systems.
- Design modularly. Build reusable code and design (a design system). Retain organisational knowledge by documenting products so everyone can access them — and use that knowledge to design and build future products faster.
- Stay device-independent. Build products that work across most platforms regardless of screen or system, and focus on users’ needs on each specific platform.
Building a Successful UX: Think – Make – Check
Successful projects rest on the “user first” principle, with the user at the very centre of the product lifecycle. This is a Design Thinking-driven mindset operating in an endless lifecycle of evolving user needs — not a project that ends at delivery. The work cycles continuously through three modes: Think, Make, Check, oriented around making the product useful, usable, and desirable.
- Think — data analysis, prioritising findings, understanding the user (journey maps, personas, user data analysis), and developing ideas through brainstorming sessions based on the data gathered.
- Make — wireframe designs, screen designs, prototype development, code deployment, building the design system.
- Check — qualitative tests (motivation, user behaviour), quantitative tests (data-driven), analytics, and A/B testing.
The business benefits of working this way are concrete: base decisions on meaningful data; optimise product design and the integrations between parts; eliminate crowded, unnecessary areas; and focus on interface usability and user adoption. Every optimisation brings you one step closer to the perfect product the user needs.
Where This Leads: The Four Focus Areas
These foundations feed directly into the four focus areas that make up the rest of the playbook — understanding users (strategy), crafting the interface (UI tactics), organising the team (governance), and producing the right deliverables (tools). Each gets its own dedicated part.
Next: Part 2 — UX Strategy →
Part of the complete UI/UX Playbook, developed and authored by Gökhan Meriç. Questions about applying these principles? Get in touch.