How to ask the right questions, project confidence, and win over skeptics | Paige Costello (Asana)

[00:00] You're often the youngest person in the room. What have you learned about how to garner trust and win over skeptics? The thing I would say is bring the insight. Know thy customer, know thy market, know thy competitors, know thy [00:13] numbers, know thy product. I'm curious what you find most holds back new PMs. Your brain is so accustomed to having a scarcity mindset as opposed to like creating alternative options or seeing a different path. Effectively, there's this notion of how might the opposite be true. And the moment I challenged myself and said, how might the opposite be true, my shoulders dropped. I felt more relaxed. I was like, [00:40] "Oh, yeah, I can do both. It'll be fine." Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful products. [00:54] Today my guest is Paige Costello. Paige is a product lead at Asana, overseeing teams responsible for the core product experience of Asana. [01:02] Before Asana, she was director of product at Intercom, and prior to that, she was a group product manager at Intuit, where she spent five and a half years. In our wide-ranging conversation, we dig into strategies for building trust with people who are more experienced than you or older than you. We talk about coaching product managers, including why leading by example is often the most effective strategy. We talk about Asana's product development process and how it's evolved over the years as the company is scaled,

[01:32] To prep for this interview, I got input from some of Paige's colleagues and former colleagues, and everyone I talked to loved Paige. You'll soon see why. Enjoy this episode with Paige Costello after a short word from our sponsors. [01:47] Today's episode is brought to you by Brave Search and their newest product, the Brave Search API, an independent global search index you can use to power your search or AI apps. If your work involves AI, then you know how important new data is to train your LLMs and to power your AI applications. You might be building an incredible AI product, but if you're using the same datasets as your competitors to train your models, you don't have much of an advantage. [02:16] and it's 100% independent from the big tech companies. Its index features billions of pages of high-quality data from real humans, and it's constantly updated thanks to being the default search engine in the Brave browser. If you're building products with search capabilities, you're probably experiencing soaring API costs or lack of viable global alternatives to Bing or Google. It's only going to become harder to afford these challenges. The Brave Search API gives you access to its novel web-scale data [02:46] of structuring and affordable costs. AI devs will particularly benefit from data containing thorough coverage of recent events. Lenny's podcast listeners can get started testing the API for free at brave.com slash Lenny. That's brave.com slash Lenny. This episode is brought to you by Atio, a new type of CRM that's powerful, flexible, and built around your data. Traditional

[03:16] speed, scale, and data demands. Atio is different. It allows you to quickly build a CRM that matches your unique workflows and data structures. Within minutes of connecting your email and calendar, you'll have a CRM that's already set up, complete with customer profiles and automatic data enrichment. You'll also have real-time dynamic reporting at your fingertips. No more slow deployments, outdated user experiences, or tedious manual data input. With Atio, you can build and [03:46] business model or company stage. Atio is the CRM for fast-growing startups. Get started today and get 15% off your first year at atio.com slash Lenny. That's A-T-T-I-O dot com slash Lenny. [04:04] Paige, welcome to the podcast. Thanks, Lenny. Great to be here. [04:08] So you don't know this, and I didn't tell you this, but I asked a [04:11] bunch of people that you worked with and maybe currently work with for questions, suggestions of things to ask you. So this is going to be really fun. Wonderful. Now I want to know who you talk to, but we'll find out. [04:23] I'll tell you right now, a big thank you to Jackie Bavaro. [04:27] Yasmin, who is on your team, [04:29] Anne Montgomery and Steve Morin, who is currently in Asana. [04:33] And so thank you to all of those folks for giving me a bunch of great questions, suggestions. Looking forward to it. Maybe just to settle a context, can you just talk about [04:40] At Asana, what do you work with? What is your team? What do you work on? And what is your team responsible for broadly? Yeah, absolutely. So I lead the product organization that's responsible for our desktop web and mobile apps at Asana. And the teams are composed of all the people in San Francisco and New York who are focused on creating clarity for individuals, teams and organizations. And effectively, our goal is to help teams work together more efficiently and drive the outcomes they're going for.

[05:10] about the feature sets if you're an Asana user, like goals, portfolios, projects, tasks, reporting, all that. But really, we want to help people answer the question at work, who is doing what by when and why? So that notion of clarity of purpose, clarity of plan, progress, and responsibility are often so painful in people's work lives. And when there's certainty there and clarity there, people can be much more efficient in getting the work done. [05:40] where my focus is, every day I'm a product leader for that group. [05:44] Cool. So basically like the core, like when people think of Asana, it's all of that stuff is what it sounds like. Yeah, there's another group that's focused on our process management, but a lot of the core work and project management core is in my group. And then we have a growth and enterprise scale team. And you've been at Asana for about four years now. Yes, four years this summer. Cool. So something I'm always curious about, about companies that are at this scale is just the evolution they've gone through in terms of how they develop. [06:12] product. [06:13] And so I'm curious, just in the time you've been there, how has the product development process at Asana [06:19] changed and maybe even simpler, like what are some of the bigger changes that [06:23] have been made to the way product is built at Asana over the years? I would talk a little bit about how we set strategy and our planning process and how that's changed in this time, as well as how we actually ship product has changed in this time. On the planning front, we have really changed what altitudes we're planning at,

