How Figma Caught Adobe By Surprise — With Carmel DeAmicis

Carmel DeAmicis was the 20th employee at Figma, a startup that Adobe just acquired for $20 billion. A former journalist and editor at Figma, DeAmicis saw the company rise under the nose of Adobe — the giant in the space — and eventually grow so fast that Adobe acquired it in a defensive move. In this week's episode, DeAmicis explains how a startup caught a major, established company by surprise. And why changing design culture played a big part in it. You can find DeAmicis on Notion. Learn more about your ad choices. Visit megaphone.fm/adchoices

Speaker names marked ? are inferred from speaking time and the show’s known hosts — they are not voice-verified.

• 0:00Alex Kantrowitz?

  This episode is brought to you by Genesis. What does it actually take to put Agentic AI to work across an entire enterprise? I recently spoke with Genesis chairman and CEO Tony Bates about why orchestration is emerging as a competitive advantage in customer experience and what companies need to get right in the AI era. Then I sat down with Adam Mitchell, head of enterprise business solutions at Voya Financial, to go inside a large-scale Agentic CX transformation, including the business decisions, trade-offs, and lessons along the way. You can watch both conversations now on my YouTube channel today. It's never been more challenging to get frontier compute. How do you know where to look, who to trust, or how much to pay?

• 0:43Alex Kantrowitz?

  Akash is an open cloud that provides easy access, flexibility, and peace of mind. That's how companies like Razor were able to cut their inference cost by 15 times. Visit akash.network/alex for a free consultation. That's akash.network/alex for a free consultation.

• 1:03Speaker 01

  LinkedIn Presents.

• 1:19Alex Kantrowitz?

  Welcome to the Big Technology Podcast, a show for cool-headed, nuanced conversation of the tech world and beyond. Recently, you might have seen in September, Adobe, which is the preeminent design company, acquired this company, Figma, for $20 billion. It's one of the biggest startup acquisition deals of all time. And it took a lot of people by surprise, including Adobe investors, who immediately sold the stock a bunch and helped tank that stock. And in some ways, it was an admission that Adobe had been bested by this company, Figma. And it really went against the narrative that we have that big tech will always crush the little company. Because actually, it was Figma that turned the tables on Adobe.

• 2:03Alex Kantrowitz?

  I think it's a really interesting story, really indicative of what can happen when the market actually does its thing. And maybe some of the bigger tech companies, and I admit that Adobe isn't on Google or Facebook's side, but what happens when bigger tech companies can let their guard down? So we're going to talk about it today. And joining us all the way from San Francisco is Carmel Diamis. She used to be an editor at Figma, was employee number 20 there. She worked on the blog, marketing, comms strategy, internal comms. And she's also a friend of mine, a former reporter at Recode, GigaOm, and Pando Daily. So her success rate of picking startups is much better than her success rate of picking news companies because two of the

• 2:46Alex Kantrowitz?

  three went out of business. But anyway, this is really going to be fascinating. And as you can tell, there'll be some good banter because Carmel and I go back a long way. And I'm lucky that A, she has seen Figma from the very beginning and B, decided to come on and talk about it. Carmel, welcome to the show.

• 3:05Speaker 02

  Thanks for having me, Alex. This is pretty wild. If you had told me when you were advising me not to take the Figma job, that this is where we would be five years from now, I would have thought you were crazy.

• 3:16Alex Kantrowitz?

  Yeah, same here. And you had told me, oh, this is a design company. And I was like, okay, don't do that. And you had this opportunity to become like a partner at a public relations firm. And I think the money was better. And it was a company that I'd heard of versus Figma. And I thought, okay, maybe take that safer route, since you had already, you had a nice track record of being at companies that failed. Anyway, I was wrong.

• 3:45Speaker 02

  I think that PR firm also no longer exists. So that, you know, path between two, path through a forest, two paths to diverge by, wow, getting lucky this time.

• 3:56Alex Kantrowitz?

  Right. And the, yeah, the Carmel curse is actually not a thing, which we learned. You also have a, well, anyway, we might get into your, your other career stops, like the fact that you did this viral report on a meat factory in Dubai, for Dubai television.

• 4:16Speaker 02

  Alex wants to prove that he can help me hit 7 million on a very old, unfortunately, semi-viral video.

• 4:26Alex Kantrowitz?

  This thing could go off the rails quickly. So let's, let's start talking about Figma. What is, what is Figma? Because for a lot of folks, you know, it will be the, the first time really digging into what this company is and does.

• 4:39Speaker 02

  That is not new to me because when I joined Figma, nobody knew about it. So at this point, I think the tech industry has cottoned on, but it's still a why the hell did Adobe buy this company that half of us have never heard of question. It's a UI design tool, which means anything digital that you might interact with your Uber app, or you go on Google, maybe even your Tesla dashboard is probably designed in Figma, sort of like Photoshop, but for anything that's interface or virtual.

• 5:12Alex Kantrowitz?

  So it's just-

• 5:12Speaker 02

  Except video, no video. So we're talking, you know, more static or, you know, minimal motion.

• 5:18Alex Kantrowitz?

  So is it just UI, like people designing apps there? Or do people like do Photoshop style design there as well?

• 5:25Speaker 02

  It's definitely started to grow, but initially it was interface design. It's built for that. That's what the features are for. But more and more creatives have gotten their hands on it. So we have started to see a lot more illustration, really crazy detailed illustration, beautiful stuff happening in Figma. But that was not the initial purpose.

• 5:41Alex Kantrowitz?

  Yeah. And I see, I see Paddy McCormick, who's the author of Not Boring, do these Figma photo chops. But maybe he's not the best reference point exactly for figuring out what, what the app does or what web app does. So from my understanding, so Adobe has, you know, is the, has the set of tools that you would imagine people would design, UI and Photoshop Illustrator, et cetera, et cetera. But Figma decided to build a competing tool and do it differently, right? It said, instead of building this in software that you would download like you would in Photoshop and Illustrator. Why don't you just use it on the web in the browser? And can you talk a little bit about about how that was possible?

• 6:26Alex Kantrowitz?

  And why that why the company made that decision? Because it ends up playing a pretty big role in its ability to really challenge Adobe for its life afterwards.

• 6:35Speaker 02

  It was a really risky decision when they went down this path, which was, you know, a company that started roughly 2012. And from 2012 to 2015, there was a lot of testing and experimentation. And pretty much before that point in time, it actually wasn't possible to build a design tool that would be fast enough on the web or in the browser, because browser technology had not come far enough. The advent of something called WebGL allowed for that. And so that, you know, opens up the design process to all these other people that previously were stuck just receiving like a static file or like checking a static file after a designer had already made whatever changes they wanted. And so, yeah, that was the biggest shift. But I would say that Adobe was not completely

• 7:20Speaker 02

  on top of the UI design market either, regardless of whether you're talking about a design tool that's a Google Docs in the web versus not.

• 7:28Alex Kantrowitz?

  And why does it open it up to different people?

