I'm a documentation leader who designs learning experiences — I just usually call them "user guides." Scroll to play through the journey, unlock badges for the wins, and try translating real integration-guide jargon into something a first-day user could actually follow.
Four studios, one throughline: make hard products make sense. Click a node to open the mission log.
The wins that matter most for a learning-experience role — scaled impact, not just shipped pages.
190 cybersecurity integration guides, 70% faster time-to-value for new customers.
Rebuilt 400+ guides to WCAG 2.2 ahead of a government contract deadline.
Consolidated four fragmented content systems into one searchable knowledge base.
Company-wide style guide across Product, Support, and Marketing — 40% less review time.
Hired, coached, and managed a technical writing team through hypergrowth.
In-app Pendo campaigns, driven by analytics, that measurably reduced onboarding friction.
Straight from a real integration guide I wrote at ReliaQuest. Toggle to see the same instruction in engineer-speak vs. how I'd actually hand it to a learner.
Every month, real product changes had to reach customers who'd never read the release plan. These are three consecutive editions I wrote and published.
Levels are relative to my own toolkit, not a universal scale.
I've spent ten years translating technical complexity into learning people actually finish. I'd love to bring that to Lucid's Learning Experience Designer role.