Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Lenny's PodcastLenny's Podcast

The new rules of product management in the AI era | Sherif Mansour (Head of AI, Atlassian)

Sherif Mansour is Head of AI and Product Craft at Atlassian (the company behind Jira and Confluence), where he has spent 17 years building and scaling some of the most successful enterprise products in history.

Lenny RachitskyhostSherif Mansourguest
Nov 22, 20261h 21mWatch on YouTube

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

Great conversations run long. Their best ideas don't have to.

uListen is free on iPhone, iPad, Android, Chrome, and Claude.

See how

Transcript

0:00 – 1:24

Teaser

Lenny Rachitsky 0:00 When AI became a thing, many people were like, "PMs are over. We don't need them."

Sherif Mansour 0:04 For a while, especially a year ago, it felt like the narrative was everyone's becoming an AI builder. We moved some of our product management designers to a team. Everyone was the AI builder. There was no PM or designer. I remember checking in with one of the PMs in the first few weeks and he's like, "It's unbelievable, man. We'll move faster than ever before." After about a month, he comes back and he's like, "Everyone's gone back to doing their traditional jobs." We realized throughput's not our problem, direction's our problem. I need more people to steer the ship.

Lenny Rachitsky 0:29 In spite of what we keep hearing, PM should be shipping code, PM should be building.

Sherif Mansour 0:32 PMs are some of the worst solution designers in the world. Because you have access to the tool doesn't mean you're an expert at the domain that you have access to. AI is really good at amplifying your strengths, and equally it amplifies your weaknesses.

Lenny Rachitsky 0:43 You spend a lot of time thinking about what makes a great product manager.

Sherif Mansour 0:47 They don't own decision-making. PMs own decision-making velocity. The largest, most important part of their job is they're literally filling context. The best PMs are the ones that are thinking about building a shared brain at any scale product or software team.

Lenny Rachitsky 1:00 What's trending up in what you are looking for when you are hiring PMs?

Sherif Mansour 1:03 This may sound a bit spicy. One misconception I'm often debunking is you don't need to hire juniors anymore. They bring different ways of working to the team. My 12-year-old son vibe codes his own games. He's gone from scratch straight to vibe coding. He's missed the whole syntax and whatever. He thinks that's normal. [gentle music]

1:24 – 4:17

What makes a great PM

Lenny Rachitsky 1:24 Sherif, thank you so much for being here. Welcome to the podcast.

Sherif Mansour 1:28 It's so awesome to be here. Thank you for having me. Uh, long time listener, first time caller.

Lenny Rachitsky 1:32 [laughs]

Sherif Mansour 1:32 So, uh, uh, it feels surreal but good to be here.

Lenny Rachitsky 1:36 I get that a lot. Um, you are Head of AI and Product Craft at Atlassian. You and your team build some of the most important and influential products in the field of product. Uh, Jira, ever heard of it? Um, something that is very cool about you and your job is you spend a lot of time thinking about what makes a great product manager, how to develop great product managers, how to hire product managers. You spend a lot of time on the craft of and the skill of being a product manager. Let me ask just this big question and see where it goes. What makes a great product manager?

Sherif Mansour 2:14 In any medium to large organization, I'm gonna focus on that 'cause I think it's quite different to a startup, um, I think that the, the largest, most important part of their job, to use a phrase that everyone loves using today, context, is I think they're literally filling context. They're filling context with humans, and I guess these days with agents too, but they're the ones who realize that the best way I can advance this product is not by me taking all the decisions and all that stuff. It's one of my popular misconceptions I'll have to debunk, product managers on all the decisions. Um, but it's about if they can build a shared brain with their team, their cross-functional team, especially their engineers, on, I always say three types of context to my teams. Uh, you have the customer context, you have the product and market context, and you have the business that you operate in context, and you're always filling context gaps. Like, the hardest thing I've had to do, Lenny, if someone asked me the other day, "What's the hardest thing you've ever done at Atlassian?" And I feel like without a doubt, it's just scaling product teams. Everything breaks, trust breaks, shared brains break, us and them culture starts forming. In any scaled organization more than 20, 30 people, you're gonna run into this. Um, so having a job of building a shared brain as a group on those three contexts becomes key because if you can empower everyone with that context, um, th- they can move faster. I always say to PMs, "Your job is to stay away from the Jira backlog." And they're like, "Wait, what? You, you work at Atlassian, you can't say that." And I'm like, "No, no, hang on a second. Hear me out for a sec. Run away from your backlog because why, why is it that you think some card is more important than another card?" There's some context that you have that the rest of your team doesn't. So how can you power your product engineers, your feature leads, your designers, et cetera, with that context so that they can make those decisions themselves? Now, granted, you may never work yourself out of a job, but you're always filling context gaps. It might be a vision gap this year. Next quarter, it might be a customer gap, might be a landscape gap. Like, you're always trying to fill context. Um, and I think the best PMs are the ones that are thinking about building a shared brain at any scaled product or software team.

4:17 – 7:10

Why your job is to fill context gaps, not make decisions

Lenny Rachitsky 4:17 So a big implication of this advice, 'cause I don't think many people would think this is what makes a great PM. This is a really interesting and unique take, this idea of just providing context for the team versus, uh, there-- You, you even said this, like your job as a PM is not to make the decisions, it's to help your team make better decisions, and through that it's give them context. So kind of the implication here is your job is to help the team have all of the information such that they can all make the right decision versus you having to convince them or be the decision-maker.

Sherif Mansour 4:48 Yeah. I remember, um, early on in my career, uh, uh, I remember sitting down with my manager saying, uh, like, "This is insane. I have so many decisions I need to make. The team's blocked on me. I, like, I, I, like, I need to move in this direction, in that direction, in that direction." And she looks at me after me venting for like 10 minutes and straight in the eye, and I can tell she's sort of looking past me, not really listening, and she says, "Sherif, you just need to spend more time on the strategic things." And I'm like, "Well, how do you have time for these things? Like, I'm too busy, like, planning the sprint, working what we're doing next, et cetera." And, uh, you realize that the best way to make you and the team scale is by making sure that everyone has a shared brain. You know, simple as it can go by simple examples like I try never to do customer interviews without engineers in the room. Like, you're building context in your brain. Like, sure, I can do the interview, then get an agent to summarize all that stuff and hand it off to a human and say, "Look, here's the findings." But if you're sitting in the same call as me, Lenny, like your aha moments and your empathy that you built for the customer is, you know, 100 times better than someone who's just handing over reports of, "Here's my customer findings." So, you know, that's an example of filling customer context. How can I do that in a way that more engineers feel empowered for that? Um, but you know, product and strategy context, you might get your team involved in visioning together and looking at market landscape together and trying out different tools together and- Rather than one person doing it and, you know, coming down from the mountain handing over these instructions.

Lenny Rachitsky 6:10 This episode is brought to you by this season's presenting sponsor, WorkOS. What do OpenAI, Anthropic, Cursor, Replit, Sierra, Clay, and hundreds of other winning companies have in common? They're all powered by WorkOS. If you're building for enterprises, you have felt the pain of integrating single sign-on, SCIM, RBAC, and audit logs. WorkOS turns those deal blockers into drop-in APIs built for B2B SaaS, and now there's a new kind of user that needs access to your app, agents. AI agents need to register, authenticate, and get permissions just like a person. WorkOS handles it all. Agent auth to give agents scoped, revocable identities, agent registration with AuthMD and Airlock to judge every agent action and allow, deny, or escalate to a human. I've noticed that every startup that I am an investor in that expands upmarket ends up using WorkOS because they're the best. Go to workos.com to make your app enterprise-ready

7:10 – 11:25

Examples of context-sharing done well and done poorly

Lenny Rachitsky 7:10 today. I'd love to hear more examples of what this looks like in practice of either what not to do, uh [chuckles] to do this badly, and what you think are kind of counter examples of a PM, uh, and/or, uh, doing this context sharing really effectively.

Sherif Mansour 7:24 If you think something's more important than, than something else, ask yourself why did you conclude that? And like, you know, reverse engineer your thinking and what made you realize that, and why does the other person that you're telling them that does-- why don't they know that? And so it might be because they don't have the data points of the quantitative or qualitative data, they weren't involved there, et cetera. Um, it might be because, um, you know, they weren't in those meetings or they don't have that co- e-s information. Uh, and so, uh, you're always thinking about, "What can I do to bring people along on the journey?" So the best designers, as a great example, aren't handing over the designs necessarily. They're getting the team to co-create w- together, uh, and they're exploring concepts together. Now, they may take that all and then finesse it and finish it and bring out this, but the, when the team's involved in that process, their aha moments completely change. Um, another example might be I had a, um, a product manager the other day that's getting every engineer in the team to go and use different AI tools and to come back and tell them what worked and what didn't work for them. And that's something we typically wouldn't do. Like, we'd say, "Oh, the, the PMs or the designers will go do that." But, like, getting everyone involved in the process, um, is a huge one. We, uh, we just came out of our team, our annual, uh, biannual event in, in Europe with customers. We try to take engineers to the booths, and engineers man the booths with me and, and other people, and they're fronting customers and hearing feedback, and that's ways we can build shared brains together, right? So, um, a lot of that. Now, granted, you may start every project and you take the decisions yourself and you're trying to get things going, but your job always as a PM is like, how do I move away from this thing? How do I get better alignment on the vision? They, they, they put this on the roadmap and I disagree with it. Why do I disagree with it? There maybe there's some strategic beliefs that I have that I haven't built a shared brain around with the team, or maybe I'm wrong and they're right. And so you're always trying to close those gaps. So you're always trying to find where are the gaps, and then what activities can you do to close those gaps?

Lenny Rachitsky 9:15 So interesting. So there's kind of this spectrum that you could think about PMs that, um, of how they operate at different companies, and one end of the spectrum, they're the boss, make all the decisions. They are basically managers of the team. The other is they're just completely equal, no additional power of any kind in decision-making. Where in that spectrum do you think PMs should be?

