Talked product management out of cartoon animals in the error states.
Making an expert tool usable for people who aren't experts
A platform built for daily power users needed a new extension for a completely different audience: people who might log in once a quarter, with no time to learn the tool and no patience for complexity. The job was making it feel self-explanatory without losing the professional tone enterprise customers expected.
You're all caught up. When someone sends you a request, it'll show up here.
Empty state from the shipped product
Read the full case studyHide the case study
The challenge
The core platform was built for full-time risk, compliance, and security professionals who used it daily and had been trained on it. A new product extension needed to serve a completely different audience: employees, vendors, and third parties who might log in once a quarter to complete a single task, with no time to spend learning the tool and no patience for complexity.
The content design challenge was making the product feel approachable and self-explanatory, without abandoning the professional tone the platform's enterprise customers expected.
My approach
Plain language over industry jargon. I replaced technical terms from the rest of the platform with everyday words that non-expert users could act on right away.
Warmer, but still professional. Contractions, shorter sentences, and direct address, all still appropriate for a workplace tool rather than a consumer app.
Guidance-forward. Since users were unfamiliar with the workflow, every screen had to answer "what is this?" before "what do I do?"
Documented and scalable. I captured voice and tone decisions in a guide the product team could write against as the product expanded.
Where I pushed back
Product management proposed playful imagery, including illustrated animals in error states, to make the product feel friendlier. I pushed back: this was a workplace tool used for required compliance tasks, not a consumer app, and playful imagery in that context reads as undermining rather than charming. We landed on copy that was clear, reassuring, and focused on helping the user recover. Someone stuck on a required compliance task doesn't want to be charmed. They want to know what to do next.
Sample copy
"You're all caught up. When someone sends you a request, it'll show up here."
"There are questions that still need answers before you can submit. Jump to incomplete questions."
"Request submitted. The team that sent this will be notified automatically — you're done."
Outcome
The product shipped and was adopted by enterprise clients, later expanding to additional use cases: a sign the content foundation held up under growth. Looking back, I'd push even harder for direct research with real end users rather than relying on internal assumptions about who they were. That's a good instinct to bring into any new project.