Back to all ArticlesI design systems that help users decide what matters.
Most products treat settings as a secondary screen.
A place for toggles. Preferences. Small adjustments.
That works — until your product becomes complex.
When systems grow, settings become critical
In data-dense environments, settings are no longer optional.
They define:
- what users see
- how they are notified
- how workflows behave
- what decisions are possible
And yet — in most products, settings still look like a form.
That’s not a UI problem. That’s an architecture problem.
When settings are not designed as part of the system:
- users lose control
- behavior becomes unpredictable
- signals get buried in noise
- decision-making slows down
This is where UX starts to fail at a systemic level.
So I didn’t design a settings page
I designed a system control layer.
A structured way for users to:
- define how the system behaves
- control how information flows
- manage feedback and notifications
- adjust the system without breaking their workflow
What this means in practice
Settings are connected to the system
Not isolated.
They directly impact:
- navigation
- notifications
- system behavior
Changing a setting is not cosmetic —
it changes how the product works.
Modular structure instead of chaos
Instead of one overloaded screen:
- Profile
- Notifications
- Navigation
- System settings
Each module represents a domain of control, not just a section.
Real control over notifications
Users can decide:
- which events matter
- where they are delivered (system / email / desktop)
- how visible they should be
This turns notifications into a controlled system, not background noise.
Designed for speed and clarity
This system was built for users who:
- work with large amounts of data
- monitor processes
- need fast, reliable decisions
So everything is:
- predictable
- fast
- frictionless
Integrated with the product
Settings are not separate.
They shape:
- what appears in navigation
- how feedback is delivered
- how workflows behave
This is what makes the system usable at scale.
The outcome
Instead of a passive settings page:
- users gain real control
- noise is reduced
- behavior becomes consistent
- the system scales without breaking UX
Why this matters
Because in complex products:
usability is not about simplicity
it’s about control
What I actually design
I don’t design screens.
I design systems that:
- support decision-making
- reduce cognitive load
- scale with complexity
- connect UI with real system behavior
If your product is growing…
…and your settings still look like a form,
you don’t have a UX problem.
You have a system problem.
👉 Full case study:
https://zofiaszuca.com/project/designing-settings-as-a-system-control-layer