Sherif Mansour 9:37 They're always striving, uh, to be in the, uh, equal, uh, n- no additional power. Now think about it also, in theory, PMs don't have... An, an s- a PM working in a squad has no reports to them. Th- they have to influence without authority, right? By definition. So, and there are two operating models here. There is the I will hand over the spec and you will do what the spec says, or there is the model of I'm gonna get you all bought into the vision and we're gonna work on this together to the point where the best engineers are almost, like, suggesting their own features to solve the customer problems. Some of the best stuff that we've had, if I could share a quick exa- I remember, um, I love telling this story 'cause it's an old story and people are like, "What?" In 2010, I remember interviewing a Confluence cust- a set of Confluence customers, and we could see that, um, before emoji even existed, customers were putting in these little icons in their Confluence pages, right? Um, and now quantitatively you look at the data and you're like, "Oh, people are putting in these icons. We should, we should ship more icons, give them more variety of icons," whatever. And we particularly found in this one customer call that, um, you know, they would put these red stars and these green stars in their meeting notes in Confluence. And I'm like... And we'd, we saw this with multiple customers, like a different system they built, and we're like, "Why are you doing that?" And, you know, they would, they'd be like, "Oh, the red stars are the things we haven't done, and the green stars are the things we've done." And this engineer at the time left the meeting and she's like, "Why don't we just put a checkbox in a Confluence page and let them, like, actually tick it?" Now, don't forget, this is 2010. No one had done this on the web. The, like, putting tasks in a document editor was not a concept that existed, and she just pioneered that because of her, her aha moment from observing the customer. Um, we wouldn't have got that otherwise. Look, there's lots of examples of these, but when they're involved in that journey, you're, um, you're making them the mini product managers, uh, in, in each of the areas.

11:25 – 12:38

The GM/scientist/artist PM triangle

Lenny Rachitsky 11:25 I know you also have this, um, framework of how you think about architects of-- archetypes of PMs. There's, um, artist PMs, uh, there's a couple others. Talk about that 'cause I think a lot of people, they hear PM and it's, like, one type of person, and it turns out you can be a successful PM in different ways. Talk about this, this framework.

Sherif Mansour 11:44 Yeah. We, we, we have a, a framework that is, um, uh, Joff Redfern actually created it when he joined, uh, us. He shared it with me and we've, we've stuck with it then. You know, there are different types of PM frameworks out there. I think if you pick one and stick with one, it's useful. But he has a, what we call, he calls the PM Craft Triangle, that, you know, one side of the triangle he has a general manager, other side he has a scientist, and the other side he has an artist. And, um, the, the positions in the triangle represent how you might do product discovery more naturally. So as an example, uh, a, a scientist PM will be very hypothesis-driven. Think of them in growth teams, think of them as A/B testing a lot, et cetera. General manager PM will think more in TAM and business and profit and revenue and, you know, all that kind of stuff. And a, an artist PM will be more just emotionally vision-led and experience-led. [lip smack] Uh, and I found this to be a helpful framework because you- the classic, "Let's just throw a PM in a team," isn't the right ment-

12:38 – 15:01

How to use the triangle in hiring and calibration

Sherif Mansour 12:38 thing to do. It's, it's like don't throw bodies at the problem. Think about like what type of PM are we after, and how can we best map that PM? So we use that a lot in calibration when we're comparing PMs. We use that a lot in hiring. Like you'll, you'll ask a general question like, "What's your favorite product, and what will you do to make it better?" It-- you can tell someone's-- where they sit in the triangle by how they answer it. Like the make it better answers for the general managers often like, "There's a new business opportunity we should go after, and I think the TAM is this big, and I'm gonna measure it," and whatever. The, and the scientists will start with a hypothesis, and they'll be like, "Oh, we could, you know, test these different variants," et cetera. And the artists will just paint some visual vision and then kind of back their way into what the problems are. But they'll start with like this solution experience that they wanna paint 'cause they feel emotionally led towards that destination for a particular reason, their intuition, their usage or whatever, and they'll work backwards. And so you can do that. So it's a, it's a very helpful tool to say, "Oh, we need a new PM on this team." And I'm like, "Oh, what kind of work are we looking at, and do we need a more of an artist, a scientist, a general manager?" You get some PMs that say, "I'd like to do all three." The reality is, I've found very few people in my career that can do all three really well. Uh, and but you can get a lot of people that do all three at a, at a basic level, and they're, they're awesome for zero to one projects, startups, et cetera. Like as in you need to do whatever you need to do to get to the outcome. That you need that culture a lot in smaller zero one projects or startup teams. Uh, the bigger you get, the more you c- you have the luxury of being like, "We need someone just to really focus on the growth metrics of this particular product in this particular area," or et cetera.

Lenny Rachitsky 14:14 What I love about this, there's a bunch of reasons. One is it shows you you can be successful in different ways, and you don't have to be one specific type of PM. Two is this explains why you may be suffering and [chuckles] and failing right now, is you may be the wrong kind of PM for the team you're on now.

Sherif Mansour 14:31 Lenny, the amount of times I've had someone who may not be finding their groove on a particular project, swapping the type of project they're on, and they've bounced back, got a newfound energy. I can point to so many examples at Atlassian. It happens all the time, and it's a classic of like just find the work that's most suitable to that person and just-- it's not about just throwing PM bodies at the problem. Uh, it's just about who would've thought diverse teams still matter? What kind of person do we need in this team? Uh, how do they complement the other people? What's the kind of work? And, you know, you kind of map that

15:01 – 18:09

You don’t need to be great at everything

Sherif Mansour 15:01 there.

Lenny Rachitsky 15:01 I know that you also have this, um, and I, I share this, this, uh, philosophy that you don't need to g- be great at everything. Uh, just as a, as a, as an employee, as a, as a, but, and as a PM as well, that you don't need to be great at everything. Instead, figure out what you're strong at and focus on that. Um, and it connects to this framework. Talk about just that, and I think it's just this kind of myth you think a lot of people believe.

Sherif Mansour 15:26 Yeah. It's, uh, it's also l- selfishly, Lenny, it's, um, it, it, uh, it makes me feel good. Um, so the running joke at Atlassian is, uh, I'm like the worst general manager-type person to ever have. Like, [chuckles] like if, if it's about running the business, don't give that to Sherif. Now, I'm in the exec team. I'm the head of AI. I run the Product Craft, and I love that people can joke about that about me because I think what that does, Lenny, is it creates a safe space for other people to be okay to share their weaknesses. And then here's the challenge people run into when they run into a weakness. They, they have two options. They could try to get better at that thing. Now, sometimes that's left brain, right brain stuff, and they might need to work harder at one thing, uh, than it is, you know, nature versus nurture kind of topic. Or what I have found to be more useful in my career, and I've, I've tried to be the, "Oh, I'll get better at that thing," is actually find the thing you're good at and run for the hills towards that direction and ignore everything else. And then build a diverse team around you that are good at the other things. So I am a very heavy, strong artist PM. Uh, but in my, you know, I'm responsible for AI across Atlassian. I have a complement, Jamil. He works, uh, with me. He is the complete opposite of me, and, um, and it- we are such a good team together and I'm so grateful for him because in my weaknesses, he shines, and his weaknesses, I shine, but together we're an awesome team. Um, and so, uh, s- I always say if you're early on in career, try as many things as you can to discover, like we discover products, we do product discovery, you should do career discovery. Discover what you're naturally good at. Then you have two options: balance it out or just keep running towards the thing you're naturally good at. My recommendation's always, uh, run to the thing towards you're naturally good at. Celebrate your weaknesses publicly so that you can build a complementary team around you, uh, and create a safe space for everyone else to, to, to feel like they can share the same.

Lenny Rachitsky 17:16 I believe it's important to say you don't y- you can't be terrible at things. Like you-- there's probably a baseline. You have to be good enough at meetings, good enough at strategy, good enough at arti- at taste at, but you're, you don't need to be the best at every category.

Sherif Mansour 17:31 Correct. Yeah. I think it's the, um, again, one of those misconceptions that like everyone wants to be Steve Jobs-esque. Come on, uh, like I'm good at everything, et cetera. Now, Lenny, don't get me wrong. There are a couple people in the company, like I would use Mike, our CEO, co-founder, as an example. He will be in a strategy review with you, and he'll tell you why your drop shadows are off by five pixels, why the padding and margins are off on the left here. Then he'll go tell you why your business model's completely wrong and flip it around, and then he'll go and look at the data inside out and tell you something you ne- you had no idea about. Like those people are incredibly hard to find, but, um, the vast majority of folks, I think, find the area they're good at and just keep going in that area.

18:09 – 21:14

Career coaching: early-career unlocks

Lenny Rachitsky 18:09 Let me ask you this. [clears throat] When you coach people in their early career and then- ... in later career, if you had to pick one or two kind of most common unlocks that help them accelerate. So say you're coaching someone early career, if you think about the people that you've helped at the beginning of their career, and then the second part is just later career. What are kind of the most common unlocks that allow them to all of a sudden become a lot more successful, yeah, at, at product management?

Sherif Mansour 18:38 Giving them an opportunity that is just above their level at the right time is key. Um, and that opportunity you should be very deliberate about. It's something that plays to their strengths specifically. Um, uh, for example, uh, this product manager comes to mind that she used to work with me on the early days of a new product that we launched a few years ago at Atlassian. And I realized at the time that she was at the stage where she was more in the scientist brain, that the product was growing, and I realized also that, like, I'm probably not the best to lead this. And I stepped aside and just said, "Hey, you know, Rachel, you should probably take over this piece of work." So I think it's just really about finding... If you know where each person is at on their journey and you have a high- you can see where they wanna head and what they're good at, waiting for the right opportunity, and your job as a leader is to see that opportunity arise, and then, you know, that might be moving them across to a different team or whatever it is. Um, I think that is the sweet spot of giving people something. I've been fortunate to be here 17 years, and like every time I've, like, looked around, there's a new opportunity at Atlassian. This is like 'cause we've just grown so much, so, and these opportunities have happened to play to my strengths. So, you know, in the same token, I, I need to be looking at that for the people on my team and, and, and passing that on as well. So, um, I think that's key is just identifying opportunities inside the business is, um, such an important thing that doesn't get talked about as much. Yeah.

Lenny Rachitsky 20:08 So say, um, early career PM is listening to this, they're gonna be wondering, "Okay, what kind of opportunity should I be looking for that is most likely to help my career?" What are signs that this is a good opportunity that may accelerate their career?