• 7:31Speaker 02

  It's just like it's just like Google Docs or, you know, if you use any kind of web based tool, you're able to be in the file at the same time as someone else. You're able to make live changes and they're seeing the changes made live on there. And it's the kind of thing that we've become so used to in the remote COVID era because we need it. Whereas when Figma first started in 2012 or 2013, it wasn't necessarily the norm in a lot of different industries. I don't even know when Google Docs was launched, but that felt like that was one of the first big moments of people realizing how different it would feel to work on the web versus. Just on your local computer with others.

• 8:12Alex Kantrowitz?

  Yeah, it was the mid 2000s and Google made all those acquisitions. It's kind of interesting because Google made all those acquisitions that ended up leading to docs and sheets in the early 20, mid to early 2010s. And it was just as Microsoft had this, this stranglehold on the desktop. Yeah, chokehold, stranglehold on the desktop. And Google was really reliant on Microsoft's browser at the time, which is interesting. So they basically said, we're going to create these programs on your browser that are going to challenge your tools, such as Office. And of course, Microsoft kept the browser slow and that led to Chrome. This is, you've read about it because you've, you helped me work on edits in my, my book Always Day One. But this is something that's in there.

• 8:58Alex Kantrowitz?

  And is this kind of similar for, for Figma when it, when it comes out and says, okay, we can do this collaborative design. Obviously, the people had been, well, not obviously, but I imagine the people had been working in Photoshop before, so it gave them this, an opportunity to replace Photoshop for UI design.

• 9:19Speaker 02

  So actually, what they would have been working on in would be either have been fireworks, which was Adobe's first attempt at tackling the UI design industry a long time ago. It was a big inspiration for Dylan, the CEO of Figma. But eventually they shuttered that project. And so actually, it was a European company called Sketch that exploded and Silicon Valley did not pay attention to that most UI design was being done in because it was one of the only design tools purely focused on that. And at some point in Sketch's history, Adobe then released something called Adobe XD, which was their version of trying to tackle that problem. So, you know, depending on when you're looking at Figma's time history, it would have had different competitors. Adobe XD had not captured the market by the time that I joined Figma.

• 10:03Speaker 02

  Sketch had this sort of unknown, I think it was like Norwegian or something like that company. So, but otherwise, the story is somewhat similar insofar as when I joined Figma in January of 2017, I was really confused that this didn't already exist for designers. I am not a designer, I'm a writer, and I couldn't have worked with editors or other people without Google Docs. And so it kind of blew my mind that design was so behind the game. The difference being designers hated the idea of designing in the browser or on the web initially. They did not like the idea of the file being open and accessible to anyone. And so even in January 2017, when I joined, Figma had been around four or five years, but we hadn't released to the public until the year prior.

• 10:46Speaker 02

  We were fighting this uphill battle of trying to convince designers it wasn't the end of the world if other people can get in your file while you're still working on it. And it's not this perfect final product.

• 10:56Alex Kantrowitz?

  Yeah, I mean, my first job was a marketing job and I remember, you know, working with designers. And I was, I was marketing manager. I'll tell you, there was no way they were letting me into their design file. It was strictly like, write the creative brief, hand it over to folks, let them work. And then they return a final product. You give feedback and you can't say make this bigger or smaller. What you have to say is make this more prominent or less prominent. Or, you know, I really like it to feel this way. And then you let the designers go ahead and do their thing. They, they very much do not like being told by non-design folks how to design. So that being said, how did Figma get designers into the idea

• 11:40Alex Kantrowitz?

  that there could be other people in the window while they were designing?

• 11:44Speaker 02

  When I first joined, we hadn't. And so I'll never forget, you know, I joined Figma thinking this seems like an obvious duh to me. How does that, this not exist? And I really loved Dylan and the team that interviewed me. And then I interviewed my first few designers, my first week on the job. And one of them messaged me when he saw the Adobe news. And I basically said, you know, what do you think of Figma? I was working on a story about design systems. And he was like, I mean, I would hate the idea of designing in the browser. And that was my first, oh shit, am I allowed to curse in your podcast?

• 12:15Alex Kantrowitz?

  Yeah, you can.

• 12:17Speaker 02

  So that was my first, oh shit moment of, you know, I never would have thought that would be a feature people did not want. And so that's where we were starting from. And it meant that we had to really invest in building community with the design community. We had to get to know people. We had to bring in people from the community who could be our evangelists. We had to encourage other evangelists and we had to listen really closely to what they were saying about what they wanted, even if the entire foundation of the product was not actually what they wanted. Uh, and so that meant. I mean, there was a whole range of different programs that we did from bringing in designer advocates at different stages who are now a core part of our sales process. It's a huge team now to bringing me in as a journalist to work on content because they didn't

• 13:03Speaker 02

  need the kind of growth SEO content at that point of time. What they really needed was storytelling and brand storytelling to earn designers' trust that we were really thinking deeply about the design process and we weren't just some outsiders trying to completely take their control away. The irony being, once you open up the design process, then designers all of a sudden rise in power in company. And we were seeing that they become more part of the leadership because everyone can be involved and they can be involved earlier. They're not just the polish on top at the end.

• 13:33Alex Kantrowitz?

  Yeah, so I was gonna ask you, who else was was in the design process with them? And is it mostly apps or websites or everything?

• 13:40Speaker 02

  I mean, it's evolved. So, you know, back then it was digital, so that apps and websites. Now we've shifted to a world where almost everything is digital in many ways, like your car dashboard is digital, right? You're you have an Alexa screen if you have the visual Alexa. And so, very glad we turned off my Alexa for the interview. And so, so it's evolved and it's gotten bigger and bigger, this sense of digital UI or where you can change, you know, your product at any point in time after you've already shipped it to people. Very different from physical. And so, back then, it was much smaller companies or is the one-off designer at Microsoft.

• 14:21Speaker 02

  We had these two guys from Eastern Europe that were our Microsoft users in like 2017. And we begged them to do a case study with us that couldn't get cleared by all of Microsoft. Now, most of Microsoft is using Figma. So, it's really evolved over the years, but and as we talked about, it's becoming also, it's moved into illustration and these other areas, brainstorming, PowerPoint, things that we didn't think back then, but that's changed since 2017.

• 14:48Alex Kantrowitz?

  So you would have like CEOs coming in and and product leaders coming in and saying? Giving instant feedback versus waiting and I imagine UI is something that changes very quickly, like for instance, Facebook back in the day used to push various changes every day. So is that what it was like?

• 15:09Speaker 02

  So the way the design process used to be pre Figma was often, you know, leadership and product managers would come up with a vision for something. They would rough sketch it out. Then they would sit with the design team who was supposed to do pixel perfection, you know, make it look beautiful, everything, you know, you remember from the switch to the iPhone era. And then the design team would work on that and then they would send back a file or it would be, you know, on a, you know, a shared server, but you couldn't open it when they were also in it. There are all of these limitations. And so, you know, it really meant that the feedback was happening in this discreet, a couple checkpoint review kind of way. Whereas when Figma came in, it's this living URL. Once you've shared