[06:43] the time horizon we're planning it, [06:45] Some of the inputs have gotten a lot more precise and opinionated. So for example, we have always had pillar plans and team plans, but maybe we didn't have an intermediary layer of like an area perspective. Well, what's an area perspective? Well, [07:02] you know, as your organization grows, we've had to reorganize to create more [07:07] agency and accountability close to teams that are focused on specific target customers and problems. So if you think about the way Asana is organized, we've got our R&D, the pillar structure, the areas within them, and then the working teams. It might actually help if you even describe, like, what is a pillar? What is an area? Yeah, absolutely. So when I said I'm responsible for that core product pillar, that's one pillar. But then there's also the adoption and enterprise [07:37] and the workflow pillar. And then when within each of those there are subgroups and we call those areas. And each of those areas has a very specific target customer and problem space they're solving for. We've often also dialed up the clarity of the metric at that level. So while we have an R&D set of metrics, we have pillar metrics, we have area metrics, and then at the team level there's often like one or two [08:07] a nested structure around our product strategy, as well as how we measure success. And when I joined, we didn't have areas. We were organized around projects and around locations. And then we worked to make sure that

[08:24] the thinking was more durable and problem focused, so that our roadmaps were not about features, but were instead about [08:31] what was most meaningful to tackle for our business growth. And so that's a big thing that has changed, the altitude of planning and how that nests. Another thing that has changed is the time horizon. [08:45] Before we planned annually primarily, and now we plan every six months, but for a rolling 12 months. And so we have higher confidence in the immediate half, lower confidence in the following half, but we just plan every 12 months, every six months. Because it gives our business more confidence in what's coming and a better opportunity to align our go to market and product planning. [09:10] Amazing. So I just actually was talking to one of the heads of product at Shopify, [09:16] And they went through a similar transition where they used to plan yearly, and now they plan for the next six months. [09:21] So it's interesting that I'm hearing this more and more. [09:23] And you're saying that every six months you revisit the plan for the next year. So it's kind of like an interesting hybrid of those two. [09:29] Yeah, absolutely. I think the more you try to do things in a joined up way, where you have a single target customer with sales and marketing, and you want to make sure that [09:42] the impact of your releases hit their mark, the more it's important to reflect on it frequently and to be able to pivot quickly. Because our strategy, even when we think we have a two year vision, something will change. And then we say, wow, we made so much faster progress on this than we thought. And we actually believe that there's a new opportunity or a new technology that we should be leveraging. Let's go bigger on that. And so it reduces the feeling of churn and thrash.

[10:12] It makes us all more principled and it helps us just make sure we're making the best use of our teams. [10:20] And I like that it also admits you're not going to actually have a yearly plan. Like everyone plans for a year and then halfway through they're like, no, let's start rethinking everything again. I like that you're upfront about that. [10:29] Yeah. [10:30] Okay, and then within the plan, [10:32] Do you have quarterly plans and sprints? Is there anything more fine-grained with a detailed roadmap? Yeah, not really. I mean, teams know approximately when are they expecting to do the work, but... [10:45] and [10:46] If you ask too much for a particular quarter or a particular week or date, people make strange choices about scope. And so really, we align on what success looks like and the teams do their best job to ship as quickly as possibly, as iteratively as possibly. And we really encourage prototyping. [11:16] was on the roadmap, it had to be done, and that's just not smart. Got it. So essentially there's a six-month roughly detailed plan of what each team is going to [11:24] Got it. Interesting. Maybe just a couple more things just to make them super concrete for folks that might be listening. What's an example of an area? Like what's an actual team that would be an area? [11:35] And then the other question I have just while I'm saying questions is, are there some metrics you could share just like what some of these teams might be gold on? Just examples of how you think about metrics. The area that came to mind when you asked about one of our areas is something called coordinate. And their job is effectively making sure that the slice of Asana that helps teams work together is working effectively. And so that's projects and tasks and the data that you might put into tasks and.

[12:05] all of the back and forth that is required when people use Asana for their core working team. Some of the metrics that they care about are like org paying weekly active users, as well as really thinking about like healthy project use. So we make sure that we understand like what does good look like and what is a dynamic that we want to be creating in terms of people getting real [12:35] sure that we're not driving one metric at the expense of people really getting what they need out of Asana. [12:41] Just a couple more questions along these lines. I'm a nerd sniped about process. I think you use a process called the double diamond process at Asana. Okay, cool. I've seen images of this in various places, but I don't know of any company that's actually using it as the process. [12:56] Can you just describe what the double diamond process is and how you use it? [13:00] So you might be familiar with kind of lean startup concepts and double diamond as it relates to going broad and then going narrow. And so you go broad when you ask, like, what customer should I solve for? And then you pick one. And then that's the narrowing. And then you go broad and you say, what are the problems this customer has? And you narrow and you say, this is the problem they have. And then you go broad and you say, what solution should we do to this? [13:25] And then you go narrow and you say, this is the solution that we should start with. That process of going broad and going narrow and going broad and going narrow forces people to get out of their opinion driven lands. Because so often we really want we need to be curious quantitatively and qualitatively about

[13:47] what we're doing and why and be more systematic and rigorous about getting there. And it doesn't take long, but it just like breaks the frame. And so this the the double diamond process that Asana effectively [13:59] Each of our typical reviews or artifacts sit at different inflection points on the double diamond. So we actually ask people to do a kickoff where they collect different [14:12] information at different scale depending on the size of the problem and the ambiguity they're solving. Some people have already done enough customer selection and research that they're starting with [14:24] what are the possible solutions to this problem? And then they're bringing the spec, and that's the narrowing alongside designs, et cetera. But it's really mapping our [14:34] our artifacts against this notion to make sure that the product thinking has that [14:41] quality of decision making. Yeah. And the way you described it is it was very customer [14:47] target-oriented? Is that the actual framework? Is it around who to build this for and then what to build? [14:53] Or is it more... [14:54] - It is, okay, you're nodding your head. - It is, yeah. It's really important because then you also know what success looks like. Because if you pick your success metrics as using a feature, [15:04] That's it. You're teaching to the test. It's not actually driving the outcome. So while our planning process is around effectively defining category and like how we win and making sure that customers receive certain benefits from using work management, the through line to the

