Design system consumer shadowing by Alice PackardDesign system consumer shadowing by Alice Packard
Design system consumer shadowingAlice Packard
Sometimes you don't know what you don't know. If your team is up for it, I will shadow them to better understand where they could level up their use of Figma. Here's how the process works:
I'll schedule a 1 hour call with the designer OR they can send me a 1 hour screen recording of them doing heads down work in Figma. If we do this live, I will be camera off/on mute the entire time. Just observing and taking notes. The number of designers I do this with will influence the timeline and price.
I'll do the same thing as step one, but with a developer who is referencing that same designer's Figma file in their dev work.
I'll process my notes, looking for larger patterns and recurring themes across multiple designers and devs.
I'll create a report to share my findings with you and your team. Depending on everyone's comfort levels this can be fully anonymized. The benefit of deanonymizing the findings means more frank conversations can be had. The point is to share real examples of how folks work and expect to work, not shame anyone for having an imperfect workflow (all workflows are imperfect).

What's included

Report
I'll detail 👉 weak points in designers workflows where they're wasting time or risking errors 👉 weak points in developer's understanding of design files 👉 suggestions for improvements and education areas for both designers and developers
Contact for pricing
Tags
Figma
Design Systems Specialist
Service provided by
Alice Packard District of Columbia, USA
Design system consumer shadowingAlice Packard
Contact for pricing
Tags
Figma
Design Systems Specialist
Sometimes you don't know what you don't know. If your team is up for it, I will shadow them to better understand where they could level up their use of Figma. Here's how the process works:
I'll schedule a 1 hour call with the designer OR they can send me a 1 hour screen recording of them doing heads down work in Figma. If we do this live, I will be camera off/on mute the entire time. Just observing and taking notes. The number of designers I do this with will influence the timeline and price.
I'll do the same thing as step one, but with a developer who is referencing that same designer's Figma file in their dev work.
I'll process my notes, looking for larger patterns and recurring themes across multiple designers and devs.
I'll create a report to share my findings with you and your team. Depending on everyone's comfort levels this can be fully anonymized. The benefit of deanonymizing the findings means more frank conversations can be had. The point is to share real examples of how folks work and expect to work, not shame anyone for having an imperfect workflow (all workflows are imperfect).

What's included

Report
I'll detail 👉 weak points in designers workflows where they're wasting time or risking errors 👉 weak points in developer's understanding of design files 👉 suggestions for improvements and education areas for both designers and developers
Contact for pricing