Skip to main content

Lean UX

Skill Verified Active

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", "outcome over output", "design studio method", "assumption mapping", or "lightweight research". Also trigger when reducing design documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

Purpose

Apply lean thinking to UX design by replacing heavy deliverables with rapid experimentation and collaborative practices to build products users love.

Features

  • Hypothesis-driven design framework
  • Structured assumption mapping and prioritization
  • Guidance on various experiment types (prototypes, MVPs, A/B tests)
  • Collaborative design methods like Design Studio
  • Integration strategies for Lean UX within Agile sprints (dual-track)
  • Outcome-focused metrics and OKR examples

Use Cases

  • Applying lean thinking to UX processes
  • Designing new features or products based on validated learning
  • Reducing design documentation overhead and speeding up iteration cycles
  • Getting cross-functional teams to co-design and build shared understanding
  • Running fast usability experiments to test design hypotheses

Non-Goals

  • Replacing deep domain expertise with procedural guidance
  • Providing pre-built UI components or code
  • Acting as a replacement for foundational UX principles (e.g., usability heuristics)
  • Enforcing a rigid process over team learning and adaptation

Workflow

  1. Identify and prioritize assumptions
  2. Formulate testable hypotheses
  3. Design and run appropriate UX experiments
  4. Synthesize results and decide to iterate, pivot, or ship
  5. Collaborate with the full team throughout the process

Practices

  • Hypothesis-driven design
  • Collaborative design
  • Agile integration
  • Outcome measurement
  • Experimentation

Prerequisites

  • Understanding of Agile development principles
  • Cross-functional team members (PM, Designer, Developer)
  • Access to design/prototyping tools (optional but recommended)

Installation

First, add the marketplace

/plugin marketplace add wondelai/skills
/plugin install skills@wondelai-skills

Quality Score

Verified
98 /100
Analyzed about 23 hours ago

Trust Signals

Last commit17 days ago
Stars953
LicenseMIT
Status
View Source

Similar Extensions

Design Sprint

100

Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development. Use when: **New product concepts** that need validation before building; **Big feature decisions** with significant investment required; **Stuck teams** needing to break through analysis paralysis; **Startup pivots** when direction is uncertain; **High-risk bets** where failure is expensive

Skill
guia-matthieu

User Story Mapping

100

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

Skill
deanpeters

Measure Experiment Design

100

Designs an A/B test or experiment with clear hypothesis, variants, success metrics, sample size, and duration. Use when planning experiments to validate product changes or test hypotheses.

Skill
product-on-purpose

Brainstorm Experiments New

100

Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.

Skill
phuryn

Design Workflow

100

Anti-AI-generic design guidelines. Use when creating UI prototypes, reviewing designs for generic AI patterns, or setting up a project design system.

Skill
spartan-stratos

Kaizen

99

Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.

Skill
NeoLabHQ

© 2025 SkillRepo · Find the right skill, skip the noise.