Marcus Andrey Study
Ler em português Library

UX Lead · 6 min read

Design your UX practice

Turn everything in the course into your own practice model: 3–4 pillars, what good looks like, signals and first moves.

CConsistent practice

A shared base of principles, standards, components and process across domains.

Builds: modules 06, 08
GGrowth and learning

Designers share knowledge, get feedback and grow, even when they work alone.

Builds: modules 04, 11
TTransparent capacity

Demand, capacity and trade-offs are visible and decided with agreed criteria.

Builds: modules 07, 10
EEvidence-driven UX

Decisions use research, usage data and quality measures, within data protection rules.

Builds: modules 05, 09

Diagnosis → 3–4 pillars → what good looks like → signals → first moves

One example practice model: four pillars, each answering part of the same diagnosis.

Why it matters

Without a practice model, a new lead's work turns into random acts of UX: a critique here, a template there, a dashboard nobody asked for. Every request feels like a priority, because nothing says what the practice is for. And when a stakeholder asks "what is UX doing this year?", you have a list of activities, not a story.

A small set of pillars fixes this. It tells your team what to focus on each week, gives you a reason to say "not now", and gives stakeholders something they can recognise in the results.

A worked example: four pillars

This is one example from a fictional organisation: an internal operations platform where UX grew domain by domain, with designers often working alone in their product teams. Read it to see the shape of a practice model, then build your own.

1. Consistent practice

The problem it answers. Practices and components drift between domains, so users meet different patterns for the same task and designers solve the same problem twice.

What good looks like

  • A short set of opinionated design principles that the team uses in critique.
  • A governed design system with a clear contribution process and pattern tiers.
  • A common process "minimum standard" every domain follows, with room for local decisions.

Signals to watch

  • Design-system adoption % and detach rate.
  • Consistency defects (QA bugs tagged "UI inconsistency").
  • Contribution health: number of proposals and cycle time from proposal to release.

First 90 days

  • Draft 5 opinionated principles with the team and run the "opposite test".
  • Agree a governance model and a lightweight contribution process.
  • Run a design-system standard workshop with designers and frontend developers.

Built in this course: Module 8: Design Systems & Standards Governance · 06 › Design principles · 07 › DesignOps: the three layers · 05 › Designing for expert users · Cards: Design principles · Design system governance models · Contribution process · Pattern tiers · Design system adoption playbook · Design system metrics · Definition of Done for design

2. Growth and learning

The problem it answers. Designers are isolated, often one per domain, so they get little feedback, learn slowly and have no clear picture of how to grow.

What good looks like

  • A regular cross-domain critique ritual where feedback is safe and specific.
  • Regular 1:1s, a development plan per designer and a career ladder everyone can read.
  • Mentoring pairs and a shared knowledge base, so learning doesn't depend on the lead.

Signals to watch

  • Team health-check scores over time.
  • Share of designers with an up-to-date development plan.
  • Critique attendance and the number of designers who bring work to it.

First 90 days

  • Start regular 1:1s with every designer.
  • Run your first cross-team critique and set the rhythm (for example every two weeks).
  • Run a first team health check to get a baseline.

Built in this course: Module 4: People Leadership · 04 › Psychological safety & team health · 11 › Cross-team design critique · 07 › Rituals for a distributed UX team · Cards: One-on-one meetings · SBI feedback · Design critique · Individual development plan · Career ladder · Psychological safety · Team health check

3. Transparent capacity

The problem it answers. UX demand is invisible, so work is allocated by urgency and by who shouts loudest, and designers are overloaded.

What good looks like

  • One intake for all UX requests, describing problems, not solutions.
  • A capacity map that shows who works on what, with a 15–20% buffer for urgencies, practice work and learning.
  • Prioritisation criteria agreed with stakeholders, and trade-offs decided with the right people.

Signals to watch

  • Share of UX requests that go through the intake.
  • Capacity map reviewed monthly with domain leads, and how many attend.
  • Designer-reported "workload sustainable" score.

First 90 days

  • Draft an intake form and a first capacity map.
  • Agree weighted scoring criteria with product leads.
  • Run a UX capacity and priorities session with product leads and product managers.

Built in this course: 07 › Capacity & resource allocation · 07 › UX team models · 10 › Saying no (or "not yet") well · 11 › UX capacity & priorities session · Cards: UX intake · Capacity map · Weighted scoring · RICE scoring · Allocation patterns · Decision rights matrix · Saying no formula

4. Evidence-driven UX

The problem it answers. Decisions rely mostly on opinion, because usage data isn't systematic and is constrained by data protection.

What good looks like

  • A UX maturity baseline per domain, repeated every 6–12 months.
  • Metrics chosen goals first, and a GDPR-safe tracking plan agreed early with data protection.
  • A lightweight benchmark of top tasks, mixed with qualitative research.

Signals to watch

  • Maturity baseline score per domain.
  • Share of projects with research before development.
  • Stakeholder satisfaction from a quarterly 3-question survey to product managers.

First 90 days

  • Run a maturity baseline and a listening tour.
  • Write a Goals-Signals-Metrics table for one product.
  • Pilot an analytics event taxonomy in one app.

Built in this course: Module 9: UX Maturity & Measurement · 05 › Research in internal contexts · 06 › Connecting UX to the business · 08 › Measuring the design system · Cards: UX maturity model · Goals-Signals-Metrics · HEART framework · UX benchmarking · GDPR-safe tracking plan · Qual and quant balance · UX value model

Notice how the pillars reinforce each other: shared standards make cross-domain critique possible; capacity transparency frees time for research; evidence feeds the standards.

Build your own

  1. Diagnose. Write the critical challenge of your practice in 3–4 sentences, ideally after a listening tour of your first 30 days (see 30-60-90 plan). Mark each claim as evidence or assumption.
  2. Draft 3–4 pillars. Group your planned actions into themes. For each pillar, write what good looks like, 2–3 signals and 2–3 first moves. Check that each pillar helps at least one other.
  3. Test with your team and stakeholders. Share the draft with your designers and a few product leads. Rename, merge or drop pillars until both groups recognise their problems in it.

Use the canvas below. It saves in this browser.

Your practice model saves automatically in this browser.
3. Your pillars3–4 is usually right. Each one should be something your team can act on every week.

    Check it every quarter

    • Score each pillar from 1 to 5 in the canvas: how close are you to what good looks like?
    • Look at the signals. Are they moving, and do they still measure what matters?
    • Adjust the first moves into next quarter's moves, and share the update with your stakeholders.
    • Retire a pillar that no longer matches your critical challenge. A finished pillar is a success, not a failure.

    Connections

    ← 12-Month Learning Plan · UX Lead Course · Module 6: UX Strategy & Vision

    Saved only on this device.

    ↑ ↓ to move · Enter to open · Esc to close