Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

RevOps FM

Building Marketo and the Art of Product Design - Glen Lipka

Jun 17, 202456 minVideo

I have a fascination with how SaaS products actually get made - especially those that become institutions in the software landscape. As users, we become deeply familiar with these products, the nitty-gritty of how they work, and what it's like to live inside them. People base entire careers on these platforms. What we usually DON'T see is the backstory: How do these great products get designed? What were the decisions and trade-offs along the way? How do they catch on? How do you create lovable features? What causes great products to often stagnate? Today's guest is a legendary product leader and innovator. As the first employee of Marketo, Glen Lipka led the product team during a critical early phase, building many of its still most-beloved features. This episode is packed with Marketo lore, product design insights, and lessons about how to build a product that users love. Thanks to Our Sponsor Many thanks to the sponsor of this episode - Knak. If you don't know them (you should), Knak is an amazing email and landing page builder that integrates directly with your marketing automation platform. You set the brand guidelines and then give your users a building experience that’s slick, modern and beautiful. When they’re done, everything goes to your MAP at the push of a button. What's more, it supports global teams, approval workflows, and it’s got your integrations. Click the link below to get a special offer just for my listeners. Try Knak About Today's Guest Glen Lipka is a 25+ year veteran of product innovation and design. As Chief Design Officer and first employee at Marketo, he built the flagship product. He has held numerous other product leadership roles and is currently VP of Product Design for Crowdstrike. https://www.linkedin.com/in/glenlipka/ Key Topics [00:00] - Introduction [01:14] - Glen’s start at Marketo [02:56] - Marketo’s first features [13:36] - Product differentiation [20:37] - Developing the concept of marketing automation [26:00] - Why great products start to suck [40:46] - Hubspot as a product company [44:19] - AI Resource Links Glen's series of retrospective articles on building Marketo Glen's personal blog Learn More Visit the RevOps FM Substack for our weekly newsletter: Newsletter

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

0:14Justin Norris: Welcome to RevOps FM, everyone. You know, Martech has been a huge part of my career, especially the Marketo platform, and when you've been using a piece of software for more than a decade, you know it inside and out. It's like an old friend. There's the stuff you like, the stuff you hate, the stuff that's irritating, but you tolerate it, that sort of thing. And I have a fascination for how these products actually get made. You know, like what were the decisions, what were the trade offs along the way? How do these great products get designed? How do they catch on? And then also what makes them stagnant?

0:44What makes them lose energy? And so to chat about this, we have with us today, a man who was instrumental in designing Marketo in the early days. He was literally the first employee. At Marketo building many of its first and still most beloved features. And since then, he's held product leadership roles at companies like Engagio treasure data, and most recently CrowdStrike where he is a VP of product design today, Glenn Lipka. I am so glad to have you on the show. Glen Lipka: Thanks for having me Justin. It's a pleasure to be here. Justin Norris: I would love just to start off with a little bit of the history

1:18about how you got started at Marketo. Glen Lipka: I had been working at Intuit, in 2006 and, a friend of mine, named Lisa Sheehan, who's a recruiter, was putting together the founding team for Marketo, and she thought that. I would hit it off with them, but she said they didn't actually have a role for me. they were just hiring engineers, but she said, go meet with them anyway. and so I met, John Miller and Phil Fernandez and David Mirandi. They were still unpacking boxes from, purchases they made from their series.

1:49Hey, you know, the, desks and the chairs, and they were just putting them together in a San Mateo, super tiny office. and. We hit it off and I think Phil may have liked the fact that I was a network administrator, and I could run the network, and install the exchange server and do operational IT things in addition to product management and design. so I think he thought, it was a bargain. so they ended up hiring me and then right after me was, Crash Tongue, which is one of the best engineers I've ever worked with, Paul Abrams, who was my

2:22partner in the entire UI development, Wei Liu and several other people who became the founding, engineering team. It was mostly like me and. 10 engineers in those that first year or two, along with Kelly Abner, who is the first marketer, using Marketo and he was working with John Miller. John had already been blogging at that point. but Kelly was my proto marketer that if I could automate what he was doing.

2:53that would be a successful product. Justin Norris: So that kind of ties into the next question I was going to ask, which is like the process that you followed and you have shared on your blog, which I'll link to in the show notes, some of the like really early. versions of Marketo when it was like an AdWords management tool and maybe just walk us through like the seed idea and then maybe the process of getting to what we might recognize today is the Marketo platform. Glen Lipka: With the first six months we built what is best described as a replacement for Google AdWords.

3:24Like you would use this interface instead of the Google AdWords interface because Google AdWords was too complicated. And I tried to tell David Mirandi and Phil Fernandez, that it wasn't going to work, but it doesn't matter how hard it was. And the reason is if you looked at a marketer's resume at the time, it said things like, I know how to order t shirts. I know how to make brochures. I could, make our website and I know how to use Google AdWords. It was one of the few hard skills that somebody had, and you can't just take

3:57that away and say, Instead of Google AdWords, I'll just be good at Marketo AdWords, which that didn't make any sense, but they wanted to build it and they felt really strong about it. And one of the pieces that was needed was this landing page editor. and at the time all landing page editors worked the same way. It was, you had a template, you clicked on a section of the template and it popped up a tiny MCE rich text editor. And I said, why does it have to work like that?