[15:25] individual project that a team might be leading is they need to know who they're solving for and what it means to have that problem solved. And so there, it always starts with enough customer insight such that we can creatively do what they're trying to do. I mean, really inventing on behalf of customers. [15:43] Can you maybe repeat if there's like terms for each of those phases? Yeah, absolutely. And then is there like an example of a... [15:50] feature or product that went through this that you could share. If nothing comes to mind, that's okay. [15:54] The inflection points are... [15:57] The kickoff, which is that going broad, [16:01] And then customer and directions selection. [16:05] So this is both the target as well as [16:09] of the 10,000 foot views. [16:11] of how you might pursue solving this problem, which path are you broadly going to take? [16:16] and then going broad within that path on different concepts. And then there's a [16:22] design concept review, [16:25] and the product's back. [16:27] then the full experience review or design crit of the end-to-end experience and launch. [16:33] Yeah. [16:33] And so that launch review is often just, hey, here's the thing, here's what we said, here are the fast follows. Most of the time, [16:42] By that time, it's already been dogfooding internally for some time, and it's more of a formal [16:48] Do we have the right metrics in place? Are we ready to shift? [16:52] Awesome. [16:53] Do these reviews happen in person on Zoom or asynchronous?

[16:56] It depends. So it depends on the complexity of the work and it depends how much we want to talk about it. A lot of our crits happen in person on the design side. A lot of spec reviews are more asynchronous. And then we'll say, depending on the number of questions people have, we call a meeting. Otherwise, we do mostly async, but it's a mix. It really depends on the complexity and ambiguity of the work. [17:22] solution and how much people have questions about asynchronously beforehand. [17:27] I'm going to take a tangent with my questions here and talk about [17:30] I work from home policy at Asana. This is something that I've been [17:33] wondering more and more about how it's changing because it feels like there's been a shift back [17:37] to the office. So what is the current policy at Asana and what's changed maybe over the past couple of years? Well, we were fully remote during the pandemic and then we came back to the office in an office centric hybrid format. So we're in the office Monday, Tuesday, [17:53] Thursday and then work from home mostly on Wednesdays and Fridays. And that [17:59] dynamic has been designed from the start. We wanted to make sure that we [18:06] took advantage of what's great about working together as teams. And so it's, [18:13] It's been the standard. So I would say what's unique about maybe Asana is, we knew we would do that from the very beginning, instead of hemming and hawing about would we be a remote workplace or not, and what would that mean, and how would we come together, and how would we budget for it? Like, nope, this is going to be an office-centric hybrid, because we wanted to create spaces for people to work together and move quickly. It's been interesting watching people

[18:40] get back into the swing of things. It was not, even though we knew, it didn't mean that on day one, people were great at being in the office. People, you know, were taking stand-up, sitting down. [18:51] Whereas before, you would walk through our office and you could hear people at stand-up because there were stand-up chants and people would be out on the floor. Now people are more likely to do their stand-up in a room and we're trying to, you know, like the next level of standing up during stand-up. But it's kind of, um, [19:08] I'm sure it's a shared experience for other people who are working in offices to get used to using the whiteboards again, to get used to standing up during your meetings. [19:20] bizarre that we could lose a muscle that we had that was so innate so quickly. And I think [19:27] Even in the last month, I would say, and it's in June of 2023, there's more vibrancy in the office, more conversation, more casual. [19:38] someone eating alone at the cafeteria and someone sitting down next to them. So it didn't happen overnight. I've been seeing a lot of tweets of founders just being like, [19:48] Work from home has failed. It's time to go back to the office. [19:51] And I'm curious if that ends up rolling into more and more companies or if it's just like, you know, a few founders here and there. I think it's a real thing for mental health. I do think that having social casual relationships as well as more opportunities to talk strategy with people you're not. [20:08] forced into a meeting room with has been super beneficial. I can say that just today I was having lunch and sat down with my head of data science and we had an impromptu chat about how we review our experiments and how to evaluate whether we had ROI on learning, not just the metrics. And it was one of those things where if we had to schedule it, it might not have happened. And if it did happen, it would have been a couple of weeks from now.

[20:36] It feels like just coming into the office once or twice, or sorry, being at home once or twice a week is not that different from how things used to be, where... [20:42] There was a day of no meetings and a lot of people stayed from home. [20:45] - So it feels like it's almost reverting back to that? - And people are better at it than they used to be. So I would say our remote days are more impactful, and then the days we're together, we're getting into the swing of things. [20:56] Yeah, I feel like as a PM, the only day I was productive in getting real deep work done was the No Meeting Wednesday. It was at Airbnb. I would encourage you to know your chronotype and to lock that time where you have the most headspace to do that work. [21:10] For me, it's mornings. Say morning chronotype. What is that? I'm a morning person, and so I try to make sure that I don't have any meetings before 10, sometimes before 11, and that's when I do my hardest task for the day. [21:26] I also just thought about stand-ups... [21:29] while I was at Airbnb and how not only how much energy they brought, but almost too much energy sometimes where there's like another team doing a stand up and they're just like laughing and clapping. And we're just like trying to work over here. I feel like we need more of that again. Totally. Yeah. [21:44] Yeah. [21:45] Okay, so moving in a slightly different direction, something I heard about you is that you're often the youngest person in the room. [21:52] And you often lead people with [21:54] decades more experienced than you. [21:56] And-- [21:57] I want to ask... [21:58] What have you learned about how to [22:01] Garner Trust. [22:02] And whenever skeptics, especially when they're maybe more experienced,

