Design for scale and enable the people who build it
A successful UX solution has to survive beyond the original designer. At enterprise scale, that means reusable components, clear content structures, documented rules, accessible patterns, and tools that let other people produce good experiences without a UX expert beside them. Much of my work has been designing that infrastructure.
A design system for content editors
Generic CMS styles had accumulated over time and were used inconsistently. Some styles could be mistaken for other purposes, and the underlying markup created accessibility and maintenance problems.
I helped redefine the editor styles around clear purposes, and designed approximately a dozen reusable modules. Editors could now build complex page components through structured fields and uploads instead of working through the CMS's underlying complexity. The components were device-agnostic, starting with small-screen layouts and extending those patterns to larger screens.
The result was a more consistent and accessible toolkit for content teams, in a framework that can take on additional modules without disrupting what's already there.
Structured content that others can maintain
The structured-content work extended the same principle beyond individual components. Rather than asking editors to maintain the same information in several places, I designed a model where content is entered once and rendered appropriately at different levels of the site. That reduced duplication and gave the people responsible for the content a more scalable foundation.
UX documentation and enablement
Enterprise UX systems only work if the people who operate them can use them. The people creating and maintaining a digital experience are users too, and this part of UX work is easy to overlook.
Training guides and documentation for SiteExecutive, Sitecore, WordPress, proprietary applications, and SharePoint.
More than 50 component-library pages explaining how each component is used and built.
Online training delivered to groups of up to 45.
Documentation written for editors with very different levels of digital experience.
Success starts after launch
I don't define success as handing developers a design and moving on. I think about who maintains the system, how new content gets created, what happens when requirements change, whether accessibility survives production, and whether other teams can use what was built without recreating the problem. The leadership value is creating the structures, standards, and shared understanding that let good UX scale beyond a single project.
Faceted search, wayfinding, and persona development.
Read this page →Appointment making, structured content, and designing for multiple audiences.
Read this page →Need UX that outlasts the launch?
Let's see how your pieces scale.
Get in touch →