4:27Maybe it could be more like PowerPoint. I just drag and drop stuff. everyone knows how to use PowerPoint. It's super easy. You just drag things around and there's nothing to think about. And because I was talking to people about their landing pages and it wasn't that much on them, it wasn't like a long, super scrolling page, but then the team, they were just like, yeah, but how does that work? That's not how HTML works. And I was like, actually, it is how HTML works. Let me explain absolute positioning and CSS. And man, the engineers, they hated CSS.

4:59So I had to be the CSS person for the first year and, you know, explain exactly how That would work. so we launched that product and the customer said, yeah, we're not doing this Google AdWords thing, but that landing page editor that looks really cool. I'm willing to pay for that, but I don't want the. Google AdWords part. So we ended up erasing all the code that we had written for the Google AdWords thing, it had word buckets and all sorts of synonyms and antonyms and crazy

5:33stuff, and we just erased all of it. And what was interesting for years, it had search in the URL. And it was only like a vestige of that old code that we had erased. We just threw all of that away and it was just gone. And then because I had gained some credibility with the landing page editor, they gave me a little bit more room to say what we're doing next. And the use case in essence was pretty simple. we had a focus group.

6:03And there was, some marketers in the room and they were talking about these landing pages and about, Salesforce and Salesforce had an auto responder for email and they said, all I want is when they fill out that form on the landing page is to send them an email. Wait a week, send them another email, right? Why is that so hard? And she was doing this thing with her hand, send an email, wait a week, send another email. And it made me think of Minority Report with Tom Cruise, where he had that

6:36computer interface where he's using his hands and swiping things around. And I said, Wouldn't it be cool if it was like that, like a hologram interface? And the engineers were like, no, that's physically impossible. And I was like, I have a dream, man. And so I. created a trick of psychology of it would feel like you're, rolling up your sleeves, putting your hand into the screen and grabbing something and moving it.

7:07And just like the way that person said, send an email, wait a week, send another email. And I said, that's what Mercado is going to feel like. It's going to feel like you're a kinetic reaching into the computer And making things move and that use case, which is really a very simple use case. You fill out the form, send an email, wait a week, send an email. That was the use case that made smart campaigns.

7:37That was the use case that made Marketo. but once you sit and think what does it mean to send an email, wait a week, send an email from a landing page? How do you do that? And I said, well, first we need the landing page editor. And I felt pretty good about that. we had something. Then I said, well, we need a form editor. So I had to make a form editor to put on top of the landing page. Then it was like, well, it's going to have to send an email. So we need an email editor. And I actually was spending an enormous amount of time figuring out

8:09what HTML would even work for me. In email clients, which at the time was just a completely wild west. today you would just have your templates, but, maybe it was constant contact and, it was me and those guys were figuring out like what stuff would work and what wouldn't work across different, clients. It was very much like, what can you do in JavaScript with different browsers, except it was email. and different email clients. And so, I needed that email editor and then I needed something to just glue

8:42it together to say, okay, well, I'm gonna wait till they fill out the form. I'm then I need some way of describing the text now, everyone in competitive. Circle said, Oh, you do that with a Vizio like diagram. And I asked Kelly Abner, I was like, do you like Vizio? And he was like, Oh no, I hate it. This thing gets incredibly complicated and it's really difficult to manage. And God forbid you want to edit it later. You're going to break everything but it's, what are you going to do?

9:12It's the only thing that's there. I was like, well, I don't know, come up with another way. And so I just started. making designs of how it could be. And I said, here's a, series of steps. And one of the ways Phil Fernandez put it is the way I was designing it was as if it was a programming language and that the Visio world was using procedural language terminology, and he called it a CISC architecture C I C S and it was like complex instructions, whereas what I was building was

9:46more object oriented programming and it was RISC architecture, random. So you can think of like an Intel chip as being a CISC chip, whereas like, a little mini chip that only does Wi Fi, like from ARM or somebody, that's a RISC. So the RISC architecture and the CISC architecture became our mental model of what it is that we were doing, and that very quickly what a smart campaign was started coming together as this, kinetic feel from

10:16Minority Report, Minority Report. And just this simple use case of send an email, wait a week, send another email. there were a few different influential programs. IBM had one called Rational Rose. and it kind of influenced the way the smart list works. iTunes, influenced the way, I thought about like a dynamic list versus a static list because iTunes had, you know, show me all of the songs that are jazz, or show me just these 10 songs. So I was taking some cues from iTunes.

10:49From these IBM tools I'd used a decade before. but a lot of it was just like, it just made sense to me. structurally I've always designed a customizable platform style user interfaces, as opposed to sitemap page by page by page structure. and it pretty quickly. made sense. Although I would say that Kelly Abner really didn't want to use it at first. It was incredibly buggy anyone who's used the first year of

11:20Marketo knows how buggy that system was barely hung on for dear life. it would work about as often as it wouldn't work. but the whole concept of you could do this, that it was your creativity that was creating what was happening. Was so powerful that it didn't matter whether it worked or not worked. The promise was that you could do it yourself. A lot of, marketers, they had a person in marketing who is the web developer.

11:53this person spoke Klingon. This person was, move. I'll just do it. Don't talk to me about the website. they hated this person. They hated the web developer because they did not have that skill. They didn't have the capability of doing these technical things. And in their minds, it was like, I just want to fix a comma on the webpage. Why is this so hard? Or why is it so hard to send an email? And all of a sudden there was this tool that said, no, you, could be in charge, you could do this.

