Cast & Role Ideation

Ideation

Initial Framing

With the requirement provided by Product, we gathered together and framed the initial direction of cast and role.

Requirements

  • Person and Role are created as separate nodes.
  • There is a Cast Collection which connects Person and Role in the format of "[Person] as [Role]". It also has credit information, where brand can freely enter names and roles.
  • These collections can be connected to a content type, such as series, season, episode, and event.

Sketch of the Requirement and Initial Framing with Product

Ideation Session

Framing the problem

In the beginning of the session, we first introduced the participants to different variety of workflows and pain points regarding cast and role. Then we walked the participants through the users' journey, accompanied by the questions to be solved at each step. The questions were to guide the participants to think in the perspective of the users and ultimately solve the specific painpoints.

Click here to see the presentation deck for Cast & Role's ideation session.

Screenshot of Ideation Presentation Dock

Design Charrettes

Everyone in the session drew out and discussed their ideas regarding cast & role and its workflow with the group. At the end of the session, we voted for the best ideas and took photos for the record.

Voted ideas | number of votes

  • Cast collection embedded in context | 5
  • Create Cast collection within Season or Event context | 5
  • Ability to assign multiple roles per person | 2
  • Ability to create person (new tab) in context | 2
  • Ability to import cast collection from a different series, season, and episode | 1

Ideation Session Photos