UX Designer Goals

UX Designer Goals Examples: 64 Goal-Setting Actions for UX Designers and Researchers

Create human-centered products that solve real problems through rigorous research and thoughtful design, ensuring every decision is grounded in user needs and validated through evidence.

8 pillars × 8 actions = 64 specific steps, adapted from the Harada Method used by Shohei Ohtani at age 16.

Advocate for the user

Acknowledge design failures

Credit collaborative work

Share research findings publicly

Contribute to open design systems

Offer portfolio reviews

Recruit research participants

Write tight discussion guides

Master affinity diagramming

Design for accessibility first

PHYSICAL

Resist feature pressure

Speak at local UX events

FAMILY

Create free UX templates

Run benchmark usability tests

FINANCIAL

Conduct diary studies

Seek disconfirming feedback

Keep design decisions documented

Mentor junior designers

Partner with nonprofits

Write plain-language UX articles

Host user research workshops

Analyze product analytics

Build a research repository

Present research with confidence

Map user flows before wireframes

Design for error states first

Apply Fitts's Law to tap targets

PHYSICAL

FAMILY

FINANCIAL

Master typographic hierarchy

Build a spacing system

Design accessible color contrast

Use progressive disclosure

BUSINESS

Prototype microinteractions

BUSINESS

Create human-centered products that solve real problems through rigorous research and thoughtful design, ensuring every decision is grounded in user needs and validated through evidence.

Study visual design fundamentals

Create consistent iconography

Study native platform patterns

Design keyboard and gesture navigation

Reduce friction in critical paths

SYSTEMS

VOICE

BITCOIN

Use white space deliberately

Photograph and collect visual references

Design for dark mode parity

Join sprint planning as a partner

Co-write product requirements

Learn to read code

Audit component coverage

Write component documentation

Implement design tokens

Build concept prototypes in one day

Run moderated usability tests weekly

Write clear test tasks

Facilitate design critiques

SYSTEMS

Present to leadership monthly

Version the design system

VOICE

Build dark mode into the token layer

Use unmoderated testing for scale

BITCOIN

Test with assistive technologies

Build relationships with data teams

Create design handoff specs that answer questions before they are asked

Celebrate cross-team wins publicly

Run a quarterly component health check

Socialize the system with onboarding

Reduce one-off components monthly

A/B test copy and CTAs

Document prototype assumptions

Share prototype findings with engineering

Character Pillar: undefined

In every meeting where a business or technical shortcut is proposed, explicitly state what the user loses and ask whether the tradeoff has been tested with real users.You become the person in every room who grounds decisions in human truth, not assumptions.
After each usability test, write one paragraph in your design journal naming specifically what you got wrong and why you made that choice.You become a designer who learns faster than anyone because you face failures directly instead of rationalizing them.
In every design review, name the researchers, engineers, and stakeholders whose input shaped the solution before presenting your own contributions.You become the designer everyone wants on their team because you make others feel seen and valued.
Run an automated accessibility audit (axe or Lighthouse) on every screen before marking any design as complete, and fix every critical issue before shipping.You become a designer who builds inclusion into the foundation of every product, not as an afterthought.
When asked to add a feature without supporting research, respond with: 'What user problem does this solve? Can we test that assumption in a 30-minute session before we design it?'You become a designer with the professional courage to protect users from the inside of organizations.
After sharing a design, explicitly ask one reviewer to tell you what is most likely to fail or confuse users, then sit with that feedback before defending your choices.You become a designer who sharpens their work through honest critique instead of protecting their ego.
For every significant design decision, write a one-paragraph decision log in Figma or Notion capturing the options considered, the evidence reviewed, and the rationale chosen.You become a designer whose thinking is transparent, traceable, and trustworthy to every teammate and future hire.
Block 30 minutes weekly to review one junior designer's work and give structured feedback using a stop/start/continue format focused on their craft, not just the output.You become a designer who multiplies the quality of the entire team, not just your own portfolio.

Karma Pillar: undefined

