How to Train and Develop the 12 Competencies of UX Design

How Do You Train and Develop the 12 Competencies of UX Design?

Train the team you have. UX designers who are experts in every aspect of user experience are unicorns -- you can search your entire professional life and never find one. The more practical approach is to build a broad foundation across the 12 competencies of UX design with the talented designers already on your team.

These 12 competencies are foundational UX skills that robots won't be able to replicate any time soon. You'll need human designers with solid grounding in these concepts to achieve long-term success. The good news is that with a few simple steps, you and your team can start building that knowledge and identify where you need to go deeper.

What Are the 12 Competencies of UX Design?

The 12 competencies are a framework of foundational UX skills that every designer and design team should develop. They cover everything from understanding user needs and building a clear vision to prototyping, writing, collaboration, and design leadership.

Below is how to start developing each one.

1. Lean Into the "Why?"

The most common UX mistake is jumping to solutions before understanding the problem.

We're all guilty of it -- solving the "how" and the "what" while skipping right past the "why." That's the UX equivalent of running through a stop sign. You might get lucky and land on the right solution, but run enough stop signs and you'll end up with a wreck on your hands.

Every solution needs to begin with the "why" behind it:

• Why does your user need help?
• Why are you the right person, product, or service to provide that help?
• Why will they choose your solution over a competitor's?
• What is the larger purpose of the work, and how will it make the world a better place?

Asking these questions isn't enough. You need processes that force you and your team to stop and answer them before moving forward -- so you can communicate that purpose and passion to customers and stakeholders.

How to Get Started

• Build basic templates for user journey maps and simple personas. They don't need to be complicated or polished -- they just need to help you practice getting into the heads of your users.
• Use these tools as part of larger design thinking workshops to identify pain points and opportunities that help you and your stakeholders articulate the "why" and think beyond the pixels.
• Install processes and checklists that give your team the tools and confidence to push back against one-off solution requests from the business.

2. Only Proceed with a Clear Vision

Once you have your "why," build a vision of what the solution will look like before touching screen designs.

It's still tempting at this stage -- especially for skilled graphic designers -- to jump straight into visual solutions. You need to cultivate the discipline to stay focused on where you want to take the user.

Ask yourself:

• What does success look like for the user at the end of the workflow?
• Do they want to make a purchase, download an app, access information, or contact a rep?
• What should that experience feel like?
• What are the key problems and pain points in the current experience?

Taking the time to create a clear vision of success helps you craft a story that resonates with others -- and that story can unify the entire business behind your plan to make the world a better place for your users.

How to Get Started

• Establish a concrete vision of what success looks like for both the business and the user by connecting your "why" to specific problems and pain points. Learn how to tailor that presentation for different audiences.
• Think creatively about possible solutions, but don't just settle on the first one. At the same time, use your clear vision to avoid getting trapped chasing moving targets as focus shifts from goal to goal.
• Create storyboards to help people outside your team understand your vision of success. Share them to build unity, focus, and enthusiasm -- and to keep your team motivated as the project progresses.

3. How Do You See the World Through Your User's Eyes?

Think of it as empathy, not just research -- and don't let a lack of time or budget be an excuse to skip it.

People equate the word "research" with dollar signs and time. They worry they don't know how to do it right. That leads many in-house design teams to move forward on best guesses.

Sure, formal research is great when you have the resources. But don't let a lack of time and money stop you from at least talking to users through whatever channels are available. If you can't do that, take the time to empathize with them through your user journeys and empathy maps.

Most designers already have an inquisitive desire to understand users. The key is creating an environment that encourages them to question and correct assumptions, defend their decisions, and ultimately advocate for users.

How to Get Started

• Discuss your journey and empathy maps as a team and write out how they impact the solution you're designing.
• Talk to users through existing channels (email marketing, focus groups, customer advocacy groups, social media, etc.) so you can base your solution on data rather than assumptions.
• There's absolutely no shame in grabbing a coworker, a friend, or even a stranger for a quick take on something you're building throughout the product development process. Small gut checks can be just as helpful as big formal research projects.

4. How Do You Establish Measurements for UX Success?

Simplify evaluation by learning the language of the Experience Success Ladder and using it to frame how you're improving the user experience.

Evaluating and validating your designs is another step that often gets written off as too complicated. It doesn't have to be.

The Experience Success Ladder gives you the vocabulary to sell your work to other business units and the leadership team. Keep in mind that the things your leadership cares about most -- boardroom metrics like loyalty and low customer churn -- are often found at the higher ends of the ladder. Done right, this gives you a great way to show how your UX designs contribute to business success.

How to Get Started

• Identify your key metrics for success, create a plan to gather those metrics, and get a baseline measurement at the start of each project to show progress over time.
• Develop a common vocabulary and language (like the Experience Success Ladder) that everybody can use to evaluate and communicate success internally.
• Create procedures and a plan to constantly measure success through user interviews, analytics, usability evaluations, or other methods -- and adjust your approach as needed.

5. How Do You Engineer the Right User Flow?

Like a building or a house, good UX design relies on a strong foundation and good architecture.

Review your user flows and consider what structure you need to build to solve user problems with as little friction as possible. Then think through the tactical elements that will fit within that structure -- and remove anything that gets in the way.

For example, many designers come from a marketing background where copy needs to be promotional. But users of a product or service need content to guide them through a specific process. Anything more will clutter the experience. It's a different need, a different structure, a different user flow.

