I’ve seen a lot of takes on the Figma Adobe deal in past week and think most VCs/finance folks misses the point since they don’t really understand the market or tools Adobe and Figma makes. Figma is not a Photoshop killer and Figma didn't put "Photoshop in the cloud".
First, Adobe business is making tools for specific creative fields like photographers, illustrators, magazine editors, videographers etc. The talk about some kind of “Adobe” bundle doesn’t make sense since most people only have a need and proficiency in 1-3 of the Adobe tools.
This is very different from the "MS Office bundle" where regular office worker might use all of most of the tools on their day job and the integrations. But what Adobe makes are tools for completely different creative fields and professionals.
This also means that when companies buy Adobe products, they specifically count how many of each licenses they need. Some companies buy the bundle but historically been quite expensive especially when majority of few users in company only need few of the tools.
Secondly, the talk about “photoshop in the cloud” is off. Photoshop is not a tool for designing digital products. It initially emerged from ILM as digital editing tool for stills and frames. Photoshop features are around editing pixel based assets like photos or scans.
Many did design apps and websites (me included) in Photoshop back in early 2000s because there wasn’t nothing much else on the market.
However somewhere in early 2000s UI industry started from pixels assets to rendered UIs. On web you would style the UI with CSS and on mobile you would use platform frameworks. The pixel assets, and most part pixel based tools no longer had a place in that world
The digital app industry took off (basically where all the VC funding has gone last 20years) but some reason Adobe completely missed it. Even worse, they acquired Macromedia Fireworks in 2005 and neglected it. In 2010 Sketch came along and finally took the product designers away
Sketch came vector based tool for designing digital products, like websites, mobile apps etc. It was really good, but it was a native Mac application that dealt with local .sketch files.
To work in a design team you would have email files or have these wacky Box/Dropbox folders that were synced (which someone always messed up). For engineers to see the designs they would have to have same version of Sketch installed and constantly find the latest file
The other disadvantage for Sketch was they were initially operating as a small team in the Netherlands and were kind of removed how Silicon Valley teams design and build products. They were still focused on building a tool for a designer vs building a tool for a teams
When Figma came along, they were behind of Sketch in terms performance and design features, but they had the cloud first architecture. Everyone in the company had and could access to all the files. No versions, you edit the latest file. Google Docs vs Word.
IMO the cloud first architecture was more important the multiplayer mode. Like with Google Docs, most of the time you design or write alone, but because there very little friction to share files and everyone has access, it's easy to get people jump in when needed
Figma caught up with Sketch performance and features fairly quickly and also listened what Silicon Valley and design & product teams actually needed. They were discovering the product for designing products rather than building an tool for a designer.
For example they came to the Airbnb design team to ask about what we would need for the design system and then they basically built that (I assume they also talked to other teams). It was way better what Sketch symbols where and obviously matched closely where the industry was at
They addressed the whole process, not just designing the UI. They built simple prototyping tools which then killed Invision. The web sharing and basic handoff tools kind of made handoff tools like Zeplin and Abstract obsolete.
Finally in 2016 Adobe caught on and announced Adobe XD and spent tons on marketing, paying design influencers and hosting dinners. But it was too late and the product was meh. And still felt like Adobe's "software in a box".
It didn’t help that Adobe brand is fairly tarnished by their use of dark patterns and predatory pricing. One of my happiest days was to uninstall the Creative Cloud app which only job seemed take 50% your computer resources and make you login each day to to verify your license
So in the end what Figma built was a design tool and platform that product designers and the product teams needed to design products. It had the cloud, collaboration and the features that work in a way that reflect the how things are designed and built today.
Figma's go to market and pricing is also geared around growth mindset vs the scarcity and haggling customers are used with Adobe. You likely have more Figma licenses than you have designers because you see there is a value in collaboration
Adobe still seems operate in the “software in a box” world where they sell these app binaries for specific types of users for but there is no understand how teams operate today. They sell the tools, but not solutions. Their creativity is spent on pricing, not on products.
Adobe to me seems the perfect example Steve Jobs comment on what happens sales people and marketers run the company. They lost their touch with the industry and customers to hit quarterly financials.
To summarize, Adobe missed the one of the largest transformations in the design industry and lost the product designers for over a decade. Spending $20B on Figma is their ticket back in and hopefully evolving their thinking from the "software in a box" model.
And I'm always happy when startups and best products win. Adobe had all the classic advantages but they still couldn't compete. Btw Adobe office also came to Airbnb office but there wasn't much interest from the design team to talk to them.
And to fair Adobe did evolve from “software in a box” to “software in a box in the cloud”. But just putting things in the cloud and turning on subscriptions doesn’t make a better product. That just changing the distribution
I’ve been thinking about this deal more is since Figma’s approach is similar to us at @linear. We are interested discovering what modern software teams need to build well. The individual features can often look very simple, but the magic happens when all of it comes together
Ben Thompson on @stratechery got some feedback on Photoshop vs Figma narrative.

