design feels like one of the only creative professions where you can just blatantly not know how to use your tools, to the point of being successful and celebrated for how much ire you cause your coworkers

Counterpoint: Mastery of software like PS, Sketch or Figma in (virtual) product design doesn’t matter, and is myopic, because its output’s just facilitates discussion or document decisions—in high detail—for others (ENG) to build the darn thing from

I don’t organize and name my layers in Figma for the same reasons I don’t organize and name each section on a whiteboard: They’re immaterial stepping stones that output jpegs. (Design system & components is the exception since they’re an end in and of themselves)

A whiteboard is erased when youre done with it. A design file is not. That is not a good analogy.

A whiteboard is erased by necessity, but it doesn’t *have* to be—I’ll bet most orgs have a hundred un-deleted, years old Miro or FigJam boards at this point. And a design file, that’s kept around but unmaintained, is just cruft, and I bet this happens more often than the inverse.

This is a deflection that doesn't make your analogy make more sense or your argument any stronger. The point is that design files are not just vehicles for ideas that are going to be thrown away anyway; they are living, working documents that snapshot an interface in time.

Working documents that someday—be it tomorrow or in 2 years— will be used by someone else as the starting point for their work. It is courteous to make a file that isn't a shitshow of unnamed, unframed layers so that that person can get started quickly and easily.

I don't think that every file needs perfectly named layers—the name is relatively unimportant. But if you don't group things logically, use features like autolayout, or do otherwise make your file sanitary then you're doing a poor job.

Which leads back to the thought about being understaffed. In many situations, people don't have the luxury of scrutinizing craft because you only have 1–2 designers and hiring more is either very difficult or not an option.

What you’re describing is a messy workshop-problem, not an tool-incompetence problem. Chefs clean their workstation for next morning’s shift, not a potential 2-years-in-the-future-shift, or even a 2 week one. The “design” is the one that ships. Not the one imagined in Figma file

So long as any changes happening between a design file and shipping don’t flow back into the design file, the neatly organized file will always be a historic artifact that’s out of date

Think this is a good example. The reason you’d have to remake this is that it has no concept that it will need to be built in code and rendered on different screens. It’s not just a tidy thing, it’s an understanding the system that will be used to build it thing.

I understand where you’re coming from on this but I have to ask: — what # conversations did you have *in partnership* w engineering on this? — % o projects you explicitly followed up post-launch on whether the structure of your components in Figma matched that logic in code?

I ask because I’ve seen so much work in design orgs in anticipation of the perceived beliefs of how people further down a converter belt, or an okay understanding of code makes you think you know about code production. And it’s humbling how little design teach you about all that