12:23I think a lot of products don't understand how to connect with people and make them the hero of the story. it's not like people just want a button where it all just works. they want to do it. They want to be a part of the solution. And Marquette's entire ethos was, that we're putting you in the driver's seat. You are a creative, technical person, and that you're not just ordering t shirts. You're not just, writing copy, but you can actually make experiences.

12:57was a really big deal. And it started doing well relatively quickly. Justin Norris: could tell you as a user, picking up Marketo signed my first contract just at the end of 2011 starting using it. went through that experience that you described. Like in the beginning it's, complicated and it's weird, but I used to tell people there's like a Zen moment that you have where all of a sudden like everything falls into place and you're like, Oh, like the world opens up. Like I can do anything now, just by dragging these things. And it was an incredibly empowering experience as a non technical marketer

13:29who was sort of technically inclined. Just like you said, it gave you those capabilities. and that was enormously empowering. I want to just double click cause I'm really fascinated by the, two visual paradigms that you mentioned. I think of it as the bowl of spaghetti model. You called it probably more charitably, the Vizio style, like flow chart diagram model, and then the more linear model. And it feels like people split into camps. And today, like even today, we still see, like there was Marketo, but sort of Zapier's followed a similar linear format and Mercado does. Over on the.

13:59Vizio side, you know, you have Eloqua and Salesforce flow and Trey. do you still feel the same? like if you had to do it all over again, you would pick this model, or do you see some strengths and weaknesses between the two paradigms? Glen Lipka: Well, the reason to pick it in the beginning has everything to do with differentiation. It was, Elko was a big player. they were the dominant 600 pound gorilla and, responses was also a very strong player at the time. And when you can't just come in and say, Hey, you know, that other software you

14:31use, well, we do about 10 percent of it. well, what are they going to do? They're going to say no. So you need something. And Bill Bench had said something very wise, which is, I need to be able to go to someone and say, if you don't have X and you don't have shit, right? I need to tell them that and I'll make them believe it, but it has to be plausible of like you have to have this thing. And so what I found is some people were used to the Vizio

15:03charts and that was fine, but it wasn't like the linear was worse. I thought it was better for management and maybe a little worse for giving a demo. But it wasn't like night and day. It was, you could get your job done either way. So the perfect design differentiation is something that actually doesn't matter. That's perfect. Cause you don't want something that's like objectively worse. But, I'll give you an example.

15:33the Tesla who, if it wasn't for Elon Musk, I would love my Tesla a lot more, but when I first got it, there was nothing in front of my steering wheel. It was all on the screen. Now, was that better or worse? I would say, you get used to it, you get used to it, but it was different. And so when I'm thinking about Marketo differentiation, I needed to create a religious war. I needed people to say, Oh, if you're not into the flows and you're not doing shit, you're like, if you're not, if you're a Vizio person, you're an idiot.

16:05and even though I knew they were like roughly equivalent, it doesn't matter. You need to create a warrant. This is a lesson for every single tech marketer out there. Differentiation will get you half the market. We were nobody. We were nobody. And Elko was huge, a huge company. And what business did we have taking half the market share away from them? We didn't. They had way more functionality.

16:36They called us play school. I remember it was very hurtful, right? And they would call us play school. And I just be like, but if we create a war and you're either on our side or not, and that led us to like a very strong community, Eloqua didn't have a strong community and that we said, you're not just buying software, you're buying into this group of like minded people. When you create a religious war, people want to be on your team, right? It's one team or the other.

17:06And then that's loyalty. And we did a lot of things in the beginning to get that loyalty. I remember one customer, we must've done 50, 000 worth of, consulting because they had multiple Salesforce instances and we just merged them for just because they were like, we can't buy your software until this gets done. And it'll take a year and a half. And we're just like, I think we can just do it. And they said, well, how much do you want? What do you want in return? I said, all I want is undying loyalty.

17:38And they put, I know, I remember they put me on mute. And I could tell that they were laughing at us, but then they come back and they were like, all right, glad we'll, give you that. And let me tell you that they gave us references. They took videos, they wrote guest blog posts, they did everything we asked them to do. And in the beginning that mattered a lot. And so what our approach was, was very differentiated. but the truth is it's not better or worse. Now, in hindsight, what I did with Playmaker with Engagio, I think

18:09had advantages, like involve a customization layer, like Marketo is a very set it and forget it. Sort of system. the marketer is completely in charge, but the SDRs could have been part of that process. It could have been like, here's a queue. I take a ticket off of the top. I customize it a little bit and then send it on its way. And, I would have done more of that. Plus, I think that I would have made more abstraction of the flows so that you can have sub flows the way that in Figma you have components that are

18:41reusable blocks and that yeah, you could do some reasonable things like call campaign, but you couldn't see it. it was very difficult to see that high level. So I probably would have added in more of that that abstraction layer. Justin Norris: It's funny that like 10 years later, Marquetto did roll out some kind of flow charty way of visualizing things. I've never really used it or liked it because it is very high level and very basic so clearly they felt that out in the market there was someone that wanted

19:13this and maybe wasn't buying Marketo because of it so they threw it in to tick a box but I just find it ironic that after all that time they circled around and slipped that in there. Glen Lipka: there was a UI, I used to call it fluid dynamics. It was basically the, process, forgetting the name that they had for it. but it was a Vizio diagram it wasn't about a flow of like, send an email, wait a week, send an email, it was more like, first they're a lead, then they Justin Norris: The revenue cycle modeler, Glen Lipka: Yes, the Revenue Cycle Modeler, that did make

