Design Ops · Leslie's
Figma Transition
This was never just a software switch. I redesigned how the creative team builds, reviews, versions, and hands off work—then helped the new way of working stick.
Reusable components and a clearer workflow reduced production time.
The team could finally work from the same current files and libraries.
I designed the structure and the everyday habits that made it useful.
Every round created another version—and another place to look.
Creative lived in loose Adobe files. Feedback arrived through email, chat, and documents, so every review created more copies and more uncertainty. As more teams touched the work, nobody could quickly answer a simple question: which file is current?
I designed the workflow before I designed the library.
I mapped where work slowed down, then built a creative-operations system around those moments: shared files, reusable libraries, clear ownership, and a review rhythm the team could follow. The goal was not simply to launch Figma. It was to make the next project easier than the last.
Make the right choice the easy choice.
Reusable components replaced copied-and-pasted artwork, and shared libraries gave everyone the same current building blocks. Consistency no longer depended on someone catching every small mistake at the end.
The tool only worked once the team trusted the process.
I paired the files and components with simple working habits: where feedback belongs, how versions are named, when a file is ready, and who owns the next step. That turned Figma from a new tool into the team's day-to-day workspace.
The result was not just a cleaner file. It was a calmer way of working: faster production, fewer handoff gaps, and a system the team actually adopted.
