UX
Reducing Decision Fatigue in a Complex Product
A strategic approach for keeping feature-heavy products usable as they keep growing, using questions instead of more UI.
Complexity map
The accumulated surface of a mature product — features, toggles, and edge cases added release after release, plotted against how much of it any single user actually needs.
Decision points
The moments in a flow identified as the right place to ask, rather than assume — where a short question determines what the user needs to see next.
Anticipatory forms
Lightweight prompts placed at those decision points, designed to capture intent in one or two questions instead of exposing every option up front.
Adaptive disclosure
The same core screen reconfigured based on the answers collected, surfacing only the relevant path while keeping full depth available for users who need it.
Challenge
Every new feature added another option, another toggle, another edge case, and the interface still made every user walk through all of it whatever their task. More features was turning into more friction.
Process
Instead of bolting each new feature onto an already dense screen, I mapped the natural decision points in the user's flow, looking for what a short, well-placed question could settle before the interface had to show anything at all. The first version asked too many questions and felt like a form before the real screen. The one that worked asks once.
Research
What I kept seeing in the usage patterns was that most of a complex product is irrelevant to any one user in any one session. The complexity itself was fine. Showing all of it regardless was the problem, and it left every user filtering by hand.
Design
At the points where we couldn't guess what the user wanted, we ask. One or two questions, once. The answer decides what the screen shows next. The product's full depth stays reachable, it's just no longer the default view for someone who doesn't need it.
Outcome
New features could keep shipping without piling onto what any one user has to deal with. Tasks got faster to finish, onboarding needed less explaining, and power users kept the full product through an explicit path.