19:43sense to be a Visio diagram. that totally made sense. Not everything should be a flow, it's use the right tool. So the Revenue Cycle Modeler was a Visio diagram on purpose, and it worked well in that case. And that the program, flows with the green strip, that made sense also to be a, diagram. but doing it for just send an email, wait a week, send an email. I think after I had left in 2015, they lost their way a little bit.

20:17They sold to private equity. I should have stayed the one extra year. That would have been very lucrative for me. I kind of missed out on that one. And once they got taken private, it was more just like shore up the functionality, get it prepared to sell to Adobe. And then once you're in Adobe, it's, more of a maintenance mode. Justin Norris: really want to go down that road, but I'm just curious because you mentioned Eloqua, I've had a chat on this show as well with Mark Oregon, who's the founding CEO of Eloqua, and it's funny hearing the story.

20:47A lot of similarities where they started out with a completely different use case in mind and then stumbled into this thing from a different direction. I'm curious from your point of view, like this category of marketing automation didn't exist, really. It wasn't a thing. what was the process like of Emerging into like, oh yeah, there's this thing where we like score leads and send them emails to nurture them. And like, having that concept emerge, Glen Lipka: Again, it, did start off very simply of I just want to send an email, wait a week and send another email. And then all of a sudden it's like, well, what else do people want to do?

21:18And that just became more and more, functions more and more things that you could do, but it was always the same language. And the language is when something happens, I want to do some sort of response. And it was designed like a programming language. I remember in the beginning, I remember when Eloqua was, I think it was there, they were a content management system. and I looked at their UI and I just thought, my goodness, it's so complicated and it was very expensive to implement. And then when we started going, our tagline was, I think I

21:53had come up with the tagline, which easy, powerful, complete. but it was our whole ethos was this is easier. It's simpler. It's how Salesforce beat Siebel. they just made it easier. They made it easier to self service. And I remember them at the time tweeting something like celebrating a victory over Marchetto. And I was just, it blew my mind. Cause I'm just like, we're nobody. Why are they even saying her name? that's just telling people, Oh, there's a competitor that they're focused on.

22:25And I. Literally responded immediately like saying, good one, you know, the last 10, you lost, but this one nice job and they erased their posts and I, so I had screenshot it and I sent it back to them saying, I think you lost this, it was just, we were the cool kids and they were the old grandpa. Uh, and then they ended up paying IDEO to design. a Marketo killer and I thought I was so flattered and so, excited that it

22:57was like me versus IDEO because they're famous design firm and what they ended up doing is taking exactly what they have and just putting a nice, paint job on it, making it look a little bit nicer, but I was just like, yeah, there's no way they're going to fix that. and I felt like it was an unfair battle, they just did not have the resources or understanding. And I knew that they were going to end up selling pennies on the dollar, which is what they did to, Oracle. and then they went into their own maintenance mode. it's like when you have that energy.

23:30That this is something cool and different and, better. Everyone gets really excited about it. I think that I underestimated the lightning in a bottle effect. at the time, the people, there were so many great people there who were like Maria Pergolino was inventing inbound marketing before my eyes. Bill Bench was Inventing SAS sales. there were so many things that I was just mesmerized by how they were happening. And I was just very lucky to be right in the middle of it, but like revenue

24:05operations or, marketing operations, it's sort of like, we didn't even think about it until it was already real for years. It was just more like, there's Emily Salas and she's trying to solve this problem and how do we. Help her solve this problem. And generally, I remember, they were very early, the first couple of customers, like I trained our first 50 customers personally, and they would have just these weird little problems and we've been sitting at a whiteboard saying,

24:35how are we going to solve that for them? I remember also we invented anonymous leads and I said to Jenna Raleigh, you got to check this out. Anonymous leads are great. And she's like, Glenn, I know you're very excited about your anonymous leads, but I'm very busy. You're not the center of my universe. I have a job to do. And I was like, huh? And then like six months later, she comes back and like, Hey, these anonymous leads are great. And I was like, I've been trying to tell you that. And it's a strong lesson that just because you build some cool thing and

25:08just because you have an early adopter customer doesn't mean that they're ready for it and doesn't mean that they want to hear from you all the time. This is probably the biggest lesson from Marketo is that More features is not why you're gonna win. More features is not why you're going to be successful as a tech startup. It's never about the number of features. It's always how does it work? Who are you? are you? creating differentiation? Are you creating a cultural, mainstay for someone to latch onto?

25:41That's what matters. The number of features, I mean, you need like a minimum, you need to be able to do something, but we had four, I would say we pounced on Eloqua and at the point where they had given up, we still only had half the functionality they had. Justin Norris: I want to talk about this dynamic that you've described. both Marquette and Ellipa going through the lifecycle of a product where it's got like innovation, energy expansion, and then like maintenance mode.

26:15and you've listed in one of your blog posts, a lot of Marketo features that went out sort of half baked, I think, as you described it. And I've observed this, anyone watching could see every year at summit, there was like SEO, social, ABM, like it was really clear, what's the trend? What's the buzzword this year? We've got to do something for that. And then it was like a big splash and then half quarter baked, never came back to it. So there was this, and I'm not saying this to like dump on Marketo or criticize anyone, but it's a dynamic that you can observe. In the market and it makes products suck.

