What is Antro?
Antro is a 2.5D rhythm action platformer set in a stylised underground city pulsing with urban music. The player navigates layered environments, solves puzzles, and fights through a totalitarian regime, all synchronized to the beat of an original soundtrack.
The project had been in active development for three years before I joined. I was brought in during the final push to close out production and ship the game through Selecta Digital, one of Spain's leading indie publishers.
Joining a 3-Year Project in Its Final Sprint
Most producers join a project from day one. I joined Antro mid-final-sprint on a title that had been in development for three years. The team had established workflows, pre-existing dynamics, and a publisher deadline already in motion.
The challenge wasn't starting something new. It was integrating fast enough to immediately add value without disrupting a team that had been working together for years, while coordinating an external QA company and a publisher simultaneously.
What I Owned
I stepped into a team that had been building their own way of working for three years. Rather than imposing a new system, I mapped their workflow first, spending the first days understanding their communication patterns, Notion structure, sprint cadence, and interpersonal dynamics.
- Managed a cross-functional team of 10+ developers (programmers, artists, designers) through the final production phase and into certification
- Acted as the primary communication bridge between the Lead Producer and the full development team, translating strategy into daily execution
- Organised sprint planning sessions and milestone reviews to keep the team aligned on deliverables against the publisher timeline
- Developed a production plan for the Gold version, breaking the final months into trackable milestones and assigning ownership to each deliverable
I was the sole point of contact between Gatera Studio and the external QA company, managing the full bug pipeline from initial report through developer fix and final sign-off.
- Triaged incoming bug reports, assigning priority and ownership to the right developer on the same day they arrived
- Tracked resolution status in real-time, escalating blocking issues directly to the Lead Producer
- Wrote and maintained the bug-tracking workflow in Notion so QA, developers, and the producer could always see the same picture
- Ensured all critical gameplay issues were resolved before the Gold submission deadline
Beyond internal production, I handled the studio's external-facing communication, a responsibility that required discretion, clarity, and understanding of the publishing landscape.
- Managed the company's email inbox, reviewing and drafting responses to inbound publication offers and partnership enquiries
- Evaluated incoming offers against the project's current status and commercial goals, surfacing relevant opportunities to the Lead Producer with context and recommendations
- Maintained a professional tone across all external communication, representing the studio to third parties
Three years of development meant three years of accumulated documentation. I audited, restructured, and maintained the production infrastructure so the team could move fast in the final stretch without losing critical context.
- Reorganised the Notion production hub — separating active tasks from archived work and creating a clear milestone tracker visible to the whole team
- Updated Miro boards to reflect the current state of the project, removing outdated flows that were creating confusion
- Established a documentation standard for the Gold phase so any team member could find the status of any task without asking
Screenshots & Visuals
Shipped in 4 Months
Antro shipped on schedule — delivered to Gold through Selecta Digital within four months of me joining the project. A three-year development cycle closed out on time, with a 10-person team, an external QA pipeline, and a publisher relationship all running in parallel.
The key lesson from this project: late-stage production management is a distinct skill. It requires fast context-switching, high trust, and the discipline to not fix things that aren't broken, while still fixing the things that are.