Should product design favor simplicity, or can purposeful complexity serve users better?

Scott Farquhar · Oct 9, 2023

Jira will never be as simple as a tool built from scratch for a five-person team, and shouldn't try to be; its edge is scaling with the customer and integrating across products

You never outgrow Jira whether you have 20 or 20,000 engineers, and simple point tools can't provide the workflows and integrations Atlassian can

Scope: Atlassian continues investing heavily in simplification

35:13 20VC: Atlassian Co-Founder Scott Farquhar on The Biggest Lessons Scaling Atlassian to $50BN Market Cap; The Four Roles of the CEO, The Funding Round That Net Accel $6BN, The Regrets of Omission and Commission & The Honeymoon Cut Short

Fernando Fanton · Jul 27, 2025 · hedged

Simple is not always better in design; complexity is fine when it purposefully draws the user deeper, though unnecessary complexity is never the solution

Whoop's UX is not simple at all, but the complexity serves the goal of drawing you into understanding how your body works and what you should do

Scope: complexity must have a purpose; unnecessary complexity is still bad

19:48 20Product: Should We Kill the PM Role Entirely | How Does Product Design Change Most in a World of AI | How Do Monzo Build Product Today: What Works, What Does Not | Why Most Product Sucks and What Makes Truly Great Product

Kevin Systrom · Feb 22, 2023

Products are 'hired' by consumers to do a specific job, and adding features dissonant to that core job confuses users and makes them stop opening the product

People can only hold a simple enough idea of your product in their head; like dissonant tones in music that make listeners stop listening, off-job features grate on users

23:48 Products are hired for one job so dissonant features confuse users and should be avoided

Adam Mosseri · Jul 24, 2023

Simplicity is not always better in design; it is a means to an end such as usability or broad appeal, and one must be clear about that end

You have to be clear what end simplicity serves; there are instances where the more complicated thing is the better means to that end

23:45 Simplicity is a means to an end not inherently superior

Adam Mosseri · Jul 24, 2023

The Instagram app is too complicated, and the awkward navigation isn't deliberate — it's accumulated complexity

When a large team gets excited about a new idea they build a new thing rather than extend an existing pattern, because extending requires coordination and is less specialized; that adds complexity by death by a thousand cuts

24:18 Accumulated complexity from uncoordinated new features not deliberate design causes bloat

David Meyer · Nov 1, 2023

'Simple' is a near-meaningless product principle and simplicity is not always better; the real constraint is not diluting the superpowers of the user you're serving

Simple doesn't necessarily mean removing optionality — sometimes it does, sometimes it doesn't — and you can still give a user superpowers while reducing the number of ways to do a thing, as long as they can still do what they came to do

35:22 Simple is a near meaningless principle the real constraint is preserving user superpowers

Noah Desai Weiss · Jun 16, 2023

Simplicity means how comprehensible something is, not how few clicks it takes; in enterprise software more clicks can be better, since a guided flow with one decision per screen can perform better by bringing users along.

Guided flows make people feel they have mastery of the software and confidence in what they're doing, whereas consumer instincts push toward removing clicks and options.

19:31 Simplicity means comprehensibility not click count so guided multi screen flows can be simpler

Harry Stebbings · Oct 6, 2023

Retaining product simplicity over time is the hardest part, because serving both enterprise and SMB makes feature creep inevitable and products end up looking like Workday

Each new segment demands more features, and the accumulation is unavoidable

22:51 Serving both enterprise and smb makes feature creep and complexity inevitable

Gustav Söderström · Oct 12, 2022

Having multiple parts of the app perform the same job for the user — radio versus personalized playlists — is a product mistake

A genre radio and a personalized playlist in that genre return essentially the same songs, so the features compete with each other and surfacing one imposes a cost elsewhere; Spotify grew up on the playlisting paradigm and never resolved which paradigm to lead with

16:05 Redundant features serving the same job compete with each other and should be consolidated

Shishir Mehrotra · Sep 25, 2020

In consumer products, a consistent experience matters more than comprehensiveness once you have enough content or inventory

Google Shopping was strictly more comprehensive than Amazon yet lost, because users valued knowing how product pages, reviews, shipping and returns worked; the same held for online video

13:45 Consistent experience beats comprehensiveness once inventory is sufficient

Mike Hudack · Sep 13, 2024

The real art of product is understanding what people want to achieve and helping them achieve it with the minimal amount of work.

Advertisers don't actually want to target ads or think about optimization — they want to sell more product; so the simpler the machine you give them to do that, the better.

9:33 Understanding user goals and minimizing effort is the core of good product design