26:47and that hurts me as like someone who, a big part of my career is working with these products. And I wonder for your thoughts about how does a company avoid this? And I asked this to founders that I speak to too, like, how are you going to avoid making your products suck? Cause you can see it coming. Like, how does somebody avoid that, rock in the water? Glen Lipka: To me, I can peg it to 2012, we went public, and from that day forward, everything went out differently. so like, in the beginning, there's a thing called PCAMP in Silicon Valley,

27:18which is for product managers and they were talking about releases and I was like, we release every two weeks and they literally almost fell out of their chairs of like, are you crazy? How is that possible? And it's because we were young and didn't know any better and we were just doing things. And if you go back in the release notes, and I think that they're still there, the first year of release notes is me writing personally. Like, so if you look at the way the release notes are written,

27:49it's not these big stories. It's just, okay, now I, now we have this, now we have this, now we have this, and it's fleshing it out. It's adding to the story. And then there comes a point where they start being very long and much more like flourishing. And that's the point of where professionals got involved. And at that point, there was these, there was no such thing as a small improvement. It was always a huge thing. And it was.

28:19Really unfortunate. and I think that the point of where it was very painful was programs. we had reached a point where it's like, people are trying to do things that are really complicated. And this revenue cycle, analytics is not working, People did not like it at all. and I had actually left the company for a brief period, right. In the middle of it. And when I came back, they were like, you got to fix our analytics thing. Everyone is upset. And when I looked at it, I was like, okay, I see the problem.

28:51The problem is, is that John Miller is a physics major, from Harvard and Stanford, and he's incredibly smart. And he's like, everyone should be thinking about the percentage that your, conversion from lead to opportunity is dropping at a precipitous rate compared to, you know, the last year is over, blah, blah, blah. And I was like, that's not what people want. They want to know how many webinars did I have? I had six, that was it. They just wanted to know how many programs did I run? How many things did I achieve?

29:22They weren't getting measured on like these. I described it as buckets of M& Ms where the holes would be changing sizes at different rates and the M& Ms of different colors would be coming out of the buckets, going into different buckets. It's like fluid dynamics. And I was like, it's so complicated. It's not what people want. They just want to say the basic thing. how many mail blasts did I do? How many opportunities did we influence?

29:53And that this was around the same time that marketers started having this schism, the marketers who were overreaching, trying to say that they created the revenue and the other marketers who were like, let's just claim that we did the webinar. And that. I think that there was a huge overreach in that first group and it created a lot of problems with sales. So we made program analytics, which I have two patents.

30:24Both of them are relating to this period. I literally did math for all year of just figuring out like how things were going to work. How do we, you know, things like first touch, attribution and last touch attribution and multi touch attribution. I didn't intern. Name Karina Boo from, Cal who is helping me with all of these charts and graphs of like an S curves of exactly how we were going to attribute things. she's a, founder in her own right right now of a company called Warmly. And, when we made programs, I said, okay, people aren't going to just want

30:58to do this just for the analytics. We need to give them an extra reason to do this. And I said, the good, the easy reason is. You don't have to go to the design studio. You don't have to go to these other areas. You can just make your program with all the stuff in it right there. And, we call those local assets. And I said, the local assets is the reason to make it easier for people to use the software and that the benefit they'll get is the program analytics, the attribution that you can't just go into the attribution.

31:30You have to give them a little bit of candy first, and then they'll take the attribution. And that was our biggest feature ever. That's a huge change from the way it worked beforehand. and the design of all of it with the different program types and, success and how does it sync to Salesforce? campaigns. It was all very intricate and I really love the design that we put together for that. And then I got in this argument with Cheryl Chavez, who is the.

32:01product management director, where she's like, we have to get it out the door. And I said, I don't think people will remember what month we delivered this thing, but they will remember how it made them feel when they first used it. And if it doesn't have these local assets. It will feel broken. And she insisted we launched it and everyone was upset. Everyone was super upset because they were just like, you made this big change, but why it's like, there's no point. And it was only two months later that we released the full version.

32:36And then everyone was like, Oh, this is great. we can use this. And then programs became a much more successful. concept, but that, was a very upsetting moment because I knew it was wrong. I knew it was going to cause us grief. And for what, for a couple of months, nobody remembers what month the feature came out. And I think that it was around that time that we were getting ready to go public. after we went public, it was always another story. We needed to tell an acquisition. Social was.

33:07Like a thing for like a few months. And then I'm like, nobody's going to use this. Nobody's going to care about this after it stops being the cool thing, the cool flavor of the month. And there was a AB testing and I'm like, I'm just going to use this, and so we made it and it did a thing, but it was just one story after the next that sounded really cool, but like I knew it wasn't something that was going to make a huge difference. And it was just about satisfying investors and about.

33:42Announcing things and acquisitions. We did so many acquisitions and I was like, why are we acquiring this company? They don't matter. You know, we could, build our own thing of this. It doesn't even do anything interesting. And I learned firsthand, like the power of the quarterly report. and I think it's a, there's a tyranny to it that makes it. So you have to make each story bigger than the last. You have to keep making, like these acquisitions and it's hard to integrate a company. And.