[22:06] or older, and especially in other functions, I don't know, execs or designers, engineers, what have you figured out there? The thing I would say is bring the insight. Know thy customer, know thy market, know thy competitors, know thy numbers, know thy product. If you can be the person in the room who has watched customers use the product and has a point of view about why one tool is significantly better or worse in a given dimension, and you can do that, you [22:36] with confidence and clarity, and you don't need to know the other person's functional domain, and you don't need the expertise and what they're experts at. [22:47] you can bring insight that makes people [22:50] curious and trust you and just immediately believe that there's an opportunity [22:56] that you're not advocating for, that just is... [23:00] is true. But I think that's a really tricky and unique thing is not to [23:06] pretend like you have more experience than you do, but to be willing to ask great questions and then like, [23:13] be curious enough that you're bringing insight to every meeting that people may or may not have, but you're always willing to share. [23:21] That's such a good answer. [23:22] Because it's like, there's not a trick to it. It's just... [23:25] do the work, spend the time to become the person that has answers that people value, [23:29] And obviously, they will respect you, value your opinion, want to hear from you. [23:34] - Yeah, yeah. Our former board member, Anne-Raymondi, and now our head of business, wrote an article on First Round that was really great about kind of the trust equation. And it really resonated with me, and I don't know if you've heard about it. But she said that trust is equal to credibility

[23:58] plus reliability. [24:01] plus authenticity. [24:03] divided by or over [24:06] perception of self-interest. And I think when you're met by someone who doesn't know you, doesn't know your work, your job is to create credibility. And that's where I said, like, bringing the insight is where you can really tip the scales here. Reliability, this is all about your say-do ratio. Authenticity is just, you know, being vulnerable, being yourself, and then making sure that [24:33] people know that you're not in it for some [24:36] other outcome or cause, that perception of self-interest really can change whether people [24:43] like how much they trust you. [24:46] In terms of knowing [24:47] the insight and knowing thy customer, [24:50] Putting the time, I imagine, is a big element of that. Is there anything, is that [24:54] Is that how you do that? [24:55] Or is there anything else along those lines that's just like, here's how I get really good at this? When you take a new role, become best friends with a researcher and... [25:04] spend time with watching customers use the product. [25:08] firsthand because what they maybe report on or are trying to do a study about might be very different from what you observe, but you really just need that front row seat with customers. And so asking for how do I actually set up time with customers? How do I compensate them? How do I read the tickets? Whatever. It's amazing how little you have to do to quickly catch up to

[25:38] really use your product versus how your team's [25:41] use your product, especially in organizations where there are heavy dogfooding cultures. It's [25:47] really risky to become less sensitive to the needs and behaviors of customers because people think they are their customer and it also becomes very navel-gazy. So I think the more you get out and break up, [26:03] how people are having conversations about what we should do and why, and what we shouldn't do and why. And it's not about your opinion, it's about [26:11] asking questions and then bringing insight can really change the nature of the conversation and build trust. [26:18] I love that. [26:19] In terms of confidence, you talked about the importance of [26:22] communicating these things confidently. [26:24] Is there anything you've learned about how to [26:26] Be more confident. Part of it is having the answer. [26:30] but is there anything there that maybe you coach your PMs around or other folks have just like, here's how you communicate confidence? [26:36] It's a great question. I think being... [26:40] Being brave and courageous in little moments is just kind of what you have to do. You have to show up and say it before you're ready to say it and ask for forgiveness and be vulnerable. And I think... [26:53] When you're vulnerable, people actually trust you more than if you come with all of this armor and say, I know this and this is how we're going to do it. And so real confidence is often conveyed by being willing to ask the question or to say, I don't know what you mean by that. Can you say that again? It's also just how you communicate looking people in the eye, your.

[27:19] body position, your body language, so much of this, I think, people forget about because it's really easy to be in a meeting and looking at your computer and going through Slack messages. And so one of the best things you can do is if you're in a meeting, be in that meeting. [27:36] Continually scan the faces of everyone in the room, see if someone has a question, [27:41] pause at the beginning and welcome people and chit chat while people land and then close asking questions like, did I get all of that? Is there anything you would have expected to cover that we missed? It's really about being open and that conveys confidence more than being assertive and advocating 100% of the time. This episode is brought to you by Round. Round is the private [28:11] of coaching, learning, and authentic relationships to help you identify where you want to go and accelerate your path to get there, which is why their waitlist tops thousands of tech execs. Round is on a mission to shape the future of technology and its impact on society. Leading in tech is uniquely challenging, and doing it well is easiest when surrounded by leaders who understand your day-to-day experiences. When we're meeting and building relationships with [28:41] thinking and achieve our goals. [28:43] Building and managing your network doesn't have to feel like networking. Join Round to surround yourself with leaders from tech's most innovative companies. Build relationships, be inspired, take action, visit round.tech slash apply, and use promo code Lenny to skip the waitlist. That's round.tech slash apply.

[29:04] from my chats with folks that you work with, [29:06] It's really clear that you put a lot of time and energy into... [29:09] mentoring. [29:10] and coaching PMs on your team, and I think probably broadly at Asana, [29:14] And one thing specifically that came up [29:16] is that you're very big on [29:18] leading and teaching by example, not just [29:21] Here's how you do this thing. [29:23] And so if that's true, I'm curious, [29:25] where that came from for you and why you think that ends up being a lot more successful than like [29:29] In a meeting, you should do XYZ versus like Y. [29:32] doing it and then letting them see. [29:33] I think the main thing is repetition. We're all students of repetition. If you see something done [29:40] a few times, you're more likely to remember it and internalize it. And so it's also something that [29:47] a way that I learn, and so I think that's probably part of it. But I remember hearing about a framework called the three E's: experience, exposure, and education. And I think [30:03] It was helpful for me to hear that as like a way of growing your career or being more purposeful about your growth because [30:13] I think... [30:14] When people are earlier in their careers, they tend to think education, education, education. And then they start to think experience, experience. Like, how do I get the experience of being a manager? I need to, like, read about it and then be a manager. It's very linear. And exposure was such an important one where I thought, like, okay, so you're not in the driver's seat, but you're in the car. And you hear what's happening and you're evaluating how this is, like, what the impact is.

