What's included

• Design Systems That Scale

  I don’t just ship files. I install scalable systems, elevate teams, and work hand-in-hand with CPOs to turn product chaos into clarity. Developer-focused UX docs, SDK quickstarts, and API integration guides → I write for speed, clarity, and trust — not fluff. Internal Notion/Markdown-based hubs that scale with your team → Everything lives where your people work — no more doc hunting. Design–dev handoff systems that stop Slack confusion and raise trust → I eliminate the “what does this mean?” messages before they happen. Support content frameworks that reduce repetitive tickets by up to 40% → Less “where do I find…” — more empowered users, fewer hand-raisers. Shared component logic that bridges product specs and real-world implementation → I don’t just design components — I make sure devs can build them right the first time.

• Product Strategy & UX Ops

  I work side-by-side with CPOs to turn product vision into scalable systems, aligned teams, and designs that ship with purpose. UX Ops Built for Scale, Speed, and Alignment. Rapid UX audits (no fluff — just signals, gaps, and next steps) → I don’t give you a laundry list — I give you a tactical roadmap. Redesigns of your most critical flows to boost activation and reduce churn → I fix the friction that kills growth and rebuild trust with your users. Responsive wireframes, final UI, and annotated flows ready for sprint → No waiting, no guessing — your team can ship tomorrow. Alignment frameworks I’ve used with CPOs to connect product, design, and roadmap strategy → I speak executive, design, and dev — and I make them all understand each other. Rituals + playbooks that get PMs, designers, and engineers thinking together → I install alignment into your process — not just your Figma files.

• DevEx & Documentation Infrastructure

  Most teams treat documentation like a checkbox. I treat it like a product. I build developer-facing systems that reduce support tickets, cut onboarding time, and eliminate the Slack ping chaos. Developer-focused UX docs, SDK quickstarts, and API integration guides. → I don’t write documentation — I build developer trust at scale. Internal Notion/Markdown-based hubs that scale with your team. → If your developers are confused, I’ll fix that — with systems, not PDFs. Design–dev handoff systems that stop Slack confusion and raise trust. → Turn scattered specs and Slack questions into clean, scalable, DevEx playbooks. Support content frameworks that reduce repetitive tickets by up to 40%. → Your API might be solid, but if your docs don’t work — I make them bulletproof. Shared component logic that bridges product specs and real-world implementation. → Saved dev teams hundreds of hours with docs they actually want to use.

• Developer Experience Is a Product. I've Built It.

  I don’t just write documentation — I build clarity at scale. → Docs are infrastructure, and I treat them like product — with structure, trust, and repeatable value. If your developers are answering questions your docs should, you’re already losing velocity. → I eliminate Slack confusion and create systems that let engineers focus on building — not explaining. I've built SDKs, API quickstarts, internal hubs, and full documentation ecosystems. → These aren’t one-offs — they’re scalable, adopted, and used daily. DevEx isn’t a nice-to-have — it’s the reason great products succeed. → I make sure your team’s internal experience matches your external promise. I’ve saved teams hundreds of hours and rebuilt trust through better docs. → Because when the documentation works, everything else moves faster.