The complexity
keeps growing.
The clarity
doesn’t have to.
Thirty-five years of practice across entertainment, enterprise SaaS, federal healthcare, and AI-assisted operations. One consistent thread: making complex systems legible to the people who have to work inside them.
Discipline
Senior UX Designer & Accessibility Leader
Active Since
1989
Focus Areas
Enterprise SaaS · Accessibility · AI Workflows
1989 – 2006
Everything started with systems you could touch.
Before software, there were spaces. Signage systems that had to guide ten thousand people through unfamiliar environments. Stage sets that had to read from two hundred feet. Theme park environments that had to tell a complete story in forty seconds. Movie props that survived close inspection and still read correctly from across the room.
Art direction is systems work. Environmental graphics are wayfinding systems. Stage design is spatial navigation design. What looks like aesthetic judgment is almost always information architecture operating at a physical scale, where there is no update to push if you get it wrong.
The entertainment and creative work (for Warner Bros., Universal, Fox, Sony, and Disney-related projects) wasn’t a detour from a UX career. It was UX’s foundation, taught through an entirely different medium and under entirely different constraints.
2006 – 2012
When the internet arrived, it felt like translation, not transformation.
The same questions applied. How do people orient in an unfamiliar system? What do they need immediately, and what can safely defer? How do you design for time pressure, cognitive load, and varying levels of expertise simultaneously?
Working at FreeConferenceCall.com, one of the world’s largest conference calling platforms, meant designing for millions of concurrent users with no shared context and no margin for confusion. Operational clarity at scale: every interaction had to work on the first try, or the call was already a failure.
The iPhone arrived. Android arrived. The mental model shifted from pages to flows, from sites to systems. I shifted with it, and brought the physical-systems discipline with me.
Accessibility Philosophy
“Accessibility is not a feature you add. It is a quality you either build in from the beginning, or spend forever trying to retrofit.”
The practice began with formal ADA and Section 508 training at Blackboard, a platform serving millions of students, staff, and faculty across thousands of institutions. Many of those users had disabilities. The obligation wasn’t theoretical. It was present in every page, every form, every interaction.
What the training produced wasn’t compliance checklists. It produced a lens. Designing accessibly demands precision: every interaction must resolve without visual ambiguity, every label must be semantically unambiguous, every flow must operate under unpredictable conditions. Those constraints don’t narrow design; they sharpen it.
Federal healthcare work with CMS.gov deepened the practice. Government digital systems reach people in moments of genuine need. At that scale, accessibility is less a compliance requirement and more a form of care, a recognition that the people who most need these systems are often the ones they’re least designed for.
This philosophy carries into everything: not just the WCAG-compliant heading structure or the focus state on every interactive element, but the foundational assumption that every design decision has a human consequence.
2012 – 2022
Enterprise UX is different in one fundamental way.
The people using your product don’t choose to. They arrive at 8am, they need to complete a task, and they leave. They’re not evaluating your interface; they’re trying to do their job. The design’s only obligation is to stay out of their way.
A decade across Blackboard, Rouse Services, Age of Learning, and enterprise healthcare platforms produced a specific kind of competence: how to think about a system that thousands of organizations depend on simultaneously. How to make a change that doesn’t break any of their workflows. How to hold the full complexity of a platform while still designing for the individual encountering one small corner of it.
Healthcare added different stakes. Pharmacy management, patient records, clinical workflows. These are systems where errors have real consequences. The design principle is identical: clarity under pressure. The reason it matters is permanently amplified.
AI arrived. I was already building for it.
The framing of AI as a future technology missed the actual story. When you’ve spent three decades building systems that help people work more efficiently, AI is an obvious continuation, not a disruption.
Trigger-based workflows that eliminate manual overhead. Agentic systems handling research synthesis, content generation, and data processing without intervention. Local LLM infrastructure that keeps sensitive operational data in-house, responsive to real constraints rather than theoretical best practices.
This isn’t AI as novelty. It’s AI as a design medium, the same discipline of operational clarity applied to the infrastructure layer between people and the work they’re trying to accomplish.
- Trigger-based workflow automation
- Multi-agent orchestration pipelines
- Local LLM infrastructure
- AI-assisted UX research synthesis
- Content generation at scale
- Cross-platform SaaS orchestration
Systems Philosophy
“The goal has never been to design something beautiful.
The goal has always been to design something that disappears,
so the work can proceed.”
Ronald Schnier
The ecosystem that thirty-five years of practice makes possible.
Happy Path Studios began as an answer to a question that enterprise work kept raising: what would this discipline look like, built entirely from scratch, without institutional constraints?
The answer is an ecosystem. SaaS platforms built around specific workflow problems. Accessibility services for organizations that need the practice, not just the certification. AI-assisted operational systems designed to solve actual operational problems. And HPS Golf, a hybrid digital and physical experience that connects a traditional recreational activity to modern engagement infrastructure.
It’s not a pivot from enterprise work. It’s the same discipline applied in a context where the brief is entirely self-authored, and the constraints are chosen rather than inherited.
Closing Reflection
The through-line, across all of it.
The discipline of making complex things legible to the people who have to use them. Whether that’s a signage system in a theme park, a healthcare communication platform serving millions, a federal reporting interface, or an AI automation pipeline running quietly in production every day, underlying question is always the same.
What does the person on the other side of this system actually need? The form the answer takes changes. The question doesn’t.
My career began in creative direction, branding, and marketing before evolving into enterprise UX, accessibility, product strategy, and AI-assisted workflows. Today I help organizations take complex products from concept to launch by aligning user experience, business strategy, accessibility, and go-to-market planning.