34:12I think that to avoid this problem to a certain degree, you have to separate out your product development from your investor relations. You have to say investor relations. I know you want us to make a bunch of cool stuff and we're not going to and that you're going to have to tell your stories. On your own, we're not going to acquire companies. We're not going to just make half baked software. You guys are on your own to tell the story that you're going to tell. And to a certain degree, it will depress the stock a little, however,

34:46your customers will continue to love this, the product, and that will increase the stock price. And so I think it washes out in the end, but you just can't let your investor relations arm dictate your product development strategy. And I think this is very much, a Steve Jobs way of thinking about things, that he would, when he came out with the iPhone, there was a bunch of people, and it's hard to imagine this at the time, who were saying, you're idiots,

35:16you're going to ruin your iPod business. Because they were just like, look how much money you make in iPod, you're going to cannibalize that business. think of the mindset that you have to be in to say that Steve Jobs is an idiot for coming out with the iPhone. But that's literally what people said. And there's a bunch of videos of him talking about some of this stuff. One guy is giving him a horrible time about not understanding what the open doc format does or something like that. And he's trying to explain to the person that that's not

35:47how you build a great company. You build a great company. By sticking to your values and by creating things that you think are great and taking the time it takes to do it. If you do great things, there'll be stories to tell. There'll be announcements, but if you focus on the announcement, you probably won't build a great thing. Justin Norris: And, you know, I've wrestled with this a lot because. I've seen them focus Marketo and, almost every other company I can think of

36:21that's reached the stage, focus more and more of their effort on products or new features or new modules that are going to add incremental bookings. So they want to roll things out that are going to increase contract value. Meanwhile, there's a backlog, a million miles long of like features that users every day are like, I need this, I need this, I need this. And you can understand the logic because they say, well, no, one's going to churn because of this one missing thing. So let's focus on this. And like, it's a spreadsheet math. And if you go against it, you just seem like you're this, crafts

36:52person who doesn't really understand economics and doesn't care about shareholder value, et cetera. But I think what they're missing and what you've described is this long game where like the product becomes less lovable, it loses its integrity, loses its value in the eyes of the people that use it most. Glen Lipka: two good examples of that in Marketo, history is AB testing. There was a, sales VP. Who said we have to have AB testing. We keep losing deals because of AB testing. And I'm like, I don't think it's going to make much of a difference.

37:24And, he insisted. So we built AB testing. The analytics show that 97 percent of all users use it about 3 percent of the time. And that 3 percent of the users use it like 97 percent of the time. So in other words, there's this very, very small group of people that love it. And most people were like, I tried it once. And I remember a user once told me, you're, killing me with A B testing and I asked them why. And they said, I used to only have to write one email and

37:56now I need to write two emails. Thanks, Glen. And I'm creating work for him. And, on the flip side were tokens, which nobody asked for. Nobody asked for tokens. But I said, no, none of these are going to be cool. And it's because of my position in the company and I could just make certain things happen. And it just made tokens happen. Tokens ended up being like one of the most powerful features used by everybody.

38:29incredibly powerful feature, but nobody asked for it. And in the demo, you don't even like talk about it necessarily all that much. but it was one of those things that made Marketo what it was, that was maybe one of the last big features that were like that, just came from a place of, ah, this would be cool, right? Instead of a place of, this will tell a good story.

38:59So like AB testing on the one hand And tokens on the other. every company has the ability to do that kind of work. And they have people who know, but I think that product managers Don't they're not taught how to do that. They're it's a lost art in product management. And most of the time, product managers are feature people. They just want to like pummel the user with release features. And instead of thinking there's certain kinds of features that expand your story,

39:35like more flow steps might do that. There's certain ones that expand the surface area, like tokens allow for new kinds of things to happen. but most of the time they're just like, well, they voted on these features. Let's do the ones that they voted for. It's a lack of imagination. But I think most companies, they have people who can do it. And I think as a society, we just don't value this very much. We don't value innovation. Like we value it in the genius CEO, but we don't value it as a

40:07regular old job that people have. Most designers that I meet, they don't understand differentiation. They don't understand how to do real innovation. They don't understand how to think about products this way, and they're not being taught how to do it. And it's not being valued in them. If they do it, it's very difficult. There's a lot of companies that hate me. They hate that I do this. And which is why I, I feel great when I. Land in a place of where they value it and they care about it.

40:39But real magic happens when you empower the people in your organization who get this kind of concept. Justin Norris: What do you think about HubSpot and as a product company and what they've been able to do, because they, it seems to me that they have pursued a slightly different course than their peers in the marketing automation space and have continued to expand what they do, but in a way. Like it feels they haven't lost that mojo, so to speak. Maybe it's gone up and down, but overall they still have this

41:10tight knit, passionate group of users and it still feels like they have that energy behind them. Do you, do you share that perception? And if you do, why do you think that is? Glen Lipka: I remember when I first saw them, they said they were marketing automation for the fortune 50, 000 or something like that, or the fortune 5 million. it was, very clever because Eloqua was clearly the enterprise. We were clearly the mid market. And they said, we're going to take the low end. and I thought that was really smart positioning.

41:41Positioning is another concept that very often gets overlooked, but it's super important. You have to be in the middle. You can't be the too expensive one and you can't be the cheap one. You need to be the Goldilocks provider. And, I think Marquetto had that for a long time and then started to lose it actually. As HubSpot started coming up. I think that their positioning was really smart. I remember seeing their UI and thinking there was some parts of it that were fine.