• 15:53Speaker 02

  it with someone, they can jump in at any time. They can jump in while you're live experimenting with it. They can leave comments at any time. And so obviously that can lead to chaos and can make things a lot harder, but it also enables designers to be even a part of the brainstorming from the very beginning in a way that they weren't before Figma, if that makes sense.

• 16:11Alex Kantrowitz?

  Yeah, it does. Cause I'm thinking back to my marketing meetings and it would be like I, the marketing manager would have a meeting with all the stakeholders, write up a creative brief and then send it to the design studio. Whereas like if they were just there, there'd be a lot less telephone.

• 16:26Speaker 02

  Right. And they're trained to think about user experience in a way that like we always relegated them to pixel perfection in tech, but they're trained to think about how people choose things and things like that. But if their tool is closed off, then that means their knowledge is closed off.

• 16:41Alex Kantrowitz?

  Yeah. And so all these factors are probably like, why I was like, maybe you shouldn't do this. And then there was also the aspect of

• 16:48Speaker 02

  You were traumatized.

• 16:50Alex Kantrowitz?

  Like also, yeah. And the question is like, what was the total market, total addressable market? Because it's not like it was designed completely. It was UI. And so, I mean, we're going to go forward and then we'll go backwards a little bit, but UI, the UI market, design, the UI design market to be $20 billion market. That seems, you know, astonishing. Like what is Snap's market cap compared to that?

• 17:17Speaker 02

  You're gonna have to look that up.

• 17:18Alex Kantrowitz?

  Thirteen billion. I mean thirteen billion. So, um, so why is this such a massive market?

• 17:25Speaker 02

  Well, I think if you're think, well, for one thing, if you're thinking of it just as UI design, you're already thinking too limited in terms of the threat that Figma posed to Adobe. Because once you teach creatives or show creatives what it can be like to work in this more open way, and once they get more comfortable with that, um, then that means they want that for their Photoshop where they're editing memes and photos and things like that. They want that for Illustrator where they're doing, you know, um, cool print design. They want that for InDesign, which used to print newspapers, you know, um, even Premiere, which is video editing. Uh, once you show that that is a better way to work, that's going to give you more power and more say in how things are made and also brings more people into

• 18:07Speaker 02

  your process. You know, it's a runaway train at that point. And so I do feel like Adobe bought Figma in part for, um, that market threat, um, and in part for the fact that it could grow its business because all of a sudden you have people who are willing to pay for design tooling that were never the designers, that were never part of the process, that didn't have the technical know-how. You know, it used to be you could open up a PDF of a Photoshop file or InDesign or whatever and see what the newspaper was gonna look like and, you know, maybe you print it out and write on it. You know, now we're at a point where if you have a web-based tool, then you have all these other people that wanna pay to, to be a part of it, even if they're not actually the designers. So

• 18:48Speaker 02

  that's the first big opportunity to grow the design market past like people with the technical know-how.

• 18:54Alex Kantrowitz?

  Fascinating. So it's interesting that it's culture, right? Culture is, is really the change here. It was a software that changes culture inside organizations versus software that, you know, necessarily, you know, just on the fact that it was cloud alone is what helped Figma gain success.

• 19:13Speaker 02

  And in fact, I think in Adobe's announcement blog, they talk about community a lot, which probably seems maybe confusing or like, oh, that's bullshit to someone who's on the outside and doesn't really understand. But what they're talking about are these values and these norms around openness in design that didn't exist before, even among designer to designer, you know, because it just wasn't possible. It wasn't technically feasible and that had sort of structured, yeah, the culture that design worked in.

• 19:40Alex Kantrowitz?

  So you join and there's 20 people there. Tell me a little bit about the company you walked into.

• 19:47Speaker 02

  It was wholesome.

• 19:50Speaker 02

  And that struck me as a big surprise because this was January 2017 and I was a tech reporter before that along with you. So we're coming hot off the heels of the bro Uber culture scandals. Or I maybe they were just starting to break. Actually, I feel like 2017 was when I watched all of you spend so much time having to chase down Uber. You know, Airbnb, you know, WeWork was starting to bubble up. And so Figma was a stark contrast to that. And I felt really comfortable and safe and sort of cared about, which is, I know, you know, silly to say. But, you know, I have stories that back me up. So from the beginning it felt like a

• 20:33Alex Kantrowitz?

  Yeah, go ahead.

• 20:34Speaker 02

  Yeah. So from the beginning, it felt kind of like a group of nerds that really cared about what they were doing and geeked out on it and geeked out with each other versus what was happening in Silicon Valley.

• 20:45Alex Kantrowitz?

  Right.

• 20:45Speaker 02

  Everywhere else at the time.

• 20:46Alex Kantrowitz?

  And the CEO is what 22 years old. He is a Thiel fellow, Dylan Field. And was he a college dropout or something like, tell me a little bit about about him.

• 20:56Speaker 02

  My understanding is that he dropped out roughly at 20. And for those who don't know, he was one of the first generation of Thiel fellows. So he got $100,000, him and his co-founder Evan Wallace, to start Figma from Peter Thiel. And

• 21:14Speaker 02

  By the time I joined, he was 23 or 22. His mom came a month into my job there and brought cupcakes to celebrate his birthday. So that was the moment I realized, I knew he was younger than me, but that he was five or six years younger than me. And so it meant that he didn't have any, you know, preconceived notions about how to run a company or what to do. And that really impacted Sigma's early culture in a positive way from my perspective. We didn't have these norms or established systems that we were trying to build towards. We were able to build exactly for our users and us and where we were, which also made things more chaotic, but that's the creative process. So I like that.

• 21:55Alex Kantrowitz?

  Right. And it starts tiny and then starts gaining more and more market share. So I imagine as part of this voice towards community, but when did you see it maybe hit an inflection point from being like, oh, this idea might or might not work to, oh, this idea is working?

• 22:14Speaker 02

  So, you know, I'll confess that as a writer, I was not paying that close attention to the business metrics. They were really open about them from the beginning. I would mostly just get the analysis feed from Jamie Wong, who was one of our earliest engineers, like, tell me if I need to be worried. Otherwise, I'm just here to do my job and, you know, I'm not paying that close attention. But the shift really happened around the time that we switched offices. So it felt both like this symbolic shift in terms of going from this beautiful office, but had had all these really horrible problems. Like, I can tell you really funny stories about our Series B fundraising that was just a mess.

• 22:51Alex Kantrowitz?

  Okay, wait, wait. No, no, we're not going to pass that and not hear it.

