Rebuilt from the original reporting format with fictional data — the real figures are internal.
Project Overview: Turning Four Months of Raw Data Into an Actionable Roadmap
At Meta, following the conclusion of a major 18-week data collection, leadership needed more than a simple “we finished” announcement. They required a defensible, front-line account of the effort’s true costs and outputs, while our planning team needed clear guidance on what practices to replicate and what to eliminate. I owned this retrospective end to end, transforming raw session logs and survey responses into rigorous reporting visuals and a structured team debrief that produced an explicit carry-forward action list.
My Role
Operating as the lead Research Assistant and project manager for the wrap-up, I owned every phase of the retrospective process—from data hygiene and visualization architecture to stakeholder delivery:
- Defining core metrics and reconciling overlapping operational figures.
- Cleaning and auditing master session trackers across complex participant populations.
- Designing a cohesive visual reporting system and synthesizing qualitative survey data.
- Facilitating the live team debrief and tailoring deliverables for different internal audiences.
Methodology & Execution: Data Wrangling, Visualization, and Synthesis
To deliver a transparent, actionable account of our four-month effort, I employed a rigorous analytical framework:
- Metric Standardization: Defined and reconciled overlapping figures—such as the roughly 20% gap between participant session time and actually captured data due to setup and consent overhead—to ensure cross-slide consistency.
- Data Cleaning & Auditing: Audited master session trackers by removing dropped rows, resolving blank attribution cells, and aligning session counts across three distinct participant populations.
- Custom Data Visualization: Designed eight charts within a cohesive shared design system, including a custom polar staggered-coverage ring to effectively visualize a phase where Research Assistants began at offset positions.
- Qualitative Synthesis: Collected input through dedicated surveys for on-site staff and the vendor team, synthesizing findings with lead-RA observations while strictly tagging themes by source to separate raw feedback from interpretation.
- Audience-Scoped Reporting: Recognized that broad organizational announcements required a different lens than tactical planning insights, building two distinct versions rather than a single compromise.
Key Findings: Lessons in Retrospective Design
This project yielded critical methodological takeaways for how I approach operational reporting:
- Small-n qualitative data must be presented as themes, not statistics: With only five total survey responses, percentages would have been theater, and direct quotes would have risked re-identification in a close-knit team. I paraphrased throughout.
- Audience scoping is part of the deliverable: Material that is genuinely useful to a planning team is often unhelpful as a broad organizational update. Tailoring the format to the consumer is essential.
- Highlight mid-flight adaptations: A retrospective that only lists complaints hides the team’s own agility; calling out fixes we’d already implemented mid-collection proved invaluable for future planning.
Outcome & Strategic Impact: Strategic Clarity
The retrospective delivered immediate clarity and shaped future organizational strategy:
- Defensible Transparency: Provided the broader organization with its first concrete, hour-by-hour and session-by-session picture of the collection’s true operational footprint.
- Actionable Roadmap: Equipped planning teams with a ranked carry-forward list of operational recommendations, explicitly highlighting adjustments that had already been successfully validated mid-flight.
