Ideation — Ingest & Prep Workflow

Ingest and Prep Workflow Ideation Session

We held an ideation session with our UX team in order to generate ideas and solutions for the Ingest and Prep workflow. By framing the problem at hand and encouraging the group to use divergent thinking, we all came up with great insights that will help in the design process.

Problem Statement

Program operation managers need a new Translator interface that transfers their complicated production delivery and QC workflow into a simple and easy one to promise the on-time delivery of high-quality content and create more accountability.

User Persona: Program Operations Manager

Role

  • This user manages the delivery of content by recording delivery dates and making sure is ready in time

  • Conducts quality control and records what needs improving

  • Requests technicians to fix content on specific assets

  • Marks all edits as completed until none left so content can deliver

  • Communicate back and forth with technicians to fulfill the request

Needs

  • Needs a way to add multiple edit request on different asset versions

  • Needs to tag technicians

  • Needs ability to mark an edit as completed or not needed

  • Needs ability to create new edits

  • Needs organization of edits based on priority -> delivery date

Pain Points

  • Currently there is no way to view the edit request without going into the comments of google docs - is hidden

  • No way to flag priority

  • Too much checking/unchecking/mouse clicks

  • No easy way to assign specific users edit requests

  • No permissions - anyone in google doc can edit anything

Requirements

We compiled preliminary requirements based on our research findings from the three discovery sessions and collaborating with the product team members.

  1. Assets represented in view; Edits are tied to an asset

    • Can do more then one edit with same metadata except different timestamp

  2. Ability to bulk edit edits

  3. Ability to tag technician

  4. Required fields for edit:

    • Edit Name

    • Timestamp(s)

    • Fix file name

    • Description

    • Comment thread

  1. Ability to add multiple notes/edit request in one note i.e. for one file

    • Because most metadata will be the same except for timestamps

    • “+” at the end to add more edits with the following metadata: Fixname (file name); Timecode of when it is; What fix is; Comments (optional)

  2. Move “status” section in notes/edits section

  3. Stronger indicator that the GMO ID is the source file name

    • Remove source file from note/edit form

  4. Copy and paste edit requests

Ideation Session

Design Charrettes

In the ideation session, everyone sketched and/or listed their ideas for the Ingest and Prep workflow. There were two rounds of design charrettes with the first one being an individual round and the last round being pair-up with a partner. After each round, everyone presented their ideas and we held group discussions about the strongest points. At the end of the session, we were given three stickers to vote for the solutions we felt strongly about. The final results are listed below.

Annotation from Photos | Ideas (number of votes)

  • A | Header with summary & pipeline visualization (3)
  • B | Checkbox on asset level to edit (1)
  • C | Pop-Up with edits per asset (3)
  • D | Sidebar with bulk actions menu; possibly extra metadata is only one asset selected (1)
  • E | Duplicate an edit button/icon (1)
1 / 8
2 / 8
3 / 8
4 / 8
5 / 8
6 / 8
7 / 8
8 / 8