[30:44] And this goes back to being really present and analytical and being a learner, because if you can be a learner, not just in an education or experience context, but in an exposure context, you can really grow so much more quickly and in so many more directions than you will get from just, you know, what does your day entail from what work is directly required of you. [31:08] Is there an example of that [31:11] happening either to you or you saw a manager leader do this and you're like, oh, I get it now. [31:15] or you doing that and it helped. [31:18] So I'll give two examples. One is like the way I run my meetings are the kind of meetings I want to be a part of. So I try to make sure that I start with a clear agenda and I move quickly, but give time for conversation. And it's not fully just sharing information, but debating where appropriate. I think knowing how to [31:44] like manage the conversation and [31:48] courteously pausing people who are going on too long or like taking the group in a different direction than was intended. And just think about the experience of everyone there and create the experience that you hope that they're creating in the rooms that you're not a part of. An example that I have in terms of experience is like sometimes the experience is you doing the thing

[32:18] you need an education, you need a mentor, you need a coach, who will tell you what they're saying or give you advice. I was in a really high stakes product review at Intuit, and at the end of it, [32:32] Everyone else had left and the leader of the business unit, as she was leaving the room, said, "Always ask. [32:41] or always answer the question that they should have asked. And always answer the question they should have asked. And I [32:50] was [32:51] pretty surprised by that advice because it was very profound in the moment. Because I think when you're a student and you are accustomed, if you're an achiever, you would like to get A's, you're probably going to hear a question and answer it. You're like one-to-one, one-to-one, one-to-one. But what I learned from that was that there's actually another altitude, another point of strategy when you're in a meeting or in a conversation to make sure that you're covering [33:21] point, the bigger picture, the alternative that the person asking the question maybe didn't see or consider. And so I think the mix of experience, exposure and education really helps you make sure that [33:37] consciously [33:39] moving forward on each of those fronts or finding people who can help you there. [33:43] I love that piece of advice, and it makes me want to ask, [33:46] Are there other pieces of advice that have been really impactful to you?

[33:50] Or are there common pieces of advice you give to your team that just like is a recurring [33:55] theme of advice that maybe people even make fun of like, "Ah, Paige is always saying this." [33:58] There are a few ways to think about advice, and my... [34:03] advice often meets a mark when it's for a particular person at a particular time in their career. And so I would say advice I love giving to people who are early in their career is don't self-select, because I think it's really easy to say, "I don't have the experience," or "I'm not XYZ enough," and not apply. And so I really push people not to self-select, and I try to remind myself where [34:33] Think big, ship small. Think big, ship small. Like what's the smallest thing you can do to do that thing? But let's not, [34:41] because we're trying to shift [34:43] all the time and in small chunks, start thinking in small ways, because it's really easy to get a little too incremental, a little too wrapped around the axle around optimizing a metric and miss the bigger picture. And so think big, ship small, is another piece of product advice I give. And the last piece of advice that I would say [35:05] that [35:06] I... [35:07] I like is more of a way of thinking. So this is a little abstract, but when employees join Asana, they get a book called The 15 Commitments of a Conscious Leader. It's led by the Conscious Leadership Group. They also get two day training on some language and tools for how to

[35:27] effectively work with other people. And it's a really, like for me at least, it was transformational because I learned some vocabulary and methods that I could share with my peers. And one of the things that you learn [35:45] is to be above or below the line. And something that is this concept of where are you? Are you above the line? Are you below the line? If you're above the line, you're committed to learning. You're open and curious. Things are funny here, more playful. If you're below the line, you're committed to winning. You're committed to being right. Things are more black and white. And all of us have days where we're having a conversation and we're really like in that [36:15] space where it's like, no, it just is this way. There's no two ways around it. And that concept of understanding your personal headspace and then being mindful of how you're operating when you're in that place really was great advice for me. And also recognizing where other people were when it related to decisions we were making or context. [36:38] It also... [36:40] helped me think about rejecting false trade-offs and challenging, like, effectively, there's this notion of how might the opposite be true. And that's [36:52] That's a piece of advice that I give myself like this morning. I think it was yesterday. Actually, I was like, how am I going to do tomorrow? Like tomorrow? I have to deliver the clarity pillar brief to the area leads and make sure they understand our stack ranked metrics. And they need to know exactly what our strategic priorities are and why. And they need nudges and they need to be able to translate our voice of business and usability lists into those plans. And I need to establish a perspective and make sure this is all written.

[37:22] down and they really understand it and I have a great conversation with them where I get open questions and they feel like they can really challenge my thinking. I also am having a podcast with Lenny in the afternoon and [37:37] At first, it was like, "This is just too much. I should try to move or cancel one of these." And then I asked myself, "How might the opposite be true?" [37:47] And, you know, [37:48] I was like, "I can do both." It was just enough to pop the balloon because sometimes your brain is so accustomed to having a scarcity mindset as opposed to creating alternative options or seeing a different path. And the moment I challenged myself and said, "How might the opposite be true?" My shoulders dropped. I felt more relaxed. I was like, "Oh, my God." [38:13] Oh, yeah, I can do both. It'll be fine. Well, have a great conversation. I'm, you know, ready to show up and be curious and, like, really engage with you on... [38:25] the topics that you've [38:27] Sound. [38:28] interesting and we'll just do that. And so how might the opposite be true has been a really helpful piece of advice or line of questioning that I use of myself to make sure that I'm not taking myself away. Wow, what a fruitful question that ended up being. [38:46] That was amazing. [38:47] How'd this clarity pillars strategy go? Are people into it? Is it working? [38:52] Yeah, I'm pumped. It's a really interesting time to be a product leader,

