zlacker

>>emilsj+(OP)
Has anyone else worked with teams where their entire idea of "product" was to create 100s of designs in Figma, and then just hand them to developers?

What started this mentality?

>>roflye+pc
What's worse is treating engineers like "just implement the mockup eyeroll" but then the logic of the mockup makes no sense with real data or product.

I'd rather have a napkin sketch that we can work on together vs throwing pictures over the wall.

As impressive as it is, I feel like Figma makes this situation worse. It's like "see we've figured it all out devs, look how nice this looks. No discussion needed"

>>gedy+Gl
I feel like that might be an organizational problem. At my company the designers will present their figma designs to engineering and we'll have a meeting to go through them and bring up concerns with exactly those sorts of issues e.g. "This list may actually have hundreds of entries in practice, are bullet points still right?". Then we iterate.

>>birthd+Ro
Took me years to finally push this culture. The designers no longer try to get away with designs that are too difficult (read: pricey) to achieve, and developers have to keep their skills sharp resulting in less blame and a more competent skillset. Then the designers and developers who thought it was part of the culture to never work together nicely were immediately noticed and shown the door.