lean-ux

Applies hypothesis-driven design, collaborative sketching, and rapid experiments to UX workflows.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill lean-ux-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-ux
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/lean-ux
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill lean-ux-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Traditional UX processes waste months producing heavy deliverables built on untested assumptions. This Skill replaces documentation-heavy design with hypothesis-driven experiments, collaborative design sessions, and continuous lightweight research so teams learn from real user behavior before over-investing. ## Core Features & Use Cases - Assumption Mapping & Hypothesis Statements: Declare business and user assumptions explicitly, prioritize by risk and uncertainty, and convert them into testable hypotheses with pre-committed success criteria. - MVP Experiments & Collaborative Design: Choose the lowest-fidelity experiment (paper prototypes, smoke tests, Wizard of Oz) to validate ideas, and run Design Studio sessions where cross-functional teams sketch solutions together. - Continuous Research & Agile Integration: Embed weekly usability testing into every sprint and run dual-track agile so discovery feeds delivery one sprint ahead. - Use Case: A product team kicking off a new feature uses this Skill to run a 30-minute assumption mapping workshop, write a hypothesis ("We believe trial-to-paid conversion will increase 10% if new users complete a guided setup wizard"), test a clickable prototype with five users, and score the process against the 10/10 Lean UX rubric. ## Quick Start Ask the AI to help you write a Lean UX hypothesis statement and design the smallest experiment to test your riskiest product assumption.

Frequently Asked Questions about lean-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a Lean UX hypothesis statement?▼

Use the standard format: "We believe [outcome] will happen if [persona] achieves [action] with [feature]." Specify the persona, action, outcome, and measurable signal, and pre-commit to what validated and invalidated results look like before running the experiment.

What is the difference between Lean UX and traditional UX design?▼

Lean UX replaces heavy deliverables like wireframe specifications with rapid experiments, collaborative sketching, and continuous research. Success is measured by outcomes (changes in user behavior) rather than outputs (shipped features or design artifacts).

How do I run a Design Studio collaborative sketching session?▼

Follow the diverge-present-critique-converge cycle: each team member sketches ideas individually, presents them, receives critique, then refines a converged sketch. A 90-minute session with the full cross-functional team builds shared understanding that replaces lengthy specs.

Can Lean UX work inside Agile sprints?▼

Yes, through dual-track agile where a discovery track (research and design) runs one sprint ahead of the delivery track (engineering and QA). Validated hypotheses and tested prototypes are ready when the delivery sprint begins, avoiding the sprint-zero bottleneck.

How many users do I need for usability testing in Lean UX?▼

Five users uncover approximately 85% of usability problems according to Nielsen's research. Lean UX favors small weekly tests embedded in every sprint over large quarterly studies, keeping feedback fast enough to influence current decisions.

When should I not use Lean UX experiments?▼

Do not use Lean UX to skip accessibility, security, or compliance work, since these are non-negotiable quality standards rather than testable assumptions. Also avoid smoke tests that mislead users into believing a product exists without disclosing the test status.