Disagree on the design to code idea. Design is explorative, quick & dirty. Implementation needs to be solid & performant based on the app architecture. Mixing those two likely makes both worse
If you want to understand Figma better, I recommend reading @kevinakwok's excellent write up (2020) kwokchain.com/2020/06/19/why…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Karri Saarinen

Karri Saarinen Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @karrisaarinen

Aug 27
Been designing the last few weeks and realized how simple but effective the @linear design system is. There is no design system team, no councils, no meetings about what we should call it or if it’s “atomic" or not. We have a system which has colors, type, icons and components
We have had the system from the beginning which helped to speed up both design and development, and even allow supporting dark, light and custom user themes in the app. We have one file in Figma which describes it and also built in to the code.
Colors. So we have basic groups like Bg, Label, Control. So when I’m designing I just draw a shape, then write "bg base" to get the default background color, and label base to get the default text color. Then there is variations like Shade, Muted, Faint etc.
Read 10 tweets
Feb 2
I was just reminded that for our Series A, we sent a questionnaire to the investors we were considering to understand if we have alignment.

Then the investor needed to write a doc or a presentation explaining their answers and thinking.
It had questions like which other investors they would add to the round and why, what kind GTM they would see effective and examples, how to resolve specific challenge X, Y, Z, key hires and how they help with hiring, how to grow business to ARR, how sales plays etc...
This helped us to understand much better the differences between the investors.

Ideally we wanted to see that the investor had similar values or alignment but also they they could add something and impress us with their thinking.

Very similar how we do hiring for all roles
Read 6 tweets
Mar 29, 2021
Being a designer, and obviously design was important for Coinbase, this is a bad take even by Twitter’s standard.

(Btw, I was managing the metalab’s work for the landing page. We stopped working with them after that project and I redid the landing pages few months later)
The reality is more nuanced. When I joined as the first designer back in 2014, Coinbase had already hired compliance and legal. They thought about security, banking relations. Things that make or break it. Companies don’t succeed or fail because of a color choice
The success happens because get lot of things right, and not that many critical things wrong. The early team was excellent in many ways. Everyone regardless of the role completed 2 week work trial before getting an offer.
Read 8 tweets
Feb 8, 2021
At @linear_app, we don’t write user stories. They’re unnecessary and slow down the team.

I also always found them very weird to write and read. It’s like the tasks are in ancient Greek instead of English that everyone can understand. Wonder if other people felt this way?

More👇
User stories are a roundabout way to describe a todo. It would be ridiculous to write your todos this way. “As a human, I need to go to the store in order to have food to eat”. You would never write that. Instead: “Get groceries” and list items to buy.
Or imagine trying to build a rocket with user stories. Behind the “Fly me up the gravity well and not blow me up” user story, there is thousands of technical parts systems that needs to be built and considered. User stories is the wrong kind of abstraction for most tasks.
Read 9 tweets
May 12, 2020
1/ For anyone considering leaving SF, here is my story: After living 7 years in SF, 6months ago finally moved out to San Diego, close to Encinitas
2/ My main worry was losing on the SF scene and ambition but actually been able to keep in touch with many investors and fellow founders and friends, especially now since no-one can meet anyway. Also, I guess in 7 years to learn a lot that stays with you
3/ There are some startup, YC founders, etc here and I’m guessing more will also come here as companies go remote. At this pre-launch stage, it’s been also good be away from the SF distractions and focus on the company and the product. T
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(