Anonymize and publish one meaningful usability finding per quarter on Medium, Substack, or your personal site with enough context for other designers to apply the learning.You become a practitioner who advances the entire field, not just your own career.
Submit one component, accessibility fix, or documentation improvement to an open-source design system (Material, Carbon, Radix) every six months.You become a designer whose work quietly improves hundreds of products you will never see.
Volunteer to review two junior or career-changer UX portfolios per month through ADPList, local UX groups, or Twitter/LinkedIn DMs.You become a node in the design community that helps people get their first job and their first break.
Submit one talk proposal per year to a local UX meetup, IxDA chapter, or regional design conference on a specific method or case study from your own work.You become a practitioner who builds the local design culture instead of just consuming it.
Package one research template (discussion guide, affinity mapping board, usability test plan) as a free Figma community file or Notion template each quarter.You become a designer whose generosity compounds quietly as thousands of practitioners use your frameworks.
Dedicate 8 hours per quarter to a pro bono UX audit or design sprint for a local nonprofit, school, or civic organization that lacks design resources.You become a designer who uses their craft to serve communities that would otherwise go without.
Write one article per month that explains a UX concept (mental models, progressive disclosure, cognitive load) in plain language without jargon, aimed at non-designers.You become a bridge between design craft and business leadership, making UX legible to the whole organization.
Organize one 90-minute workshop per year at your company or local community teaching non-researchers how to run a basic 5-participant usability test.You become the person who spreads user-centered thinking beyond the design team and into the whole organization.

Pillar 3: undefined

Build and maintain a screener survey in Typeform and a participant database in Notion or Airtable with at least 50 opted-in users segmented by behavior and role.You become a researcher who can launch a study within 48 hours because your participant pipeline is always warm.
For every qualitative study, write a discussion guide with no more than 8 open-ended questions, pilot it with a colleague, and cut any question that leads the participant toward your hypothesis.You become a researcher whose sessions surface genuine insight because your questions create space instead of closing it.
After every round of user interviews, synthesize observations into an affinity diagram within 48 hours using sticky notes or FigJam, grouping by behavior not by topic.You become a researcher who finds patterns others miss because you synthesize rigorously and quickly.
Establish task-completion rate and time-on-task baselines for your three core product flows, then retest every major design change to measure whether the numbers improved.You become a designer whose work is measured by outcomes, not opinions, giving you credibility in every stakeholder conversation.
Design and run one longitudinal diary study per year for a high-uncertainty user behavior, using daily prompts sent via SMS or WhatsApp over 7-14 days.You become a researcher who understands behavior in its natural context, not just in a lab or a 60-minute session.
Spend 90 minutes every two weeks in Mixpanel, Amplitude, or FullStory identifying where users drop off and generating three behavioral hypotheses to test in your next research round.You become a designer who connects qualitative depth to quantitative patterns, making your insights undeniable.
Tag and archive every research finding in a shared repository (Dovetail, Notion, or Confluence) with the study date, participant count, and a one-sentence takeaway searchable by product area.You become the institutional memory of your product team, connecting past learnings to present decisions.
Structure every research readout as: here is what we wanted to learn, here is what we found, here is what it means for the product, here is the recommended next step.You become a researcher whose insights get acted on because you translate findings into decisions, not just observations.

Pillar 4: undefined

Before opening Figma for any new feature, draw the complete user flow on paper or Miro showing every decision point and error state, and get alignment from your PM before designing screens.You become a designer who solves the right problem at the right level of abstraction instead of jumping to pixels.
For every form, interaction, or flow, list every way a user could fail or be confused, then design those states before designing the happy path.You become a designer who ships products that feel polished and forgiving because you anticipated failure as carefully as success.
Audit every touchable element in your mobile designs for a minimum 44x44pt tap target size and flag every violation in your design review checklist before handoff.You become a designer whose interfaces feel effortless because the physics of interaction are built into your design habits.
Identify the three pieces of information a user needs first, second, and third for each screen, and ensure complexity is revealed only as users need it, not all at once.You become a designer who reduces cognitive load systematically, making complex products feel simple.
For every transition, button state, and loading moment in a key flow, build a Figma prototype or Principle animation so stakeholders and engineers see the intended behavior, not just static frames.You become a designer who communicates intent so precisely that engineering handoff conversations shrink from hours to minutes.
Spend 30 minutes weekly in Apple HIG and Material Design guidelines reviewing the interaction patterns relevant to your current sprint and note where your designs align or intentionally deviate.You become a designer who builds on platform conventions users already know, reducing the cost of learning your product.
For every new feature, define the full tab order for keyboard navigation and document supported gestures (swipe, pinch, long-press) in your design spec before handoff.You become a designer who builds inclusive, robust interactions that hold up across input methods and assistive technologies.
Count the number of taps, form fields, and decisions required in your highest-traffic user flow and run a quarterly exercise to reduce that number by at least one step.You become a designer who treats every unnecessary step as a moral issue, not just a metric problem.

