I’m curious to know how they’re defining “best”? Notion has great brand design but if the goal here was endless permutations (in Figma! TM) that the CEO could shed to shreds it feels akin to design-by-committee or micromanagement. Maybe they’re lucky the CEO has style for example? Best needs defining.
The article is also light on details. I would love to see the actual evolution of a feature that they drew out in Figma. But the screenshots provided look like flows or wireframes. Showing more would help us all learn.
Agreed with this. Not really any tactics other than:
“Our general philosophy is to go crazy with permutations,” he says. “If the taste is there, which you can grow by studying typography and the giants of industry, you can churn out versions until you find the best one.”
Which fwiw, I whole-heartedly agree with. I even buy Figma is best suited to do this. But it's definitely more puff piece than resource despite the promising title. Still, though - enjoyed the short read.
I buy the approach to brand and general principles. My question is why mutli-user iteration is necessary. FWIW I also think Notion has a great brand presence to it that I personally really love.
What I want is an example of a Notion feature that started out as v1, and what explosively and divergently iterated on until they got to vFinal. The result isn't as important to me as the process and leadership/mgmt style it took to get here with a piece like this.
Hey Andrew, I'm the writer on this piece and I really appreciate yours and Giovanni's feedback. I'm trying to write more tactical design process stories on the Figma blog, and I want to get the details right so they're actually useful. Would you be game to hop on the phone with me for 15 minutes so I can get a little more color from you on what you would've liked to see in the story? If so, my email is carmel at figma dot com.
Hey Giovanni, I'm the writer on this piece and I really appreciate yours and Andrew's feedback. I'm trying to write more tactical design process stories on the Figma blog, and I want to get the details right so they're actually useful. Would you be game to hop on the phone with me for 15 minutes so I can get a little more color from you on what you would've liked to see in the story? If so, my email is carmel at figma dot com.
This sales pitch of realtime, collaborative, everyone can comment on everything works great when you're a team of about 5 and all of the same page ideologically.
Although in larger organizations even a single bad actor can turn it into an experience that borders on bullying at times. Worked in a place once with a high level member of the design team who just didn't understand how to delegate and wanted final say on absolutely everything (even if it technically wasn't his responsibility) and would in the early hours of the morning go into your Google Documents and completely change them without asking or telling you, just drop a little "Oh I made some notes on that doc" at some point during the day but really he was up till 3am rewriting the whole thing.
No way in hell would I want to bring the possibility of that happening again into any other part of my work.