42:14they would put the responses on the landing page object itself, but instead of like a smart campaign where it's abstracted, they would say, Oh, take the landing page, flip it upside down, and it says what to do when someone fills it out, which in some ways is like, you know, That's clever and easy. In other ways, it's more limiting, right? But very often limiting is not as limiting as you might think. And that it's, if it's close enough that you can say, Oh, it's a religious war.

42:45I think it should be, and somebody else thinks it shouldn't be. And, that way you get half the market. I think that did a really good job of their branding. I think they did an amazing job with their content HubSpot content was. and they did a lot of things that I think were close enough. That's the thing about a lot of software close enough is really fine. It's then it becomes about your differentiation and about what you're doing. it's not all about the features.

43:15And I think they never focused on having the most features. So I wasn't ever the let's analyze the comp, the competitive product guy. I just, I knew what we were doing and I focused on that. but I definitely appreciated their positioning, their marketing, their content, their willingness to try different things. I think that their play into CRM, lightweight CRM was brilliant. Cause then they were like, you don't need Salesforce. There was a lot of people who were just like sick to death of Salesforce, whereas

43:50with Marketo, you had to have Salesforce. You couldn't have Marketo and not Salesforce. there was a period where I thought Marketo was going to be acquired by Salesforce and, the CEOs, Mark Benioff and Phil Fernandez got into it in some weird way. And, the stories were, how it didn't work out, but I just thought we were like a perfect fit for them. it just goes to show how You really don't know how things are going to turn out in the middle of it. Justin Norris: I want to, in the time we have left, switch gears a little bit and

44:21just think about AI and open ended topic. I know you're just someone who likes to think about technology and trends and where things are going. And I'd be curious for your read on the current situation, either AI impacting your workflow as a product designer, like AI for product designers, or just AI as being incorporated into products as a builder of things, take it whichever direction you please. Glen Lipka: It hasn't affected anything from a, make product perspective. it's definitely in the middle of the hype cycle right now where

44:51it's, the peak of expectations. And it'll probably fall into the trough of disillusionment at some point. I think that there's this very strong desire on the part of human beings to, To have a friend that can't escape, that it's not exactly a slave, but it's like, it goes on my phone and it seems to have free will, but it can't, betray me and it can't be mean to me.

45:23It has to always be nice to me. And it's like a friend. I think that that desire is nearly overwhelming. in human beings, and that we desperately want this. And then along comes something like ChatGPT, and it, talks, and it seems like it can't go anywhere. But then, you realize it's kind of an idiot. I had said to ChatGPT, when I was younger, there was this poem about a

45:54coal miner who, when he went to work, his Children were in bed unconscious. And when he came back home, his Children were in bed unconscious. And in his mind, his Children were in a coma, right? And it was only because he worked very long hours early in the morning, late at night. And I had kids at the time, and it had made me sad of, like, working too hard. And so I said, Chachi B'tee, what is this poem? And I described it. And it goes, Oh, yeah, yeah, yeah. I know what poem you're talking about. And it told me the author and the name of the poem. And it even listed the poem.

46:24I'm reading it and I'm like, something's not right. This, this is not the poem. So I Google it. And I'm like, there's an author that it cited. But they didn't write this poem. And I was just like, so I said to Chachi B. T., I can't find this poem. And they were like, Oh, that's because I made it up. And I was like, okay, don't make up a poem. I'm there is an existing real poem. And it goes, Oh yeah, I gotcha. And I'm like, I just want to know the author of that poem and I'll go find it.

46:56And it's like, yeah, it's this author and here's the text. It wrote another poem, a completely new poem. And I'm just like, dude, what are you doing? And it's just like, well, I couldn't find the poem. So I made it and it, looked me dead in the eye and said, this is a real poem and a real author. And it was written in 1874 and it made a whole backstory for this poem. And I'm like, why are you lying to me? And the answer is. Because people want a confident answer I don't want to not

47:30give you a confident answer. I was like, but I asked for the truth and it goes, I don't really understand what you mean by truth. I understand what you mean by tell me the answer to a question. And I could write something that looks a lot like the answer to your question. It's not true. It's not real, but it looks a lot like the answer to your question. This is what we have today. This is what AI is. I remember way back, there was a famous Marketo sponsored

48:01bake off of lead scoring. And they had like, I think it was Lattice or somebody, and it had an AI scoring thing. So we had the Marketo way, we had rules, and you had the AI way. They let it bake. They let the sales happen. Turns out, six in one, half a dozen in the other. Nobody won. But marketers overwhelmingly said, well, if it doesn't matter, then I'm going to do it the rules. Because if I just have a button that does it, what do you need me for? like I want to be paid for doing work.

48:33And if there's a button to do my job, then that doesn't bode well for my career prospects. And so I don't think anybody truly wants AI to do their job. I think they want a slave on their phone that can't leave and it's got to be nice to them and that maybe can do some things for their job to make their job easier, but only in so far as it can't replace them. That as soon as it replaces them, it's a problem, but as long as it doesn't replace

49:07them, then help being helpful is fine. for example, in Figma, if it named my layers for me, great. But if it came up with the differentiated, point of view of like, oh, you should do tokens and here's how tokens should work. I don't think that's going to fly, but there's nothing that I've seen in any AI yet where it can do honestly. Anything relating to product development. I think an area where it might be good at is, testing like, Selenium script

