S.R.Bloome
Designing systems, experiences, and products that bring clarity to complexity.
I bring a multidisciplinary approach to everything I build. Whether I’m designing interfaces, developing learning experiences, leading programs, or creating interactive worlds, my work is grounded in clarity, empathy, and purposeful design.
My impact? I strengthened enterprise adoption and proficiency outcomes while improving operational alignment across business units. My work has increased engagement up to 40 percent for client brands and established scalable learning ecosystems that improved onboarding, adoption, and user confidence.
Bringing Clarity to Complexity
I design intuitive digital experiences grounded in usability, research, and real-world constraints. My work focuses on clarity, accessibility, and building interfaces that support users rather than overwhelm them. Designing Trust at Scale Enterprise Learning Platform Redesign | Content Architecture + UI Language Systems Role Learning Experience Developer Content Designer & Writer Focus Content systems, UI language, information architecture, trust-forward design ⸻ The Problem What happens when your learning platform becomes a digital junk drawer? Over time, our internal learning ecosystem had turned into a catch-all. Too many pages. Too many paths. Too much outdated and duplicated content. Employees were overwhelmed. We supported thousands of users across regulated teams. But the experience felt heavy. Navigation was unclear. Compliance language was rigid and cold. Finding the right information took too much effort. The result: • Low engagement • Slow onboarding • Repeated support questions • Low confidence in critical workflows The current state wasn’t working. My task was clear: Tidy the mess. Rebuild clarity. Restore trust. ⸻ My Approach I didn’t start by redesigning screens. I started by diagnosing the problem. What was creating friction: • Redundant content • Outdated material • Fragmented navigation • Poor UX patterns • Inconsistent system language Instead of treating this like a copy refresh, I treated it like infrastructure work. Content wasn’t decoration. It was the system. ⸻ What I Led 1. Information Architecture Reset First step: reorganize how people actually move through the platform. I shifted the structure: • From department-first → task-first • From dense menus → progressive disclosure • From internal jargon → human language The goal was simple: Make paths predictable. Reduce cognitive load. Let users find what they need without thinking too hard. This created clearer flows and removed unnecessary friction across the platform. ⸻ 2. Voice and Tone System Next, I built a lightweight language framework that could scale. Not rules for “nice copy.” A system for consistent communication. Core principles: • Clear over clever • Supportive, not corporate • Direct, not defensive • Calm in high-stakes moments This became the baseline for all learning modules and interface surfaces. One voice. One system. Fewer contradictions. ⸻ 3. UI Copy for High-Trust Moments Many flows involved: • Compliance acknowledgments • Policy confirmations • Behavioral risk training • System warnings and prompts These moments matter. They shape trust. I redesigned: • Error states • System prompts • Confirmation language • Instructional microcopy The goal: Reduce fear. Increase confidence. Keep legal accuracy without sacrificing empathy. This is where language becomes experience design. ⸻ 4. Cross-Functional Collaboration None of this happens in isolation. I partnered closely with: • Legal • Compliance • Product design • Engineering My role was translation. Turning regulatory requirements into user-first language while protecting business risk. This is where content becomes connective tissue between teams. ⸻ The Impact After rollout, we saw: • Fewer repeat support requests • Faster onboarding completion • Higher training completion rates • Stronger internal usability feedback But the real win wasn’t just metrics. Employees trusted the platform again. They knew where to go. They understood what to do. They felt supported instead of monitored. That’s the difference good content systems make. ⸻ What I Learned This project changed how I design. I stopped thinking in pages. I started thinking in systems. I learned how to: • Build scalable content frameworks • Design reusable language patterns • Balance compliance with human tone • Advocate for content as product infrastructure These skills now anchor everything I build. ⸻ How I Apply This Today I use this same model across every platform I touch. Today, I: • Design modular content systems for WBT experiences • Build reusable UI language libraries • Create navigation structures that scale • Partner early with designers and engineers • Present content strategy to leadership This is how teams move faster without sacrificing quality.
Designing for Engagement
My foundation in game design continues to shape how I approach interaction, engagement, and narrative systems. I build experiences that prioritize immersion, logic, and emotional engagement. Designing Engagement Through Experimentation Interactive Learning Experiences | Behavioral UX + Content Testing Role Experience Developer Content Designer Enterprise Digital Platforms Focus Interaction design, experimentation, engagement systems ⸻ The Problem Static training didn’t work. People clicked. Scrolled. Checked the box. But retention was low. And completion didn’t mean understanding. The experience felt passive. Mandatory. Easy to rush through. That wasn’t a learning problem. That was an experience design problem. So I stopped treating training like content delivery. I started treating it like a game loop. ⸻ My Strategy I didn’t redesign everything at once. Instead, I built small experiments inside real products. The goal was simple: Test engagement patterns that actually change behavior. Then scale what works. ⸻ What I Built 1. Interactive Knowledge Checks Traditional quizzes weren’t doing enough. So I redesigned them into active decision moments. What changed: • From passive multiple choice → scenario-based decisions • From “right vs wrong” → contextual feedback • From static screens → progress-driven interactions Each interaction gave users immediate feedback and clear next steps. Not just “correct.” But why it mattered. Result: Higher completion rates and stronger knowledge retention. ⸻ 2. Feedback Loops That Create Momentum Next, I added lightweight reinforcement patterns: • Visual progress indicators • Clear success states • Micro-rewards through confirmation language and milestone feedback This wasn’t gamification for novelty. It was motivation through clarity. Users always knew: • Where they were • What came next • Why it mattered Momentum is built when the system removes uncertainty. ⸻ 3. Language Experiments That Change Behavior Then I tested the smallest variable with the biggest impact: words. I ran controlled content experiments across modules, testing: • Instruction phrasing • Tone shifts (formal vs conversational) • Call-to-action language •Error and guidance messaging Small changes produced measurable engagement differences. This reinforced something I use every day: Language isn’t decoration. It’s behavioral design. ⸻ 4. Modular Interaction Systems Once patterns proved successful, I made them reusable. I built modular templates teams could plug into future content: • Scenario cards • Decision paths • Feedback overlays • Progress components This allowed designers and developers to move faster without rebuilding logic every time. Good systems scale. Great systems remove friction for teams. ⸻ The Outcome After implementation: • Participation rates increased • Session engagement time grew • Learner feedback improved •Content abandonment dropped But the most important shift was behavioral. People stopped rushing through content. They started interacting with it. That’s the difference between consumption and engagement. ⸻ What I Learned This project strengthened my product instincts. I learned how to: • Prototype interaction ideas quickly • Test content at small scale • Iterate based on real user behavior • Balance fun with purpose • Build engagement without gimmicks It changed how I design every experience. ⸻ How I Apply This Today Now I approach content like product design. I regularly: • Design interaction models before visuals • Prototype flows with designers • Test language patterns • Build reusable UI components • Optimize based on engagement data I don’t just write content. I design systems that move users forward.
Using Language That Works
I bring structure to digital environments. My approach focuses on clarity and collaboration. This empowers my teams to do their best work and allows our users enjoy the results. Writing for Trust Under Pressure Sensitive UX Language Design | Compliance + Safety Experiences Role UX Developer & Writer Content Designer Enterprise Platforms Focus Trust surfaces, safety language, regulated UX content ⸻ The Problem Some moments carry weight. Account warnings. Policy acknowledgments. Security prompts. Risk disclosures. Behavioral guidance. These aren’t neutral screens. They shape how users feel about the platform. When language is cold, people disengage. When it’s overly legal, people panic. When it’s unclear, people make mistakes. My responsibility was simple and difficult at the same time: Protect users. Protect the business. Build trust. ⸻ My Approach I didn’t treat trust as copy. I treated it as a design system. Every high-stakes message needed to work together. Consistent tone. Clear structure. Predictable patterns. Trust is built through repetition and reliability. ⸻ What I Designed 1. Humanizing High-Stakes Moments First, I rewrote critical system language across sensitive flows. My goals: • Reduce fear • Increase clarity • Remove unnecessary jargon • Maintain regulatory accuracy Instead of language that felt punitive or robotic, I shifted toward guidance that felt transparent and supportive. Not “you did something wrong.” But “here’s what’s happening and what to do next.” That shift changes behavior. ⸻ 2. Deep Collaboration With Legal and Compliance Trust language doesn’t live in isolation. I partnered directly with: • Legal teams • Compliance stakeholders • Policy owners Together, we: • Translated regulatory requirements into human language • Preserved intent without copying legal text into the UI • Aligned tone across platform surfaces This reduced revision cycles and allowed teams to move faster without increasing risk. Good language systems protect both users and organizations. ⸻ 3. Designing Repeatable Safety Patterns Once strong patterns emerged, I made them reusable. I created consistent language frameworks for: • Confirmations • Alerts • Required acknowledgments • Risk-related instructions Consistency created familiarity. Familiarity reduced hesitation. Reduced hesitation increased trust. This is how language becomes infrastructure. ⸻ The Impact After implementation: • Fewer user errors in high-risk flows • Better comprehension of policy-driven actions • Reduced confusion during compliance steps • Stronger internal confidence in content accuracy But the biggest shift was emotional. Users felt informed instead of intimidated. Supported instead of warned. Guided instead of blocked. That’s what trust-centered design does. ⸻ What I Learned Trust isn’t built with disclaimers. It’s built with clarity, tone, and consistency. This work strengthened my ability to: • Write empathetically for sensitive moments • Balance safety with simplicity • Advocate for user-centered compliance design • Design language that protects without overwhelming These skills now shape every product surface I touch.