Sherif Mansour 20:22 It's probably started with someone telling you you did a good job at something. That's probably a good sign that that's the type of work that you're good at. So if you're feeling like you've, you've found that and people are saying they, you know, they really like the thing I did here or this particular project, they really love how I led growth in this particular area, or they love how, you know, I solved this customer problem in this area. Analyze that type of project, then ask yourself what-- how did I approach it? How did it work? Then your next thing is what are, what other types of projects that are similar that I can go do, um, is, is what you should be looking at. Tell your manager about it. I always say to folks, a good conversation to have with your manager is pull up one of those frameworks like, "Here's where I think I am in the triangle." Whatever framework you want, there's lots of them out there. "I'd love to do more of this stuff," if you're still discovering or, "I would love to get better at the thing I'm good at here." Put it, you know, tell them, indicate to them that you're after the next opportunity, I think is a huge step you can do to, to help

21:14 – 22:19

Career coaching: senior PM and manager unlocks

Sherif Mansour 21:14 yourself.

Lenny Rachitsky 21:15 What about, um, let's say a senior PM, you know, I don't know, like L6 or even like early manager? What's, what's kind of the most common unlock that accelerates their career from that point?

Sherif Mansour 21:25 I think at an L6 you, you've really found your groove. Like as in, so you- I think you're at that decision where maybe you don't wanna accelerate. If you say accelerate your career, Lenny, and you mean accelerate your, uh, levels, maybe you wanna go diverse, as in go try something totally different. You could argue, is that accelerating your career? I would still say that's accelerating your career, right? So or just keep chasing the similar type of work, I think is key. Um, you know, this, uh, particular lady in one of my teams, y- yesterday we celebrated her 10-year anniversary at Atlassian. She found the kind of work that she's really good at. She leads a lot of our pricing and packaging work across AI and all that kind of stuff, and she's so good at it. Uh, and we just-- she keeps finding more work across the business that lines up with that. So she's, you know, chasing, uh, that kind of work 'cause she knows she does such a good job, job at that

22:19 – 23:42

Why PMs are thriving in the AI era

Sherif Mansour 22:19 stuff.

Lenny Rachitsky 22:19 Okay. I wanna talk about something that's hot off the presses. I've never sh- I haven't shared this with anyone yet. Uh, this I think will be out by the time this episode comes out. I'm doing a state-of-the-tech job market report. I do this every, a couple times a year. I've done it maybe three times now, where we basically look at hiring trends across tech, and we look at PM, engineering, design, things like that. One of the most interesting takeaways right now that I hope is out there by the time this is out, is that PMs seem to be benefiting most in the AI era. We are seeing the most open PM roles of any role. Uh, engineer is actually slowing down, open eng roles. Design is very flat, not looking great. Uh, user research, uh, really not great. There's, uh, 100 open roles for user research globally at tech companies right now, 108. So, uh, interestingly, when AI became a thing, many people were like, "PMs are over. We don't need them. Why do we need them? Get rid of them." Uh, surprisingly, it's the role that seems to be most thriving right now, and I actually had a post about this that I predicted this. I feel really good about this. So let me ask you this. Why do you think this is the case? Why do you think PMs are, are doing so well in the, in the AI era?

23:42 – 25:01

Atlassian’s AI builder experiment—and what it revealed

Sherif Mansour 23:42 I think for a while, Lenny, if I could use a, a misconception I've been trying to debunk, uh, for a while with especially even our customers in- inside Atlassian. I wrote a post about it. But I think for a while, es- especially a year ago, it felt like the narrative was everyone's becoming an AI builder. Everyone-- Um, and if the definition of an AI builder here, to make it more useful, is someone who spends most of their time building software with AI, and AI builders is all you need, and the roles are merging into one, et cetera. Um, if I could share a case study I think that adds to one of your data points inside Atlassian. So what we did was we're like, "Okay, maybe, maybe this is where it's headed. Like, let's look at it as a craft. Let's try to create a few squads that have AI builders," and we moved some of our product manager and designers to a team, a few teams that ran these exper- basically build product where everyone was the AI builder. There was no PM or designer, but they came from different crafts. I remember checking in with, uh, one of the PMs in one of the teams and, and one of our one-on-ones in the first few weeks, and he's like, "It's, it's unbelievable, man. You, you... Like, you're constantly building. It's so good. Like, I feel like we've moved so fast. We've moved faster than ever before." You know, early days, it was just amazing. Yeah, everyone's gonna be an AI builder. I'm like, "Wow, really? Like, is that where it's gonna hit?" Um, after about a month, he comes back and he's like, "Everyone's gone back to doing their traditional jobs." I'm like, "W- sorry, what

25:01 – 28:48

Why throughput is no longer the bottleneck; direction is

Sherif Mansour 25:01 do, what do you mean by that?" And he's like, "This sounds so obvious in hindsight." It's like, we realized throughput's not our problem; direction's our problem. Uh, throughput's getting cheaper. So, you know, uh, I wrote this blog post internally that was, you know, Direct the ship, don't row it. And there was a lot of PMs coming to us saying, "Should I be coding? Do I need to code?" And, you know, quite a few of our PMs have committed code in, in some capacity or whatever, but it's very obvious in a world where we have... Again, the nuance here is if you're a startup and everyone's moving really fast, everyone needs to do anything, which I, I'm fully bought into that, or a zero to one project. In an engine- in a company where you have the luxury of hundreds, thousands, tens of thousands of engineers, um, dozens of engineers, your problem is your direction, uh, not, not how quick you can pump things out. So, people who are actually helping everyone steer the ship, uh, not more throughput, right? So, I think that probably is in support of that, Lenny. I think more people are realizing there's more throughput, so I need more people to steer the ship, which is probably reflective of some of the results you're seeing on, on, on more PMs being hired.

Lenny Rachitsky 26:06 That is an awesome answer. Uh, and that, that makes... Like, I imagine so many people hearing this are just nodding along. They're like, "Yes, this is exactly right," in spite of what we keep hearing, just PM should be shipping code, PM should be building. Um, there's a few directions I want to go here, I guess. Just like, like the trend kind of to double down what you're saying, what AI is enabling is anyone can build, which is creating a ton of chaos and a lot of prototypes and a lot of ideas, and, uh, what you're seeing here with this data is probably showing is just now the need is, what the hell are we actually doing? Let's all get on the same page. It's like more buy-in. [chuckles] We need more buy-in. We need more alignment. We need all the things PMs are great at. Also, uh, what is great? Is this ready? Is this good? Is this what we want? Is this gonna hit our goals? So it's, so it's like now that we think about it, I see. This makes all the sense. Here's why we need more PMs. Uh, it's so interesting that we thought the opposite would happen.

Sherif Mansour 27:03 And, and we thought the same thing would happen with other crafts, Mert. I mean-

Lenny Rachitsky 27:06 Yeah

Sherif Mansour 27:06 ... uh, Lenny, you were, uh, you were probably around w- I'm guessing, um, I'm gonna guess your age, Lenny, so no, no offense. You, you were probably around during the Balsamiq mock-up era, right?

Lenny Rachitsky 27:16 Oh, absolutely.

Sherif Mansour 27:17 So, like, you know, w- what did we, what... Well, the, the promise there was everyone can do mock-ups. Mock-ups are so easy, right? Let's just ignoring AI prototyping. And Atlassian, yeah, Balsamiq exploded, and we used a whole bunch of mock-up tools, and it was we liberate mock-ups. I, I learned so much through that era at Atlassian. I learned that, one, yeah, everyone can create a prototype or a mock-up, but yeah, actually, PMs are some of the worst solution designers in the world. Like, as in you, you realize like, uh, because you have access to the tool doesn't mean you're an expert at the domain that you have access to, right? So, like, uh, now some PMs, the more the artist ones, end up doing just generally better mock-ups than others. So, AI's really good at amplifying your strengths, and equally it amplifies your weaknesses. Um, so we learnt there in that world that specialists, specialists are still important and specialization's still important. Like, you can only get the AI to do something as good as your knowledge of the specialization is, if that makes sense, 'cause you gotta learn how to prompt it. Um, we saw that with the mock-ups era, and now we're seeing it again with the prototypes era and everyone can generate a prototype. It's awesome. I mean, it certainly helps up speed up decision-making and all that stuff, but it, um, it's a fly in the wall with like all PMs and our designers. Like, it's, yes, everyone's circles are getting bigger, like think of a Venn diagram, but the, the circles aren't overlapping. It's just they're all equally getting bigger. So, if they're equally getting bigger, you know, th- then they're not compressing, if that makes sense. Uh, the specializations are still needed to improve the quality and taste that's coming out of each of those things. Um, yeah, that's just often missed as well, I think that,

28:48 – 31:04

What PMs should actually be doing with AI

Sherif Mansour 28:48 that whole topic.

Lenny Rachitsky 28:49 I love this. Okay. So, uh, so again, this is an, a fun spectrum. On one end of the spectrum of what a PM should be doing, on one end, you are now an engineer. You're shipping production. This is part of your job now. The other end is don't even touch AI at all. Just do what you used to do. Like, you, you, you actually spent a lot of time thinking about, uh, career ladders and calibration and what a great PM should, what a successful PM looks like, so this is something you spent a lot of time on. What sh- what do you think a PM should be doing in terms of AI infusing their job prototyping, I imagine. Should they be shipping code? Um, what do you think is the right answer for PMs these days?

Sherif Mansour 29:25 I tied back up to the top, Lenny, which is their job is to make sure the team... They don't own decision-making. PMs own decision-making velocity, and so they're, they're thinking of, "How can I help the team move faster?" The second question is, "Oh, can AI help me in any of those?" I think that's the right mindset. So it's like if I realize that, okay, customer empathy and customer awareness is a huge problem, a context gap my team has, and, um, I just feel like they're not making the right micro decisions 'cause they're, they don't understand this persona over that persona, et cetera, then you'll probably be thinking about how can I involve them in the process, but also how can you use AI in the process to accelerate them filling that context gap. Um, I, I, I think I would, I would go back to the top and just answer that question of like, look at your team today. You-- There's some things that you might feel like is not gelling well and go, "What is the context gap?" And then look at how AI can help you do that. Is it because you don't have direction of the vision? So sure, prototyping might help you get a better vision and clarifying it and all that kind of stuff, um, but you might realize that they don't have a good understanding of the market dynamics, and you might send off a bunch of agents to do some analysis and build that with a team, et cetera. So- Using, you know, first stating the problem with the context gap and then using AI to help solve that, I think is, is the right approach.

Lenny Rachitsky 30:45 I love that answer. Uh, very unlikely it will be the bottleneck, uh, for decision-making and shipping code to production. Uh, most likely that is the last thing that you need to speed up because that is so easy now.

