GDT Table & Rights Management — Ideation Session

Ideation Session

We engaged in an ideation session with members of the Product and Engineering teams in order to generate ideas and solutions to create a content registration workflow for the MVPD GDT Table & Rights Management. By framing the problem at hand and encouraging the group to use divergent thinking, we all came up with great insights.

Contents

Requirements

We collected requirements from the brands gained during our discovery sessions as well as from the Product and Engineering teams.

Requirements we identified from our research for GDT table, log of changes, and rights management.

Ideation Session

Framing the problem

At the beginning of the session, we introduced the problem that GMO is trying to tackle - TKX replacement and our effort to move away from vendor services. We explained the significance of the GDT table and the rights spreadsheets in the authentication and authorization process our customers go through when accessing one of our video experiences. We also presented current workflows of how Content Distribution, the Affiliates group, and GMO interact in order to get information and update these tables. Current workflows were shown to highlight the pain points users face when trying to update these tables through vendor services. We shed light on why building the GDT table and rights spreadsheets into MVPD Admin would be of value. Requirements were given to the participants in order to guide their thought process during the multiple rounds of ideation.

Click here to see the presentation deck from ideation session for content registration.

Screenshots from our Ideation Presentation Deck

Design Charrettes

In the ideation session, everyone sketched and/or listed their ideas for the MVPD GDT table & rights management in low-fidelity wireframes. There were three rounds of Charrettes with the last round consisting of working in pairs. After each round, we discussed all the ideas from the group. 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.

Ideas/Features Generated From Ideation

  • A | Specifying policy type when adding a new policy - either retrans or blacklist
  • B | Sharing changes with other people from the log
  • C | Importing existing Excel sheets
  • D | Logging user who created and last updated a policy
  • E | As an MVP, the workflow of creating a policy will be agnostic to creator and approver - the UI will have one view where the creator can both save and publish
  • F | Clickable filters (i.e., clicking a partner and adding a filter)
  • G | Log updates shows user comments like a conversation
  • H | “Consumer Msg” and “Log” are two separate columns in the table
  • I | When adding a new policy, the user will have the ability to add notes/comments and custom error message
  • J | 1:∞ mapping of station to MVPDs - there can be many MVPDs that map to one call sign
  • K | An e-mail will be automatically sent when a policy is published out
  • L | Ability to add a “Brand” column for brand-specific rules and a “Policy Name” column
  • M | 70:30 ratio of table to log side panel
  • N | Ability to toggle between retrans and blacklist under one Rights Management page
  • O | “Last Updated” column launches users into the log of changes for that specific policy