Why Figma Wins
11–20 of 191 posts
Re: Why Figma Wins
#12Software solutions will never fix problems that are caused by people.
Sketch, Figma, whatever the next design tool is. Google Docs, Quip, Notion. Trello, Pivotal Tracker, GitHub/ZenHub, Jira. I've gone through tool-switching fatigue with all of the above. Sometimes it doesn't matter much, other times it bogs us down with metawork for months as you figure out which features you gained, and more importantly, lost.
Back to design. I have seen design die the same way every time. Product misuses design resources, effectively making them contractors that hammer out one-off pieces of work. Those pieces of work get nitpicked by some vocal minority holding a lot of clout, until the end result violates the framework that the designer created.
This frustrates everyone over time.
Designers are frustrated because the systems they built are ignored.
Engineers are frustrated because they are adding new debt with every designed feature that has to rebuild parts of the world to make exceptions to systems work.
Product is frustrated because they just don't get why things are slow after they delivered a clear design to the engineers.
Let it all build up and people will start leaving your company.
So yes, use Figma if it suites your company well. If you're reaching for it because your team is frustrated, maybe consider digging into that more before you swap out yet another piece of software for all the wrong reasons.
Re: Why Figma Wins
#13The standard trend in enterprise software is towards oligopoly, with a few strong incumbents that struggle to actually kill one another as their products converge over time. Most enterprise businesses focus primarily on sales/marketing as they grow, rather than doubling down on a product that can kill incumbents. The fact that Figma has done both is really impressive and as an enterprise product head definitely something that I admire.
Re: Why Figma Wins
#14Figma sounds like a great tool, but it feels overhyped to me - especially in this article. This reads like a long-winded pitch to a Figma investor more than an honest review. I’ve been wanting to try it out but this article was a little bit of a turn off because it is so enthusiastic. Every tool has strengths and weaknesses so an article like this makes me wonder, what are the trade offs?
It is really easy to get up to speed to a workable draft sketch so I suggest you just try it out and see.
Re: Why Figma Wins
#15My main issue with Adobe XD and I believe this is an issue with Figma as well is the fact that there is no versioning on shared designs. We found ourselves in this situation with Adobe XD a few times where the designs were delivered to the developer and after part of the implementation was done the designer pushed changes which made the implementation look as if it was no longer following the approved UI. I looked at…
Re: Why Figma Wins
#16I wish Figma would add page formatting and links so that it could be used as a wiki also. Figma is on a much better track to make a good product than Notion.
I totally agree and have been moving my spec work from Notion to Figma too!
Re: Why Figma Wins
#17I wish Figma would add page formatting and links so that it could be used as a wiki also. Figma is on a much better track to make a good product than Notion.
Re: Why Figma Wins
#18I wish Figma would add page formatting and links so that it could be used as a wiki also. Figma is on a much better track to make a good product than Notion.
Re: Why Figma Wins
#19Re: Why Figma Wins
#20My main issue with Adobe XD and I believe this is an issue with Figma as well is the fact that there is no versioning on shared designs. We found ourselves in this situation with Adobe XD a few times where the designs were delivered to the developer and after part of the implementation was done the designer pushed changes which made the implementation look as if it was no longer following the approved UI. I looked at…
I share different screens and version them.