Sherif Mansour 30:56 Mm.

Lenny Rachitsky 30:57 Uh, unless, as you said, if it's like a startup or just like a new team or it's just a PM, for example, working on something.

31:04 – 32:44

What’s trending up and down in PM hiring

Lenny Rachitsky 31:04 Okay. Amazing. So while we're on this topic of AI, what... You hire a lot of PMs, you interview a lot of PMs. Uh, I love asking this question. What do you-- what's kind of trending up in what you are looking for when you are hiring PMs? What are kind of emerging newer skills, habits, traits? And what's trending down? What's less important now?

Sherif Mansour 31:23 Trending up in, in certainly larger organizations, uh, I would say, again, to, to be more nuanced in the, in the topic here, is, um, [lip smack] PMs that I'd say that are certainly more of the artist type. And why that's the case is because taste has become more important than ever before when everyone has access to the same intelligence. Uh, and I think that's been covered heavily in your podcast. But I think it's certainly people are more leaning towards, um, experience-led, uh, uh, PMs. I think that's certainly trending up. Um, the other big thing that's trending up obviously is, you know, if anyone is in an established workforce, as in they have teams that already exist, right? You're asking yourself, "How can I reinvent how each me- each member of my team does their job in the world of AI?" The problem you have is probably cultural change, if you define culture as how work gets done. And so you're looking at... One thing I often do with the interviewers and the, the interview process is you're looking at what new culture would this person bring to the team? And that means how can they transform how we work, especially in the world of AI, right? So asking people how they work with AI is a fascinating question, and getting to the deep beyond the like, "I use it to summarize stuff," and whatever, and like actually getting to that because you're also looking at cultural adds, um, you know, AI natives or how... AI native's such a relative term 'cause, you know, by the time you

32:44 – 38:07

The case for hiring more juniors in an AI world

Sherif Mansour 32:44 kind of... But like you're always looking at like what new ways of working can this person bring, so that's probably the second thing. [lip smack] And the third thing, Lenny, I think this is counter-cultural to some of the narrative that's out there, is around hiring people that don't know any better except for AI. And this may sound a bit spicy. Maybe their AI slop levels are higher, but they're actually, they didn't grow up, uh, with knowing anything else. Uh, in particular, I'm talking about juniors here. So one misconception I'm often debunking with a lot of established organizations is you don't need to hire juniors anymore. And I go, "Well, why do you, why do you say that?" And it's because, "Oh, well, AI can do that for me," yada, yada, yada. But I'll say, "But as an organization, what are some of the problems you're having?" And often the problem is, "Well, I have a workforce that needs to transform and learn new different ways of working." And I don't know about you, but it's really hard for me to unlearn the ways I used to work and then learn the new ways of working. That's very hard. It's much easier to grab someone out of college that's basically been cheating in their university assignments or not known any better, or I love using example of my son, 12-year-old son. He vibe codes his own games. He's gone from scratch, like a visual coding language, straight to vibe coding. Like, he's missed the whole s- syntax and whatever. He thinks that's normal. Like, I'll-- I'm always blown away where he'll dismiss a model and be like, "Dad, this Gemini wasn't that good," or, "Blah blah wasn't that good. It did this." And I'm like, "Dude, that would've taken like four days for someone to build." He's like, "Yeah, yeah, whatever." And I'm like, [chuckles] I'm blown away and he's just like, you know. [lip smack] But the long way of saying is I think the third type of person you're after is, and I think in particular juniors for established workforces, they bring different ways of working to the team. Now, juniors are not great at identifying AI slop 'cause they don't have the domain expertise. But your established team, your existing team, your seniors, your people that are specialized, they can pick AI slop a mile away because they know the domain really well. And so you're actually looking at how can I build a complementary team here, a complementary workforce between the juniors and the seniors, um, so they can work together. So I would say that's the third big thing, is like, uh, we have definitely over-indexed on hiring more juniors than seniors because, because again, our context is we have an established workforce, an established team that are learning to transform how they work, which is every organization in the world. And so you're going, "What, what's, what person can I bring in that doesn't know any better?" And so we run these like AI builder weeks, and they're fascinating weeks, Lenny, 'cause like we just take a week where all the crafts stop and they like tinker with AI for a week, engineering, design, et cetera, at the same time is very important. The juniors or the, the younger people tend to be like showing all this coolness and like demos and tools or whatever, and the seniors tend to focus on identifying slop, evals, quality problems, et cetera. Like, you just notice that just natural gravity, and you're like, "Wow, this is diverse teams." And diverse teams are still very important in the world of AI.

Lenny Rachitsky 35:42 This season's supporting sponsor is DX. Now that everybody at your company is finally using AI, the question that engineering leaders face is no longer, "Are we using AI?" but, "Is it paying off?" With DX, you can measure and benchmark the impact of AI adoption across your full product life cycle. DX shows you where AI is helping developers and where it's creating new bottlenecks. You can also use it to evaluate AI vendors, monitor costs and licenses, and see exactly what's limiting your agents. That's why hundreds of enterprises, including Snowflake, Sony, and BNY, use the DX platform to measure AI's impact on developer productivity. Visit getdx.com/lenny to get a demo of DX. That's getdx.com/lenny. Sherif, I am loving this conversation. There's so much good stuff here. [chuckles] Uh, okay. So, uh, on this junior piece, uh, very inspiring I, I imagine for folks listening to this that are earlier in their career, um, or trying to break into PM from something else after school. Are there any kind of trends of where the best, uh, junior/young folks come from college-wise? Like, is it... Are they still going to college? Are they studying computer science? Are they MBAs? Uh, anything there?

Sherif Mansour 36:59 Uh, I don't think I have anything unique to share here. I think it's still a mix of computer science. I, I spoke to our... I went to our, uh, APM cohort, uh, last week, uh, in, in, in Sydney, and we had them all together and it was a mix of Phil- uh, uh, uh, there was like some people with arts degrees, uh, uh, someone with a law, uh, law and technology background. So it was a good mix. Um, again, you're looking for the critical thinking, the, uh, the, the usual stuff. The curiosity is super high, willingness to try different things. They, they got no fear, so they're just willing to try anything to try to make it work, uh, because they haven't done anything any other way, right? So, um, uh, and we, we have numbers to show this, Lenny, both internally and externally with our customers, our research team. So like something like, uh, almost 30, I think it's 38%, the exact... I've, I've posted a blog about it, but like of juniors are more likely to adopt new tools than the seniors, both internally and with customers, uh, et cetera. On the flip side, the seniors are getting more quality and better productivity out of the ones they're using, but they're less likely to try different ways of working.

38:07 – 46:05

How to spot the artist streak early in candidates

Lenny Rachitsky 38:07 Okay. So if I were to connect, so you have three kind of answers of what is trending up. Um, artist PMs, people that bring, uh, a culture of, of open-mindedness and, and, and trying stuff and experimentation because things are changing so fast, which feels actually pretty close to the third bucket, which is new, newer, newer workforce folks that are just AI native, essentially. So the Venn diagram is essentially artist PMs who are new, uh, juniors, let's say. Um, so going back to the artist PM, say a little bit more what that looks like because people listening to this are gonna be wondering, "Am I that? How do I become that?" Talk more about, and as one, as you self-describe yourself as, what does, what does that look like? What are you great at as an art- artist PM?

Sherif Mansour 38:49 An artist PM is, in contrast to a general manager or a scientist type of PM, the way they lead product discovery is largely through visions. They may often actually start with solutions and work back into problems, which sounds, again, very counter-cultural because they have some intuition in some particular area. They tend to focus on experience more than numerical, you know, uh, more, they're more data-informed than data-driven. Then I want someone in growth to be a little bit more data-driven than data-informed. You kind of want that healthy tension, right? So, uh, they, they'll tend to do that a lot more. Um, a lot of them will tend to... Actually, a good signal is like you'll see a bunch of prototypes, the artist PM from different PMs. The artist ones will generally do the ones that seem more logical, uh, or, or, uh, flow better. You'll find sometimes, I always say when you're in a room and you- you're t- discussing a concept or a topic and someone sometimes feels the urge to pick up the whiteboard marker and draw, that's a pretty good signal. They're like, "Are we talking about this or are we talking about that?" Like, uh, and so they'll often, uh, tend to do that. But I, I think in the world where more, more vendors and more software is cheaper to build, more people will have the same sets of features. Experience matters more than ever before, and I'm not a believer that everyone's gonna chat to an agent and the agent interface is the, is the final interface. I think there'll be many. Uh, and so I think experience still matters a lot. So I think that in a world where just generally speaking, more people can build more stuff cheaper, faster, easier, experience matters more because that becomes one of your possible differentiators. And so those artists tend to kind of be a better asset, or not a better, a good asset in that world. And so you're trying to complement your workforce to make sure you, you've got a mix of these skills.

Lenny Rachitsky 40:42 I imagine it's hard to actually find that combination of a new entrant into PM and very good at this because my suspicion is you need to do this for a while to build that gut feeling and the, you know, the artist experience. True or, or not true?

Sherif Mansour 40:57 S- someone just sent me... We asked all our APMs from last cohort t- the new cohort coming up to record a Loom of a take-home exercise, and I watched a few of them a la- a week before last actually, and it was fascinating again to see how, again, they don't have domain experience, but we gave them an exercise to build an app, um, for a particular thing and, um, to see how they chose to present it and lead the narrative of why they're building this particular app or whatever. You, you do pick up the artist streak in them very early on. You can see the ones that will... As an example, there was a, a Loom of someone that went through and, uh, they walked through basically graphs before they even got to any experience, and they were like, "Here's the business case, here's the TAM, here's et cetera," whatever, whatever, whatever. And they were like, "Here's experience," and they spent very little time on that. In contrast to this other candidate, and she walked through the end-to-end journey and talked about, like, it's funny, she talked about delighters and like, "I think this would be a way to build an emotional connection with someone." Again, don't have to, don't have any domain experience, but you can see the way they tended to do product discovery tends to be more visual, uh, than, than the o- than the other person. So you can at least identify that streak early. Um, I mean, Lenny, I've got two kids. My son's really good at maths and, uh, and logic and whatever, and my daughter just loves drawing and just naturally we bought them in the same household. We read to them the same books as kids, at least I think we did. But you can just see the natural, their preference in, in their style of how they, how they work and how they think. Um, and so I think that there is a bit of nature and nurture here as well.