Consider the environment in which the user flow exists, weigh the top priorities and hierarchy, then think through the best ways to help your users navigate it.

How to Get Started

• Before designing tactical solutions, look at the basic architecture of your solution. Create and revise site and user journey maps and set some ground rules for what will keep the user flowing through the experience.
• Create quick wireframes to spot friction in the process -- either through internal team reviews or with actual user testing. Pay special attention to the small things that can trip the user up, and designs that look nice but aren't really what users need.
• Establish best practices to help your team learn the common friction points within your suite of products, services, and user flows.

6. What Is the "Art of the In-Between" in UX Design?

A big part of user experience happens in the transitions between screens and states -- not just in the static designs themselves.

Many new designers start with principles grounded in static design. They're focused on how an interface looks and feels in a single state. Many forget that what happens between screens matters just as much.

Develop the "art of the in-between." Think about the moments between actions and screens that validate the action the user just took in the step before. Bridging these gaps and learning to think through them in your initial design will push the user experience to the next level.

How to Get Started

• Sketch out all possibilities and states (including the non-golden paths) before jumping into high-resolution designs so you can map out the entire experience through different scenarios.
• When building prototypes (especially for testing), look for opportunities to represent the various states of a product and the transitions between those states to get better feedback on how the actual design may feel in the end.
• Think through and plan for different responses on different devices. How would this feel best for a user on a desktop versus a mobile device? Consider the amount of screen real estate available for both.

7. How Do You Become a Fast (and Balanced) Prototyper?

Always sketch before you screen. A quick pencil-and-paper sketch beats an hour in front of a design tool every time.

In any design there is a delicate balance between what is technically suitable and what will deliver true delight to users. Sketching first helps ensure you've thought through the entire solution systematically instead of as a one-off design.

Many designers feel that wireframes (like journey maps or user personas) have to be polished and perfect drafts. They don't. Early wireframes and rough sketches help you think through the big questions -- mapping out a balanced hierarchy, consistent styles, and the fine points of how you'll deliver a premium experience for all users.

How to Get Started

• Practice doing quick sketches of your ideas using pen and paper before touching a computer.
• Become familiar with approaches like Atomic Design that can help you roll out balanced and consistent interfaces quickly by thinking about hierarchies and design libraries at the start of a project.
• Create a shared design library as a team that can be used from one product to another to save time and create brand consistency for your organization.
• Make sure your team has a strong baseline understanding of visual design fundamentals (colour theory, typography, etc.).

8. How Do You Hone Your UX Writing Skills?

Great product writing adds clarity and flow to the user experience and helps build trust and confidence. Bad product writing clutters the interface and blocks users from accomplishing their goals.

Sounds pretty straightforward, right?

Writing is one of those skills that requires constant practice to master over time. Not all designers are comfortable writing. But all designers have to be comfortable identifying how copy will work across all levels of a design. The best way to do that is to practice writing as part of designing -- then practice some more.

How to Get Started

• Take a step back from your visual design and start writing real copy (not just "Lorem Ipsum" placeholder text). Writing copy that the user will actually see, even in the wireframing stage, helps you think through the complete user experience.
• Keep your writing on brand by reviewing your organization's brand voice and tone guidelines (or creating some). A fun, hip startup sounds different from a big established corporation.
• Practice writing copy that is accessible and friendly for screen readers by using a clear hierarchy of headings and subheadings, keeping text short and scannable, and using keywords that match the user's language.
• Constantly look for places to trim your copy to get it as succinct and informative as possible -- and avoid jargon.

9. How Do You Use Technology to Reduce Effort for Your Users?

You want to know your users so well that at any given moment you can prompt them with a message that will assist and comfort them -- without waiting for them to tell you they need it.

Most of us rely on users to tell us when and where that's needed. But to become a top-notch UX designer you'll want to push for innovation rather than stick with the status quo.

Ask yourself:

• What can be done outside

Frequently Asked Questions

What should I do if my organization doesn't have a formal UX team or dedicated UX budget? You don't need a large team or a big budget to start building UX competency. Begin with low-cost habits like sketching before designing, running informal hallway tests with coworkers, and using free or low-cost tools to create simple personas and journey maps. The goal is to build consistent practices, not perfect outputs.

How do you prioritize which UX competencies to focus on first when your team has limited time? Start with the competencies that address your team's most common failure points, whether that's skipping user research, jumping straight to visual design, or struggling to communicate value to stakeholders. A quick team audit where everyone honestly rates their confidence across the 12 areas can reveal the gaps that are costing you the most right now.

How do you get leadership or stakeholders to take UX investment seriously? Tie your UX work directly to metrics leadership already tracks, like conversion rates, customer retention, and support ticket volume. When you can show that a smoother user flow reduced drop-off or that clearer copy cut down on customer confusion, the business case makes itself.

Can these competencies apply to solo designers, or are they mainly relevant for teams? Every competency applies to individual designers as much as to teams. Solo designers benefit especially from building personal checklists and templates that replicate the accountability a team naturally provides, since there is no one else to push back on assumptions or flag skipped steps.

How do you know when a team member has genuinely developed a competency versus just being familiar with it? A solid indicator is whether they can teach it, defend their decisions using it, and apply it under pressure when timelines are tight. Familiarity tends to disappear when deadlines loom, while true competency holds up because it has become part of how someone naturally approaches a problem.