Migrations and Information Architecture

Context: Meta, Documentation Engineering Manager, 2022
Audience: Internal employees, documentation maintainers, and partner teams
Team: Four documentation engineers

This program moved product-documentation wikis into a central knowledge hub. One migration represented one product wiki. Each wiki contained approximately 3 to 80 pages. The work required content discovery, consolidation, information-architecture decisions, repeatable tracking, and coordination with Product Management, Engineering, and Release Management.

Program scale and results

I led a four-person team that migrated 101 product-documentation wikis across seven team groups. Those projects contained 1,157 source pages. After the team reviewed, archived, removed, combined, and restructured content, the destination set contained 469 pages, a 59% reduction in page volume.

My contribution

I led the four-person team and the department migration program. I created processes where none existed, coordinated with partner teams, documented the migration workflow, and helped make the work repeatable.

I also built migration tracking and content-discovery workflows that saved an estimated 150–200 hours of manual work.

Decisions and artifacts

Need	Response
Find source content and owners	Used content-discovery templates and migration tracking.
Reduce duplicate and outdated pages	Decided what to keep, merge, restructure, or retire before migration.
Show progress across teams	Reported product-wiki projects and page counts as separate measures.
Make later work repeatable	Created process guidance and training for the migration tracker.