Lenny Rachitsky 42:35 Yeah. So the implication here is it's not like you can, you train to become an artist PM archetype. It's mostly you, that is how you are as a person, and then you build enough experience to actually be good at it. Like, I know, I'm sure, uh, uh, like tell me if you disagree, but it's prob- like this is you and then- You can become better at it, and you can probably learn how to do some other things better, but I don't know. Yeah, you're nodding along. You're slightly looking around.

Sherif Mansour 42:57 Yeah. I, I think it's easier to, to accelerate at the thing you're naturally good at-

Lenny Rachitsky 43:01 Yeah

Sherif Mansour 43:01 ... and it's harder to accelerate the thing you have to learn to do, right? I think that's-

Lenny Rachitsky 43:04 Yeah

Sherif Mansour 43:04 ... that's gonna apply to anything. So, is it possible to train artists? Yeah, totally. Um, and you can at least help people identify things or whatever and, um, it's just harder, right? It's, um, it's not as, uh, e-easy for that, like, to do.

Lenny Rachitsky 43:18 I love how, like, it's another counter-narrative, I think that's the word you've been using, of like, okay, we don't need junior people anymore or they're done, there are no careers left. Like, you could argue they are on- the only people that we'll wanna hire now. Um, I don't think this is what you're saying, but it's like these are the people that are so open-minded and so, uh, native with what is possible now and not stuck in this old way that that's maybe who we need, and the people stuck in the old ways are not-- are only slowing us down.

Sherif Mansour 43:44 It, it's the theory of diverse teams is still true today and even more true in the world of AI. Like, it's, it's just so true.

Lenny Rachitsky 43:50 So this data that I've been seeing of, uh, designer roles not growing, there's just been, like, a stasis in the number of designers being hired in tech. Um, I wonder if it's because basically PMs are filling in more of that, of that gap as you've been describing PMs basically kind of being the... I'm not, I'm not, and I'm not saying designers are not very useful and amazing and important. Uh, and I, um, I'm surprised that designers aren't thriving more in this era where, as you said, the experience is a huge opportunity and differentiator. But that's just what the data's showing right now, and I wonder if it's because PMs are filling in more of that gap.

Sherif Mansour 44:28 I'd love to dig into that one. I, I think there are some other hypotheses I would have. Like-

Lenny Rachitsky 44:32 Hmm

Sherif Mansour 44:32 ... another hypothesis I would have, I don't know if this is true or not, is that the market still hasn't got past the aha moment for experience matters more than anything else. I mean, uh, in the world of AI. Uh, uh, maybe if you rewind back, we said all PMs are gonna be builders one day, and I think we're learning that's certainly not the case. I think there's still a misconception to be, be, be debunked or proven that design is more important in the world of AI than ever before. Because if everyone has access to the same thing, one of the only things that'll really matter is-

Lenny Rachitsky 45:04 That's what I was thinking

Sherif Mansour 45:04 ... why you, why you prefer something. I, I, I think that's just a reflection of possibly where we are. That, that would be my leading hypothesis. Um, I can just say at Atlassian, [chuckles] uh, uh, we- design has never played a more important role in roadmap driving than ever before, and I've been here for 17 years. Um, uh, and I am fully convicted by, like, experiences will matter most. Yeah.

Lenny Rachitsky 45:32 Wow. I love that. Uh, let's, uh, takeaway, stock up on your designers right now. Buy low while it's on- [chuckles] no one's realizing that's the opportunity. Load up. Put them in the, [chuckles] in the garage with your spare water. Uh, okay. I, I like, yeah, I've been feeling the same thing, and it's interesting. So your feeling is maybe we're not yet realizing that this is a huge, uh, opportunity and a way to differentiate and, and win.

Sherif Mansour 45:58 Yeah. I mean, um, we'll, we'll, we'll see if that, that theory is correct. Uh, that's my current hypothesis, yeah.

46:05 – 52:42

When starting with the solution is the right move

Lenny Rachitsky 46:05 Cool. Okay. Um, I wanna go back to a couple of these, uh, counter-narratives you mentioned because I think they're really interesting. One that you touched on a bit that I think is worth spending a little more time on, which is not starting with a solution. Uh, PMs are constantly told, "Do not start with the solution in mind. Be, start with the problem, with the customer pain. D- uh, don't even, don't even talk about the solution yet," all that stuff. Your feeling is that's not actually true in a lot of cases. Talk about what you've experienced, what you've learned there.

Sherif Mansour 46:39 Yeah. I think it's, again, one of those misconceptions. It's a classic easy thing when you're in a meeting and someone says something, and if you wanna look smart, you'd be like, "Whoa, slow down, everyone. What's the problem we're trying to solve?" And that's like, yo, that person really brought some in-

Lenny Rachitsky 46:51 Take a step back.

Sherif Mansour 46:52 Yeah. Le- yeah. Nice, Lenny. You, you got that one. Um, it's a good question to ask, honestly. Yeah. What's the problem? I think it's, it's still a good question to ask. I just think it is-- what's not talked about enough is sometimes it's, it's a great way to start with a solution. So a few examples if I could run through them. I think, one, um, sometimes it's okay to start in a solution when you're trying to discover... You feel like there's a hunch in an area. You're trying to discover what the things you could productize a-are. Uh, maybe some recent examples, uh, at Atlassian, we have Rovo- Rovo Chat, which is our AI assistant if you're using our platform, um, and Rovo Agents. They're, um, agents you can deploy in loops inside Jira workflows, Confluence workflows, and so forth, et cetera. And believe it or not, Lenny, uh, again, three and a half years ago when we created Agents and Rovo Chat, uh, three now? Yeah. Geez, AI, it's gone fast. Um, we were debating if we should put these in there because the, the, the theory was why would we put, like, a general, a chat in there, and why would we put agents in there and let people create their own agents? Why don't we productize, like, build the feature that people want, don't give them the general canvas, right? So let's not put chat in there. Like, let's not... Let's put a summarize button on top of Confluence pages rather than having a chat button to, uh, to do that. And what you often learn is actually if you give people a canvas, y- there's sometimes the fastest way to discover what the main problems are and productize some of those problems. So a, as a simple example, in Confluence whiteboards, customers can draw sticky notes and collaborate with them, whatever. And, you know, one of the common scenarios is you might use Rovo Chat to group sticky notes into common themes. Now, chat's not, maybe to tie it back to our experience discussion, chat's a terrible experience to do that visually. Like, you're typing, you're kind of, like, filling out a f- Then which sticky notes do you wanna group into themes? How do you select them? And so obviously you can productize that feature and that team lets you select a bunch of sticky notes and decide, you know, I'm gonna group these ones into different themes, and AI goes and does that for you. Really good example where you productize the use case that chat had, but chat was the infinite use case. Um, another example is- Uh, customers love putting... You know, we have like nearly 10 million agents that run in loops every, every month inside Jira and Confluence and, you know, you, you wanna give a tick- uh, you know, a ticket to an agent, and the agent picks it up and does the triage, or agent generates the code, or agent reviews the legal contract, uh, whatever it is. That, that's quite common inside Jira. People put agents in loops. And so, like, we can learn what kinds of agents they're putting in loops. And for some of them, we're gonna leave them as the infinite use case. Let, let, let customers build their own. And for some of them we're like, "Actually, we're gonna build an AI triage feature and make that native to the product." And so starting with the customer solution and understanding what the customer's doing helps you work out what the problems are, and then you might productize their manual workaround into a, a set of capabilities into your product. It's a pretty common tactic. Um, I think I've heard some people refer to it as paving the cow path.

Lenny Rachitsky 49:51 Hmm.

Sherif Mansour 49:51 Like, you know, there's a p- uh, uh, a, you know, there's a walkway and there's a cow that walks straight in the middle across the grass, and you're like, "Well, why don't we just make that the cow path?" Uh, and so starting with a customer solution there is a really good, uh, approach. The second big one really is strategy, product strategy. The best product strategies are starting by looking at what assets or what solutions do you already have today. 'Cause you need to answer where do we play and how do we win? And to answer how do we win, you have to look at what unique things that we have as a company, as a business, as a product, right? So, you know, classic, the example everyone-- I love to give people is, like, the Amazon bookstore is such a good example, who built this ridiculously sized bookstore. It's a huge inventory. You know, like if you read, uh, Jeff Bezos' book, he's like, what other things... He's starting with a solution. What other things need a ridiculously large inventory that is a crazy scale? But what if it was an everything store? Like, do you know what I mean? Like, so, so starting with a solution for product strategy thinking is another good tactic. You know, I always say to teams, write down what assets you have today, then write down your beliefs and see if there's any connection between those two of where things will head, uh, and do that. So, you know, giving people a canvas to try things and productizing the solutions that they manually built is a good strategy. Uh, and so is when you are doing product strategy, start with what solutions do you have today and what unique problems can you solve with them.

Lenny Rachitsky 51:12 Got it. Okay. So it's nice to have here's the paths where starting with solution's good. Uh, you're not saying always start with solution or it's always beneficial. It-- and essentially, in most cases, you actually don't, except in these two situations.

Sherif Mansour 51:28 Y- yes. I would-- actually, I don't know if it's most cases, but it is important to understand the cases. I would say that a lot of customer discovery is by learning what customers are trying to do with your product and then trying to make that better. So you're actually observing a customer trying to create a solution for themselves in most products, and then you're like, "Oh, let me make that better for you." Like, et cetera. So it'll be fascinating to try to come up with a percentage is that most of the time is, you know, you're actually implicitly starting with a manual customer solution, uh, if you like. Um, I think that's a good thing, good thing to, to think about as you go into do exploratory, which we, which by the way, with AI teams to do enough of, of just talking to humans. Uh, it's become much easier to stay behind more dashboards.

Lenny Rachitsky 52:12 By the way, I didn't know, so you guys have a-- I didn't know you had this product, uh, the whiteboard product. I didn't know that was a thing. So this is like Miro, FigJam-ish?

Sherif Mansour 52:18 Yeah, Confluence Whiteboards. It's huge.

Lenny Rachitsky 52:20 Okay.

Sherif Mansour 52:20 Yeah. So, uh, yeah, customers can embed whiteboards in Confluence, and they add agents to them-

Lenny Rachitsky 52:24 Cool

Sherif Mansour 52:24 ... and they collaborate, real-time collaboration, add sticky notes.

Lenny Rachitsky 52:26 All right.

Sherif Mansour 52:27 Turn 'em, turn 'em to Jira tickets, all that kind of stuff.

