Perceived Simplicity

Advanced features are discoverable when you look, but invisible if you don't

Casey Winters
Why most product managers are unprepared for the demands of a real startup

Perceived Simplicity

"We strive for this concept of what we call perceived simplicity, which is there are advanced features in the product and they are easily discoverable when you look for them, but they're effectively hidden if you're not looking for them." - Casey Winters

What It Is

A design philosophy for managing product complexity. As products grow, they face Scott Belsky's product lifecycle trap: users flock to a simple product, the product adds features for power users, and users flock to the next simple product. Perceived simplicity breaks this cycle.

The goal: advanced features exist and are easy to find when you look for them, but effectively invisible when you're not. The majority of users never encounter complexity that would confuse them.

How It Works

The Problem

Products face a constant tension:

  • New/casual users want simplicity
  • Power users want advanced features
  • Growing products naturally add complexity
  • Users shift from casual to sophisticated over time

Common Solutions That Often Fail

Approach Why It Fails
Unbundling (separate apps) Fragments experience, loses integration benefits
Progressive disclosure Doesn't work when you never want some users to find advanced features
Segmentation Fails when users shift between segments over time
Proactive training Doesn't scale for consumer products

Perceived Simplicity Approach

  1. Advanced features exist in the product
  2. Easily discoverable when a user actively looks for them
  3. Effectively hidden from users who aren't looking
  4. Majority never encounters complexity they don't need

The WhatsApp Model

WhatsApp exemplifies perceived simplicity:

  • Core experience: Simple chat that works great
  • Advanced features: Voice messages, video calls, phone calls
  • Discovery: Easy to figure out when you need them
  • Default: Hidden complexity if you're just chatting

How to Apply It

Design Principles

  1. Lead with the core use case - What does 80% of your users need to do? Make that frictionless and obvious.

  2. Hide advanced features in plain sight - Don't bury them, but don't surface them until relevant.

  3. Design progressive entry points - Users should naturally discover features when their needs evolve.

  4. Avoid premature education - Don't teach users about features they don't need yet.

Evaluation Questions

For each feature addition, ask:

  • Will this confuse users who don't need it?
  • Can it be surfaced only when relevant?
  • Does it clutter the primary path?
  • Could a user discover it in less than a second when needed?

Common Patterns

  • Contextual reveal: Feature appears when context makes it relevant
  • Expandable sections: Advanced options behind "More options" or disclosure arrows
  • Smart defaults: System makes good choices; customization available but not required
  • Secondary surfaces: Settings, menus, or modes that contain power features

When to Use It

  • Product is growing: Adding features for new use cases
  • User sophistication varies: Serving both novices and power users
  • Facing the Belsky trap: Users leaving for simpler alternatives
  • User personas shift: Users graduate from simple to complex needs

Source

  • Guest: Casey Winters
  • Episode: "Why most product managers are unprepared for the demands of a real startup"
  • Key Discussion: (21:32) - Casey explains perceived simplicity as Eventbrite's design philosophy
  • YouTube: Watch on YouTube

Related Frameworks

Back to Product Strategy