[38:59] especially with all of the tech transform, like truly the technological transformation on LLMs. It's astonishing. The pace of development, the ability of our teams to just ship quickly and ship really intelligent things. Like we're not [39:17] in an operational figure it out land. We're not in a place where we're trying to decide how to do a better job and get it out to customers. We really have [39:27] lots of interesting paths forward and are trying to make sure that we're on the cutting edge while really looking at like, what does it mean to serve the companies and organizations that we want to serve with new ways of serving them? And so it was a really fun conversation. And I also had to be honest with people and say, this is a 70 percent cut. 30 percent of this is missing or incorrect. And that's why I'm coming to you early. [39:57] And it's the start of our journey. [40:01] our 12-month rolling planning conversation. [40:05] Let me pull on this AI thread because it's clearly top of mind for a lot of people. Yeah. How do you think about it? [40:11] splitting up investment in AI exploration within [40:15] the product team are you like hey team everyone should be thinking about ai as part of their product or is it [40:20] Here's a team where they're going to think about AI and LM integrations and everyone else keep doing what you're doing. We've had an ML team for quite some time, making sure that we have like test prioritization models and notification prioritization models and are making...

[40:36] our product less work for people to use. But when it came to the massive leap forward in LLMs recently, we staffed a team to really prototype quickly and discover what was possible and just apply hypotheses outside of the typical norms of how we work. So they kind of went straight to prototyping instead of going through that double diamond I was explaining earlier. What that meant [41:06] "Wow, this is just so much better than we imagined," and we'd never have prioritized it because we thought it would take so much longer. And then in other cases, [41:14] That sounded good in theory. And so skipping a lot of that to just really try it on for a size has been key. And then what we're doing is giving the teams with the most expertise in the customer problems, for example, status and progress reporting, [41:31] the keys to that car and saying, "Here's the starter, here's the hypothesis, here's how far we got with it. It's dogfooding. What do you want to do?" And so we're able to nudge people without wasting time and build the skills locally within the teams that then move those experiences forward. [41:50] I want to come back to the coaching topic. I had a few questions there that I moved off of, but I feel like that's a rich area of exploration. [41:58] You mentioned Intuit. You worked at Intuit. [42:01] Intuit is kind of famous for having a really good APM program. [42:05] and really good training for product managers. What did you take away from that?

[42:09] experience that you bring with you to coaching or even I think there's an APM program at Asana too. [42:14] into it and [42:16] excellent training programs, the APM program and their manager training. So on the PM front, the biggest thing that they taught was around customer centricity. And it really started with the founding of the company. For anyone who works into it or has worked into it, they know that there's the story about Scott Cook watching his wife balancing her checkbook at the kitchen table [42:46] typical for the product training at Intuit to be all about like [42:51] How do you spend, like, how do you actually watch customers using your product or just doing the things they do? Collecting the artifacts, knowing the workarounds and using that. [43:03] experience to build [43:05] opportunities for surprise and insight that then you can capitalize and create products around. They also are very specific about how they define durable advantage and think about [43:18] overall the product process from a [43:22] place of customer insight through to like the market landscape. So the PM program there was absolutely super thoughtful, especially for taking someone who has never PMed into being a super skilled PM. They also have a wonderful manager training program. And I think the biggest thing that I took away from their manager training was really on the feedback side. So delivering feedback

[43:52] more critical because if you don't do it and you don't say what you mean and you don't do it in a way that it can be internalized and acted upon, you really don't set up your teammates, your teams for growth or success in their careers. And so their program for helping you think about like, okay, I'm going to convey this feedback as situation, behavior, impact. Like the situation is like on Tuesday in that meeting at three o'clock, [44:22] you [44:23] You interrupted me while I was saying this thing, impact. [44:27] "Made me feel like you weren't listening to me," or "Made me feel like your voice was more important than mine," or "Impact blah blah blah blah." It doesn't matter what the impact is because the way you've set it up is it's [44:41] a subjective observation. It's not what the camera recorded, it's what you experienced, and therefore it is true and valuable feedback. And it gets the conversation started such that you can then talk about next steps. And that format and framing really helped me understand that [44:58] Delivering feedback isn't about being right or about getting the right information to the other person. It's about [45:05] sharing the impact of different decisions that they're making. [45:10] Especially if you have to give feedback about [45:12] God forbid, what someone wears to the office, or, you know, how detailed their work is, or how they're communicating, or their body language. Having enough support where you can be really clear about what you're intending and the spirit behind that, but that it's formalized enough that people can really engage with it, has been enormously helpful, and I still use it today.

[45:36] It's interesting how some of the most impactful [45:38] Training is like such soft skills. So basic. And basic, yeah. It's just like how to give someone some feedback. But it's like... [45:46] Not like how to prioritize, how to do a meeting, how to do a presentation. It's like, here's how you get feedback to someone. Yep. [45:53] So you've worked with a lot of [45:54] early product managers. [45:57] I'm curious what you find most holds back [46:00] new PMs in being successful in their career. And even on the flip side, what most helps [46:05] New PMs. [46:07] be successful in terms of skills or behaviors, habits, things like that. [46:11] I would say this illusion that you have to be all-knowing and super confident. [46:17] sets you up to be in a place of advocacy [46:21] instead of inquiry. And so PMs, [46:25] who are newer in their careers or who are like in a different space than they're accustomed to working really want to be pro really fast and what pro means is trying to cut that straight path and that can reduce [46:40] information and conversation that makes you smarter. And so some of the challenges that some PMs face are feeling like they need to be the expert, they need to be the smartest person in the room, or God forbid, they think they're the smartest person in the room. And then what happens is they're really doing that customer or product discovery or a spec in a little dark room. And then they show up and they say, this is it, this is right. And I know what's right. And let's do this.