Lenny Rachitsky 52:29 So this is like a feature within Confluence.

Sherif Mansour 52:31 Yeah.

Lenny Rachitsky 52:31 And, and it's... Okay, cool. All right. Folks don't know that ex- I didn't know it existed. This is, this is great. Good, good marketing for the whiteboard product.

Sherif Mansour 52:38 Didn't intend it to be as marketing, but it's a good example, I think. Yeah.

Lenny Rachitsky 52:41 Yeah.

52:42 – 56:01

Why “bolting AI on” is often the right product strategy

Lenny Rachitsky 52:42 Okay, cool. There's another counter-narrative that you have, which is around AI, and this kind of, um, concern people have with just bolting AI onto stuff, and your feeling is that's actually good in many cases. Talk about that.

Sherif Mansour 52:56 This is where the catchy headlines, Lenny. Um, it is very catchy to say, "Don't bolt AI into your product."

Lenny Rachitsky 53:02 Yeah.

Sherif Mansour 53:02 "You should reimagine the workflow." I, I, I, I certainly believe that. I-- but however, the nuance is, I think if you have an established product, you have something ready today, the best way to reinvent your product to be AI native is to understand the flows that exist in your product and literally bolt on AI to them, which sounds dirty. Like, you may not market it that way, but actually, n- just think about it for a sec. You've got a product, the product has millions of users. What I see some people doing, and I talk to a few startups or whatever, they're like, or a few product companies, they're like, "We're gonna rewrite our product from scratch." I'm like, "Yeah, I think you could do that." Um, but isn't the better way to actually work out is how to, to evolve, not like totally, uh, transform? So the example I love to give is, uh, the Rover Agents one I just told you about is a good one, which is, um, customers have already modeled billions of business workflows in Jira. Just as an example, like Jira is like largely used by many non-software teams. It's a misconception most people have is Jira's already like y- many... For a while you, like, you get a app approved in your app store, went through a ticketing system like Jira. It was Jira for a while, and then it goes through a whole review process. Like, if you complain about your, uh, particular service with a telecommu- company, it goes through Jira ticket. Like, so customers have billions of workflows already modeled on, on our platform as an example. And so when it came to, like, understanding how will agents help humans move work forward, we looked at what are the human workflows that exist in the product? So that's a good formula to go, what are the human workflows that exist in my product? Some of them are rigid workflows, as in someone's literally defined something. Some of them are informal workflows, like lowercase W workflows. They're humans doing something. And then you can go, where can, you know, agents assist with steps of the workflow to generate new value, re- improve efficiency or something, or whatever it is. And so in Jira Workflows, we basically added the ability to add agents to columns and cards and whatever. Is that bolting on, Lenny? Let's use another term. Like, uh, maybe like if I was building an AI native work tracking tool, that's probably what I would do anyway. Like, I would build a workflow and then let agents work on bits of the workflow. And so my message to teams out there is like, hey, yes, reimagine the workflows. You should do that a- as an exercise. But look at where your customers are today, and if you have an established user base and established users, your job is to help them move from AI novice to AI native. And so you're trying to transition your customer cohort across as well. And so think about where they're working and where you can slowly introduce AI in those workflows. So again, another misconception there, I think that, uh, from a marketing perspective, yeah, you probably wouldn't say bolt on, but literally that's like we literally let you bolt on a agent to a Jira workflow, and you stick it in a loop, and then agents works in loops, and they run, you know, millions of times and whatever, and you-- they, they're measurable value. If it doesn't work, you kick the agent out or you make the evals better for the agent. There's a whole bunch of stuff

56:01 – 1:01:31

The importance of nuance over hot takes

Sherif Mansour 56:01 you can do there.

Lenny Rachitsky 56:02 I love all these takes. There's, uh, when we-- before we started recording this, I asked you what's, what's a goal you have for this conversation, and you talked about how we need more nuance in the conversation of building product. There's all these hot takes, uh, that these really, you know, viral clips that go out and people are like, "Oh, that's how I have to do." And like, I'm guilty of people on this podcast saying a thing and then people at a company taking that, and this is the way to do it. Lenny's Podcast said that's the way to do it, uh, [chuckles] which I hate. Uh, but I-- and so I love that that's kind of what you're trying to do here, is add a lot more nuance to all these, what people think is, um, is true and, um, and show that it's not, you know, we've got all these spectrums and gradients that we've been talking about. Maybe just say more about that, why you think that's important.

Sherif Mansour 56:47 You know, the classic thing in, in product, I think especially, is like every advice you've probably got on how to do product, someone probably has a counter, totally opposite advice that works just as good. And again, you as a product team or a PM or a product leader, you're trying to understand the context in which their advice worked in and, and that's where a lot of the nuance gets missed. You know, the AI builder is one, Lenny, that we just talked about is a great example, where like I think zero to one projects, even in large organizations, you should put an AI builder type onto it. I'm fully convinced of that. But again, most organizations that have access to developers, this is not their problem. Their problem is where to direct the ship. So the context in which the advice is given is super important. Just like start with the solution, not the problem. I, I would equally advocate to start with the problem, but not enough people talk about the, the counter thing. Um, it also just gives people confidence in like, am I doing things the right way? And I'm like, is there a right way? L-like, is it like, um, you know, if you do something and you've learned something, share it with the world. Like I, I would often, you know, for a while I used to try to write blog posts about like I would share every craft lesson I've learned, you know, that, you know, one of the most, uh, things we're talking about internally is like how do we scale product management inside Atlassian? And I go back to when I started Atlassian, there were no product managers on Confluence. The way we did that was these things called product engineers, and I learnt what a product engineer was and I, I realized there was no term codified out there, and I wrote a blog post about what I learned about product engineers, whatever, and you realize product engineers help product managers scale. They help you. They're the champions of that shared context that you- we talked about earlier, right? So all those nuances, you're like, you know, I, I don't think get talked about enough, but I, I appreciate you running these, these talks and hearing people out share their nuances. I think that's, that's what needs to happen more.

Lenny Rachitsky 58:38 Yeah, it's tough. Like I'm in a tough spot sometimes where people share an opinion and many people are like, "That is wrong. Why did you give-- Why did you not push back on that?" I find the best thing I can do that scales is have different perspectives here and not try to, you know, have everyone, like get everyone in line. This is the way to do it. And then people can decide, here's what fits for me. Someone actually built a really fun project. Uh, so I don't know if people know this. If you go to lennysdata.com, you can actually, uh, connect to an MCP that has all of my podcast transcripts. You're gonna be in there. You're gonna be slurped into this MCP soon. [chuckles] Uh, and it's also all my newsletter posts that you can use it any way you want. And somebody built, I think it was Noam actually, Noam Segal, uh, built a tool that's like shows both sides of every debate. [chuckles]

Sherif Mansour 59:24 Oh, that's awesome. L-like the contradictory-

Lenny Rachitsky 59:27 Uh-huh

Sherif Mansour 59:27 ... advice?

Lenny Rachitsky 59:27 Exactly. Yeah.

Sherif Mansour 59:28 That's so good. Uh, and, and then you want-

Lenny Rachitsky 59:30 Yeah

Sherif Mansour 59:30 ... like that'll be a-- I'd love to see that dashboard and you'd love to see why it worked. Like this advice and why it worked, and this advice and why it worked, um, uh, is a, is a, is a, it's such a g- that's awesome. That's so good to see.

Lenny Rachitsky 59:43 Is there anything you want to say that'll feed into this MCP that'll be forever part of the data set?

Sherif Mansour 59:49 I think I've given quite a few misconceptions here. So we've talked about misconceptions of AI builders. Everyone's a builder. We've talked about the misconception of, uh, all, all PMs are the same. I think artist, scientist, general manager is one framework. You could, you could do that. Misconception of, um, PMs make all the decisions, right? I think that's another one we talked about. Oh, management. Management's another one, Lenny. So like, uh, you, you d- uh, you-- everyone runs into their career in product management, and usually most organizations you hit a path where you, hang on a second, I wanna be involved in the strategy discussion, the strategy offsite. Oh, but it looks like the people that go to that thing or do that activity seem to be managers. I went through this experience myself, so therefore I need to manage. And they hit this fork in the career where they feel like that's the decision. And, uh, and so the other, I think, misconception we need to help debunk is, you know, I think we try to do more of this at Atlassian. You know, we have multiple distinguished engi- uh, product managers and engineers now, um, where they work at the execel- executive level. And so we're huge champions of the dual track career paths for individuals and, uh, managers. And some-- a lot of people switch between both depending on the season. Um, they're in. Or the thing- they're starting at zero one. They'll go to managing a small team for a while, and then it'll get big, and they'll move back off. And we should celebrate that more because it, it plays to that person's strength. Um, uh, and so that's another, that's another misconception, like to, to be involved in large strategic decisions at exec level at large companies, um, you need to be a manager. Nah, we have a lot of individual contributors that, that contribute at the exec level, yeah.

1:01:31 – 1:02:42

Why managers still matter

Lenny Rachitsky 1:01:31 Well, sure. A mis- c- uh, counter-narrative that I've been feeling, which is that there's all this talk of we don't need managers, and that managers should be IC-ing as well, and I feel like that's just not a good idea. I feel like manager is actually very important.

Sherif Mansour 1:01:46 Mm-hmm. Yeah.

Lenny Rachitsky 1:01:46 And I feel like to be a good-- And I feel like to be a good manager, it's very hard to also do IC work, like meaningful IC work.

Sherif Mansour 1:01:54 It's, uh, really hard. And so you can take two worldviews there, that you could take- if you're gonna manage, manage a lot, so take like 10, 15 people. Or a, we want managers that'll take three or four and own a project as well. And, and the reality is we have a mix of both at Atlassian. Um, and, uh, again, try to play to each person's strength, um, and that's how you'll get the best outcome. Uh, and so do we have, we have-- The span of control for managers, we generally try to say you should have at least three or four people minimum. I think most are in the eight or nine bucket. I mean, something like that. But it, um... Yeah, you do have some managers that will take on a few people and will own projects, and some that will take on a lot and play a coach role, uh, a lot more.

1:02:42 – 1:04:05

The most common mistake new PM managers make

Lenny Rachitsky 1:02:42 Let me ask you this. Uh, um, for new PM managers, say you just got into it, what do you find is the biggest sh- issue that they run into/thing they sh- should probably be working on?

