Robust documentation regarding risks and potential mitigation plans can be an extremely helpful resource both within production and with respect to individual disciplines.

Despite differences in day-to-day and higher-level role responsibilities, production fundamentals stay largely the same across project scales and from developer- to publisher-side. Methods and approaches learned in the AAA space can be effectively applied to projects even at the student level if contextualized and re-interpreted properly.

A significant part of the publishing role lies in market research and product management, and it often falls to producers to sort out differences between those concerned with the bottom line and teams oriented more towards the artistic vision of a game.

Outdated or unclearly-deprecated documentation is a liability best mitigated by either a transparent and team-facing revision process or document retirement.

Feedback is only as helpful as it is traceable; all involved parties should have access to the status of distributed and received iteration requests at any given time.

Gained significant insight into the similarities and differences between production on the development side and production on the publishing side, which has vastly improved my ability to reason and communicate from both parties’ perspectives.

Confluence, Jira, PowerPoint, Excel, Flow, Asana, Box

My time at Warner Bros. was spent working closely with a production team of 3 on an undisclosed title. My day-to-day responsibilities included:

Compiling data-driven reports on key titles and the gaming market to guide strategic decision-making regarding product design and marketing

Presenting requested findings to Production, CPM, Finance, and subsidiary studio teams to inform relevant and current work

Reworking a critically-important spreadsheet that visualizes major project information to be more user-friendly and intuitive, and supporting upkeep and training up to the executive level

Analyzing reported risks and mitigation plans with a fine-toothed comb to ensure all potential project concerns are being addressed by studio-generated documentation

Creating and subsequently managing a Confluence tool that tracks iterative feedback across several streams, after identifying a lack of efficiency and transparency in how feedback was previously shared amongst teams

Supervising the periodic delivery of essential project documentation to keep all parties involved in the development and publishing processes up-to-date with the newest information

Pursuing late or missing deliverables as needed, and communicating statuses to the teams and individuals concerned

Writing and distributing notes and agendas for crossdisciplinary and external meetings and stand-ups