Latest / Not Just Faster Horses / Vijay Nathan Ex-SVP, Product at Apartment Therapy Media
Transcript
- 0:00We have not been in a period where innovation is happening at such a rapid rate that is literally in our fingertips on the next day.
- 0:07Ton of individuals and companies are using AI for X, Y, and Z stuff, but the company's not really seeing any increased value. Having this be 10% of one of your other pers- people's time just doesn't work.
- 0:17What I found is that some of the most transformational stuff we did at Apartment Therapy using AI actually ended up having no AI in the end product.
- 0:23This is Not Just Faster Horses, conversations about deploying AI in media companies across people, product, and technology.
- 0:29I'm Ben May, founder of The Cone Company, and today I'm speaking with Vijay Nathan, who until recently was SVP of product at Apartment Therapy Media, the home and food publisher behind Apartment Therapy and The Kitchn.
- 0:42So Vijay, you joined Apartment Therapy Media in 2015 as the first product manager. Talk about what the business grew from when you started to when you just most recently left. It was a very different time back then.
- 0:54You know, I was coming off of the heels of being a founder. I had a startup in the food media space that I did for three years and multiple pivots.
- 1:00And you know, to be honest, I came in with zero actual defined product [laughs] manager experience, and, you know, that- that's really what I got brought on to do, was not only be a product manager but figure out what product meant at the company.
- 1:11And I think that's, like, a very interesting question when you talk about, like, what is product at a media company? Depends who you ask, I think is the answer. Uh, yeah. Y- yeah. Yeah. For me, really, the, the...
- 1:20My mission was to figure out how do I make product an integral part of this company's operating strategy, not just a support role, uh, not just taking in requests constantly from other teams, but actually being able to have a seat at the table to be a leading voice in strategy and help co-create that with the rest of the company.
- 1:36How does Apartment Therapy Media, how have you historically thought about product engineering, editorial, how those sort of functions across the business all work together?
- 1:43Yeah, so one of the interesting models that we took is that product engineering and let's say web design have always sat under the same umbrella.
- 1:50We've never had engineering and design be separate or engineering and product be under separate, um, leaders.
- 1:56The, the thing that I really tried to do was embed myself into all of the other teams, and as I started hiring people, what I used to tell them was, like, "It is our business to be in everyone else's business."
- 2:05That meant developing close relationships with, uh, people of all levels on other teams, whether it's editorial, various parts of the revenue organization, and really establishing constant two-way communication, um, where people knew who they could go to to talk about an idea.
- 2:18They knew that ideas were welcome to be brought forward. We knew that we could bring things forward to them, and really building, like, a very collaborative relationship.
- 2:25And that, that was kind of a key part of what we did that ended up paying a lot of dividends over time, was product was not just this kind of separate team and org.
- 2:32It was really embedded throughout the entire organization and, you know- And, and the business sort of tripled, we were saying, over, over that sort of 10, 11 years you were there.
- 2:40And what's the product look like when you first started versus when you left? How did you leave the business thinking about that? So when I started, like, no one knew what product was.
- 2:47And so [laughs] that's both a good and a bad thing. I had to kind of figure that out, establish that for myself, but it also gave me a lot of
- 2:53runway to say, like, what do I think this should be and how can this be, this role be most effective within this company?
- 2:59To start, I mean, it was just basically a flood of tickets coming in from various, you know, or, or requests coming in from various, uh, internal teams. Very small engineering team.
- 3:08I think we had five, maybe six engineers at the time, one product person, one designer. Like, that was basically it. And we covered, you know, the en- the entire stack top to bottom left to right.
- 3:16So is this another word for project manager? So does that, like, the thinking back then was just, like, facilitating what the devs are doing? Yeah. Yeah. I, I think that's, that's, that's probably a fair way to put it.
- 3:24And then over time, you know, as, like, I was able to expand our presence, I think that became much more of, like, a leadership-oriented role. Peopl- people looking to, um, product for guidance on how to solve problems.
- 3:35Mm-hmm. Pe- people bringing us problems, not solutions, um, which is really how product should operate- Yeah... in a, in an ideal, ideal world.
- 3:43What do you think media companies sort of struggle to put their finger on with product?
- 3:46I mean, to be honest, I actually think that media companies and product people in media companies have a lot to take from and learn from and be inspired from going down that Lenny's podcast realm- Yeah...
- 3:55or the How I AI realm. Like, going into that world of, like, deep, deep SaaS, B2C major product management and how they think, how they operate, what best practices are.
- 4:05I actually think we have a lot to learn on the media side from that. Mm-hmm. And that was always where I looked for inspiration. I'm like, I don't care that much about how other media companies are doing product. Yeah.
- 4:13I care about how the best-in-class product teams in the world- Yeah... are doing product.
- 4:17So, so leaving after 11 years and sort of being through this whole phase of, like, where we were in 2015 building web to now with obviously AI in the mix, um, how is product sort of working in the business now, uh, as, as you leave?
- 4:32Uh, how's work getting done from, from when you started? Uh, I would say especially in the past year to year and a half, um, I was on the early, I was on the early adoption side of a lot of the AI stuff and, and- Yeah...
- 4:41and ended up bringing a lot of that into my, into my product management team. Um, and I will say especially in the past year, it's really changed how we approach the standard product development life cycle. Mm-hmm.
- 4:52Especially on the kinda early parts of that process, the discovery, the prototyping, the requirements gathering, being able to iterate through ideas rapidly, being able to critique and get feedback on ideas rapidly.
- 5:04Mm-hmm. Our ability as, as let's say non-engineers to push ideas much further than we could have before, that's really changed a lot. Yeah. Now, that comes with, I think, its, its downsides as well, right?
- 5:16Um- Early adopter fear, yeah. Yeah, early adopter fear. In some ways you're now moving faster than your counterparts- Yeah... inside and outside of your team. Yep.
- 5:24And so the, the, the, the burden has just shifted, [laughs] right? Yeah. It's not, it's not- Yeah. You're moving faster, but can other people keep up? Yeah. Yeah.
- 5:31Not in a bad way, but just in the sense of, like, they're used to working with a certain kinda cycle. Right. And now if that doubles- And it's a larger team, change management, all these sorts of normal things.
- 5:40Yeah, it's, it's... The change management's a, it's a big part of it too, which, which we can talk about, but that's really, you know, in at least in my pod of product- Yeah...
- 5:46um, and especially product design and, and engineering, we were really starting to lean in heavily to how do we just completely rethink the way that we work. We were changing things up all the time.
- 5:55No, no manifesto internally? [laughs] No manifesto. Yeah. I, I thought about it many times and I was like, "This doesn't make sense 'cause in three months we're gonna change it anyways." Yeah.
- 6:03But when you have a small team that's highly capable- You have the right people there who all work well together. You can afford to be a little bit loose on some of those things- Yeah...
- 6:11with the interest of, like, we're always just going to be improving the way that we work- Yeah... for whatever best meets the business need at the time.
- 6:19How are you thinking if you were to be dropped in tomorrow at a blank canvas, um, would you be thinking about designing out product engineering function from sort of idea to delivery? Yeah.
- 6:31I, I mean, the, the, the thing that I took away from my time at Apartment Therapy, especially working with AI, being one of the early adopters, power users, seeing other people start to upskill and, you know, use it more- Yep...
- 6:43was that you hit this inflection point, and it happens pretty fast when you have a bunch of individuals in the company doing their own thing, doing great work, being leveled up with AI, doing really awesome stuff.
- 6:53But once you start working with some of these tools, you start to realize, like, you know, you sort of have to balance individual increases in productivity with long-term business- Yeah...
- 7:03value, and those things are not always the same. I think, you know, you hear a lot of the news saying, "Ton of individuals and companies are using AI for X, Y, and Z stuff." Yeah.
- 7:12But the company's not really seeing any- Yeah... increased value, and I, I totally see that being true because not enough time is spent early enough investing in the system. Yep. But what next?
- 7:22And I think what next is we're quickly moving from individual capabilities and enablement to, like, team capabilities enablement. Investing back into something that actually scales with the business. Yeah.
- 7:35There's no point in having half a dozen power users at 500% speed, and then there's some people who are doing chat, like, once a day or something, and that's about it. Are there anything that jump out at you?
- 7:44Like, what things have stopped?
- 7:45What have the team stopped doing that you would've been doing a couple of years ago that sort of AI has allowed you to sort of either rethink completely or, or just not needed entirely anymore?
- 7:54We really spent a lot of time focusing on the, the sort of design and prototyping part of the product development life cycle. Mm-hmm. Let's make something up.
- 8:05E- editorial comes to you with an idea for some new feature in the CMS. Yep. Okay. Previously, we would have taken that idea. Maybe one of our designers would've done some, you know, wire frames, lo-fi wire frames.
- 8:16We would've taken that back. You know, someone on an editorial team may not grok a lo-fi wire frame as well as they would like something, you know, more high fidelity- Polished. Yep... polished. Okay, so then we go back.
- 8:25We do that again, and we go through all that, and eventually, we get to a place where we're like, "Okay, it's not, it's not really interactive," [laughs] you know? Yeah.
- 8:31It's kind of static or just some slides or whatever. Yeah. Um, and then we go into engineering and blah, blah, blah, right? Like, it goes through that whole process, and there's so much iteration that happens- Mm...
- 8:41from a product concepting perspective- Yeah... that the more you have to hand back and forth, back and forth, it just creates a ton of churn that is... really provides no value to anyone.
- 8:49No, it's just t- It- It's just coordination time. Coordination time.
- 8:53Um, and so I think allowing both our product managers and our designers to just have those tools available for that relatively hi-fi prototyping- Mm-hmm...
- 9:04across our stack, whether it's our consumer sites, experiences, or our internal tools, and actually be able to, like, iterate on those things and get really far so they can hand an editor- Yeah...
- 9:15within a few hours a good enough prototype- Yeah... of how this thing could work. Yeah. Which means you shorten the ability to get... shorten the timeline to get feedback. Mm-hmm.
- 9:24You improve the quality of the feedback because the people giving feedback are seeing something that feels more real. You can quickly adjust within minutes to, um, to changes or requests or feedback that they have. Yep.
- 9:35And then when you actually hand that over to engineering, you have, you know, y- ideally, you have accounted for a lot of the things that would've come up during the development process. Yeah. Yeah, that's right.
- 9:44E- error states, button interactions, X, Y, Z. Like, you've kind of a- have accounted for all that. S- so we did a lot there, and one of the key things that we did was actually build out, um, agentic design systems.
- 9:56Mm-hmm. So Designs MD and kind of all the associated things ar- around that, um, which is sort of a, a new, newer part of the whole, you know, s- world. But we did that for our two main sites- Mm-hmm...
- 10:07core experiences, like basically all the, the site, site Chrome, site modules- Yeah... components, all that kind of stuff, as well as for, um, a couple of our key, like, internal tools.
- 10:17And so we covered a lot of ground for, you know, someone says, "I wanna add X button to X page on X article." Like, okay, we can prototype that in- Yeah... a second.
- 10:26But also, it allowed us to incorporate our actual design systems and design standards into that so when someone was prototyping, the button looked like the button was supposed to look.
- 10:33It wasn't a rainbow, uh, experience. Exactly. So in terms of, like, prototyping and thinking through ideas, like, were you getting...
- 10:39Like, obviously, product managers, like, they'll c- someone will come to you with a problem.
- 10:43Were you also sort of encouraging, I guess, like, an editor to actually do that first r- round of prototyping themselves before you even sort of bother a product person with, like, "I've got this idea.
- 10:53I don't know if it's any good," or give that to you? You've now got Claw. You've now got a design system. Like, you go figure it out, and they've done 15 rounds of iteration- Before they even bring it to you...
- 11:01before they even bring it to a product- Yeah...
- 11:02product manager who can then polish it up a little bit more, who can then finish that off and then take it to an engineer who's like, "Oh, great, I just have to, like, not screw this part up and, and ship it." Yeah.
- 11:10I mean, I, I, I love that. A- admittedly, we did not get quite there, but that- Yeah... was always where all of that effort that we put in was going. It is a good goal. Yeah.
- 11:19And the way that we built out the sort of agentic design system- Yeah...
- 11:23was always meant to be like, oh, in theory, someone else in the org who- The CEO wants to, like, have an idea in the middle of the night, they can just, like- Well, he was doing, he was doing it.
- 11:29So [laughs] we, we, we got him on board. Yeah. But you know, if an editor or someone else on another team wanted to prototype something on the site just to, like, explain their idea- Yeah... they could.
- 11:36That was always why we built that, h- how we built that system to intend to work. Um, but I will say that I think there's a lot of pre-work that has to happen before- Yeah...
- 11:46you can give someone, something someone like that and be like, "Go use this," right? Yeah. Um, there is a certain level of, like, core fluency around using any AI tool- Yeah... that one must have.
- 11:56There's a certain amount of desire [laughs] around- Yeah... using an AI tool that one must have. Really understanding, like, that change management side of things. Mm.
- 12:03So if you actually wanna get your company to be AI powered, if you actually wanna find efficiencies, like, how do you actually... Yeah. What, what, what, what needs to happen a- and starting with, like, a people level?
- 12:11Yep. Um- Because the assumption that everyone is excited about this, and I, I will say, I, I, I fell into this trap very early being a power user, just being hungry for knowledge and learning. Yeah.
- 12:20I'm like, "Everyone should be using this." Yeah. "This is so exciting. Why aren't you using it?" It's easy to become a bit AI-pilled, uh. It is, it is easy.
- 12:25And, uh, you know, but then i- if you're gonna do this from a leadership perspective- Yeah... you have to balance that against reality. Yeah. And people have very real and valid concerns about these things.
- 12:37When we started taking AI, the idea of AI transformation outside of product and engineering, taking that to the rest of the company and thinking about, what does this mean for the rest of the company? Yeah.
- 12:46We really were considering the people side of it as a- Yeah... significant part of that. Uh, and that ended up working out well. Yeah. It, it is a long road.
- 12:55It is not a quick turnaround to do that if you wanna do it in a really thoughtful way. And, you know, it's, it's, it's, it's maybe not right for everyone- Yeah... in the org.
- 13:03Even if you gave them the capability, if you made the capability available- Yeah... I actually think the, a number of people who would take advantage of that- Yeah... without some, like, mandate to do so- Yeah...
- 13:12is very small. Yeah, yeah. They also- They've got a lot of work to do. Like- People have day jobs. Like- Yeah... this is not their core job. Yeah.
- 13:18This is all on top of what they are already doing and are probably already stretched very thin to do. Yeah. So, like, the role of product is really to be the strategic mind here. Yeah. Right?
- 13:28Like, you might have an idea and you have a hunch, and that's well-founded and it's coming from your expertise and experience. And we're gonna s- figure out, like, how and where and if. Does it make sense- Mm-hmm...
- 13:35in our product experiences? Yeah. And aga- also, how does it balance against other priorities we might have? Yeah. There's plenty of good ideas out there, it just may not be the idea to work on right now. [laughs] Yeah.
- 13:44How is that sort of changing, do you think, for businesses around, um, how they structure ratios of teams? Like, how we've worked for so long being sort of upended.
- 13:53I, I've always had maybe hot takes on sprints, but I also see the idea of a sprint as, like, uh, almost like a, a managerial lever.
- 14:02I think the question of how do our ratios change becomes very interesting because the assumption there is that ratios can reduce- Mm-hmm... if everyone on that team is moving at the same speed. Right.
- 14:13So let's just say you have one product manager, one engineer, and one designer on a pod. Yeah. If all three of those people are working at the same speed- Yeah... then you actually get efficiencies. Yeah. If they're not,
- 14:26then you're really no, in no different of a place than you were before. I think that's a very tricky thing to achieve. Mm-hmm. We have, um...
- 14:33But, so what, what we ended up doing is, especially when we wanted to go after something that we felt was highly valuable but we also didn't wanna spend a lot, lot of time on it- Yeah...
- 14:42we didn't want this to take up three months or a quarter or whatever. We wanted to see how far we could get in a month. Yeah. We would sort of shuffle around the squads- Yep...
- 14:49get the right three or four people in the room, and just say, "Go." Right. And move as fast as you can to get to this one thing, and take everything else out of their way. Yeah.
- 14:56And you can't, you know, with small teams and people, you know, product managers working across multiple functions, you can't always, like, just say, like, "Lock yourself in a room and go do this." Yeah.
- 15:04Or at least say, "This is your number-one priority. If anything else comes up, bring it up," you know? [laughs] Yeah. Um,
- 15:09and that worked well because not only were, we were combining people who worked well together- Mm-hmm... who could move at a similar style of working and pace- Yeah...
- 15:19and who had the expertise to do what they needed to do without pulling too many other people in. Mm-hmm. And that was kind of like that highly empowered, uh, squad model- Yeah...
- 15:27it was really, uh, it was really effective. And, and, and again- It was what you-... we used that as a lever. Like, we used that. It wasn't always what we did, but when we needed it- Yeah...
- 15:35it was something we would employ. You could do. Did you have a receptive engineering team that was, like, just as excited by AI?
- 15:42Was it you had, something you had to drag through to get, sort of live up to the vision that you were sort of having?
- 15:47It's, um, so, so I led the, the, the product or side of the org, um, and I had a colleague who led, led the engineering side of the org. Yep.
- 15:54And we, we rolled into, into one joint kind of, uh, chief product and technology officer, chief product officer. Mm-hmm. Also, we were a very tight team. We, many of us had been there for 10 years, eight years. Yeah.
- 16:03So we were very close, very close-knit. I learned a lot from, like, getting involved in the engineering side. Mm-hmm.
- 16:08And I think there's a lot of conversation in the industry about non-technical people getting into technical areas- Yeah... through vibe coding or whatever else it may be. Yeah. I was one of those people.
- 16:17I am one of those people. Yep. Um, I am rather technical to begin with, but I am absolutely not an engineer.
- 16:22I, I think that, like, this is where that idea of some people moving faster than others really catches up to you. Mm. Because it, it creates a bit of, like, a cultural awkwardness- Mm-hmm...
- 16:33when you have certain people, whether it's me or anyone else, it could have been an engineer, it doesn't really matter- Yeah...
- 16:37who's just like, who are saying, "We gotta be doing X, Y, Z, and all these kinds of things, and we're moving ahead." Yeah. And everyone is like, "Wait, what?" Like- Yeah, yeah [laughs]...
- 16:43"We're, we're, we're supposed to be doing what? Right?" I'm still filing my sprint report, yeah. Yeah, exactly.
- 16:46And, and so, like, that really is where my mind got going, was like, okay, if you're gonna do this, like, you have to bring everyone along for the ride. Yeah.
- 16:53And you really have to make sure that you are clear on what the expectation is around it. Mm-hmm. Not just be like, "You have these tools, now go use them." Yeah. Like, it's just never gonna...
- 17:02You're never gonna see the change you want to see. You're expecting to see, yeah. So that took us a while to f- to learn. Mm-hmm. Um, and it's a really, it's very top of mind for me moving forward, is, like,
- 17:14really being clear upfront about if you're gonna do all this, what, what's on the other side of it? And, you know, and then I think the other side is, like, what are your expectations of people to get there?
- 17:24I think very similar to what we saw on the editorial side and more of the creative functions, there is a lot of concern with AI usage in engineering as well. Yeah.
- 17:34And a lot of what engineers were maybe hired to do or brought on to do or had earned their expertise over years and years- Right... of experience at is now very different. Yeah. And some people
- 17:45are excited about that- Yeah... and, like, immediately excited about it, and some people need more to get there.
- 17:52So I think as, like, leaders and managers, uh, and facilitators, like, it's really important to think about the people you have on your team. Yeah. What do they need as people to get- Yeah...
- 18:03to where you ideally would like them to go, or the way of working that you wanna get to for your organization?
- 18:08Funny enough, like, in, in, like, talking about this under the tent of a media company, like, editorial people have been dealing with this for a long time of like, "Ah, I can use cl- I'm a writer now."
- 18:16Like, where anyone can set up- Yeah... a blog that they're a media company. Like, media people have had, like, so many existential challenges, and now it's come for, like, engineering- Yeah...
- 18:24because engineering has been like this You know, um, untouchable discipline for so long. Everyone was getting told a couple years ago, like, "Learn to code. Learn to code." Right.
- 18:32Which has just completely done a 180, uh, in, in, in months or y- years at best. Uh, how do you, like, manage that sort of gatekeeping? Yeah, yeah. It's, it's...
- 18:43You know, there, there, there's an interesting question of here is, like, what role does a product person play in, like, the engineering life cycle?
- 18:50You know, I was always very close to engineering because, you know, uh, uh, that's just how our team operated. Yeah. And I expected my product managers to be very close to engineering as well. Yep. And so it was very...
- 19:00I- you know, it was always intended to be a very collaborative, you know, relationship. Mm-hmm. But at some point you start to hit, like, okay, now the burden shifts to code review. Yeah.
- 19:08And- Now we have 40 PRs a day and no one can, can do anything. Right. Yeah. And so then, you know, my head really goes to, all right, so, like, what are you gonna do about it?
- 19:15And I think it goes back to you saying, like, and in a way, like, a lot of these businesses have got so much of this information all over the place. Yes. But to codify it so you have those standards.
- 19:23What are our engineering- It's a lot of work. Don't get me wrong. It's, it's like implicit- It's a lot of work... but it's not explicitly written down. Like, we've talked about it or whatever else.
- 19:29Like, we need to draw all of that out. I think sometimes, like, we, we, we overcomplicate- Mm... how much you need to do- Yeah... to get to, like- Yeah... a better result. Yeah.
- 19:38I actually don't think it's as much as people, people think. But to be fair, it's, it's hard to take time away and energy away from, like, executing or delivering the thing you're supposed to deliver- Yeah...
- 19:47to go, like, write a spec. I mean, it's just- Right? [laughs]... it's, it's like, it's the oldest time, like, the whole- It is... I think the IBM study of, like, what is it?
- 19:53If you have to do a s- a task seven times, like, del- Like... And that's when you get the efficiency. It's like, well, it's similar. Like- It's no different... don't do it right now.
- 20:00Go build the skill or go build the whatever you need to do to optimize that process, and then it will have paid for itself by the seventh time- Yeah... or, you know.
- 20:06And I, and I like, you know, I like what Every, you know, Every has talked about this as, like, compounding. Mm-hmm. I think that is, it's a, it's a brilliant term. [laughs] Yeah. And it's something that people...
- 20:12Like, clicks with people. Yeah. Um, there's many ways to execute that. Yeah.
- 20:16Uh, but I really buy into that f- that philosophy of like, you know, every time something happens that either should or shouldn't happen- Yeah... build that back into the system so the next time it is better. Yeah. Yeah.
- 20:27Um, a- and that's sort of a, a very different way of thinking- Yeah... than maybe traditionally product and engineering teams have operated. Yeah.
- 20:35Or you might just tell someone, "Hey, do this different next time," right? [laughs] Yeah. But if you actually codified it in any way, probably not.
- 20:40Where's your head go to the sort of, you know, one of the sort of visions people, some people have around where this ends up is product sort of essentially is, like, driving the robots that's doing the vast majority of engineering.
- 20:52Do you think that's a pathway that we end up in or, and some businesses end up, where you'll basically have a more technically competent product team that can do the vast majority of build a Jira ticket?
- 21:04You, you've done your PRD, you've approved it, you've, you've- Yep...
- 21:07dropped all of that context into a, a ticket or whatever you, system you use, and boom, it's there and it's ready to review a few hours later type thing. Is that a future, uh, for some?
- 21:16Uh, I, I think it is, but I would not say that it is a, you know, product, uh, uh, maybe a less technical person or a pr- a technical-leaning product person who is driving that. Yeah.
- 21:24I think whoever is the right person to be driving that should be driving that. Yeah. Is that the m- your most senior technical engineer? Possibly so. Yeah. And that person has more product sensibilities. Is it a- Yeah...
- 21:33you know, technical-leaning product person? You know, as a designer, like, I, I, I think that the role doesn't, to me, doesn't really matter. Mm. It's more of like, what is the work that's needs to get done? Yeah.
- 21:43And where are these agents or tools operating? Yeah. And who is the best person to understand and guide that- Yeah... you know, e- efficiently? How do you think about when you, when you're talking to
- 21:55other companies about, like, what they should be looking for in building out a new team? Like, what is the team of the future? In my mentality, if you want to get, like, a top-tier person into this kind of role- Yeah...
- 22:04it's almost as if hire... as if you were hiring, if you were a startup. Yeah. It's like as if I would've hired 11 years ago, which is maybe not how I would've hired five years ago. Right.
- 22:13Five years ago I might have needed someone with a specific set of expertise in a specific domain area. Mm-hmm.
- 22:19That was something that was maybe shared before, and now we have enough business there that we need a dedicated person- Yeah... and we go and find a person who's done this somewhere else. Yep.
- 22:25That might still be a need at some companies. Mm-hmm. Sort of ro- role players. Yep. But I increasingly think that, like, I would look for someone who has more of that hustler- Yeah...
- 22:35mentality, who really can go and figure it out. Yeah. And, you know, be really clear on what, know what they know, what, know what they don't know. Yeah.
- 22:44Um, even if they don't necessarily come from with, like, strong, you know, uh, exact product experience.
- 22:51It's, it's tricky 'cause, like, and I think about this when we look at hiring as well, like, you want people who've got, like, enough experience, but not necessarily so institutionalized- Right...
- 22:59that I've read them the manifesto and I follow- Right... the, the thesis on da, da, da, da, da, and we can't break anything. It's like, well, you have to break. Right.
- 23:05You have to, you have to be able to b- move out of lines and... I, I do think it... Like, I think there is a large amount of value of hiring from a, from within the industry. Mm-hmm.
- 23:15Which makes, maybe makes things more complicated, but I think, like, if you...
- 23:19A- a- and you know, I interviewed and talked to people in the past where we were thinking about bringing in people from other industries into our company. Yeah. And I'm just like, you know, these people are awesome.
- 23:27They're super talented. Yeah. But our organization at our size- Yeah... cannot support- Yeah... all of the training that we'd need for that person to really understand the business. My quality bar is now much higher.
- 23:38Yeah. My expectations of what something looks like before it gets to me- Yeah... is higher. Because I know you have the tools to do it. Exactly. You have no excuses. Right? Yeah.
- 23:45So if you're not doing it, that just tells me something, right? Yeah.
- 23:49So I think that personal motivation, so, you know, the, the, the eagerness, the willingness to learn, the, the h- the, the hustler mentality, figuring it out, um, being really, really strong at critical thinking and rigorous thinking is- Yeah...
- 24:01is important and that is a, that is not something you are born with. That is a- Yeah... skill you learn [laughs] Yeah, yeah... um, in various ways. Uh, and I think, like, bringing that to the table will,
- 24:13uh, you know, out- outperform other skillsets these days. The other piece is, like, if you've had a team that's been together a long time- Mm-hmm... bringing in people who have
- 24:24participated in fundamentally different ways of working- Mm... been in orgs where they just like, even if it's another media org, where they just work completely different- Yeah... is a good thing. Yeah.
- 24:32Because you sort of break the cycle. You have a chance to break the cycle of, like, just assuming that the way that you've done things is, you know- Yeah... the right way.
- 24:38So you've obviously been doing this in one place for a long time, and there's a lot of knowledge built up, and lessons, and watching this sort of, this story arc happen.
- 24:45What are you sort of excited about, I guess, as you're going to sort of independent work now, uh, and helping brands with? Yeah. What I saw at Apartment Therapy is that we had this momentum starting to build up.
- 24:58And, you know, largely I was lead- I was leading that, but it was part, only part of my job. Mm-hmm. Right?
- 25:03I was still [laughs] leading product every single day, and then got very involved and invested in kind of organizational-wide AI adoption and rollout, talking about company policies and, you know, guardrails, enablement, upskilling.
- 25:13Like, that, I'm very passionate about that stuff, and it was- Yeah... really fun. But that was not my day job. [laughs] Yeah.
- 25:18And so to find the time and space to actually dedicate towards that, to make the change that I, uh, that I think the org would benefit from- Yep...
- 25:27you know, I started to realize, like, doing that as a sliver of your full-time job- Yeah... makes it really hard to make progress- Yeah... in a meaningful way.
- 25:35And talking to other companies inside and outside of media, I sense that there is a lot of other similar companies at very much that same inflection point. Yeah. They have some momentum.
- 25:43Maybe they have some early adopters. Maybe it has some pods and teams using it. Yeah. And they're hitting this point where they need to put some more structure around it- Mm-hmm... an organization.
- 25:51It's not necessarily about guardrails, but it's about, like, figuring out where does all this AI stuff fit into our company strategy? Yeah. Where are we, where do we need to invest more of it in?
- 25:59Where do we invest less of it in? You know, what are our policies? Yeah. Um, you'd be surprised, and we found, like, how many employees are just asking for, like, rules. Yeah. Yeah. Yeah.
- 26:10And what tools can I use, and is it, is my data safe? Like, the, the- Yeah... what some might think of basic questions are really not so basic when you get into many orgs. Yeah.
- 26:18The other thing I think I, I see is that, you know, you see a lot of leaders talking about we're just gonna throw AI at everything, and we're gonna AI-ify everything. Yeah. We're gonna resize the company.
- 26:26And that really doesn't resonate with me as well. I think it's, it's about finding out where AI can be a competitive advantage for you. Yeah. And that may, that may not be the same for every company. Yeah.
- 26:36In some cases, it might be, you know, AI in your end user experiences enables you to do something for your customers that you've never done before. Yeah.
- 26:44That leads to new revenue or revenue growth or customer growth or whatever. You might on the other say, "You know, I just want every single one of my, my employees- Mm-hmm...
- 26:52to be at a high level of proficiency and just let them run loose." Yeah. Or you might say, "Hey, you know what?
- 26:56I think that this workflow that we have internally, AI could do this really easily, so we're gonna go build or buy an agent or agent tool or, you know, agent or tool to do this for us." Yep.
- 27:05"And we're gonna give that to our employees to use." Mm-hmm. And the interesting thing is, like, n- all of those things can be independent of one another. Mm.
- 27:12You could have 100 people in your company, and every single person is, like, fully AI, personally AI adopted, and you could have no AI in your end product. Yeah.
- 27:20You could have AI in your end product, and someone's built it for you. Yeah. And, or you've bought something off the shelf and, uh, integrated it, and your employees might be no different. Yeah.
- 27:29Your employee skill sets might be no, no different. Yeah. And the middle ground holds as well. And so, like, that's really where my head's going, is like really thinking about and learning
- 27:37where is the right application of AI within a company- Yeah... uh, without assuming that it's, it's everywhere. Yeah.
- 27:44And, and what I found is that some of the most transformational stuff we did at Apartment Therapy using AI actually ended up having no AI in the end product. Right.
- 27:52Like, we did some incredible stuff for, like, internal processes, especially over the past six months, that I'm super proud of, and it, like, dramatically transformed some of, some of our stuff. Yeah.
- 28:01And there's not one token being used in the end product. And that's funny 'cause that doesn't necessarily fit under product's role to streamline payroll issues or, like, [laughs] leave management or- Exactly.
- 28:13Like healthcare benefits or what, all these little things. So whose job is it, right? Yeah. Whose job is it is the question.
- 28:16The way I'm thinking about it is that there's, there's sort of a fr- a fractional head of AI role. Yeah. So to be, like,
- 28:23to offer, you know, support, advisory, guidance, and perhaps even build in, uh, to be the company's AI person- Mm... in the absence of them having someone full-time on staff- Yeah...
- 28:34which they may or may not need, right? Yeah. But I can tell you for sure, having this be 10% of one of your other pers- people's time- Yeah... like, just doesn't work. No, no, it doesn't.
- 28:41You will nev- you will never get as far as you think you can get- Yeah... with that, unless you take, it becomes that person's, you know, full-time job.
- 28:48Uh, with all the changes happening then, what are you sort of most excited about how AI's changing media companies? What does the future hold? Um, what gets you out of bed in the morning?
- 28:57I get excited by how fast things are changing and innovating, and just when you think that something is, you know, is not gonna work, the next day there's a release that, that changes that. Fixes it, yeah.
- 29:08[laughs] And, uh, it's both infuriating [laughs] and exciting at the same time.
- 29:11[laughs] Uh, but I think that we have not been in a period where innovation is happening at such a rapid rate that is literally in our fingertips on the next day, and that comes with a lot of, you know, warnings and prec- warning labels and precautions- Yes...
- 29:26and, and SOS on it. But if you are the type of org that can understand how to wrangle that- Yep... and do it in a positive way for your employees- Mm-hmm...
- 29:36um, where they are empowered, they are on board, they are as excited as you might be, which is- Yeah... you know, is a hard road to get to. Yeah.
- 29:45Then I think that, um, you have, you know, you have the ability to be a really interesting, interesting org. I really think about how do you grow the business without necessarily adding headcount? Yeah.
- 29:57That's kind of question number one that I would, I would look at. For a lot of the media companies that I see, it's like- Yeah... you know, how do you show growth? [laughs] Yep. How do you get yourself back on track?
- 30:05Yep. In some cases, how do you even keep the lights on- Yeah... without growing headcount- Right... when you've had, unfortunately, to cut really deep- Yeah... um, just to, just to stay afloat, you know? Yeah.
- 30:16It will be very interesting for me to watch, and I don't know where this is gonna go, how media companies use this for innovation- Mm... for the consumer-facing innovation. I'm unsure of that. Yeah.
- 30:26I worked primarily in lifestyle media, so you know, a very large consumer audience. You know, literally everyone who- Yeah... was walking on the street could have been a consumer of ours. Yeah.
- 30:34Are those consumers, like, they will be in a year or two ready for, they will expect an AI-driven solution. Yeah. They will know what that means.
- 30:41They will have experience in other parts of their life, so when they come to, you know, one of my brands- Yeah... they know what to do. Were we the, are we the right place to, like, introduce that? Mm.
- 30:50Is that actually gonna make a difference for the business- Yeah... the next year? I don't know. Yeah. That is kind of, I think, a, a question is, like, where in the business are people using AI?
- 31:02I think there, there's some companies, let's say like the Times, that have portfolios that are content and non-content- Yep...
- 31:10where some of these things become a lot more interesting in terms of AI and the end consumer experience. Yeah. For other traditionally content businesses, I suspect that it's probably gonna go a little bit more internal.
- 31:21Mm-hmm. Which is not a bad thing, but it's just- Operationals, yeah. Yeah, uh, operationals. Um, operationals data, things like that. Yeah, great. Wonderful. It's been a great conversation. Pleasure.
- 31:31Thanks for joining me today.