Identity and Access Management


Identity and Access Management (Video)


Lisa Kaiser and Mina Adame
Role: Lead Visual Designer


IBM was preparing to launch a new business framed focused entirely on Identity and Access Management (IAM). Our team was asked to help produce an animated video to inform users of IAM without overwhelming them. Users need high-level information about IAM to increase new feature adoption and reduce support tickets.


Prior to working with this team, I didn’t know anything about IBM Cloud Identity Access Management. Along with our researcher, I spent a lot of time talking to users to better grasp the concept and framework. Fundamentally, IAM is a complex framework with the following components:

  • How individuals are identified in a system.

  • How roles are identified in a system and how they are assigned to individuals.

  • Adding, removing and updating individuals and their roles in a system.

  • Assigning levels of access to individuals or groups of individuals.

  • Protecting the sensitive data within the system and securing the system itself.

PROCESS of storyboarding

As a team, we storyboarded ideas by pulling out important and interesting points to help inform our users. Breaking the video up scene-by-scene helped us visualize how everything would come together. It was a chance to work out inconsistencies in the story and edit out any scenes that don’t make sense before you started animating. Storyboarding helped us identify:

  • The setting of our story.

  • The theme of the video.

  • Key concepts and graphics.

  • When the key concepts or graphics appear on the screen.

  • Sequencing of the story.

  • The length of the video.

Establishing a story: The first thing we had to do was develop a rough draft of our story. What was our video about? What did we want to communicate? The script became our plan and the foundation for our video. Since videos require more of users’ time than text, we spent a lot of time making sure that the video was clear, concise, and communicated a well-defined message. We used a simple Box note document to keep track of script iterations.

Sketching the scenes: I did quick hand-drawn sketches to speed up the process and help us figure out if our ideas would work. My goal was to accurately show what’s happening in the scene as clearly as I could.

Making notes to the script: As we started to sketch and refine our script, we added detailed notes about what’s happening on each screen.

Illustrations: To spice up the experience I designed the illustrations for the video. My challenge was to create visuals that were simple enough to convey the message, but serious enough to illustrate the topic.

Animation: With the animation, it was important to keep everything simple and clean. Working with our motion graphics designer, we were able to bring our concepts to life and visually represent our ideas.

Accessibility: Accessibility played a huge role in writing and designing this video. We knew that providing content as a video can limit access to the information for anyone who cannot see or hear the content. For accessibility, captions and a full transcript of the video are provided.

What I learned

Creating a storyboard helped us work out the kinks in our project before we started, which saved us valuable time. It also helped us craft a better, tighter story.

Fine grained access control is now available in IBM Cloud. See how assigning policies works from a resource group to a single resource or instance. To learn more, visit: