control-power-vs-simplicity

What problem does it solve?

It solves the mismatch between novice and expert needs by preventing either audience from being forced into the other’s interface.

Core Features & Use Cases

• Design layered control with a simple default surface plus discoverable depth for advanced users.
• Choose an architecture (progressive disclosure, mode toggle, settings panel, power-user shortcuts) based on where “depth” lives.
• Avoid common traps like feature-parity promises, settings sprawl, and “everything in one screen.”

Use when you’re building a product that serves multiple experience levels (consumer apps with power features, pro tools used occasionally, onboarding-heavy workflows) and you must decide what to expose by default vs. hide behind progressive disclosure.

Quick Start

Use the skill to recommend the best layered-control architecture for a feature set you’re designing, and draft how novices will complete core tasks without discovering the advanced surface.