• 22:55Speaker 02

  We literally had, so they were doing construction in front of our front door. We were on this alleyway in Soma, downtown SF. And, you know, there would be just piles of gross things in front of it. They wound up doing construction in front of it for like a month straight, which meant that the only way to get into the building was through the dumpster entrance. So we literally had to lead these fancy investors for our Series B, which was before Sigma was what it was today. Our Series B was probably our most on the line, will we or won't we make it round, squeezing past like gross slime, the smell. Oh, gosh. I'll just never forget it. They're in their suits. Oh, man, you know, like they're buttoned down, you know, as fancy as we dress and as if button downs and like nice slacks and

• 23:40Speaker 02

  nice, and they would just get this look on their face. And I knew I'm the timing of it was not great, but it was very memorable and pretty funny. We all laughed about it really hard as it was happening and later because of, you know, dumpster diving for VCs doesn't kill your business, then it makes you stronger.

• 24:00Alex Kantrowitz?

  Right. And then, but the customer side of it as well, like, when did, when did it seem like, you know, it was a struggle, it went from, there must have been an inflection point for you where you saw, okay, it's a struggle to get these, you know, few designers on to like, holy crap, now this is becoming industry standard.

• 24:17Speaker 02

  I feel like the inflection happened two years into my time at Figma, maybe two and a half. And it was subtle at first, kind of like whispers. It went from, you know, half the time I'd meet a designer and they would never even have heard of Figma, you know, maybe I would just be cold calling people for stories we were working on, or I would meet them at an event or something like that. Then it went to all the designers know about Figma and we have a bunch of hardcore supporters, but a lot of them are still unsure. And then there became this shift where it wasn't just the designers that knew, it was everyone in Silicon Valley. And that one was a slow growth from, you know, the product managers knew, then the CEOs and the founders knew, then the salespeople or the people that

• 25:00Speaker 02

  don't even touch design, you know, and then it reached a point where it expanded beyond and it was people that I met that lived in Colorado during the pandemic, or, you know, the final chapter of this is when the Adobe news was announced, my dad texted me to say that my 83 year old aunt had saw the news in the newspaper. And I'm like, she never understood what Figma was the entire time I've worked here, but it was front page of her paper. And that's crazy.

• 25:28Alex Kantrowitz?

  Yeah. So how did, so what do you think it was that made that switch flip?

• 25:33Speaker 02

  Okay, I think it was several factors. It was building momentum for one. Figma started in 2012 or 2013. They were in stealth, making sure that they had a product that was fast enough that designers wouldn't immediately scoff at for three to four years. They didn't actually launch to the public till 2016, a few months before I joined. I joined in January of 2017. So in my first few years there, what we have is we finally have a product that anyone can get on to, that anyone can use. Does it have all the features that designers need and have gotten used to, especially UI designers? No, my first two years were building those and we would use our launch points as an opportunity to tell a story about where we saw design going. And those would go viral.

• 26:15Speaker 02

  So we weren't paying for marketing, but we were able to go viral with good storytelling and with like tapping people, relationships in the community that we had built to help share whatever the launch was. So more designers start hearing about us and start trying. Then I think there became a tipping point where it was almost like most of Silicon Valley finally tested us and we were good enough. And I was a Figma, it was one of our launches and I can't remember exactly which one where it blew up as our previous launches had done, but in this case, all the design teams got in and tried it and found that it finally met the standards of what they needed. So Silicon Valley starts to really get on board. And then the final push was COVID. I mean, in the pandemic, all of a sudden, this old way of working with these localized files

• 27:00Speaker 02

  did not do the trick, especially when the rest of collaborative software had progressed so far that people were used to working in this like no walls kind of way. And so, you know, then you really saw us being adopted by markets that were always a question mark, like the, you know, consumer goods markets and things like that. And so that was the final, you know, push, but we were getting there before that. And then COVID sort of, the fact that we were, people, people were suspect of working in that way, but then COVID forced them to work in that way. And then they realized working in that way was actually a lot better. So then they don't want to go back and there's nobody else that does what we do. What they do, I did technically leave in February of 2021. I don't know if we recapped that at the beginning, but obviously my heart is still with Figma.

• 27:45Alex Kantrowitz?

  Carmel Diamisius is with us. She is former editor at Figma. As you can hear, she worked on a lot of the blog positioning, some of those posts that went viral. She's a former reporter, Recode, GigaOm, and Pando Daily, and also some channel in Dubai that will remain nameless. There's one part of this story that we haven't spoken about yet, but we will in the second half. It's all about how Adobe saw this community building and this takeoff happening and didn't get its act together to compete. So we will talk about that right after this. This episode is brought to you by Avpoint. Everyone's racing to roll out AI right now: copilots, chatbots, agents doing real work. But here's the part nobody loves talking about:

• 28:29Alex Kantrowitz?

  all that AI runs on your data, and most teams have no single way to see it, secure it, and prove it's under control. That's exactly what Avpoint does. For 25 years, they've been the trusted layer beneath the world's most demanding data, now extended across your entire AI estate: your data, your cloud, and the agents acting on your behalf. It's how more than 28,000 organizations deploy AI with confidence, so innovation scales without scaling risk. Avpoint, the unifying trust layer for AI. Head to avpoint.com to see how enterprises deploy AI with confidence. Learn more at avpt.co/bigtechnologypodcast. That's

• 29:14Alex Kantrowitz?

  avpt.co/bigtechnologypodcast. Violent threats against executives are growing at an alarming rate. When a company experiences backlash, executives are the first people blamed. When their address and other personal details are sitting online, this backlash can lead right to their front door. The team at Ironwell knows this better than anyone. They've protected some of the most targeted executives and individuals on the planet for almost two decades. As a wide-glove enterprise security service, they protect your people with continuous personal data removal, proactive prevention tools, and human-led emergency support. So when someone goes looking for your executives, Ironwell ensures they hit a dead end. Here's what to do. Go to ironwall.com slash big technology, fill in the quick form and

• 29:59Alex Kantrowitz?

  request your free risk assessment. Their team will show you just how exposed your executives are and how to lock it down before a threat reaches their front door. That's ironwall.com slash big technology. Learn how to stop online threats before they become real world attacks. The link's in the show notes.

• 30:24Alex Kantrowitz?

  And we're back for the second half of big technology podcast. Carmel Diamis is with us. She is a former editor at Figma, former reporter at Rico at GigaOm and Pando Daily, one of my good friends, always love talking technology with Carmel, among other things. And I'd like to hear from your perspective, you know, there's a big rise, obviously very fast rise. What the heck was Adobe doing? And why, why wasn't it competitive? And by the way, like, I just had a conversation about this on CNBC and maybe Nate, we can drop it in. I think in the short term, again, you're going to see some good things. My worry about is, is the long term. Think about what just happened to Adobe, right?

• 31:01Speaker 02

  But that is the long term.

• 31:03Alex Kantrowitz?

  Adobe is the market leader.

• 31:04Speaker 02

  They're getting market share from doing that.