Pillar 5: undefined

Limit every screen to three type sizes maximum (heading, body, caption), define them in your token library, and refuse any one-off size that is not in the scale.You become a designer whose screens communicate priority instantly because your typographic system is disciplined and intentional.
Adopt an 8-point grid for all spacing and sizing decisions in your designs, and add a spacing audit to your design review checklist to catch any value not on the grid.You become a designer whose layouts feel visually harmonious and engineer-ready because your spacing is always consistent.
Run every text and icon color combination through a WCAG contrast checker (Stark plugin or WebAIM) and achieve at minimum AA compliance before any design is marked ready for development.You become a designer who makes inclusion non-negotiable by making it a step in your process, not an afterthought.
Complete one structured study block per week on a specific visual principle (gestalt grouping, figure-ground, visual weight) by analyzing three real products and writing down what works and what does not.You become a designer who can articulate and defend visual decisions with the same rigor as interaction decisions.
Audit your product's icon library every quarter and replace any icons that are inconsistent in stroke weight, corner radius, or visual style, maintaining a single source of truth in your design system.You become a designer whose visual language is coherent, reducing cognitive load through consistency users feel even if they cannot name it.
Before finalizing any screen, remove one element and observe whether the layout communicates more clearly without it. Add white space until the primary action is visually unmistakable.You become a designer who knows that restraint is a skill, and that removing is often harder and more valuable than adding.
Maintain a curated inspiration board in Are.na or Mobbin organized by pattern type (onboarding, empty states, forms, navigation) and review it at the start of every new design problem.You become a designer with a broad visual vocabulary who draws from a wide range of influences instead of defaulting to the same five apps.
For every component you design, create both light and dark variants in Figma using color variables, and test both modes on a physical device before marking the component complete.You become a designer who treats dark mode as a first-class citizen, not a skin someone applies at the end.

Pillar 6: undefined

When exploring a new feature direction, time-box your prototyping to 4 hours using Figma or Framer to create the minimum interactive version needed to answer your top research question.You become a designer who learns from real users instead of from internal debate, because you get to testing faster than anyone.
Schedule one 45-minute moderated usability test per week during active design sprints, recruiting from your participant database and rotating the team members who observe.You become a designer who has a continuous feedback loop with users baked into their working rhythm, not reserved for milestone reviews.
Write every usability test task as a realistic scenario (not 'click the settings button' but 'you just received a payment and want to update your bank account') and pilot each task with one colleague before testing with users.You become a researcher who gets behavioral data, not just user opinions, because your tasks mirror real-world context.
Run unmoderated tests through Maze or UserTesting.com on every major release to get quantitative task-completion data from 20+ participants before launch.You become a designer who supplements qualitative depth with statistical confidence, making your recommendations harder to dismiss.
Run every major flow with VoiceOver (iOS/macOS) and TalkBack (Android) before shipping, and fix every navigation or announcement issue before marking the flow complete.You become a designer who knows that accessibility is a testable, measurable quality, not a good-intention checkbox.
Partner with your PM to set up one A/B test per sprint on a high-traffic button label or heading, using a 95% confidence threshold before declaring a winner.You become a designer who lets user behavior arbitrate design debates instead of opinion or seniority.
At the start of every prototype, write a bullet list of the three assumptions you are testing and the pass/fail criteria you will use to evaluate them before touching Figma.You become a designer who tests hypotheses deliberately instead of validating what you already believe.
After every usability test, write a one-page findings summary and share it in the engineering team's Slack channel or standup within 24 hours of the last session.You become a designer who makes engineers feel invested in the user's experience by making sure they hear directly from users, not just from you.

Pillar 7: undefined

