Scaling Self-Serve Support: Global Documentation Overhaul, Optimization & Localization

Support Scalability & Self-Serve Operations

Cross-Functional Program Leadership
Self-Serve Systems
Documentation
Localization
Scalability
AI-Accelerated
Product Use Cases
Cross-Functional
Global Operations

New user-focused self-serve flow, AI augmented search and content optimization
The Challenge
User documentation was fragmented, outdated, verbose, and inconsistently localized — impacting support load, onboarding, retention, and global adoption in a fast-growing platform.
Goal & Objectives
My Role & Approach
Owned the full documentation lifecycle: conducted audits, rewrote content for clarity and UX, defined writing and UX standards, coordinated with product/engineering/design/marketing/localization teams, planned short term English migration and long term non-English migration to a unified URL standard. Influenced cross-functional alignment without direct authority by demonstrating operational impact through draft availability for multiple pre-launch purposes.
Key Deliverables
Results & Impact
Key Learnings
Self-serve support scales only when documentation is treated as a living system with governance, metrics, and cross-functional alignment. Localization must be built-in from the start, not bolted on.
Tools & Technologies
GitBook, GitHub, Notion, Google Workspace, Slack, Figma
Collaboration Highlights
Partnered with developers (technical accuracy), designers/marketing (creative examples), localization leads (multi-language standards), and product owners (release sync) — aligning diverse stakeholders around shared self-serve and scalability goals.

Broader documentation rearchitecture and localization plan

Unified site for general users, sub section for creators with comprehensive technical and creative guidance

Old documentation (six URL structures in English, multiple multilingual URLs)

Release-aligned updates with user-focused design, change management support, and localization
Scaling Self-Serve Support: Global Documentation Overhaul, Optimization & Localization

Support Scalability & Self-Serve Operations

Cross-Functional Program Leadership
Self-Serve Systems
Documentation
Localization
Scalability
AI-Accelerated
Product Use Cases
Cross-Functional
Global Operations

New user-focused self-serve flow, AI augmented search and content optimization
The Challenge
User documentation was fragmented, outdated, verbose, and inconsistently localized — impacting support load, onboarding, retention, and global adoption in a fast-growing platform.
Goal & Objectives
My Role & Approach
Owned the full documentation lifecycle: conducted audits, rewrote content for clarity and UX, defined writing and UX standards, coordinated with product/engineering/design/marketing/localization teams, planned short term English migration and long term non-English migration to a unified URL standard. Influenced cross-functional alignment without direct authority by demonstrating operational impact through draft availability for multiple pre-launch purposes.
Key Deliverables
Results & Impact
Key Learnings
Self-serve support scales only when documentation is treated as a living system with governance, metrics, and cross-functional alignment. Localization must be built-in from the start, not bolted on.
Tools & Technologies
GitBook, GitHub, Notion, Google Workspace, Slack, Figma
Collaboration Highlights
Partnered with developers (technical accuracy), designers/marketing (creative examples), localization leads (multi-language standards), and product owners (release sync) — aligning diverse stakeholders around shared self-serve and scalability goals.

Broader documentation rearchitecture and localization plan

Unified site for general users, sub section for creators with comprehensive technical and creative guidance

Old documentation (six URL structures in English, multiple multilingual URLs)

Release-aligned updates with user-focused design, change management support, and localization
Scaling Self-Serve Support: Global Documentation Overhaul, Optimization & Localization

Support Scalability & Self-Serve Operations

Cross-Functional Program Leadership
Self-Serve Systems
Documentation
Localization
Scalability
AI-Accelerated
Product Use Cases
Cross-Functional
Global Operations
Key Learnings
Self-serve support scales only when documentation is treated as a living system with governance, metrics, and cross-functional alignment. Localization must be built-in from the start, not bolted on.
Tools & Technologies
GitBook, GitHub, Notion, Google Workspace, Slack, Figma
Collaboration Highlights
Partnered with developers (technical accuracy), designers/marketing (creative examples), localization leads (multi-language standards), and product owners (release sync) — aligning diverse stakeholders around shared self-serve and scalability goals.

Broader documentation rearchitecture and localization plan

Unified site for general users, sub section for creators with comprehensive technical and creative guidance

Old documentation (six URL structures in English, multiple multilingual URLs)

Release-aligned updates with user-focused design, change management support, and localization

New user-focused self-serve flow, AI augmented search and content optimization
The Challenge
User documentation was fragmented, outdated, verbose, and inconsistently localized — impacting support load, onboarding, retention, and global adoption in a fast-growing platform.
Goal & Objectives
My Role & Approach
Owned the full documentation lifecycle: conducted audits, rewrote content for clarity and UX, defined writing and UX standards, coordinated with product/engineering/design/marketing/localization teams, planned short term English migration and long term non-English migration to a unified URL standard. Influenced cross-functional alignment without direct authority by demonstrating operational impact through draft availability for multiple pre-launch purposes.
Key Deliverables
Results & Impact

Becky Lattof
Operations Program Manager
Systems & Enablement
Scaling Self-Serve Support: Global Documentation Overhaul, Optimization & Localization

Support Scalability & Self-Serve Operations

Cross-Functional Program Leadership
Self-Serve Systems
Documentation
Localization
Scalability
AI-Accelerated
Product Use Cases
Cross-Functional
Global Operations
Key Learnings
Self-serve support scales only when documentation is treated as a living system with governance, metrics, and cross-functional alignment. Localization must be built-in from the start, not bolted on.
Tools & Technologies
GitBook, GitHub, Notion, Google Workspace, Slack, Figma
Collaboration Highlights
Partnered with developers (technical accuracy), designers/marketing (creative examples), localization leads (multi-language standards), and product owners (release sync) — aligning diverse stakeholders around shared self-serve and scalability goals.

Broader documentation rearchitecture and localization plan

Unified site for general users, sub section for creators with comprehensive technical and creative guidance

Old documentation (six URL structures in English, multiple multilingual URLs)

Release-aligned updates with user-focused design, change management support, and localization

New user-focused self-serve flow, AI augmented search and content optimization
The Challenge
User documentation was fragmented, outdated, verbose, and inconsistently localized — impacting support load, onboarding, retention, and global adoption in a fast-growing platform.
Goal & Objectives
My Role & Approach
Owned the full documentation lifecycle: conducted audits, rewrote content for clarity and UX, defined writing and UX standards, coordinated with product/engineering/design/marketing/localization teams, planned short term English migration and long term non-English migration to a unified URL standard. Influenced cross-functional alignment without direct authority by demonstrating operational impact through draft availability for multiple pre-launch purposes.
Key Deliverables
Results & Impact