• 31:06Alex Kantrowitz?

  Yeah, I agree. And it can look that way in the near term, but the long term, you can end up having issues. Again, I'm going to point to the Adobe example, you know, they, they were the only one in the game. And then out of nowhere, right? How quickly did Figma come up? Because they weren't reinventing quick enough. And now they had to make this deal that ended up hurting the stock because it was defensive and they needed to do it. So I think that with these companies, it can look good in the near term. And I understand they can take market share. There's a way to capitalize on these moments. It's a question of whether to do it or not. Okay, so there are big companies. We think that they're going to make every possible investment. And they don't, they fail. And it's either, you know, they, they forget to see the

• 31:49Alex Kantrowitz?

  competition, or they just decide not to invest in an area of, of, you know, potential weakness, you know, when they could have because they don't want to. So what was going on with Adobe at this, at this time?

• 32:02Speaker 02

  Define this time. Are we talking January 2017?

• 32:05Alex Kantrowitz?

  Well, the whole time Figma was rising, wasn't there a fear that this was going to, you know, be taken over by Adobe, copied and then destroyed?

• 32:16Speaker 02

  There was and there wasn't. We talked about that a lot in the early days because Adobe had so much money. Adobe had not faced real challengers to its design business in so long and it's been around for decades. And if it did face challengers, it bought them up and they were small enough that it wasn't a threat. And so it had a lot of money and we did wonder, yeah, could it just decide that web was worth going after and?

• 32:38Alex Kantrowitz?

  Right, because you would imagine that the cloud becomes something that companies become interested in, but not in Adobe's case.

• 32:45Speaker 02

  Right. And Adobe does, it calls itself the creative cloud, a huge swath of its products, right? So it was attempting to own the messaging and I think maybe a lot of people didn't realize it hadn't fully owned the market because the marketing was misleading. And so, one, it's not easy to build on the web. It did take, as we talked about, years to create Figma before it launched. And so it's not an easily, you know, complicated feature the way Snapchat Stories is for Instagram or something like that. I think the second thing, as we talked about, was web technology was not ready yet. And as Figma was being built, it was getting there. What would that have taken for Adobe to realize? Well, one,

• 33:28Speaker 02

  they would have had to be paying attention to web technology. They would have had to be tuned in and think that that would be a market threat to their business when they really had never faced a market threat that was web-based like that. And you kind of have to invest in the technology and believe it'll continue progressing, you know, and that it'll get to a point where it could be a fast design tool in order to then pursue that opportunity. Third is that it was UI design. And there actually were already, like I said, Sketch companies that had decimated the UI market. Adobe XD had users, but Sketch had the bulk of the users. And it didn't impact Adobe's bottom line. They were still bringing in a ton of money from all of these other companies. So I think there are really good reasons for why they weren't feeling threatened. And I wouldn't be surprised if

• 34:12Speaker 02

  at some point in that 2017 to 2022 growth, Adobe did try to buy Figma and Dylan just said no, the leadership, the CEO. To be clear, I don't know if they did. I'm not Vida, some kind of insider knowledge, but.

• 34:26Alex Kantrowitz?

  I was gonna ask, what was the, the internal stance on, on selling?

• 34:33Speaker 02

  The internal stance, I mean, I was shocked when I saw the news that we sold because for as long as I've been at Figma, Dylan had always said that the goal was to go public. And in the beginning, every founder says that because they need investors to believe that. But usually, at some point in the growth, if they're willing to sell, they sell for a billion or they sell for two billion. Figma had reached a size where, one, we were valued so highly that who could afford us? And two, Dylan had already become a millionaire, and I'm sure so had Evan. And Dylan had then gotten into the crypto art space. There was no money motivation that often gets other founders to sell when they don't want to go the distance. So I do think this moment

• 35:17Speaker 02

  came as a big surprise to all of us. And yeah, I'd be shocked if Adobe hadn't tried to buy us at a previous point in time.

• 35:23Alex Kantrowitz?

  Right. And so, but, you know, still, I guess I would imagine that the collaboration part would be of interest to Adobe. You know, even if it wasn't UI, why wasn't that built more deeply into their products? And when you say the creative cloud marketing was misleading, were they still largely a download software that fancied itself as something more?

• 35:44Speaker 02

  Yeah, I think their version of cloud was you had ways of updating files and folders that was more accessible or cloud-based than it had been in the past. But it was not a web-based tool, as we often think of cloud products. Cloud could mean many things. So they were using that.

• 36:02Alex Kantrowitz?

  So you wouldn't be collaborating in Photoshop, for instance?

• 36:04Speaker 02

  In real time? No. Could you send a file? You know, yes, but in real time?

• 36:09Alex Kantrowitz?

  Not really a cloud, yeah.

• 36:11Speaker 02

  No. Yeah. And so I think, so why weren't they interested in that market? I asked this question a lot at a certain point in Figma's history. And the answer was they had experimented with more collaboration features, even in that version of, you know, hardware-based program where it's not on the web. But nobody wanted it. Designers didn't want it, like we talked about. They said, why would I ever want to open that process up? Why would I ever want a CEO dropping in and seeing it what I'm doing at 2am in my fury and then leaving all these comments that throws me off track? And so I think it makes sense that even though they had experimented with more collaboration features, they got pushback from their market.

• 36:54Speaker 02

  And Dylan and Evan did not start out as designers. Dylan had a design internship, but you know.

• 37:02Alex Kantrowitz?

  The co-founder?

• 37:03Speaker 02

  Evan's the silent co-founder. He's our, you know, he's not there anymore, but he was there for a very long time, including while I was there. So they were both engineering background more traditionally, although Dylan had some more design experience. And so I don't think they were limited by these preconceived ways of doing design that the market was. So Adobe tried from when I talked about it, like, no, they tried stuff, they tested things, they did user groups, and the answer was no.

• 37:30Alex Kantrowitz?

  Interesting. I just want to go back to one thing. The more we talk, the more I still can't believe that designers said yes to this. I mean, it is community building, but it's also just like, how did they get past this idea that someone was going to be in their stuff?

• 37:43Speaker 02

  So kicking and screaming for some of them.

• 37:49Speaker 02

  For some of them.

• 37:49Alex Kantrowitz?

  Was it a purchase that was driven by the designer or by the people up top?

• 37:53Speaker 02

  No, the designer. Yeah, especially when we got bigger, it was driven by the designer. So I think initially it was, you know, one person, one designer. It was often we'd have an evangelist at every company. Not on purpose. There would just be one person that saw the vision and wanted to design in a more open way, wanted to design in a more accessible way. And they would start advocating for it on their team in the company with whoever, you know, the people that buy the software tech at the C-level, C-suite level. And so, you know, they would pull people in and we would try to come up with light ways for them to do that, like little games or little um baby reviews they could do where, you know, they're not trying to convert their whole team to Figma immediately, but um they're,

• 38:38Speaker 02

  they're testing it. They're trying to, you know, um introduce it comfortably. So.

• 38:42Alex Kantrowitz?

  Right. And it's probably the more experimental folks that would be willing to try it first versus the entrenched.

• 38:47Speaker 02

  Yeah.

