Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wondelai/lean-ux
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables.
Passed 23 of 24 test cases with the skill, and 19 of 24 without it.
and 1 more in the full report
4 fixed19 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are trying to evaluate our current product design workflow. Right now, our team writes detailed PRDs, creates high-fidelity Figma mockups for every feature prior to development, hands them off to engineers in sprint planning, and runs usability testing once per quarter post-launch. Please audit this workflow using the Lean UX evaluation framework. I need to know our total score, which specific evaluation criteria we missed, and actionable recommendations to fix each failed area.
| Checked | Without skill | With skill |
|---|---|---|
| Assigns an overall process score of 0 out of 10 on the Quick Diagnostic scale | Missed | Passed |
| Identifies post-launch quarterly testing as a failed diagnostic criterion | Passed | Passed |
| Recommends replacing quarterly post-launch testing with continuous weekly user research | Passed | Passed |
The instructions your model reads when the skill loads.
A practice-driven approach to UX that replaces heavy deliverables with rapid experimentation, cross-functional collaboration, and continuous learning. Lean UX shifts the question from "What should we design?" to "What do we need to learn?"
Outcomes over outputs. The value of a design is measured not by the fidelity of the deliverable but by the change in user behavior it produces.
The foundation: Traditional UX waterfalls requirements into wireframes, mockups, specs, and code—losing context and hiding untested assumptions at every handoff. Lean UX compresses the distance between idea and evidence: declare assumptions, form hypotheses, run the smallest possible experiment, and let real user behavior settle the argument. Shared understanding replaces documentation; learning velocity replaces pixel perfection.
Goal: 10/10. Score a UX process, design plan, or team workflow by the eight-row Quick Diagnostic below: award ~1.25 points per row answered "yes" (8 yeses = 10). Bands:
Always state the current score, the diagnostic rows that failed, and the specific fix for each.
Core concept: Every design starts with assumptions. Lean UX makes them explicit so they can be prioritized and tested, rather than baked invisibly into specifications.
Why it works: Unspoken assumptions mean teams build on shaky ground and discover problems only after launch; surfacing them early focuses energy on the riskiest ones and reduces the cost of being wrong.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| New feature kick-off | Assumption mapping workshop | "We assume users want to share reports with teammates" |
| Roadmap planning | Rank features by assumption risk | Prioritize features whose success depends on untested beliefs |
test cases passed, vs 19 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.