What problem does it solve? Traditional UX processes bury untested assumptions inside heavy deliverables like wireframe decks and specs, causing teams to ship features that never change user behavior. This Skill replaces documentation-heavy design with assumption mapping, testable hypotheses, low-fidelity experiments, and cross-functional collaboration so teams learn before they build. ## Core Features & Use Cases - Hypothesis-Driven Design: Declare and prioritize assumptions on a risk/uncertainty matrix, then convert them into testable hypothesis statements with pre-committed success criteria. - Rapid UX Experiments: Choose the lowest-fidelity experiment that answers the question, from paper prototypes and smoke tests to concierge MVPs, Wizard of Oz tests, and A/B tests. - Collaborative Design & Agile Integration: Run Design Studio sketching sessions with the whole team and fit UX into dual-track agile with staggered discovery and delivery sprints. - Use Case: A product team planning a Gantt chart feature runs an assumption workshop, tests a clickable prototype with 8 users, invalidates the hypothesis, and redirects three months of engineering effort toward validated work. ## Quick Start Use the lean-ux skill to turn our new feature idea into a prioritized assumption list and a testable hypothesis with an experiment plan.