• 38:47Alex Kantrowitz?

  You know, don't, don't do anything but design the traditional way. Those people are probably, you know, native Adobe folks. So when Adobe came to them and said, hey, try this collaborative tool, they were most likely to be like, no. Whereas like someone who could use Figma, you know, might be naturally more open minded and that's essentially how it got pushed through. Does that sound right to you?

• 39:04Speaker 02

  A hundred percent. And we invested in those people in a big way. And so, yeah, I mean, one of our first hires on the marketing team was a designer advocate, which was someone that was well known. We were very local and small at this point, well known in the SF tech industry, had a lot of designer friends. And we hired him to just have a foot in the door to even showing them Figma. And then he would throw these like game nights that were like, we'd play Figma Pixel Pong where designers would have like design races in the product on a Friday night. And we'd throw these events that were ways of getting in the product that wouldn't activate the nervous system, you know, um I'm, you know, I'm in, I'm in, I'm in trouble mode. And so he was one of our first design advocates.

• 39:47Speaker 02

  And then later we grew that design advocate program. And I think now, I mean, I don't even know, it's thirty to forty, maybe even more size big of choosing people in the community who are those evangelists, like they love Figma, they see, they see the promise of it. So we brought some of them internal to be our translator. So then we would really pay attention to what these evangelists would say. We would really listen when they would give us product feedback. We would bring them into the company to meet people and feel like they actually had faces to names and involve them in our product development. It's a little bit ironic because we started the company building this thing no designers wanted, but then the way we kept it going and grew it was by really paying attention to what designers wanted. Once we convinced them, they should try this way of being.

• 40:31Speaker 02

  And so the design advocate program is huge. And then, you know, all of our marketing was pretty community based. So I would run content at various points in time in addition to the product launches. And I would work really closely with someone in the community on some story they wanted to write dissecting Tesla's new UI. Or we would, you know, involve them early in our testing of a feature. And then if they liked it, or well, even if they didn't like it, we'd then sometimes adjust the feature or change our product roadmap based on that. Then we would get to ask them to help with the marketing, not in a heavy handed way, but just in a, hey, this launch is going out. Like if you were comfortable tweeting it, we'd really appreciate it. We were spending no money on marketing at this point in time.

• 41:11Speaker 02

  And so, yeah, we were able to kind of co-develop with those evangelists in a way that empowered them to feel really even more excited about Figma and like continue evangelizing it.

• 41:22Alex Kantrowitz?

  What do you think about the Adobe testing? Did Adobe get wrong? Because you mentioned it, Adobe does have a lot of money, right? So there's this, there's this belief that, you know, a big tech company with a lot of money and can sort of run for its way through market and startups don't have a chance today. So, but this seems to tell a different story. What happened?

• 41:45Speaker 02

  Well, I think you have a feature that isn't easily replicatable. So it's not as simple for Adobe to just launch the web based version and let people try it out and see if people use it. You'd have to actually invest more time and money. You have to really believe in it to some extent, even if you have a ton of money.

• 42:03Speaker 02

  Two, the foundational thing is that we built something designers didn't think they wanted. And then when they got more used to it, they decided they did want it. And, and it gave them more power and more accessibility. And we ensured that it had the features that they needed and the things that they were asking for. And so, you know, I think you'd have to be. It's not like Instagram ripping off stories from Snapchat. It was clear when stories came out, that's a popular feature. Everyone's leaving Facebook and Instagram or whatever to go to Snapchat. Instagram's like, fine, let's just rip it off and let's try to eat the business from Snapchat out from under it. There is no business eating out from, like eating the business out from under Adobe. There's no one really challenging their market share.

• 42:47Speaker 02

  You know, there's this, until it's too big, right? There's this idea that you could explore with web in collaboration and they do and designers tell them no. So what would be the impetus to then explore it if you're not being forced to, you know? And then by the time Sigma got bigger, when we were in like 2018, 2019, that was when I really thought, oh, they're gonna do it, they're gonna go, they're gonna have an exploratory team, they're gonna pursue web. And they didn't and all I can think is that it's so counterintuitive to their business model. All of their products are not web-based. They would have to start from scratch with every single product. If they're really saying, we think web-based is the future, right? And so to take that stand when Sigma was what in 2018, like?

• 43:32Speaker 02

  Four billion, maybe ARR, again, I didn't pay that close attention to the numbers. So, you know, I'm like rereading recaps of news articles to remember. There, you know, there isn't that pressure until we hit 2019 and it grows a lot more. Then we hit the pandemic in 2020 and all of a sudden, you know, and so the threat in some ways was building, building, building, building. And then the rise of it was so fast that you couldn't actually rip it off in a second, you know?

• 43:59Alex Kantrowitz?

  Yeah, it sort of reminds me of the move to cloud where Microsoft had this on-prem server and tools business that would do like storage for, and server work for companies in their offices. And all the CIOs that Microsoft was working with told them they would never move to the cloud because moving to the cloud would mean that they would get fired and or lose a lot of their power. And so Microsoft didn't do that initially because they had this stakeholder group that really didn't want things to change. And then, and then Amazon took the lead. And then Microsoft eventually realized that, like, did another study, and this is also an always day one, did another study and realized, oh, these CIOs are either telling

• 44:43Alex Kantrowitz?

  us, are either going to flip back on their word, or they're going to get fired because there's only one way the future is moving and it's moving towards cloud. And then Microsoft reoriented itself, actually Satya Nadella, who was running server and tools at the time, read that report, reoriented the division to push towards cloud. That's where Azure came from. And now Microsoft is a solid number two. And it was able to make that flip. But it's very, very difficult to say, our customers are wrong, which is what Adobe's customers effectively were.

• 45:14Speaker 02

  Right.

• 45:15Alex Kantrowitz?

  And they all moved to Figma.

• 45:16Speaker 02

  Especially when you, especially when you add on to the fact that Adobe has not faced these threats, the way I feel like the Googles and the Microsofts and the Facebooks of the world are constantly dealing with, you know, these threatening incumbents, sorry, these threatening competitors, they're the incumbents. But Adobe was just really, I think, maybe smart with their acquisition strategy in terms of buying up companies when they're smaller. And so, yeah, they haven't faced that kind of challenge. And so I could understand, even when I was at Figma, it's still wild for me to look back and realize how much it took off. It felt like it could, but who knows? It was a very big risk. And so, yeah, I don't necessarily, and Adobe, I mean, in the end, they did, you know, they

• 46:01Speaker 02

  did buy us, they got their opportunity and they did. And so I think they're very smart for that, not only because of the threat, but also because of the growth opportunity, where all of a sudden, like we talked about, you can have these people that are willing to pay for a design tool that aren't designers.

• 46:16Alex Kantrowitz?

  Right. And what was interesting, though, is once Adobe did buy Figma, the market just tanked the stock because they're like, oh, you missed a major opportunity. And the fact that you had to do this shows your, your business is not as strong as, as you or we believed.