Sherif Mansour 1:02:55 They-- The number one thing I've seen is they go too hands-off too quickly, and they think that's the, the best behavior. Um, I would-- It sounds a bit counterculture. I think the best leaders that we've ever had at Atlassian that continue to be there, the best managers, I shouldn't say managers. Managers, leaders can be two separate things. You could have a leader who's a good manager, a manager who's not a good leader, and vice versa. Um, so the best managers who are great leaders, um, are able to go in with the team and help them get through outcomes. I can sit in a product review, Lenny, I'll be like, "This, this isn't simple enough." And it's not like the team was sitting around going, "All right, let's, let's wr- oh, sorry, I forgot to write simple to the agent." Li- like as in, um... But the best managers are like, "Let's explore some options together." And they get in and they help the team work together and get through the outcome. Uh, I think that was-- that would be my number one observation of they go so hands-off and they're like, "I'll just... I'll, I'll almost zoom out completely and let the team do that," which is good. You need to create space, don't get me wrong. But the teams love it when they see managers lead by example, so I think it's gonna be more important

1:04:05 – 1:07:12

How to work with visionary founders and strong stakeholders

Sherif Mansour 1:04:05 in the world of AI.

Lenny Rachitsky 1:04:06 That's great advice. Okay, possibly final question. Um, I've heard from a bunch of people that you work very closely with the founders and execs on the big product keynotes that the founders do.

Sherif Mansour 1:04:19 I love keynotes.

Lenny Rachitsky 1:04:19 [laughs] Something most people don't say. Um, you also work with, um, the CEO and co-founders on their, like, founder presentations, things like that. What's something you've learned about working with, you know, the top of the top that might be helpful for folks that are-- maybe struggle working with execs?

Sherif Mansour 1:04:38 There are so many. Uh, uh, dangerous last question, Lenny. Um, without a doubt, I, I describe working with as, as someone who's a strong visionary leader, um, often in founder-led companies it's still the case, et cetera. It's like me and you watching a movie, and they're on, like, scene, you know, chapter 10 of the movie, and you're on chapter three, and the rest of the teams are on chapter one. And they're saying stuff or whatever, and you're thinking, "Wait, what?" Like, you're like, "Are you sure?" Like, that's everyone's first reaction. Now, you can do two things at that point as someone who works with that stakeholder or leader or vision leader, et cetera. You can say, "I'm gonna follow orders and go do that," and just pass that on. But the, the, the dangerous thing you do that is you're doing that with no conviction. You're doing that because the boss asked me to. And, uh, or your job could be like... By the way, you know, the vast majority of the time you could argue was the st- was the stakeholder or the founder right or wrong. My, my experience, they've been right nine-nin- 99% of the time. Uh, it's just what I've realized is they've thought about that thing far more than anyone else, and the aha moments that got them there, my job now is to fill that context gap to work out why did they get there, and do I feel convicted of their thing? S- And I'll often start by like, "I don't know, man. I'm still working through this." What made you leave that conclusion? And I'm trying to get to chapter 10 as quickly as possible. And once I get to that, I know now what I need to do to bring the rest of the people along with me. So I would say often with these leaders, they're thinking about things a lot, and trust, start by trusting, but they, it's not... Uh, I think the counter-narrative here is the HiPPO, highest paid stakeholder, the whatever. I can't remember the acronym. It was the highest paid-

Lenny Rachitsky 1:06:28 Highest paid-

Sherif Mansour 1:06:28 ... opinion

Lenny Rachitsky 1:06:29 ... person opinion or something.

Sherif Mansour 1:06:30 Or something.

Lenny Rachitsky 1:06:30 I can't remember.

Sherif Mansour 1:06:30 Yeah, I can't spell people. I know. I totally butchered that one. Um-

Lenny Rachitsky 1:06:33 Highest paid person.

Sherif Mansour 1:06:34 Yeah. So I th- I think the flip side is, oh, there's some stakeholder who thinks this is the, this is their pet project and whatever. I think that's certainly true in companies, don't get me wrong. But I, I think when you have someone that you know that has thought about this domain particularly well, especially in the enterprise B2B space, um, you know, I always say to someone like, "You can find..." If someone's worked in this space for several years, it is vastly different to, I did a year here and I did a year there. It, it takes time to make large changes and whatever. And so assume they're right and assume you're wrong, and try to fill that context gap. And sometimes you'll prove them wrong, but that's not the goal here. The goal is to get the best outcome for customers. And so then you can bring the team along on the journey. Yeah.

1:07:12 – 1:10:51

When you disagree: a framework for transparency

Lenny Rachitsky 1:07:12 Let me ask you what happens if you actually disagree, 'cause I think a lot of people feel this, like go through this, and they're like, "That is a bad idea." Um, tips for handling that.

Sherif Mansour 1:07:21 So if you feel like you've caught up to the aha moment and you're still disagreeing and you feel like you have a good case for why you disagree, I will still state that, and then I will state, "Is this something you have crazy conviction for?" And I'll say, "Are you the decision-maker or am I?" Like, I will ask that. L- common question is, "Who owns this decision?" Like, just be super transparent, and if they really feel like, "I would like to take this decision," or, or, "I want you to decide. I disagree, but I want you to decide." But which, by the way, they do a lot more than you'd imagine. Like, they'll be like, "I disagree with this, but I want you to, I want you to own that decision. Um, but I will back you if I disagree, and I will back you and move along with it." So transparency is key to, to foster that relationship.

Lenny Rachitsky 1:08:02 So but what do you do when you're communicating it to your team and you disagree? Anything there? Is it stand behind it always?

Sherif Mansour 1:08:09 Uh, no, I'll present both arguments. I will state why I believe one argument is more superior than another, and I'll equally argue for the opposite. There was a recent example where, uh, you know, we're, we're branding a particular thing and whatever, and I, I think it was, like, the best of the worst decisions we, you know, best of the worst options we could make. And I'll say, "I think here are the pros and here are the cons, and if you argue for the opposite, I think here are the pros and here are the cons. We have decided to make this decision." I'll try not to call the individual out, and they're both, they're both legitimate trade-offs, and we're moving ahead with this one. Um, and, and you need to speak the room of what the th- other opposite argument that everyone's thinking and represent that appropriately. The best PMs I find can counter, like, argue against themselves and present you really good reasons why they shouldn't do the thing. The really blind ones will be like, "Oh, yeah, my thing's the best. It's, you know, we should definitely do this option. This is the best option in the world." And like, I'll often say, "Why would we not do this?" I love asking that in reviews. And then sometimes like, "I haven't thought about why we wouldn't do this." I'm like, "You should argue for the opposite as well, and feel like you've intellectually wrestled with that, and then move forward."

Lenny Rachitsky 1:09:12 That is great advice. Something that I'll mention briefly, um, when a found- when someone with power, uh, sent- shares a, an opinion, a lot of times people take it as that is what we need to do. And Dharmesh Shah has this really great framework he calls flash tags. I don't know if you know this.

Sherif Mansour 1:09:28 Yeah.

Lenny Rachitsky 1:09:28 Where he basically says, okay, he's like, hashtag FYI. So when he shares an opinion, it's like, okay, this is just an FYI, uh, or this is a suggestion, or this is a recommendation, or this is a plea. [chuckles]

Sherif Mansour 1:09:42 Yep.

Lenny Rachitsky 1:09:43 And he's c- and it's a nice way for someone that implicitly has power to communicate, "Okay, this is how I feel. Just an FYI. You don't have to do this." Or, "This a plea, please do it."

Sherif Mansour 1:09:52 Yeah. And I'll say, um, those are, like our frienders do that as well quite a bit. They'll say, "Strong opinion, not my decision," blah, blah, blah. Um, I will tell... But often you'll get people just in the, in the, in a discussion, they won't pre, you know, hashtag their discussion as they talk.

Lenny Rachitsky 1:10:08 Yeah.

Sherif Mansour 1:10:08 And so I'll say to PMs, "Your job as a PM is to be that person in the room to ask that clarifying question on-

Lenny Rachitsky 1:10:13 Mm-hmm

Sherif Mansour 1:10:14 ... level of, uh, conviction on the topic." And, you know, just to be clear, you know, you know, the classic playback technique at the very end, but, like, as part of that process, be like, "This is a conviction we will go and explore further," or, "This is something we will take as input and then may decide ourselves," and be, be clear with that. So I'll put that back on the PM sometimes 'cause the stakeholder doesn't always do the hashtag at the end of, or before, or whatever it is, if you know what I mean.

Lenny Rachitsky 1:10:38 Oh, man. Feel like we could talk for hours of all the tips and tricks and tactics you've learned. This could go on forever. I'm gonna, I'm gonna e- end it here so that we have time for another episode someday to go deeper. Um,

1:10:51 – 1:11:37

Final thoughts

Lenny Rachitsky 1:10:51 but before we get to our very exciting lightning round, is there anything else that you wanted to share, anything else you wanna double down on before we get to our lightning round?

Sherif Mansour 1:11:00 I think to your listeners, nuance, I think we've talked about the nuance, is important, so please, uh, like, share your stories. I would think the other thing I would just highlight is you're a product of someone else creating opportunities for you. So ask yourself, who are you creating opportunities for? And if you can't think of that name listening to this podcast or watching it, try to find someone that you can champion, be a, be a voice for, et cetera, because you believe in them and you, you know, uh, uh, you wanna give them a go and that kind of stuff. So, uh, just remember where you came from is a long way of saying that.

1:11:37 – 1:21:35

Lightning round

Lenny Rachitsky 1:11:37 I love that. Well, Sherif, with that, we have reached our very exciting lightning round. I've got five questions for you. Are you ready?

Sherif Mansour 1:11:46 Let's, let's go.

Lenny Rachitsky 1:11:47 Let's go. [chuckles] First question, what are two or three books that you find yourself recommending most to other people?

Sherif Mansour 1:11:53 Look, I read, I read with my kids a lot or read books with my kids. Lately, we're reading, um, The Prison Healer, um, Yvette Norri, I think her name is. Uh, it's a, like a, a fantasy book, uh, in a prison scene, dystopian, uh, prison kind of escape story. Um, awesome read with my kids. Uh, I, like I, I personally read the Bible a lot. I think it's a book that I just keep coming back and meditating to and gives me some kind of grounding in the world of where AI's headed as well. Um, uh, but like most of my books are, are kids books. The other one I read with my kids, uh, Wingfeather Saga is such a good read. Uh, it's about a, a, a bunch of kids who are heirs, heirs to a kingdom, and they don't know that, um, and they overcome adversity to get there and stuff. Anyway, so I read a lot of kids books. Yeah.

