AI adoption is a studio practice, not a software rollout

Figma’s latest field notes point to team rituals—not tool access—as the real driver of useful AI adoption.

Name the recurring task

Find one low-risk workflow where AI can remove friction.

Make the context explicit

Document the brand, quality bar, and decision rules the tool needs.

Review together

Turn outputs into shared critique rather than private experimentation.

The Story

Figma’s October 10 field note looks beyond individual productivity and focuses on how teams at Figma, Sephora, Mercari, and Atlassian are building repeatable habits around AI. The useful shift is from “which tool should we try?” to “what team behaviour makes the tool valuable?” ([figma.com](https://www.figma.com/blog/ai/?utm_source=openai))

For Studio Wensday, that suggests treating AI as part of the studio operating system: a shared brief template, a defined review point, and a record of what still requires human judgement.

The practical move this week: choose one recurring task—content variants, research synthesis, or layout exploration—and turn it into a small, documented ritual before adding another tool.

Studio Wensday Angle

AI becomes more valuable when it is designed into the team’s habits, not bolted onto individual workflows.