• 46:29Speaker 02

  And I don't know if that's totally true because there aren't other competitors, right?

• 46:34Alex Kantrowitz?

  Right.

• 46:35Speaker 02

  There is a bit, like there's Canvas, but that's consumer like PowerPoint slide type of thing. And so it's not quite the same.

• 46:41Alex Kantrowitz?

  Yeah, but the stock tank for a reason. And I think maybe that is a, a perspective on the culture of Adobe or, you know, the fact that everyone's asking if these bigger companies are able to innovate. And the answer is yes, until it's no. When you have to spend $20 billion on a competitor, maybe the answer is no.

• 46:59Speaker 02

  Yeah, but I do have, I think what all it really took is like being open to web and investing in web.

• 47:06Alex Kantrowitz?

  Right.

• 47:07Speaker 02

  And them buying Figma, to me, they're not going to shut it down. You don't buy something for $20 billion to shut it down.

• 47:13Alex Kantrowitz?

  They had to do it.

• 47:13Speaker 02

  Like they had to do it, but now they're ready and they could then expand video. Can you imagine video? Well, maybe you can't, or maybe you can't. Video editing collaboratively, I worked in video journalism pre being a tech reporter and, you know, it's very frustrating to be stuck in this contained space of Premiere, which is owned by Adobe when you're used to working collaboration. So I do think there's a huge market opportunity for them. And in some ways, the investors should be a little more excited about that when you would have thought Adobe had grown to its max potential, you know?

• 47:44Alex Kantrowitz?

  So here's a question. Do you think that Adobe's culture can handle Figma? I mean, really, I don't think they're going to shut the company down either. That would be absurd.

• 47:52Speaker 02

  Yeah.

• 47:53Alex Kantrowitz?

  But the question is, can this non collaborative culture, well, not the, not a culture not used to building collaborative apps on the web, can it then take this Figma approach and apply it everywhere? Because I imagine that like part of it is, you mentioned it in the release, right? Part of it is now that, you know, Figma, Adobe has bought this community of, of designers with Figma, it's going to want to apply it elsewhere. So.

• 48:18Speaker 02

  Right.

• 48:19Alex Kantrowitz?

  So I, I wonder, do you, do you think, you know, because you must have watched Adobe closely when you were there. So do you think?

• 48:25Speaker 02

  We watched Sketch and Envision more closely. I'll be honest, like Adobe was kind of an afterthought because UI design for them was an afterthought, but they were, they were, you know, yes, we did watch them.

• 48:35Alex Kantrowitz?

  You paid attention to them. Do you think that they have the ability to change their culture and make it one that's, you know, more geared towards the users of Figma than the traditional Adobe user? Because that requires a full. Reinvent of how you do business.

• 48:56Speaker 02

  I think it'll be really interesting to see

• 49:01Speaker 02

  what they do with Figma in the first few years. And to the extent that they let it remain autonomous while they're closely studying it and in deep conversation with all of the people building it and understanding exactly what it took to build a web-first tool.

• 49:19Alex Kantrowitz?

  Don't have to be politically correct here.

• 49:20Speaker 02

  I know. No, I, I, I don't know to some extent. I think, I think the person that's the chief product officer at Adobe, it's this guy named Scott Belsky. He's really widely respected in design. Dylan really respects him. Yeah, Scott is like well-liked and well-respected. I'm sure he was very, like, a deep part of the conversations with Dylan about the acquisition. And so I have the hope, I have so much more hope for Adobe buying Figma that, you know, they're going to learn from it and be able to apply it than I would our first biggest competitor that had a ton of money, which was Envision. Or even Sketch, because, because Sketch was this European company that didn't have these growth pressures. They weren't venture-backed, all of these things, you know. They, they didn't have this need to innovate.

• 50:06Speaker 02

  Adobe does, right? Like, their stock has been struggling like a lot of the stock market for the past six months, even pre the Figma deal. And so they have a desire and a need to make use of our learnings to be able to grow their user base. But it's also just been around a long time and it hasn't been challenged. And that, I feel like, feels like my biggest question of like, it hurts to change. Change hurts. It hurts internally, it hurts personally. And so are they willing to go through that discomfort and the hurt to accept a new way of being that they need to be? I can hope, but I, I don't know, you know?

• 50:38Alex Kantrowitz?

  Yeah. By the way, I just don't think naming your company Sketch, even if it's a company where you do sketches.

• 50:45Speaker 02

  English is not the first language, but they weren't beloved, you know? And I will also say for Adobe XD, designers really liked it. Like when I first joined Figma, a lot of them were like XD does the job for me. It has the features for UI, you know, it's not as bloated as Photoshop. Like it does what I need it to do. Why would I try this like web based startup I've never even heard of? And so that to me is promising, like they're still doing design right in some ways, even if they haven't really had to force themselves to change.

• 51:12Alex Kantrowitz?

  How will fig mates, is that what they're called?

• 51:15Speaker 02

  Yeah.

• 51:15Alex Kantrowitz?

  Like meta mates.

• 51:16Speaker 02

  Oh God, I remember when they sent out the survey and we had to like vote on like pitch an idea. I'm like Figgy, like no, like Fig Newton, oh God, yeah.

• 51:25Alex Kantrowitz?

  So how will, how will fig mates adapt to being inside Adobe?

• 51:32Speaker 02

  I think what fig mates care about the most is the user. That when I went back for the happy hour.

• 51:38Alex Kantrowitz?

  But come on, like, because that's so cliche. Yeah, it is. I mean, I want to know how they're, they're going to be in this big Adobe culture. So how are they going to adapt? You know, Adobe will tell you the same thing about the user. It's two different cultures, no doubt about it.

• 51:53Speaker 02

  Okay, so no, I know that, but you know, some of my behind the scenes stories where you know that I'm not just bullshitting you.

• 51:59Alex Kantrowitz?

  I know, I know, yeah.

• 52:00Speaker 02

  Um, and so they care, fig mates care a lot about craftsmanship. You get a lot of people who work there that are coming from a design background. And so I think if Adobe gives them continued autonomy to do right by their users, where they get to actually follow the user input that they're getting. They get to actually build the business around that. Even the community and the marketing is all baked into that. Then I think Figma will integrate really well. If Adobe uses Figma as like a learning opportunity. Um, I think if Adobe tries to squeeze Figma in and make it the same as the rest of Adobe, that's where you could really lose the magic, you know? And so, um, so yeah, like laugh all you want, but you know, when I showed up at the happy hour after the news was announced,

• 52:45Speaker 02

  you would have thought all the people that were early with me that could, this could be financially the biggest moment in their life.

• 52:52Speaker 02

  We're kind of like, yeah, yeah, yeah. I just want to make sure that we figure out how to make sure our users are heard and we hold space for them. And that's behind the scenes, you know? So I know what you mean. I was a journalist. I know that's what, that's what everyone says, but I do actually think like the desire for craftsmanship is very high. It's a design company and that wound up being a core part of our principles. So anyway, that's my thoughts. I think if they try to learn from Figma, there's a lot. I think if they try to squish it in and make it just like Adobe, you know, immediately try to integrate it into the creative cloud without giving their space for the learnings to percolate, then you know, it could be a mess.

