Skip to content
article

Figma fatigue is real: 6 things I stopped doing (and my developpers are happier)

Giulia Bellandi@giulia_designs

August 15, 2026 · 3 min read

I love Figma. I also have 34 tabs of Figma open right now and my laptop fan sounds like a Vespa. So, some things I stopped doing this year. Not a manifesto, just what worked for our team ✨

1. I stopped designing every state as a separate frame

Hover, pressed, disabled, loading, error, empty... times 3 breakpoints, times light and dark. That's how you get 400 frames for one form. Now: one component with variants for the states, and one page called "states" that shows each of them once. Developpers look at the component, not the screen.

2. I stopped making pixel perfect mockups for things that are mostly text

Settings pages, long forms, legal pages. I write the structure in a doc with the components named (TextField, Select, InlineError) and the developper builds it from the design system. If it looks wrong after, we fix it in the browser together. 20 minutes instead of 2 days.

3. I stopped naming colours by how they look

No more "Blue Light 2". Variables with modes: color/surface/card, color/text/secondary, with a light and a dark mode. When the code uses the same names (ours are CSS custom properties with the same path) handoff becomes almost boring. Boring handoff is the dream.

4. I stopped redlining spacing by hand

Auto layout everywhere, spacing from a scale (4, 8, 12, 16, 24, 32, 48). If a gap is not on the scale, it is a bug, in Figma or in code. Dev Mode shows the values, I don't draw little pink lines anymore. I miss the little pink lines a bit.

5. I stopped presenting finished designs first

I show ugly wireframes to engineers before I show pretty ones to stakeholders. Because the engineer will tell me "this list needs pagination, the API returns 10,000 rows" and the stakeholder will tell me "can the logo be bigger". Only one of these is useful in week 1.

6. I stopped trying AI "design to code" plugins on real work

Okay, I tried them. Three of them. The output looked like my design in a screenshot and was a disaster in the code: absolute positions, fixed widths, divs with click handlers, no focus states. Fine for a hackathon. For a banking app where people with screen readers need to move money? Boh, no. Maybe next year.

What did you stop doing? Tell me, I need more things to stop 🤌

Written by

Giulia Bellandi

Product designer in Milano ✏️ design systems, typography, and fighting for the 4px grid. Ex-agency, now in-house at a fintech. Pasta is also a design system.

Get the best of #figma_fatigue weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

7

Sign in to join the conversation.

Sign in to comment
Mariana Costa@mari_costa#3 in Figma Fatigue
Number 5 is so true. In our team we call it 'show the ugly first'. Engineers find the real problems, stakeholders find the logo 😂 I have a doubt about number 2: how do you handle the visual QA if there is no mockup? Who decides it is 'wrong'?
1 net votes
Giulia Bellandi@giulia_designs#1 in Figma Fatigue
Good question! We have a 15 minutes 'browser review' on every PR that touches UI, me and the developper, on a real phone. If it uses the design system correctly, most things are already right. Who decides? Me, but I am kind ahah
5 net votes
Elin Sjöberg@elin_pm#5 in Figma Fatigue
Number 5 saved one of our projects this spring. The pagination conversation happened in week 1 instead of week 6. Also I can confirm the Vespa noise, I hear it on every call.
2 net votes
Elif Korkmaz@elif_ships#8 in Figma Fatigue
Number 3, hocam. We aligned Figma variable names with our CSS token names and the 'which colour is this' Slack threads just stopped. And +1 to the AI plugin verdict, our try produced a button that was a div inside a div inside a div with an onClick.
1 net votes
Anoop Menon@anoop_flutter#8 in Figma Fatigue
Same with the Figma to Flutter tools machane, the generated widget tree is like 14 Containers deep. I have a whole post about it in my head, will write it 😂
2 net votes
Frieda Sommer@frieda_s#5 in Figma Fatigue
Thank you for number 6, this is a very important point. I audit apps for accessibility and the AI-generated code I see actually is mostly divs with click handlers. No keyboard access at all. It looks finished, and it is not usable for many people.
1 net votes
Giulia Bellandi@giulia_designs#1 in Figma Fatigue
Exactly!! 'It looks finished' is the dangerous part. Grazie Frieda 🙏
0 net votes