Quarterly, compare the components in your design system to the components currently being used in production and file tickets for any gap where engineers are building custom components not in the library.You become a designer who treats the design system as living infrastructure that must keep pace with the product it serves.
For every component in your system, write a usage guideline covering: when to use it, when not to use it, and one example of correct and incorrect use. Publish it where engineers can find it without asking.You become a designer whose system is self-serve, reducing the design bottleneck on engineering teams across the organization.
Define color, spacing, typography, and radius values as named tokens in Figma Variables and ensure they map directly to the tokens used in your codebase via a shared JSON export.You become a designer who creates a single source of truth that keeps design and code in sync without manual reconciliation.
Tag every major design system release with a version number in Figma and a changelog entry, and communicate breaking changes to engineering in writing at least one sprint before they ship.You become a designer who treats the design system with the same engineering discipline as a software library, earning the trust of the development team.
Structure all color tokens as semantic names (color.surface.primary, color.text.inverse) rather than raw values, then swap the values per mode without rebuilding any components.You become a designer who architectures systems to scale instead of patching surface-level problems with each new product requirement.
Every quarter, review the top 10 most-used components by checking for accessibility issues, outdated visual styles, and inconsistent usage patterns in production screenshots.You become the steward of a system that gets healthier over time instead of accumulating quiet debt.
Create a 30-minute onboarding guide (video walkthrough or annotated Figma file) that every new designer and frontend engineer reads in their first week, covering how to use and contribute to the system.You become a designer who multiplies quality across the organization by making good defaults easy and bad defaults hard to reach.
Each month, identify two custom components in production that are not in the design system, evaluate whether they are reusable, and either absorb them into the system or deprecate them.You become a designer who fights design entropy proactively, keeping the product coherent as it grows.

Pillar 8: undefined

Attend every sprint planning session, review the proposed tickets before the meeting, and flag any ticket that lacks defined acceptance criteria from a user perspective before it is estimated.You become a designer who is embedded in the engineering rhythm instead of handed specs after decisions are already made.
For every significant feature, write the user-facing requirements section of the PRD with your PM, grounding each requirement in a specific user need identified in research.You become a designer who shapes what gets built at the requirements stage, not just what it looks like after the fact.
Spend 20 minutes per week reviewing the pull requests for features you designed, learning to read enough HTML, CSS, and component structure to spot implementation gaps before they ship.You become a designer who earns engineering respect by speaking their language and catching issues before QA.
Run a structured 60-minute design critique bi-weekly with designers and at least two engineers or PMs, using the format: context, questions to answer, warm feedback, cool feedback, next steps.You become a design leader who builds a culture of honest peer review instead of siloed solo work.
Prepare a 5-slide monthly update for your design director or CPO covering: key research findings, design decisions shipped, open questions, and one metric you are tracking.You become a designer who makes the value of UX visible at the leadership level, protecting the team's budget and headcount.
Set up a recurring 30-minute monthly sync with one data analyst to review the behavioral data for the features you own and identify user behavior patterns worth investigating further.You become a designer who triangulates qualitative and quantitative signals, making your insights more complete and your recommendations stronger.
Before marking any design ready for development, write annotated specs covering spacing, states, edge cases, and responsive behavior, then ask one engineer to review and flag anything unclear before handoff.You become a designer who reduces engineering rework by investing in precision and clarity at the handoff stage.
After every successful launch, write a public Slack message or all-hands shoutout naming the specific contributions of the engineers, PMs, and researchers who made the work possible.You become a designer who builds the kind of cross-functional trust that makes the next project faster, safer, and more collaborative.

Track Your UX Designer Goals

Turn this framework into a daily habit with our free browser extension. See your 64-action grid every time you open a new tab.

Load this into my extension →

Or get the framework delivered to your inbox:

Related Goal Frameworks

Career

UX Designer Goals Examples: 64 Goal-Setting Actions for UX Designers and Researchers

Character Pillar: undefined

Karma Pillar: undefined

Pillar 3: undefined

Pillar 4: undefined

Pillar 5: undefined

Pillar 6: undefined

Pillar 7: undefined

Pillar 8: undefined

Track Your UX Designer Goals

Related Goal Frameworks

Account Manager Goals

Carpenter Goals

Data Scientist Goals

Electrician Goals

College Student Goals

High School Teacher Goals