Content Architecture Mapping

Overview

UX content isn't just writing. It's structure. When your help center contradicts your onboarding flow, when three teams are writing the same thing in different words, when users can't find the answer that definitely exists somewhere, that's an architecture problem, not a content problem.

I help product teams design scalable content frameworks that support onboarding, education, and conversion across platforms. I bring the same systems-thinking approach I use to build learning hubs, maturity frameworks, and AI skill libraries (340+ and counting) to your content architecture. The goal is a system that scales without someone manually maintaining every page.

I've structured content across onboarding flows, help centers, and educational platforms, including multi-region localization at B Lab across four global regions. Whether you're building from scratch or untangling years of organic growth, I help you see the system and design it intentionally.

Who this is for

This works well when you're:

• A product team launching a new onboarding experience and needing to structure the content layer before design starts
• A company with a help center that's grown organically and now contradicts itself across pages
• A team preparing for localization or multi-market expansion and realizing your content isn't structured for it
• A startup building educational content (courses, guides, knowledge bases) and wanting a scalable framework from the start
• A product leader who knows the UX writing is inconsistent but isn't sure where to begin fixing it

If you need the content itself written, Content for Thought Leadership covers narrative content. This engagement is about designing the system that content lives in.

What you get

1. Content audit. A structured review of your existing content across surfaces (app copy, help center, onboarding, emails, tooltips). I map what exists, what's redundant, what's missing, and what contradicts itself.
2. Content architecture map. A visual and written framework showing how your content should be organized: taxonomy, naming conventions, reusable components, and information flow across surfaces.
3. Style foundation. Lightweight content guidelines tailored to your product (tone, terminology, formatting patterns) so your team can write consistently without checking in every time.

Typical engagement

• Duration: 2-4 weeks
• Commitment: 10-15 hours total (audit, mapping, documentation)
• Format: Remote, with async deliverables and 1-2 working sessions