• 53:28Alex Kantrowitz?

  Okay. No, that's a good answer. I didn't quite see where you were going there. Sorry for giving you a hard time.

• 53:32Speaker 02

  No, that's okay.

• 53:33Alex Kantrowitz?

  The last question I have for you, what can we learn about the way that the market and the way that big companies and small companies interact from this entire story? I mean, we're really living in a, in a world, and I'm not going to go about to bat for the tech, big tech companies, but we do live in a world where people sort of throw their hands up and say, well, they're big, so we're toast. And if they go on the offense, then you know, might as well not compete. Is there a lesson about that from the Figma story?

• 54:02Speaker 02

  I mean, it's tough because I think the first lesson is can you build technology that is defensible? How can you tackle a problem that actually, if you get the solution right, is difficult to rip off? And I don't think there is many opportunities for that out there and there, you have to invest a lot upfront and hope for the best with those. So I do think in some ways, those are becoming the bolder risks to take because if you just, you know, build

• 54:28Speaker 02

  a feature like going live as Meerkat did back in the day, you'll just see Facebook rip it off and Twitter and all of a sudden, nobody even remembers Meerkat. So I think that's the first thing is that, you know, as technology has evolved, that's become the bigger opportunity or the bigger risk to take. And that's hard because you don't know if you're on the right path until you're five years in. So that's one. I think the second is sometimes they're not going to realize you're a threat until it's too late. And you look at that with TikTok and Facebook and you, you know, I'm, I've been obsessed with TikTok since January of 2019 or earlier even.

• 55:02Alex Kantrowitz?

  You really picked two winners. Yeah.

• 55:05Speaker 02

  But I've also picked losers. Like, I was really into yick yak and like wrote all the big proposals of that and then yick yak did not pan out. Um, anyway, so I think it's all luck is what I was saying there. Um, with TikTok, you know, they knew it was doing well, but there were so many people that didn't like it, right? Because they're like, oh, it's lip syncing for teenagers. I was on it in the lip syncing for teenagers era. There was so much more potential and there was growth happening among the teenagers era. I'm honestly shocked that Facebook would dismiss it for being lip sync for teenagers because they like love teenagers. That's their big, you know, growth market or whatever. Um, well, what happened? Once you reach a certain inflection point with growth and community involvement and, um, you know, users, then they can't catch up and that inflection

• 55:49Speaker 02

  point can happen very quickly. It can happen for Figma, I think it happened in a year from we're not a threat to, oh my God, we're a huge threat. And so when you like try tackling something new, you know, there's something to be said a little bit for, um, for taking the shots still, I think, even though I know we have plenty of examples of major something's taken out the little guy early. Maybe don't pursue PR. I like have this void PR and then that meant I think we also helped us fly under the radar for a long time.

• 56:18Alex Kantrowitz?

  I think that's a great idea.

• 56:21Speaker 02

  Don't talk to Alex on his podcast.

• 56:24Alex Kantrowitz?

  Carmel, geez. Well, if you, if you have a, an exit that's large and want to come tell the inside story, we always welcome you. And if you want, if you want to wait and risk that, you know, maybe I'll have you on one time down the line. And that's also okay. Worked out for Carmel. Could work out for you.

• 56:38Speaker 02

  We have some PR. You need a little, you know, not too much.

• 56:42Alex Kantrowitz?

  Exactly. So Carmel, you, um, you, uh, work as an independent editor now. You want to talk a little bit about that?

• 56:49Speaker 02

  Sure. Yeah. I'm a, I'm a writing coach, speaking coach and an editor. And so if you're stressing about having to give a speech, if you want to start writing more, uh, because you have unique ideas about what's happening in your industry, uh, you can go to my Notion page, which I don't even have easily accessible. I think it's bit.ly.com/carmelstories. You know, my lack of traditional marketing background is hitting me right now.

• 57:17Speaker 02

  And I'm also doing some content consultancy in terms of strategy from a high level of really catering your content strategy for your company and your product and your user base, because that's what Figma did. And it meant that we did not follow the traditional SEO, growth, marketing playbook, and it worked out.

• 57:36Alex Kantrowitz?

  Yeah, well, I thank you privately for this, but I do want to thank you publicly for the amount of help that you gave to Always Day One. Definitely a different book after you come through it. So I appreciate that and great getting a chance to speak with you today about about the Figma story. I hadn't heard it in this amount of detail. I've gotten bits and pieces, got to visit the office a bunch back in the day.

• 57:57Speaker 02

  Oh, yeah. You'd come over for beers. I forgot.

• 58:00Alex Kantrowitz?

  That was a good time.

• 58:02Speaker 02

  And Dylan would usually still be there. And I'd be like, Dylan, this is my friend Alex. He's a journalist. They don't care about us.

• 58:08Alex Kantrowitz?

  Actually, what happened. Oops. That was a big mistake. But anyway, it's really cool to hear the story and congratulations to you for being so early in a company that succeeded as well as it did. So anyway, congrats. Yeah. Awesome. Well, thank you, Carmel, so much for joining us. Another great episode of Big Technology Podcast. We have a real amazing slate of shows coming up for you. We have some CEOs. We, well, I was just saying, we might be having Tristan Harris on in the next couple of weeks to talk a little bit about the social media and the midterm elections, which I think will be really fun. Definitely going to do another politics episode sometime soon. So brace yourself for

• 58:52Alex Kantrowitz?

  that. But I do think it's important to discuss. And then, yeah, a handful of CEOs coming up in November. I think you're going to love it. If you're still here with us and you haven't signed off yet and you haven't rated Big Technology Podcast, five stars in either Apple Podcasts or Spotify would really go a long way to helping us reach more amazing listeners like you. So I would love it if you gave us a rating. Want to say thank you to Nate Guatney, our terrific and always dependable, always excellent audio editor. Thank you, Nate. Thank you to LinkedIn for having me as part of your podcast network. And thanks again to all of you listeners. I appreciate you coming back here, week after week, and joining us every Wednesday for conversations with tech insiders and outside agitators, sometimes people right in the middle, like Carmel.

• 59:38Alex Kantrowitz?

  Love having you here. All right. That will do it for us here and we will see you next time on Big Technology Podcast.

• 59:53Speaker 03

  Now, more than ever, we need someone on our side. But Rob Whitman, Whitman's votes drove up costs, cut Medicaid, and risked 350,000 Virginians' health care to pay for tax breaks for himself and his donors. He's not on our side. Shannon Taylor will fight corruption, cut taxes, and bring down costs. This November, vote for Shannon Taylor. She's for us. Paid for by HMP, the House Majority PAC dot com. Not authorized by any candidate or candidate's committee.