The rollout was scheduled for the following year.
August 2025: 0% adoption in digital production, Figma still a pilot, full transition planned for 2026.
A mandate would have been the fast route. I picked a different problem. If the new workflow demanded more explanation, more setup, or more coordination than the old one, then not adopting it was the rational choice and no amount of insisting would change that. So the work went into pre-populated templates, a shared workspace, and training sequenced around what people were ready for instead of a single launch date.
Adoption built through the busiest quarter of the year.
The measured curve: 0% in August, 21% in September, no measurement taken in October, 90% in November, 100% within digital production by early December.
Peak holiday ran straight through the middle of that. I will not claim the enablement work did it alone — the source notes say plainly that the pressure pulled people in. What I would claim is the timing: the workflow became usable enough to carry holiday at the moment holiday arrived, and that was not luck.
November's 90% is worth stating precisely, because the missing tenth is informative. It meant everything except repeat projects, and roughly half of those repeats had been rebuilt in Figma anyway. By Holiday 2025, branded promotional production was fully template-based — individual Photoshop builds with separate routing had become pre-populated templates in a shared workspace.
The percentage was never the signal.
A percentage tells me a tool is being used. It tells me nothing about whether the organization has absorbed it.
That answer came separately, when a cross-functional partner built her own colour-coded status system inside the Figma workflow. No training, no request from me, no permission asked. She treated the environment as something she was allowed to build in.
