Project ART
I Design Ops

Note: Details have been intentionally redacted for security reasons.

Made with:

About

Project ART is a custom-built Jira project with incredible capabilities. Taking complete advantage of automations; the project is a ground-up re-imagining, with a laser-focused aim – to efficiently manage active work on hundreds of contents pieces, shared among a team of 15+ members. It’s developed with a sharp focus on UX and project management, that streamlines the entire end-to-end production pipeline, with cascading automations that keep everything automatically updated without errors.

Background

Previously, the workflow was organized very differently;

Checks > Creating tasks manually > Content / Visual > Manual upload/localization.

 

This introduced many areas of conflicts and wide potential for duplicated tasks, due to the manual nature of it.

Our Approach to Problem-Solving


  • Focus on small systems that build bigger systems.
  • Prioritizing solutions that are procedural in nature and solve multiple problems.
  • Safeguard and account for possible future permutations resulting from the system.

 

Systems that talk & feedback.

Our Solution

Predict

(Information)​

Automate

(User Behavior)

Centralize

(User Behavior)

For a user-centric approach – to make it simple for the end user, there is a lot of complexity and ingenuity that needs to happen at the backend. 

 

Our simplest logical path was this:

Checks > Content / Visual > Sent for upload / localization 

 

To make this above ring true for a team of 15+ is where the complexity comes in. 

Taking our approach into account, we devised two fronts to tackle this challenge:

  1. Logically divided Issue types
  2. A series of inter-linked automations that breathed life into the system and reduced manual work to zero.

Supporting mechanisms

A good system needs approachable ways to interact with it, to support it. This is where our Jira dashboard based on Rich Filters, and a Structure for reporting came into play. Both of these provided touch-points to easily search and look up issues, the information relating to SLA and Team-wide stats were made available via the Structure.

 

Previous to this; we had extensive experience in creating automated inventories via Google Sheet, so this background provided us with key insights that were used to better the end product further.

Documentation & Roll Out

A system is not functional if nobody knows how to use it. The last stage was preparing extensive documentation for various teams (Internal & External), so people were comfortable with it. The roll-out itself happened over three stages, with each one bringing in more people into the project. Over the course of three weeks, the transition was complete.

Credits

Madina Berkenova

Mohit Sebastian