Tooltips
For
Maya

Reducing friction in high-end VFX workflows through contextual guidance.

Role
Content Designer at Autodesk
Tools
Figma, Google Sheets
Timeline
1 month
Outcome
Tooltips to bridge the gap between legacy knowledge and new tech.
Living room scene created using Maya
01 —

The
Problem

The complexity gap.

The Context

Maya is the industry standard for 3D animation, but it is notoriously complex. With the release of LookdevX, we introduced a powerful new way to handle materials using USD (Universal Scene Description).

The Friction

While powerful, LookdevX introduced new workflows and terms that alienated users familiar with the previous workflow.

The Hypothesis

If users couldn’t understand the feature, they would abandon and revert to older, less efficient tools.

02 —

Research

Tooltips aren’t going to save a new user — but they can give a regular Maya user the right context at the right time.

User Analysis

I bypassed my assumptions and went directly to our internal beta forum and Reddit. I needed to understand:

  • How senior artists talk about materials
  • How junior artists are using terminology
  • Whether people are widely talking about USD yet
The Insight

Users didn’t need textbook definitions.

Textbook (before)
“This is a compound node.”

Functional (after)
“Groups nodes together to simplify your graph.”

They needed functional context — a knowledgeable colleague, not a manual.

LookdevX graph editor timelapse
03 —

Strategy
& Build

Designing for clarity.

Information Architecture

I audited every interactable element in the LookdevX interface. Working with the Product Owner, we established a clear strategy:

  • Obvious UI: Buttons that explain themselves (e.g., “Save”) get no tooltips — to reduce visual noise
  • Complex UI: Jargon-heavy elements get “helper” tooltips
Collaboration & Engineering

I worked directly with the engineering team to implement. Our developers were also users of the product, and had additional feedback that we incorporated.

I also ensured the tooltips aligned with the broader documentation I authored, creating a cohesive “help ecosystem” from the UI to the manual.

LookdevX in production
04 —

Impact

The Outcome

Since its release, the overall reception of LookdevX has been overwhelmingly positive. I am proud of the small part I had to play in bringing this feature to market.

By embedding the education directly into the interface, we reduced the need for users to leave Maya to search for answers.

Reflection

This project highlighted the importance of Content-First Design. Even though my role has since shifted into product design, I still use a content-first approach.

In complex software, the text isn’t an accessory — it is usually the primary interface.

A button is useless if the user is afraid to click it.

Next Project →