S.R.Bloome
The Problem
Our internal learning platform had become difficult to use. Over time, it evolved into a catch-all system with too many pages, duplicated content, and unclear paths. What should have supported employees was creating operational drag.
We supported thousands of users across regulated teams, but the experience introduced friction instead of clarity. Navigation was inconsistent. Language felt rigid. Finding the right information required unnecessary effort. This created inefficiencies across onboarding, support, and compliance workflows.
The result showed up quickly in the business.
1. Low engagement across learning experiences
2. Slower onboarding timelines
3. Increased repeat support demand
4. Gaps in understanding critical workflows
5. Low confidence in compliance-driven tasks
The system was functional, but it was not effective.
Analysis
I reframed the problem as a system-level issue rather than a surface-level design gap.
I assessed how content, structure, and language were contributing to friction across the platform. The goal was to identify where users were getting stuck and understand the patterns driving that behavior.
Several issues emerged quickly.
1. Redundant and outdated content across modules
2. Navigation structured around internal teams, not user needs
3. Inconsistent UX patterns between experiences
4. Overly complex or unclear system language
5. Lack of content governance or standards
At scale, these gaps compounded into inconsistent experiences and unnecessary complexity across the platform.
Approach
I set a clear direction to simplify the system, standardize communication, and reduce friction at scale.
I established content as core platform infrastructure and rebuilt the experience around how users actually move through their work. The focus was on clarity, consistency, and confidence in high-stakes moments.
1. Reworked information architecture to follow task-based navigation
2. Introduced progressive disclosure to reduce cognitive load
3. Replaced internal jargon with clear, human language
4. Built a scalable voice and tone framework for consistency
5. Redesigned system prompts, confirmations, and error states
6. Focused on clarity and confidence in compliance-heavy interactions
7. Aligned legal, compliance, design, and engineering around a shared approach
8. Balanced regulatory requirements with user-first communication
This was not a visual redesign. It was a structural shift to improve usability and trust across the platform.
Impact
Reduced repeat support demand
Improved onboarding speed and consistency
Increased training completion across key workflows
Strengthened usability and platform confidence
Key Takeaways
Content is product infrastructure, not supporting material
Trust is built through consistent, high-stakes interactions
Clear systems reduce operational friction at scale
Alignment across teams is required for regulated experiences
Enterprise learning ecosystem
Final Reflection
This work reinforced how much clarity drives performance. When systems are structured well and communication is consistent, users move faster and with more confidence. When they are not, even simple tasks create friction and slow teams down.
I now approach every platform as a system that must scale. I build modular content frameworks, define reusable language patterns, and align cross-functional teams early to reduce downstream inefficiencies.
This approach creates consistency across teams, reduces rework, and supports long-term scalability while maintaining trust.