Lenny Rachitsky 1:12:42 Favorite recent movie or TV show?

Sherif Mansour 1:12:44 Project Hail Mary was awesome. I cr- I mean, I cry at a lot of movies, so it's probably a bad... Like, uh, yeah, just totally loved it. Awesome watch. Very thought-provoking, emotional.

Lenny Rachitsky 1:12:58 Fun fact, my cousin is the Russian scientist in that movie. Hmm.

Sherif Mansour 1:13:03 That's awesome.

Lenny Rachitsky 1:13:03 How cool is that? A little somewhat distant cousin, but still related. She's killing it. Uh, okay, next question. Favorite, uh, slash most interesting AI product that you've recently discovered or just are really hooked on?

Sherif Mansour 1:13:16 This is total recency bias. I mean- There's a few favorite AI products, but, like, I'm just gonna go with a massive recency bias. We're on a long drive with the kids and, uh, Google Maps added Gemini to Google Maps, at least in Australia in Apple CarPlay. I don't know if you've seen that before or not. And so when we drive, we typically put on... Sometimes we put on music, sometimes we put on AI and play a game. We play, like, a road trip game, or we'll play a quiz game, and we'll all take turns or whatever it is. We'll everyone will be yelling at the AI while we're driving. It's very entertaining. But it was fascinating to see in the map view Gemini added, because we just pressed the... Like, it's just such a lesson in product workflow proximity. Like, I'm in the map, I'm not gonna close it off and switch and open one of the AIs to talk to it. I'm just gonna chat to Gemini right here. But it's super contextual to the trip, so it'd be like, "Hey, we're heading to this destination." And we started playing some fun quiz games about the destination we're going to, et cetera. And it was just one of those delightful experiences in the car that I'm like, "That was awesome." It was a fun experience. I could still see the map and talk to the AI at the same time. The kids had a blast, so it was entertaining. Got them off the screens for at least 30 minutes.

Lenny Rachitsky 1:14:22 Do they just bolt AI onto it?

Sherif Mansour 1:14:24 Oh, nice. I like how you did there.

Lenny Rachitsky 1:14:26 Call back.

Sherif Mansour 1:14:27 They, they bolted it onto an existing workflow, some of the best strategies you'll ever do. Nice. Nice, Lenny. I love that.

Lenny Rachitsky 1:14:33 Example of you being right. Here we go.

Sherif Mansour 1:14:34 [chuckles]

Lenny Rachitsky 1:14:35 Okay. Uh, two final questions. Uh, favorite life motto. Is there a motto you often come back to in work or in life that you find really useful?

Sherif Mansour 1:14:42 People tell me I'm very relaxed and fun at work and always joking. It's usually how I deal with my nerves, to be honest, Lenny. Uh, but they ask me, like, why, et cetera, and, like, I'm always reminded that, like, you as a person is... Decouple yourself from your job identity, which is really hard, especially in the world of tech, um, and celebrate the individual outside their work life, I think is an important thing, uh, that we don't, we don't do enough. And, um, you know, I love playing footy, which is like, like flag tag, uh, with a bunch of, uh, folks who live locally, and none of them work in tech. And, uh, you know, they're just a mix of electricians and bricklayers and whatever, and different jobs. But like, um, they're amazing human beings that don't work in technology. And so reminding people to decouple themselves from their job as their identity, I think is something that's healthy, uh, and will keep you sustainable in your work and in your personal life as well.

Lenny Rachitsky 1:15:43 I will share a quote that, uh, has come up a couple times on this podcast that always hits people right in the, right in the heart: "The only people that will remember that you worked late are your kids."

Sherif Mansour 1:15:54 So, so true. Uh, I've heard a similar one, which is nobody goes to a funeral and the tombstone, like y- it's saying on a tombstone, "This person worked so hard," or whatever. Like, that's never in the eulogy or whatever. So-

Lenny Rachitsky 1:16:04 Right. Right

Sherif Mansour 1:16:05 ... that's a, that's another motivator. Yeah.

Lenny Rachitsky 1:16:06 They hit the quarterly number.

Sherif Mansour 1:16:07 [laughs]

Lenny Rachitsky 1:16:11 All right. Final question. I've been wondering what is going on behind you? There's, like, all these fun things that are happening. Uh, what is, what is this? Explain.

Sherif Mansour 1:16:19 Uh, Atlassian T-shirt culture. We make a T-shirt often to tell a story about a moment in our history. So this, like, Confluence Questions was an app. That was, uh, when we had our first QA team. That was when we launched a Vietnam office. There's a story behind each one of these shirts, and, uh, I love collecting them. Just a great way to tell stories. With the bigger you get, the stories become more important to, to tell the teams, and I've got hundreds of these shirts. And, um, one day my wife ripped up my shirts and, uh, surprised me for a thing she did for my birthday and created up this giant plaque, uh, this huge, uh, shirt and stitched together some of my favorite shirts that have stories behind, uh, each one of them. So that's what that is.

Lenny Rachitsky 1:17:02 That's, uh, very sweet. I could see that going horribly wrong. "What did you do to my shirts? I've been saving these for years."

Sherif Mansour 1:17:09 I, uh, wrote a blog internally that was titled, "My Wife Ripped Up My Atlassian Shirts," and people were like, "What?" And then they read the details and whatever. But then for our recent, uh, 20-year anniversary as a company, I, I just walked through 110 shirts and recorded a video on YouTube. It was, it was a lot of fun and just, like, the story behind each one, it was just very satisfying.

Lenny Rachitsky 1:17:27 Let me ask you this briefly. What's, what's a unique cultural kind of, uh, ritual of Atlassian that might be fun for people to learn of?

Sherif Mansour 1:17:36 Uh, there's a lot. We are an incredibly transparent company. Uh, open company is one of our values. Um, like, as in every exec review is usually recorded, available to search and find in Loom and ask questions and, you know, run the AI agent through it. So the transparency here, everyone that joins says, "I've never experienced anything like it." I mean, I haven't started Atlassian for a long time, so I'm used to it, but they're like, "Oh my gosh, when do you stop reading?" Like, like, there's so much content. So I would say open by default is the... Ironically, Lenny, I think it's also, I mean, partly because of Confluence and the nature we have of the product we have, people just document and, and create, and it's open by default. But sharing context is key in the world of AI. Uh, and um, and so our having an open by default approach to things is actually better in the long run for you as a company because there, by definition, it means there's more context that the AI has access to and the humans have access to. So the, uh, openness is, is unbelievable here. But, um, it's, it's pretty crazy, but, uh, people love it.

Lenny Rachitsky 1:18:41 That is, that is super interesting. There's, there's been a number of companies over time that have done this. Uh, GitLab is a good example, and it's interesting now with AI being able to read all of the things and tell you what you need to know. It changes that, and like, in theory, you could... Like, it might expose things that maybe people shouldn't have seen much more easily and quickly. On the other hand, it gives you all the context, as you described, to make better decisions.

Sherif Mansour 1:19:06 I have this theory, Lenny. So we have, we have a team anywhere policy, so you can work anywhere you like. We have a legal entity, so some people choose to work remote a lot, some people don't. And so just as an example, you know, when, um, I have part of my team is in the West Coast of the USA. They, a lot of them like an in-office culture. And for reasons, and there are some people in, in the APAC region love a distributed culture. Uh, I have a theory we're trying to prove out right now, a hypothesis, which is those that are remote are more likely to get, uh, uh, more outcomes out of AI than those that are co-located.

Lenny Rachitsky 1:19:40 Mm-hmm.

Sherif Mansour 1:19:41 Uh, and so we're just got a bunch of data scientists trying to prove that out right now, so that'll be a fascinating theory. And the-

Lenny Rachitsky 1:19:47 That is really interesting

Sherif Mansour 1:19:47 ... the thing here is that you just tend to write more and share more digitally when you're remote.

Lenny Rachitsky 1:19:52 And consume, yeah.

Sherif Mansour 1:19:52 When you're in person... Yeah, when you're in person, you just whiteboard more or whatever, and they're both good approaches, and you need both. But it's, um-

Lenny Rachitsky 1:19:59 That's interesting

Sherif Mansour 1:19:59 ... that's a, again, maybe another counterpoint of the going back to in-office culture maybe. Uh, we'll see.

Lenny Rachitsky 1:20:05 Uh, going back to this report that I'm putting out, actually, remote work has plateaued. There's no... It's kind of-

Sherif Mansour 1:20:09 Ooh

Lenny Rachitsky 1:20:10 ... stalled at 10, 15, 20% across industries, so that'll be interesting to watch if that grows again-

Sherif Mansour 1:20:15 Yeah

Lenny Rachitsky 1:20:15 ... with AI. Anyway, I keep asking you questions, but we should wrap up. Uh, Sherif, this was awesome. This was such a great, deep, important conversation that I think is gonna help a lot of people. You were talking about opportunity. I think this is gonna open up a lot of new opportunities for folks. So, uh, thank you so much for being here. Um, any... Is there some way that listeners can be useful to you? That's my final question that I almost forgot to ask.

Sherif Mansour 1:20:40 If you see something in social media, a lovely tag headline on a one-line grab, "You shouldn't hire juniors anymore," or whatever it is, whatever it is you see, be the person that asks the nuanced questions and be like, "Oh, w- wh- why did that work for you? Why didn't that work for you?" Don't be the-

Lenny Rachitsky 1:20:56 Mm

Sherif Mansour 1:20:56 ... person that amplifies that one view without first understanding the context.

Lenny Rachitsky 1:21:01 Mm-hmm.

Sherif Mansour 1:21:02 I think that applies to many things in society, not just product, but yeah. [laughs]

Lenny Rachitsky 1:21:05 Nuance.

Sherif Mansour 1:21:06 Yeah.

Lenny Rachitsky 1:21:06 Um, amazing. Sherif, thank you so much for being here.

Sherif Mansour 1:21:09 Appreciate the time and the opportunity. Thanks, Lenny.

Lenny Rachitsky 1:21:12 I appreciate you. Bye, everyone. [outro music] Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.

Episode duration: 1:21:37

In the uListen app, the transcript lights up word by word as you listen. Get uListen

Transcript of episode hRtmV1mCBSE

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.