Eleven tips to improve your UX design practice
To improve a UX design practice, talk to users regularly, frame problems before solving them, run structured critiques, build and maintain a design system, make accessibility a default, measure outcomes, document decisions, collaborate closely with engineering, share research widely, invest in skills and review how the team works every few months.
Why practice matters more than individual projects
A single excellent project can come from a talented designer working under good conditions. Consistently excellent work across many projects comes from a strong practice: shared habits, processes and standards that help every designer do their best work. Teams with mature practices make better decisions, produce more consistent products and grow their people faster.
Improving a practice does not require a large transformation programme. Most gains come from small, repeatable habits introduced one at a time. The eleven tips below can be adopted by teams of any size, from a single designer in a startup to a large design organisation. Our post on DesignOps covers how larger teams organise these habits at scale.
The eleven tips at a glance
| Tip | Benefit |
|---|---|
| 1. Talk to users regularly | Decisions grounded in evidence |
| 2. Frame problems first | Solving the right problem |
| 3. Run structured critiques | Higher quality and shared standards |
| 4. Build a design system | Consistency and speed |
| 5. Make accessibility default | Products everyone can use |
| 6. Measure outcomes | Proof of impact |
| 7. Document decisions | Shared memory and alignment |
| 8. Pair with engineering | Designs that ship as intended |
| 9. Share research widely | Organisation-wide understanding |
| 10. Invest in skills | Growing capability |
| 11. Review the process | Continuous improvement |
1. Talk to users regularly
Research is most valuable when it is continuous rather than occasional. A recurring weekly or fortnightly slot for interviews or usability sessions keeps the team close to real users and makes research part of normal work. Rotate who attends, including developers and product managers, so understanding spreads across the team. Our guide to newer UX research methods covers continuous approaches.
2. Frame problems before solving them
Many design problems start with a proposed solution, such as "add a filter" or "redesign the homepage". Strong practices pause to define the underlying problem: who is affected, what they are trying to do and what gets in their way. Writing a short problem statement before design begins keeps work focused and makes it easier to evaluate options. Our guide to finding the right design solution explains this step.
3. Run structured critiques
Regular design critiques, where designers share work in progress and receive focused feedback, raise quality and build shared standards. Effective critiques have a clear structure: the designer explains the goal and what feedback they need, reviewers comment against that goal and the session ends with agreed next steps. Our post on effective design feedback offers practical guidance.
4 and 5. Design systems and accessibility
A design system of shared components, tokens and guidelines frees designers from repeating basic decisions and keeps products consistent. Building accessibility into those components, with sufficient contrast, keyboard support and clear labels, makes inclusive design the default rather than an extra step. Our guides to building a design system from zero and accessibility cover both.
6. Measure outcomes
Measuring the effect of design work, through task success, conversion, retention, support volume or satisfaction, shows what is working and builds credibility with stakeholders. Agree success measures at the start of each project and review them after launch. Our guide to choosing the right UX metrics explains how.
7 to 9. Documentation, engineering and sharing
- Document decisions: Keep a short log of key decisions, options considered and reasons.
- Pair with engineering: Involve developers early and review builds together.
- Share research widely: Short summaries, clips and a searchable repository.
These habits reduce misunderstandings, speed up delivery and help the wider organisation understand users. A shared repository of research and decisions also helps new team members get up to speed quickly.
10. Invest in skills
- Set aside regular time for learning
- Run internal show-and-tell sessions
- Rotate designers across different products or problems
- Support courses, conferences and certifications
- Pair junior and senior designers on real work
Creating a healthy design culture
Practices thrive in a culture where designers feel safe sharing unfinished work, asking questions and challenging decisions respectfully. Leaders can encourage this by modelling openness, celebrating learning from failed experiments and protecting time for research and reflection. Clear career paths, regular one-to-ones and recognition of good work also help designers stay motivated and grow.
11. Review the process regularly
- Schedule a review: Every quarter, set aside time to reflect.
- Gather input: Ask designers and partners what is working and what is not.
- Pick one or two changes: Focus on the improvements with the biggest impact.
- Try them: Run the changes for a few weeks or a project.
- Evaluate: Keep what helps, adjust or drop what does not.
Small, regular improvements add up. A team that reviews and refines its practice every few months will steadily become faster, more consistent and more influential.
Frequently asked questions
How can a single designer improve their practice?
Start with regular user conversations, clear problem statements and simple measurement, then add a small component library and peer feedback.
How often should design critiques happen?
Weekly or fortnightly works well for most teams, with shorter ad hoc reviews as needed.
What is the most important habit for UX teams?
Talking to users regularly, because it grounds every other decision in evidence.
How do we show the value of improving our practice?
Track outcomes such as faster delivery, fewer revisions, better task success and stakeholder satisfaction.
Which tip should a team start with?
Usually regular user research, because it improves almost every other decision and is easy to start small.
Do small teams need a design system?
A lightweight one helps even small teams stay consistent and move faster, and it grows with the product.