[47:10] as quickly as possible. And everyone else says, "Wait, what? Like, I don't know. Like, I have a question." Or they don't, and they still have a question, which is even worse. So I would say something that really holds PMs back is not being, [47:24] collaborative from a place of like true curiosity like [47:29] performative collaboration where they like nod in a room or want to do a review but ultimately they don't really want [47:37] the questions or the feedback. And I think [47:41] Trying to make sure that you can be in a place of curiosity and openness, because that will make your experience more successful, is really important. Other people aren't always going to be right, but if you're present for it, you can ask clarifying questions. You can ask the question behind the question. You can hear the feedback and then say, oh. [48:01] Was that something that I must do, that I should do, or that I should consider? You can actually develop a conversation that will move your relationship forward. And so I would say that's something that I think holds PMs back. PMs tend to be so ambitious and career centric and [48:23] There are so many good things about that. But I would say, like, don't let the sound of your wheels drive you crazy. If you're present in your job and you actually have fun with it and solve the problems, people will come out of the woodwork, say you're great and tell your boss you should be promoted. You don't need to ask for a promotion. Your outcomes should speak for themselves.

[48:53] into your team. [48:55] Everyone I talked to about you was like, "Oh my God, I love Paige." And I could see why. [49:00] But I want to ask you a question. [49:02] I imagine you've made some mistakes either with your product [49:05] or your career [49:07] I'd love to hear a story of something that went wrong and what you learned from that experience. And this might be the last question, depending on where you take it. [49:15] I would say that [49:16] All of the advice I've given so far is directly related to things I've learned the hard way. So, like, especially as an IC, moving into a management role, [49:27] you aren't supposed to have all the answers. You need to ask better questions. You need to be thoughtful about like direction and agency. And so I would say one of the, the, [49:38] missteps here is [49:40] like knowing how to give guidance or direction in a way that doesn't feel like micromanagement, because what you're trying to do is to teach a repeatable pattern instead of giving a precise instruction that can be used once and then disposed of. So I think that's a pretty common manager path issue, but I think the faster you learn it and observe it and use techniques to [50:10] with a stack of post-its and I would write what I wish I was saying on post-its and see if someone else would say it first. And then if by the end of the meeting I had decided that [50:20] I still had a post-it or two that was worthwhile. I would say them.

[50:24] But [50:24] You've got to police yourself because no one else will do it because... [50:28] no matter how [50:30] accessible you think you are, [50:33] other people know that you're the boss. They're not going to necessarily [50:39] speak over you or challenge you directly. [50:42] Another challenge I had is I'm a very optimistic person and I like to look on the bright side, I'm very positive, [50:51] And I think depending on the culture you're working with, or depending on your team, sometimes they need to hear what's really bad. [50:59] and they need you to be really real, and they need you to tell them like it is. And something I realized [51:06] was that I had an experience where [51:08] I didn't realize that people didn't think I was being authentic because they thought something was bad and I wasn't talking about it. But it wasn't because I didn't think it was bad or didn't see it. It was just because my nature was to say, [51:21] Well, I'm not going to talk about bad things because we're doing the things we need to do. Like as long as the plan is good, it wasn't really highlighting all the problems I saw or like really pushing on those head on with my team. And so they felt like. [51:37] they didn't know what I was saying or if we were saying the same things. That was really [51:42] an interesting experience. [51:44] Yeah, there are just so many. [51:48] Yeah. [51:49] With that second lesson, is there [51:51] something you've changed in the way you lead and operate, where you now found a way to communicate, here's what's wrong, in a way that's still maybe optimistic and

[51:59] productive [52:00] I try to be more real. [52:02] with myself and others. [52:04] I try to show up and say, like, [52:05] Hey. [52:07] This is incomplete. Like, for example, even the thing I did this morning, the clarity brief, I said, this is 70 percent finish. The 30 percent that I don't believe is there yet are these three things. I don't feel confident in this piece of it. And hopefully we'll have more clarity by next week. So that's an example of just being as real with the small things as with the big things, [52:37] and the environment you're creating. [52:40] I'm curious. [52:41] how you think about your career going forward. [52:44] How far out do you think? [52:45] where you want to be [52:47] and how do you plan out the future of Paige's career? [52:50] I try to be really intentional about [52:54] staying as much as leaving a role. [52:57] And when I think about my career as a whole, I try to think about skills or experiences I want to have as opposed to [53:05] roles or companies or specific problems. So something that I think about is, [53:13] effectively, I evaluate whether I'm in a healthy role and in a good setup by asking myself, [53:21] about my learning curve? Is the steepness of my learning curve... [53:27] doing me [53:28] favor here because sometimes you might love the organization, love the problem, and feel like you're just not learning or learning fast enough or being challenged and that's something that

[53:41] I think is really important. So like thinking about the learning curve [53:46] Thinking about whether the environment [53:48] is positively impacting your ability to grow your career and make an impact. And so environmentally, you might have like not enough staffing or tooling or [54:00] have someone in the management team who is toxic, or have a peer who is blah blah blah blah blah. That stuff matters. And I think people don't talk about it or take it seriously enough that your environment is [54:12] should include people who are advocating for you, and it should just be a place where you feel you've got the right [54:20] Ingredients. [54:21] to set you up to do the good work. [54:24] And then the third piece is really around [54:27] just the problem, the problem your product is solving. Is it fun? Is it interesting? I often like to think about passions are made, not found, because I think people, [54:39] We do this with nine-year-olds. We say, what do you want to be when you grow up? They look cross-eyed and they say, an astronaut. Just getting a vet. I don't know. And there's this moment of panic. And I would say that. [54:54] that being comfortable saying like, [54:58] Go try different things and see if the problem is interesting to you. And if the problem is fun or interesting to you, it doesn't mean it has to be sexy. It doesn't mean the company needs to have a brand name. It just has to be something that you're curious about so that you do a better job at your job.

