Photo by Gilles Roux on Unsplash
Project Overview: Building the Playbooks, Onboarding, and Training Pipelines for a Growing Team
At Meta, as study demand surged, our research operation expanded from a handful of research assistants (RAs) to a team of twelve, alongside an external vendor team at a separate site. The primary bottleneck was not recruitment, but the fact that critical operational knowledge was siloed in a few people’s heads. I was tasked with establishing scalable onboarding, multi-site training protocols, and comprehensive documentation to make our workflows fully transferable and allow the team to scale.
My Role: Lead Research Assistant & Training Lead
As the designated training lead and documentation owner, I owned the problem of turning unspoken, individual expertise into a repeatable operational infrastructure. My responsibilities included:
- Designing and executing an end-to-end onboarding pipeline for internal Research Assistants.
- Leading multi-site training and enablement for both internal staff and the external vendor team.
- Rewriting and restructuring all protocol documentation to reflect real-world day-to-day execution.
Methodology & Execution: Immersive Training & Systemic Documentation
To build a resilient, self-sustaining training pipeline, I employed a hands-on, structured enablement methodology:
- Experiential Onboarding Progression: Designed a step-by-step pipeline where internal RAs experienced the session as a participant first, followed by structured shadowing, observed practice, and independent execution.
- Train-the-Trainer Architecture: Developed a senior RA’s capacity to lead subsequent onboarding, removing single-threaded dependencies and establishing localized troubleshooting capacity across sites.
- Immersive Vendor Training: Led on-site training and interactive practice sessions directly at the vendor facility, replacing passive documentation with active, hands-on guidance.
- Protocol Restructuring & Cleanup: Rewrote day-to-day documentation around the actual operational flow—covering setup, consent, tracker maintenance, and troubleshooting—while isolating legacy workflows into a separate reference guide to eliminate confusion.
Key Findings: Lessons in Operational Scale
This project yielded critical insights into how research operations actually break down and scale:
- Documentation fails at the seams, not the steps: Individual procedural instructions were mostly fine; new RAs got stuck on the small, unwritten things like housekeeping, access, and “what do I do when it goes wrong.”
- Participate in your own protocol: Having trainees experience the session from the participant side first surfaced structural friction points that no walkthrough could ever catch.
- Legacy instructions are toxic: Deprecated workflow steps are worse than missing ones; isolating old processes into a distinct reference manual kept active documentation clean and foolproof.
Outcome & Strategic Impact: Sustainable Operational Capacity
The new training architecture fundamentally transformed the team’s operational readiness and speed:
- Eliminated Knowledge Bottlenecks: Training capacity no longer depended on any single individual, enabling seamless team expansion across multiple locations and a rapid four-person onboarding wave.
- Standardized Reference Material: The documentation I authored became the permanent standing reference for this class of study across the organization.
- Accelerated Time-to-Independence: New RAs moved from onboarding to independent session management faster and with significantly higher operational confidence.
