Settings content
simplification
80+ settings screens. Every feature team had added their own. Different labels, different logic, different everything. For a product with cameras, microphones, and location tracking, users not being able to find their privacy settings isn't a UX annoyance — it's a trust problem.
The situation
A settings experience
nobody owned
The smart glasses companion app had 80+ settings screens across iOS and Android. Every feature team had added their settings independently — different label conventions, different description styles, different categorization logic. The result was a settings experience that users couldn't navigate.
Dogfooding feedback confirmed it: people couldn't find what they needed, didn't understand what settings did, and were confused by multi-device scenarios — what happens when you own both glasses and a watch?
For a product with cameras, microphones, and location tracking, not being able to find your privacy settings isn't a UX annoyance. It's a trust problem.
The constraint
I was the sole content designer on settings. The work spanned two device types, two platforms, and dozens of feature teams. There was no PM championing settings work. It had been deprioritized before. I had to build the case, do the work, and prove the value — all while managing my other responsibilities. And everything had to be validated. This was a shipped product with real users.
What I did
Six things, done right,
in the right order
Full audit
I conducted a complete audit of every settings label, description, and category across the app — mapping inconsistencies, identifying where users were getting lost, and flagging where content didn't match what the setting actually did.
Description framework
I developed a settings description framework that shortened labels and made descriptions more relevant. The principle: if a user can't understand what a setting does from the label alone, the label is wrong. I worked with UXR to validate every change.
IA redesign
I reworked the entire settings categorization — introducing intuitive naming conventions aligned with UXR findings. I tested 4 different IA directions with research before landing on the final structure.
Multi-device simplification
I introduced the concept of "Shared settings" to unify single- and multi-device experiences. Instead of users seeing two separate settings worlds for glasses and watch, they see one coherent experience. This simplified navigation and reduced engineering complexity.
Design system scaling
I partnered with the Design Systems team to scale 34 iOS/Android screens into reusable product infrastructure — spanning pre-prompts, permissions/consent screens, and troubleshooting templates. I consolidated UX and content templates for 10+ permission types (Location, Bluetooth, Nearby Device, Notifications, connected apps like Spotify).
Toolkit and governance
I created the comprehensive Settings toolkit — principles, best practices, rules, behaviors, and guidelines — so any team adding new settings could do it consistently. I established a governance model so the system maintains itself. 3+ teams used the contributor templates to make updates without CD involvement.
Deliverables
What I built
- A settings description framework validated by UXR
- A complete IA redesign across 80+ screens
- The "Shared settings" concept for multi-device management
- 34 iOS/Android screens scaled into design system infrastructure
- Consolidated templates for 10+ permission types
- The Settings toolkit (principles, best practices, rules, behaviors, guidelines)
- A governance model for all future settings additions
Outcome
Task success: 73% → 82%
Content decisions weren't made on instinct — they were validated. I partnered with UXR to run usability studies on key flows, using task success rates as the primary metric for content effectiveness.
The 73% → 82% improvement wasn't a coincidence. It was the result of iterating on copy based on where users got stuck, not where we assumed they would. Mean time on tasks dropped from 6.2 to 5.7 seconds. Settings categorization was adopted as the standard across two product lines.
"Ashlee's work has stepped up both the quality and coverage of our Design System. I really admire her ability to identify areas of opportunity and develop frameworks around them: that's the systematic thinking that's gonna make our system one of the strongest in the entire company."
— Scott Gary, Design Systems Manager
"As the sole Content Designer on Settings, she has skillfully managed multiple projects and successfully led the transition. Her ability to proactively navigate complex and challenging problems, combined with her clear and concise communication style, has ensured that everyone is on the same page."
— Manager review
Reflection
What I'd do differently
I'd push for a pilot study earlier. I'd known for years that settings was a high-leverage surface, but I didn't have UXR data to prove it until I was finally able to run the studies. If I'd pushed for even a small-scale usability test sooner — 5 users, 10 minutes, just the top settings — I could have built the business case faster and gotten PM support earlier instead of running this as an under-resourced effort.
When you believe in the work, build the smallest possible proof point and let the data make the case.
Product names abstracted for confidentiality.