lean-ux

Facilitate assumption mapping workshops to validate design hypotheses with outcome-based metrics.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill lean-ux-fsolla
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-ux
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/lean-ux
Command: npx skills add https://github.com/fsolla/teqo --skill lean-ux-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the inefficiency of heavy design documentation and waterfall-style handoffs by replacing them with rapid, hypothesis-driven experimentation and cross-functional collaboration.

Core Features & Use Cases

  • Assumption Mapping: Explicitly identify and prioritize business and user risks before building.
  • Hypothesis-Driven Design: Convert assumptions into testable predictions using a standard format.
  • Collaborative Design Studio: Facilitate cross-functional sketching sessions to build shared understanding.
  • Use Case: Use this when your team is stuck in the output trap, shipping features that don't move metrics, or when you need to validate a new product concept with minimal engineering investment.

Quick Start

Apply the lean-ux skill to facilitate an assumption mapping workshop for our new checkout feature.

Frequently Asked Questions about lean-ux

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

FAQPage Schema
How do I replace heavy design documentation with hypothesis-driven design?▼

Hypothesis-driven design replaces heavy documentation by converting user assumptions into structured, testable predictions. You validate these predictions through rapid experimentation and outcome-based metrics before any feature delivery, ensuring design decisions are backed by data.

What is assumption mapping and when do I need it for agile product discovery?▼

Assumption mapping is the process of explicitly identifying and prioritizing business and user risks before building a feature. You need it during early product discovery to avoid the output trap of shipping features that fail to move core metrics.

How do I facilitate a collaborative design studio session for cross-functional teams?▼

Facilitate a collaborative design studio by guiding cross-functional teams through structured sketching sessions. This technique builds shared understanding and aligns stakeholders on product direction before committing to engineering investment.

Can I integrate lean UX workflows with dual-track agile processes?▼

Yes, lean UX integrates directly with dual-track agile by separating discovery and delivery tracks. It replaces waterfall-style handoffs with cross-functional collaboration, using rapid experimentation to validate design concepts in parallel with development.

What is the best way to validate a new product concept with minimal engineering investment?▼

The best way to validate a new product concept with minimal engineering investment is applying lean thinking to UX. You formulate structured hypothesis statements, define outcome-based metrics, and run rapid experiments to test predictions before building.

Why does my team keep shipping features that do not move metrics?▼

Teams ship features that do not move metrics because they fall into the output trap, prioritizing delivery over validated learning. Applying lean UX shifts focus to assumption mapping and hypothesis-driven design to ensure features solve actual user problems.