Launch Video Library · Devtools · Launch · 2026

Command by Asana

Asana introduced Command, a product development system designed to align engineers and coding agents from plan to release.

What Asana shipped

Asana launched Command, a new planning and product development system built specifically for engineering teams. By bridging the gap between human engineers and coding agents, the platform aims to keep release forecasts current and surface risks before they become delays.

Shipping software requires managing decisions, specs, and dependencies alongside the code itself. This launch positions the tool as the central nervous system for that entire process, eliminating the need for constant status meetings.

How the motion works

When introducing a complex system like Command, pacing is critical to viewer comprehension. A motion designer could use a punch-in to move quickly from a high-level roadmap view down to a specific dependency or ticket. This rapid scaling helps the audience understand the hierarchy of information without losing their spatial orientation within the interface.

To emphasize the dual nature of human and AI collaboration—specifically engineers working alongside coding agents—kinetic-typography can be highly effective. Staggering the entrance of text elements on screen allows the eye to process complex capabilities, like automated release forecasts, one beat at a time rather than overwhelming the viewer with a dense block of copy.

Moving between planning views and release states requires seamless transitions to maintain momentum. A match-cut between a risk surfacing on an individual ticket and a leader's high-level dashboard aligns the problem with the solution visually. Easing these transitions with a swift acceleration and a long, smooth tail ensures the UI feels both responsive and grounded.

What to steal from it

  • Use sudden scale changes to establish hierarchy when showcasing dense product interfaces.
  • Stagger text animations to guide the viewer through complex product claims one beat at a time.
  • Match-cut between problem and solution states to build visual continuity across different UI views.
  • Pace the edit to give complex dashboards adequate hold time for viewer comprehension.

Want a video like this for your product?

Impractical cuts one from a single prompt — the same motion craft, in about twenty minutes.