01 / RIOT GAMES
FROM DOCUMENTATION TO PUBLISHING OPERATIONS
How an initial three-month documentation assignment grew into 18 months of building knowledge systems, adapting processes across multiple game teams, and improving publishing workflows.
ROLE
Project Manager, Publishing Operations II - Documentation
TIMELINE
September 2024 – March 2026
PRODUCTS
Teamfight Tactics · League of Legends · VALORANT · Riftbound
FOCUS
Knowledge Systems · Program Management · Process Design · Workflow Optimization
THE CHALLENGE
Knowledge existed. A shared system didn't.
I initially joined Riot to support Teamfight Tactics as the team moved its publishing knowledge into Notion. Important information existed across legacy documentation, individual workflows, and the people who knew how things worked — but there wasn't one reliable place for someone to understand the bigger picture.
The immediate ask was documentation. The larger opportunity was figuring out what knowledge the team actually needed, how people would use it, and how to build something useful enough to become part of the way they worked.
LEGACY DOCS + TRIBAL KNOWLEDGE + INDIVIDUAL WORKFLOWS → SHARED KNOWLEDGE SYSTEM
MY APPROACH
Start with the people doing the work.
Before building anything, I talked with producers and craft leads about how they worked, where information was getting lost, what made onboarding difficult, and what they wished they'd known when they joined.
Those conversations shaped both what needed to be documented and how the information should be organized.
DISCOVER → DIAGNOSE → DEFINE → DESIGN → BUILD → ITERATE
The goal wasn't to create more documentation. It was to make the right information easier to find, understand, and actually use.
01 - BUILDING THE FOUNDATION
Teamfight Tactics
I interviewed roughly 8–10 producers and craft leads to understand onboarding gaps, recurring questions, existing resources, and the knowledge people were carrying with them day to day.
From there, I built a centralized Notion knowledge hub with roughly 50+ pages and resources spanning onboarding, playbooks, runbooks, key processes, and frequently used references.
The result wasn't just a documentation library. It became a practical onboarding and reference environment for the team. One returning teammate even shared that the hub helped refresh how the team worked and made coming back easier.
02 - SCALING WITHOUT COPY + PASTE
League of Legends and VALORANT
After the TFT hub was established, I began supporting League of Legends and VALORANT simultaneously.
The challenge was that the teams operated very differently — and in some cases, the need itself wasn't clearly defined yet. Rather than duplicating what worked for TFT, I worked with each team to understand its immediate gaps and determine what could be shared versus what needed to remain product-specific.
Some practices and documentation could become reusable foundations. Others required completely new runbooks and workflows.
It shifted the question from “How do we replicate this?” to “What should be consistent, and what needs to work differently here?”
03 - OPERATING THE PROGRAM
Making the work visible
As the work expanded across teams, I also needed a simple way to keep stakeholders aligned on what was being explored, built, reviewed, and completed.
I used a lightweight documentation pipeline and shared weekly updates so partners and leadership could quickly understand where work stood.
INVESTIGATING / INTERVIEWING → IN PROGRESS → STAKEHOLDER FEEDBACK → APPROVED → ADDED TO NOTION
That structure gave the work enough visibility to move forward without creating another complicated process to manage.
04 - ADAPTING THE SOLUTION
Riftbound
Riftbound presented a different problem. The team was actively building while delivering, and creating more documentation wasn't necessarily the highest-value use of the time I had with them.
So I went back to the same starting point: listen to the people doing the work.
Conversations with Production and Operations surfaced friction around partner communication, how work was being submitted, and the amount of manual coordination required internally.
Instead of building another knowledge hub, I helped design and implement Slack and Airtable automations to streamline parts of those workflows. I partnered with stakeholders through prototyping, testing, feedback, iteration, and rollout until the solution was ready for broader use.
LISTEN → IDENTIFY FRICTION → PROTOTYPE → TEST → ITERATE → LAUNCH
The solution changed because the problem changed.
THE TAKEAWAY
The best process isn't always more process.
TFT needed stronger knowledge infrastructure. League of Legends and VALORANT needed adaptations rather than copies. Riftbound needed less documentation and more workflow optimization.
Across each team, the approach stayed consistent: understand how people actually work, identify what's creating friction, and build only as much structure as the problem needs.
What started as a three-month documentation assignment ultimately became an 18-month engagement spanning knowledge systems, process design, program management, and workflow improvement across multiple Riot teams.