What problem does it solve?
Interfaces often push irreducible complexity onto users through confusing forms, manual formatting demands, and cryptic errors, while over-simplification can hide complexity that resurfaces as downstream burden. This Skill helps you decide deliberately who should carry that complexity.
Core Features & Use Cases
- Complexity Auditing: Distinguish inherent complexity (from the task itself) from extraneous complexity (from the design) before simplifying.
- Burden Shifting Guidance: Identify where the product should absorb work users currently do, such as accepting multiple date formats, auto-populating regions, or enforcing file naming conventions.
- Over-Simplification Warnings: Detect when hiding options or over-defaulting critical decisions creates invisible downstream cost in support volume, error recovery, or lost power-user control.
- Use Case: When redesigning a checkout flow, audit each step to find decisions the product can make with smart defaults, then verify the removed complexity did not reappear as support tickets.
Quick Start
Ask the AI to apply Tesler's Law to audit a user flow and identify which steps the product should absorb instead of the user.
