AWS Deadline Cloud
Simplifying the Onboarding Experience
Reducing setup time and complexity for cloud-based rendering at scale
Project Overview
AWS acquired two powerful tools for the creative industry: Nimble Studio (cloud-based workstations) and Thinkbox Deadline (render farm management). However, smaller studios struggled to adopt Nimble Studio due to its complex and time-consuming setup, while Deadline’s deployment complexity significantly increased support costs.
To address these challenges, we built a new service AWS Deadline Cloud designed to meet the needs of both small and large studios.
The Problem
For small and mid-sized creative studios, getting started with AWS cloud rendering often feels overwhelming. The tools are built for DevOps teams, not artists so studios end up paying thousands of dollars in fees to cloud experts just to get set up, instead of focusing on their creative work.
Collaboration
- Worked with 12 back-end engineers, 2 front end engineers, 3 product managers, and 2 copywriters
- Aligned UX with AWS Cloudscape, AWS Identity Center (IAM), and cross-org studio tools teams
- Led validation rounds with in-house studio partner.
Design Process
Reseach findings
Define insights
Design opportunities
The design process wasn’t linear, I was tasked with merging two complex consoles into one cohesive render management console. The difficulty wasn’t just in the interface, it was aligning multiple teams, backend limitations, and user expectations, all while hitting aggressive monthly milestones.
Research
Methods Used:
- Reviewed customer user journeys (CUJs) and engineering vision
- Conducted pre-usability testing of existing Nimble Studio and Thinkbox services
- Conducted user interviews and analyzed support forums
Key Challenges:
- Lack of research team resources
- Mis-alignment between CUJs and engineering vision
- Cross-product integration complexity
Actions:
- Conducted a workshop with 12 cross-functional stakeholders to gain alignment
- Formed internal user focus group
Disclaimer: This is a free stock image used for representation purposes and does not violate any NDAs.
Findings
User Pain Points
Complicated identity setup
I felt like I needed to be a cloud expert before I could even begin.
Too much cloud setup
I just want to quickly create simple render farm without dealing with confusing cloud settings.
Storage setup complicated
I just want to temporary upload my files, render the job, and download the results without permanent cloud storage setup.
Define
Based on what we learned in research, I translated it into actionable strategy. Starting with problem framing, then defining key user roles, mapping their workflows, and shaping the UX approach around their needs.
How Might We
- How might we simplify onboarding to reduce deployment time and minimize support tickets?
- How might we integrate customization while keeping complexity hidden from non-technical users?
- How might we enable temporary file sharing for rendering without managing or retaining permanent cloud storage?
Design Goals
Reduce onboarding time by 60%
Reduce support tickets by 50%
Simplify user experience
Persona
Created persona and user stories
To guide feature prioritization and workflows
Used personas to align thinking
Across product, engineering, and documentation teams
Initial persona were too high-level with only role tittles and didn’t capture the differences in roles, goals, or pain points. I designed personas to help clarify:
Each role’s core responsibilities
Their touchpoints with Deadline Cloud
Their use of other tools (e.g., on-prem render managers)
The languages/scripts they used to customize pipelines (e.g., Python, Deadline APIs)
User Flow
Improved clarity and direction for the teams
Enabled engineers to design APIs, designers to begin portal work, and provided clarity for console design
Aligned stakeholders around feature sets and User Journeys
Improved alignment and clarity, accelerating progress and ensuring milestone achievement
Transitioned from user flows to visual mockups,
Helped drive progress and ensure milestone achievement
I initially started with low-fidelity mocks based on an early version of the vision document, which was still taking shape. As things progressed, it became clear we first needed to nail down the user flows to make sure everyone was on the same page. I worked closely with engineers and product managers to define those flows, and once we had that clarity, I translated them into visual mockups that helped keep us aligned and moving toward our milestones
Design
At first, integrating Deadline Cloud into Nimble Studio seemed simple but it was built for AWS experts, not creative teams. The setup was too technical and slow. I shipped an early version, then proposed a better UX strategy: a fail-safe onboarding flow that makes setup simple enough for non-technical users without losing AWS flexibility.
Before
Users were expected to think in AWS terms
Create a VPC, configure subnets, set up IAM roles, define policies, create S3 buckets... then maybe start rendering.
Layout added cognitive load
The horizontal layout presented too many tasks at once, overwhelming users with task they could understand.
After
Designed around the user's mental model
Task-based onboarding with smart defaults to quick start and full customization available later in the console.
Reduce cognitive load to improve task clarity
Adopted new AWS Cloudscape design system with simplified layouts, and clearer hierarchy to support faster user decisions and reduce training time.
Final Onboarding Design
Wizard-style approach
We adopted a wizard-style approach based on the customer's mental model, breaking onboarding into manageable steps. This allows users to focus on rendering without the complexity of AWS setups.
Watch Onboarding & Console Demo
Quick screen recording of the onboarding and console experience.
Customer’s Anecdote
"With AWS Deadline Cloud, we can scale render capacity up or down based on dynamic workloads and adjust capacity in minutes rather than hours. By off-loading undifferentiated work, we have been able to deploy seven times faster, giving us the ability to expedite our artists’ inventions so they can focus on creativity and bringing inspiring stories to global audiences."
Antoine Lhermitte
VP of Engineering at Animaj
Learning
What I learned:
- Design with scale in mind, AWS services bring many nuances like security and complexity that need careful attention
- Build strong partnerships with cross-functional stakeholders to bridge gaps
- Early alignment and clear communication make UX sign-off smoother
- Embrace trade-offs to create practical, user-friendly solutions
Other Projects
WEBSITE REDESING TO BUILD CUSTOMER'S TRUST
AllQuotes is an online service marketplace for home improvement projects that helps customers get their project quotes from the listed service contractors on the website.
E-COMMERCE MOBILE APP
Nanos Arte is an e-commerce store and turns kids' artwork into a personalized gift for family and friends to celebrate special days. An iOS mobile app helps the user design mockups before placing an order of their personalized gift.