ESRB.org
Project Management, Production
Overview
Identity
ESRB is the non-profit, self-regulatory body for the video game industry. Established in 1994, their primary responsibility is to help consumers— especially parents—make informed choices about the games their families play.
Core Activities
WordPress Backend, SOAP Integration, Quality Assurance.
The Ask
ESRB was well known for their ratings on physical copies of games but their online presence and database needed a revamp.
Areas to solve for:
➤ Visually outdated
➤ Search was not user friendly
➤ Outdated information
➤ Content did not speak to target audience/tried to speak to all audiences
➤ Tight turnaround
Solution
Crafting a visual story that served to inform parents and users alike in a fun way while prioritizing ease-of-use.
Implementing more imagery and interactive elements enhanced the visual storytelling while staying true to the brand’s fundamental key objective of informing consumers. Updating the interface to allow users to share information, access retailers, and make informed decisions based on their preferences was the key to success in making sure they felt understood and making the brand more approachable.
Rating Guide
Parental Controls
Advanced Search
Methodology
Tight turn arounds often demand agile methods.
This project required simultaneous development, testing, Quality Assurance, and deployment. Although the website was launched all at once, templates were crafted and then tested for both backend and frontend best practices, once initial testing got done, pieces were then ran by the client, feedback was implemented, and then the final code was deployed to a private “production” environment.
Project Management
We used a sprint framework to push iterations forward. Each sprint culminated in a milestone meeting that then opened up the doors for client review & feedback—the complexity of each sprint decreased, so we tackled the heaviest items first, including the foundation for the SOAP integration.
Production
I populated content while simultaneously performing QA. Population happened in a WordPress CMS backend using Advanced Custom Fields tailored specifically to each template + any syncing that needed to happen due to integrations.
Quality Assurance
QA was coordinated in a siloed manner (internal vs. client) and kept under a strict timeline. Prioritization, browser and device testing, and key functionality were all reviewed at this stage.
Let’s Connect
Schedule me for an interview and we can chat more about this project!