[55:28] as opposed to roles. So I would say that that's more my frame of reference, because otherwise I think I'm living in the future and not enough trying to [55:39] make the most out of the career I'm living right now. [55:44] Well, with that, we've reached our very exciting lightning round. [55:47] I've got six questions for you. Are you ready? [55:49] Yeah, let's do it. What are two or three books that you've recommended most to other people? [55:54] My go-to book recommendation for other PMs is inspired by Marty Kagan. I think it's a classic. [56:01] The other books that I have enjoyed and recommended lately are The Blind Assassin by Margaret Atwood and The Alchemist by Paula Coelho. [56:11] What is a favorite recent movie or TV show? [56:13] Ooh, I'm very much enjoying the diplomat right now. [56:18] And then TV show or movie. Let's see. [56:23] I just watched the Fire of Love documentary, which is about a couple who study volcanoes, and that was a great change of pace. I saw the trailer for that. I think I got to watch that. And I finished The Diplomat. It's awesome. It ends really well. Don't spoil it. But it's just good. I'm just saying it's good. That's not going to spoil it. Okay. [56:42] Okay. [56:44] Okay, next question. What's a favorite interview question that you like to ask candidates? [56:49] The good news is I can tell you this and still keep asking it. Because the answers always come up differently. So I like to ask, tell me about a time something went wrong.

[57:00] What was it? What did you do about it? Yada, yada. And effectively, the question gets set. [57:06] when the product failed, when something about the team didn't work, just... [57:12] things that [57:13] go wrong because that's what happens when you're doing this work. And evaluating people's mindset and the way they talk about it and the way they relate to evaluating the situation, I think it's a great question. It really tells you a lot about how people think and how they perceive themselves when things are [57:32] not working well. [57:34] What is a favorite product that you've recently discovered that you love? [57:37] I've been playing a lot with Poe.com lately. [57:41] Yeah, just an opportunity to... [57:44] learn more about [57:46] LLM capabilities in a firsthand way. It's been fun to create little bots. I'm playing with making a page bot. I can't say that the page bot could have had this conversation yet, but maybe next year at this time, you can have a conversation with the other me. That's what the page bot would say if this was the page bot talking right now. I would say, though, but... [58:12] The advice bits and bobs I gave you earlier are... [58:16] are absolutely things that I've been thinking about feeding. But I think the page bot would probably say ship it. [58:24] and Poe, it's the Korra [58:28] founders LLM chatbot. Yeah, and so you can try the different models. So you can do four and replay five and Claude and a few others. Yeah.

[58:38] There's also a LennyBot.com for folks that haven't seen this. [58:42] Somebody built, actually there's a whole post on my newsletter. [58:44] of how it was built, [58:46] And you go to LennyBot.com and it [58:48] is [58:49] trained on all of my newsletter posts, [58:51] And I think not yet podcasts, but someday it'll have podcasts. By the way, if someone's listening to this, we're looking for someone to maintain this bot and evolve it. So if you're really into the stuff and... [59:02] have done this sort of thing, please [59:03] DM me on Twitter. [59:05] And I'm looking for someone to take over LennyBot.com and make it more awesome. [59:08] Moving on, enough about me. [59:10] Next question. [59:11] What is something relatively minor you've changed in your product development process? [59:15] that has had a big impact on your team's ability to execute. One of the biggest ones is just being, once again, being real about how many reviews and approvals it takes for something to get done and who's actually responsible for reviewing and approving work. So we got really aggressive about [59:33] functionally who is in charge and at what level for a given review and pushed to say, like to actually have limits on the number of people per meeting on the the number of subtask reviews for a given body of work. And what this did is it created a lot more agency and and pace within given working teams. And so what we did was we said, we actually don't care. We don't want a [1:00:03] We just want one person with whom the buck can stop with them and they can be responsible for how the work moves forward such that the knowledge is known and we could have connected dots more effectively than we do or did. So that's kind of the logic there and it's really changed the pace and quality of our work.

[1:00:25] - I love that. Is there any more you could share on the number? Like what is the maximum? Is there anything that other people maybe can take? - Yeah, so no more than three reviews on a given piece of work where people are blocking one approver. [1:00:37] and [1:00:40] if a meeting has [1:00:42] more than 10 people on it, we asked the person hosting the meeting to kick out the other people and write better decision notes. [1:00:49] And the three reviews is three meetings looking at the [1:00:52] product as it's coming together, basically. The three reviews are three people who are assigned a task to look at something, but only one person is blocking whether it moves to the next stage. Got it. Informed people, stakeholders, decision makers. Okay, great. Final question. [1:01:09] You work at Asana. What is your favorite Asana pro tip? [1:01:11] I use Asana to run all my meetings and assign pre-reads. So I use the multi-assign feature in subtasks all the time where I make a task with a due date that says, read this thing by this date, and then I assign it to a team or a set of individuals like that really quickly. And then when I'm [1:01:33] in the meeting, I take notes live in a task and then highlight [1:01:38] parts of those notes and convert them into subtasks so that none of the action items get lost. Wow. You need to make a video or a blog post about this. Not only is it using a sonnet to build a sonnet, it's using a sonnet to run. [1:01:52] teams within Asana. Yeah. It definitely does that. Asana all the way down.

[1:01:58] People know who's responsible for what by what. Amazing. Paige, you are awesome. Thank you so much for doing this. Two final questions. Where can folks find you online if they want to reach out and learn more? And how can listeners be useful to you? [1:02:28] use Asana, I'd love to know where you'd like to see AI playing a bigger role to drive efficiency alignment for your team. So as you know, we offer a ton of goal management, work management pieces that help teams and orgs do their work together, and I'd love to hear from you about where you see the opportunity. [1:02:49] Awesome. Paige, again, thank you so much for being here. [1:02:53] My pleasure. [1:02:54] Thanks for having me. Bye, everyone. 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.