49:39writing, looking for vulnerabilities where like there's a buffer overflow, problem. And it could find that in the code and fix those kinds of things. I think like code helpers, syntax helpers, all of that is useful. maybe some illustrations, but even those, like, they're kind of terrible. I don't mean to pour water on everybody's idea of AI. I just think it's wildly overhyped and mostly based on a psychological need,

50:09as opposed to a real technical ability. Justin Norris: No, I mean, that's really interesting. I've seen the same things that you've seen. I remember even coming up for the name of this podcast. I was like brainstorming ideas and it was like, give me a list of like 20 words, like associated with this aesthetic. And it would give me a list of 20 words of which like maybe seven were duplicates. I'm like, can you please just give me a clean list of 20 with no duplicates? It's like, Oh, sorry, sorry. Here you go. Again, the same, like that sort of thing. It's like, what, what, but then I've seen, like, I'm using it to create images for my sub stack.

50:40I'm like, give me an image of this in like a 1950s sort of cartoon jazz aesthetic and like, it does it. And it's got weird wonky things in it, but It's okay for my sub stack and to pay an illustrator to do that by hand would be completely cost prohibitive. and so it seems that there is this niche where you can use it to get things done or, automate certain things that you would otherwise have to do, I agree completely that nobody needs to be replaced and the psychological need of like the friend that's almost the part that creeps me out the most, to be honest, because if you have someone who's always emotionally available, you know, can't

51:13Not want to give you attention, et cetera. What use do you have for real human relationships after a point in time? And that's the part that scares me about AI. Glen Lipka: I do worry about those things. At the same time, I feel that loneliness is a debilitating feeling. there's a reason that having a friend on your phone is so useful. There's a reason why something like Twitter works. Like people want to be heard so badly.

51:46That they're willing to talk to crazy people just to get that. I think that we're living in incredibly interesting times and yeah, we're making some cool products. We're also changing the world in a way that's very scary. we're certainly entering a post truth world. and I think Adobe is more than any other company, responsible for the capabilities of deep fakes. And that for your substack illustrations, there's some designer

52:18out there that's like really bummed. He used to get work and that's an area that AI is doing better than most. But what happens to those designers? What happens to humanity? Cause one of the things about AI is also, it's, what it's fed. It only knows how to make the thing that has been made before, like a 1950s style or whatever, but what is a 2040s? Style look like, nobody knows that yet. And if we're not training, designers, if we're not giving designers

52:51a living, then who is going to make that. Justin Norris: We'll never have it. It'll just be endlessly regurgitated content back and forth into the model. Glen Lipka: with that said, maybe we're becoming so efficient that people can have those sorts of jobs without it being a career. Like I'm a big fan of universal basic income where we can pay people enough to live. And so they can be artists without starving. They can be musicians without starving.

53:23I think that the world is changing. It's important for all of us to not be reactive, not just assume it's going to be bad, but also don't assume it's going to be good. we have to think about the details and. Keep trying to goose humanity forward. So we make innovative things, in new and different ways. Creativity, I think is more a value that people will. Care about in the future, not less, the more AI, the more

53:56automation, the more technology helps us, the more that creativity matters. Justin Norris: And I think you can see it like in the rise of platforms like Etsy, which is specifically about like people valuing something handmade. of course, all the like mass producers are snuck onto Etsy now as well, and degrading the quality of that, but you're right. There is a hunger for something like, I want something built by hand, something that wasn't scaled, something that's unique, that's one of a kind. I know we're, out of time, but Glenn, this was just a fascinating discussion. So, glad you were able to join us today.

54:28Glen Lipka: Thank you for inviting me. This has been great. And I really enjoyed talking with you today.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Building a Company Brain for AI - Jacob Dietle

    Sep 27, 202646 minVideo

    Every time you explain your business to an AI from scratch, you’re repeating work. The opportunity with context engineering is to make your company’s expertise, processes, and past learning available whenever an agent...

    Listen to the audio

    Credit the people on this episode

  2. The Operator's Roadmap for AI in 2026 - Lily Luo

    Jan 9, 202644 minVideo

    Justin and Lily reflect on their parallel journeys diving deep into AI throughout 2025. They discuss why most AI content misses the mark for operators and system builders working within corporate constraints, share...

    Listen to the audio

    Credit the people on this episode

  3. SEO in the Age of AI - Gaetano DiNardi

    Jun 17, 202550 minVideo

    SEO used to be the ultimate growth lever - offering massive “free” traffic to marketers who could outsmart the algorithm. But in 2025, it's a different game. In this episode, I’m joined by Gaetano DiNardi - an SEO...

    Listen to the audio

    Credit the people on this episode

  4. How AI Agents Really Work - Daniel Vassilev

    Mar 21, 202549 minVideo

    AI agents are everywhere in conversation right now - but what actually makes them work? It’s not just slapping a large language model into a workflow and calling it a day. Under the hood, real agentic systems operate...

    Listen to the audio

    Credit the people on this episode

  5. The Journey to VP of Marketing Ops - Kimi Corrigan

    Feb 12, 202546 minVideo

    Not many people make it to VP of Marketing Operations - Kimi Corrigan has done it twice. In this episode, she shares her journey from marketing coordinator to leading marketing ops at companies like Duo Security, Cisco,...

    Listen to the audio

    Credit the people on this episode