Video: Choose Your Player: The 3 Product Leader Archetypes | Duration: 3644s | Summary: Choose Your Player: The 3 Product Leader Archetypes | Chapters: Welcome and Introduction (80.99s), Introducing Product Archetypes (229.905s), Manager Communication Styles (566.875s), Executive Communication Strategies (1028.62s), Storytelling and Leadership (1568.46s), Applying Product Taste (2135.5752s), Developing Design Taste (2597.395s), Q&A Session Begins (2933.52s), Archetype Questionnaire Resource (3054.76s), Identifying Executive Archetypes (3161.25s), Handling Unnatural Archetypes (3404.67s), Farewell and Thanks (3589.035s)
Transcript for "Choose Your Player: The 3 Product Leader Archetypes": Hey. Hey. Hey. Welcome, everyone. We are so glad to have you here today. My name is Rocky Moon. I'm with Grammarly, and I have Shreyas and Rahul here with me who we're gonna be talking about three product leader archetypes today. But before we get started, I wanna give a quick overview of, like, what you're seeing here. Over on your screen, you'll see the chat. Please drop in that chat right now where you're calling in from. One, it'll make sure we know you know where the chat is. And two, I like to know everything. Yeah. Here we go. NYC. I love it. My brother's in Queens. Going up there this fall too for an off-site. Yeah. Miami got some friends down there too as well. Thank you. So this is the chat on the right. You'll also see a section that says docs. If you click on that doc section, you'll have our check-in doc. And you can go there, check-in for our webinar here, and also ask questions. You'll also notice another section that says q and a. Feel free to drop questions there, but we'll probably move it to that check-in doc, where we have our Dory, if you know, you know. And we are gonna be asking questions from there, at the end of the webinar. So after Shreyas and Rahul will have an opportunity to, go through everything. And, yeah. I think that's it. Again, today, we're gonna be talking about the three product leader archetypes. And our two guests who you wanna hear from, not me, I'm gonna get off the screen just as fast as possible, are Shreyas, who is a seasoned product leader who helps shape some of the most widely used products at Stripe, Twitter, Google, and Yahoo. Y'all know Shreyas. As Stripe's first PM manager, he played a pivotal role in defining the product management function and scaling the team. Today, he advises startup founders, coaches, executives, and teaches popular live courses on product and leadership. Over 400,000 people follow his insights on product management, organizational psychology, and strategy across Twitter, LinkedIn, and YouTube. So, Shreyas, welcome. Glad to have you. And then Rahul is the founder and CEO of Superhuman. Welcome to the team, by the way. We are excited to have you here with Grammarly slash Coda slash Superhumano. And he's got a successful track record of investing over, in over a 100 startups including Placer, Mercury, ClassDojo. He has a strong background in early stage investments and product development, and he has an expertise in SaaS companies, and user experience design. So we are excited for their conversation. If it's anything like the run through I got to see yesterday, y'all are in for a real treat. So let me get off. Shreyas, I'm gonna pass it over to you, and, let's enjoy the show. Hello. Welcome, everyone. Welcome. Welcome. It's great to see you all, here. So, the way this is going to work, is, I'm actually going to start with a quick presentation. But we wanted to make, this session highly interactive. And so the presentation, it turns out I just have about, I wanna say two slides two slides and a poll. So, I'm just gonna start with the presentation, and then agenda wise, Rahul and I are going to, just have a conversation about the three archetypes of product leaders, and what it means in practice for us, for the way we do our work, for the way we make hiring decisions, for the way we make our own career decisions. And then we'll have some time towards the end, for, some q and a. And so feel free to post your questions in the q and a tab, and, we will have about ten, fifteen minutes, to tackle the questions that you all have. Alright. So first, I just wanted to introduce you all, to the three archetypes of product leaders. And, I just wanna quickly say that, you know, what you're about to see on this one slide took me more than ten years of being a product leader myself to truly understand. And then once I started, like, a lot of things were not making sense to me, during those, you know, during that decade. And once I understood these three architects of product leaders, a lot more things started making sense to me around why certain things happen, why certain leaders are capable of certain things but not other things, and why there is even friction between leaders, as they're building products and growing businesses. So, the three archetypes. The first archetype, or you can call it hat, by the way. It doesn't have to be an archetype. We can call it a hat that you can put on and take off. Right? So the first archetype or hat is the operator. Okay? And the operator superpower is orchestrating actions, complex actions, primarily via how they communicate up, sideways, and, you know, all over the organization. Alright? So the operators are excellent excellent at scaling teams, and they are just magicians when it comes to aligning teams and aligning orgs, so that they can unblock execution for the organization. Now those are some superpowers and some strengths. Operators, as you see here, are not really excellent at original product insight. Okay? The best operators I know, they can extract great product insights from others on their team, but they're not excellent themselves at original product insights. Alright? So, that's a view of this archetype. And, you know, one of the other things I like to kinda point out is where each of these archetypes, likes to spend their time. So operators, I found, love to spend time with peers. So people at the same level, but kinda cross functionally at the same level as them, as well as, with executives and the board. Like, they just look forward to that. Alright? So the next archetype is the craps person. Alright? This is the craps person. The craps person's superpower is product insight. Alright? So what is you know, perhaps a a weakness for the operator is actually a superpower for the craps person. And because craps people are so good at just that kind of product insight, they love and they're great at defining the product and defining the strategy. And I found many crafts people and by the way, you don't even have to manage people to be one of these architects or hacks. Right? Like, what I found is that crafts people just love spending time with other PMs and other product people in general. So whether they're designers, engineers, data scientists who are interested in product, they just love spending time with them, and they love kinda coaching them. Alright? Now the crafts person is not very good at, dealing with, large orgs. Okay? So this is where a craps person kinda runs into their, like, limitations, where they just don't enjoy it. Craps people love spending time with the direct team that's building the product, as well as with customers, users, and stakeholders. Okay? And then, you know, perhaps people, early on get promoted, because they make a singular product impact. Okay? Because they make a singular product impact, they're just so good at this product thing, that that's kinda how they get promoted or noticed. Alright? Third and last archetype is the visionary. It's the visionary. Now a visionary and this is the rarest archetype, by the way. A visionary is, basically great at, big picture thinking and, by definition, sort of seeing what others cannot see. Alright? They're they're great at seeing what others cannot even see. The challenge that visionaries face is that they are not really great at, resolving people, and interpersonal dynamics. And they just don't enjoy, like, you know, doing some of the operational work that is required to scale. Alright? Visionaries love spending time with other visionaries. They love spending time with users, customers. They love spending time with the press. So that's when that's that brings out the best, out of these visionaries because they get a chance to talk about, what it is, that they're excited about. They get a chance to talk about this kinda grand vision they have. Alright. So those are the three, core, archetypes. And, again, if you wish, you can call them, call it a hack instead of an archetype. Now at this point, I have a poll for you. Okay? So, it's it's it's relatively straightforward. All I ask is that, like, be honest. Okay? So, there'll be a poll question, coming up on screen. So just go ahead and respond to the poll. So one of the questions is which one of these three do you think do you think is your manager's most preferred hat? So, again, understand we are asking about the most preferred hat. Okay? I will say later that, like, you know, we can wear multiple hats. But what is your manager? What do you think is your manager's most preferred hat? So go ahead and respond to the poll question here with your manager's most preferred hat. Alright. And then next next question is which one of these three is your most preferred hat? Okay. Which one of these three is your most preferred hat? Alright. So go ahead and respond to that as well. And try to remember your responses too as to, you know, what you said for your manager, or your best guess for your manager's most most preferred hat, as well as what you said for your most preferred hat. Alright. Great. So, now, I want you to type in the chat. I want you to type in the chat if you chose a different hat for yourself and for your manager. So just put me, m e, in the in the chat if you said, that your hat, your preferred hat, is different from your manager's preferred hat. Alright. So I'm seeing quite a few responses here. Katie, Priya, Krishna, Pritesh, Octavio. Who else? Rahul, another Rahul. Braden, Ashish, Josh. Great. Great. Okay. So quite a few of you are noticing, that, you know, maybe your preferred hat and your manager's preferred hat is different. And this is actually not, uncommon. In some of my coaching and advising, I find this to be one of the core, observations that just gonna, makes things make more sense, when you understand that your preferred hat and your manager's preferred hat, are different. Alright? So what do we do with this information? For those of you who did say that your preferred ad versus your manager's preferred ad is different, I wanted to leave you with, this observation. Okay? I wanted to leave you with this observation around particularly communicating. Okay? And now this is not just communicating to your manager. This can be even communicating to your CEO or your SVP of product or whoever it is that, is in the approval chain for things you wanna get done with the organization. Alright? So what I want to share with you on this slide is a way of thinking about how you can be much more effective at influencing your manager and or influencing your executive by better understanding what their preferred hat might be. Okay? So here it goes. So we'll start with the operator. So let's assume the CEO or the SVP product that you're presenting, you think they have that preferred hat is operator. Okay? Now I love operators. And if I were running a traditional start up and as it started scaling, I would be the first one to hire an operator, to lead various operational aspects of, my company. Right? So I love operators. However, however, one challenge with operators is that many of them do not have taste. Okay? Many of them do not have taste. So when somebody is an operator and they get presented with a proposal, so you wrote down some docs or you created some presentation, so you you you're presenting this proposal, The operator does not have, usually, the skill set or the confidence to judge your proposal solely on the merits of its content. I'll repeat, the operator does not have, usually, either of the confidence or the ability or both to judge your proposal solely on the basis of its content. Okay? So what does an operator do? Remember, operators are incredibly effective, the good ones, obviously. So what does an operator do in in this situation? The operator is looking for proxies. Okay? And the particular proxies that an operator will gravitate towards are going to be metrics and industry data and stakeholder validation. Alright? So please put me in the Zoom chat. If you've ever been in the chat, If you've ever been if you've ever been in a situation where you presented to an executive, and the executive, in response to the presentation, goes around the room and asks different people, their own team, what they think about the proposal. Okay? They just kinda pull various people what they think about the proposal upfront. Alright? So that is very likely an operator situation. The operator first wants to understand what others on the team think about the proposals before offering their own opinion. Alright? These are some other things the operator cares about. Near term goals, they care a lot about that, and they are excellent at identifying the right milestones and resolving dependencies. So the here's the tip. When you are presenting to an operator, make sure that you first share these things, that these items are very obvious to the operator. Because otherwise, you're gonna lose the operator, and you're not gonna be able to influence them the way you wanna influence them. Alright? So that's the operator. Now let's what if you're presenting to a craps person? Right? Well, craps people, the main thing they care about in any proposal is what are the qualitative and quantitative insights that are informing this proposal. Because a craps person without understanding what these insights are is not going to be satisfied. They're not gonna be able to assess whether you have a valid proposal or you have a an invalid proposal. Okay? Craftspeople are also excellent at product strategy. So they also wanna understand, you know, what is the strategy that is driving this prioritization. Alright? Craftspeople care deeply about getting things done. They look for more medium term goals. Alright? And they also, like operators, care a lot about milestones and dependencies. Alright? Now let's say you're presenting to a visionary. And by the way, if you work at a start up, you know, fast growing start up, you know, or if the executive you work with, has been a, say, serial entrepreneur, most likely most likely, you might be dealing with a visionary. Alright? Now visionaries, they first wanna understand what is the big idea here. What is the grand idea here? So either you tell them the idea or you give them enough bread crumbs so they can figure out what the big idea is here. Alright? Visionaries are also excellent at strategy. So they also want to understand the overall strategy. Right? Visionaries care a lot more about longer term goals. So make sure you can still have short term goals, but make sure that you appear on the longer term goals. And visionaries also care about how does this product fit into the entire story, so in in our product suite. Alright? So now here's the key thing. First, lead with these items depending on which archetype you're talking to, and then cover everything else you need to cover. Okay? So this is a very adaptive approach where you understand what this person is likely going to want, what they are seeking, what they're impatient for. Alright? So first, leave with that. And so make sure the stop part is very easy for them to find or to understand before you cover everything else you cover. Now the reason the reason this is remarkably effective in practice is that most of us are usually just not thinking about this at all. We just write a proposal, create slides based on whatever we think it makes sense or based on some template or something else. Right? So when you change that default to being intentional about what it is that you wanna say upfront, what is it that you wanna make sure resonates with the executive upfront, you will be much more effective. Okay? So so I'm done. I'm done with my, presentation and my slides. And so now, we are just, Rahul and I are going to, just have a conversation, on, these archetypes. And, Rahul, welcome. I'm super interested in hearing your thoughts, on these archetypes and mapping it to your experience. I guess I first wanted to just start by asking you, the very same poll question that everybody else answered, which is, which of these archetypes do you feel is your primary archetype? What a great question. And I think my my real answer is what I saw a lot of people in the chat saying, which is I see a piece of myself in all of these. And over the course of my career, of course, I've had to be all of these, but it's definitely the case that I'm better at some of them than the other. And so as as folks who know me or know my work may have guessed, I put in craftsperson as, my answer for what do I most, relate to. But I've also, of course, as a serial startup founder, do a lot of visionary thinking and work as well. I consider myself pretty mediocre as an operator. But one of the things I found interesting about your definition, as I I look over the slides again, is is how important communication is for, an operator, and they're communicating within the org up, down, left, right with their peers, with the executives, with the board, like you said. I think that communication is, and especially storytelling, is such a key part of building a startup or building a successful product inside a large organization. I think about Superhuman, so much of what we've been able to do has been the story we've been able to tell. I mean, thinking about what we did, which was coming into a market largely dominated by incumbents where the existing products are free, and then saying, hey. We're going to segment this market, and we're going to charge a relatively high premium for building and delivering the best products in that market. That's just as much a result of storytelling as it is building the right product. And so I I think that that kind of storytelling communication skill set runs across the the whole spectrum. As I think about craftsperson, again, this is what I think I'm probably best known for doing. It's often the most fun. I really, really enjoy the the art of design, and and I mean that in the in the most general sense. It could be designing a piece of copy, a a video, a a user interface, a brand visual, or or even things that you might not traditionally think of as design. And it is actually still where I spend most of my time maintaining and pushing the bar for craft. I can spot a single pixel out of place or a dropped frame from a mile away, and it's actually really fun for me to do so. I'm also constantly pushing the team to develop their aesthetic sense and build delightful, remarkable quality products. And I think especially for our space, it's actually really, really important that we do this well. And I think this has been alongside storytelling, a huge part of the success that we've been able to have. One of our values at Superhuman is remarkable quality, and we literally mean the word remarkable. We mean quality that is so good that it is going to cause you to remark upon it because it's that striking, it's that worthy of attention. That then becomes the basis for virality. And no matter how great the sales or the go to market team is, at the end of the day, every new consumer Internet or, really, every new Internet product needs to have a very strong viral loop behind it. And as a result, that's sort of created things that have, we think, changed the state of the art for the industry. So one of the things in Superhuman folks on the call who use it would know is, we have command k. Hit command k. Just type in what you want to do, and not only will it do it immediately for you, it will also show you the shortcut so you can do it even faster next time. And that's actually something that those of us who are power users of productivity and collaboration tools now take for granted. And Superhuman wasn't the first company to build that, of course. We actually were inspired by, code editors, IDEs, where they would call this feature the command palette, but we were the first to really popularize it and to polish it up and to make it something that we think every professional should know how to use. And that's the example, I think, of crafts people, crafts thinking at work. The product insights that this thing over here exists, it could be made so much better. Let's popularize it, and now that has changed the way that the whole industry operates. As I think of other companies, Apple, I think, does this better than anybody else. You think of face ID, you think of touch ID. Well, they weren't the first company to invent or even bring to market those technologies, but they did them so well that we now call them face ID and touch ID. So I really resonate with the idea of being a craftsperson. But, of course, I'm also a Stereol startup founder, and so much of what I do is visionary. Like you mentioned, I love spending time with customers. I especially love spending time with the press. I'm always signing myself up to do, talks and and to to speak with the larger community, not just because it's valuable to get our story out there, but because it serves as a forcing function to get one's thoughts in order and to really refine that narrative. Now you can have a narrative internally. You can have a document. You can have presentations. But there's one level when you're delivering this internally, and there's a whole other level when you have to talk, for example, to the Wall Street Journal or or in front of 10,000 people. Right? The quality of that story needs to be really, really high. And for me, that's really fun, is trying to hit and exceed that bar. I relate to, staying away from people issues when it comes to being a visionary. I've built an organization where the vast majority of people problems are solved by other people, frankly, way, way better than, I would be able to solve them. But the reason I chose craftsperson over visionary is I think I just spend more time doing the craft than doing the vision part of the work. I'm very happy and very in flow doing big picture thinking about what's next, not just now, but next year and the year after and in the next ten years. But I find I only get the luxury of future thinking doing rare moments, like, you know, it could be the the Christmas vacation or plane flights or the rare spare hour here or there, that occasionally pops up. So to answer your question, very much craftsperson, quite a bit of visionary, and a little bit of an operator early in so far as I think I've pushed myself and the organization to make communication and storytelling a core part of what we do. Oh, boy. I have so many threads I wanna, follow from what you said, Rahul. First, I wanted to ask, again, folks, if you can put in the chat, just type me. If you feel like, you wanna learn more or hear about, storytelling. It's maybe it's something that, you've been given feedback on, or maybe it's something you've, sort of seen, needs work, for yourself so you can be more effective. Alright. I'm seeing quite a few mes here, and so I'm taking it as a sign, that, perhaps we should pursue the storytelling thread. And perhaps, you know, what I can share on this topic of storytelling is what I've noticed is that, particularly the craftsperson visionary, archetype, like that kinda hybrid, tends to be excellent at storytelling. And I'll I'll perhaps share, like, my hypothesis. This is not an extremely confident hypothesis, but, I'll share my hypothesis. And I'm curious, Rahul, what your thoughts are on this topic. But my hypothesis is, you know, I even tell people that, like, if you are great at the product craft, then at some point, you will become great at storytelling. And the hypothesis I have is that the very underlying skills that you need to be great at the craft of product, which is, you know, understanding what does the user truly need, not what they say they want, but what does the user truly need? What is the unspoken, unmet, problem here? And then how do we address that problem creatively in a way that creates differentiation for our product? So if we say that those are some core aspects of, you know, the product craft, well, my observation is, these are the same things that you need to be a great storyteller too. Right? Because storytelling essentially is also about understanding, the mindset, of the audience and then, you know, telling a story that is a new resident. Right? So here, you're telling a story through words, pictures, etcetera, some messaging, whereas in the product case, you're telling the story through code. Right? Like but it's kinda similar in that sense or at least analogous. So that's my hypothesis, Rahul. You know, you are just like I mean, I've observed your work for a long time now, and, like, your storytelling skills are just, like, just extremely rare out of this world. So what what can you share, with, me and, our audience here on, storytelling? Well well, first of all, thank you. If I could blush, I would be blushing. Let's see. I really agree with you. I I think that storytelling is highly related to product craft. I would probably suggest that it is necessary but not sufficient. Imagine the hypothetical craftsperson who's not great at listening. Maybe they're orator, maybe they've got the art of rhetoric really dialed in that is captivating charismatic speaker. If at the end of the day, they they can't listen to what the user is saying and then translate that into what should be built, then even if they're incredible at telling stories, I think they're going to be limited in their effectiveness at as a product practitioner and and perhaps, you know, they they should be a a an orator or someone whose job it is to speak rather than to listen. But as product people, we have to do both, and we have to be really good at both. I often think about Paul Graham's phrase for y combinator that I suspect many of us will know, which is, as a founder, as an entrepreneur, your goal is to make something people want. And every time I heard that, I thought, again, that's necessary but not sufficient. This is actually a tale of two sides to the same coin. And if that's one side of the coin, make something people want. The other side is help people realize they want it. And so there is this art bringing an amazing product to market, which, again, I have this personal experience about just being really challenging. As I think of the email space, there are dozens of companies before us, quite literally that tried and failed, not necessarily because they had a worse product. Many of those products were actually quite good, but they didn't have a story that resonated with the overall market, and they they didn't have a a segmentation. Now they also didn't have the the right product strategy, and there's a whole bunch of other things that go into it. But storytelling is a key aspect of it. So I very much agree with storytelling being important. I think it's part and parcel of of what we have to do as, as founders and as entrepreneurs. The other thing I'll notice and, again, I'm I thank you enough. I am I'm thinking about this from the perspective of coming up as an entrepreneur and as a founder. Basically, everything that you do, and I wanna zoom all the way out from products for, to to hiring your first employees. In fact, even recruiting cofounders. I did Superhuman for a year as a single founder before I brought my two cofounders on, to selling your first customers, to raising money, and everything in but even actually when I had to buy the domain superhuman.com, all of these things required me to take my storytelling and to continually push it to the next level and the level beyond and so on. So I I simply think that trial by fire, becoming a founder and figuring out how to get through the milestones of, bringing on board cofounders, recruiting a team, building a prototype, selling it, bringing it to market, that whether or not you like it, whether or not you're prepared for it, that is going to make you a storyteller, which I think is very useful because to your point, it's also going to help you become better at building great products. Yeah. That that resonates strongly, and it sounds like, you know, one of those situations where the more you do of something and the more you realize that, like, you're not being as effective unless you can story tell in a certain way, and that requires practice, that requires experience. I wanted to switch gears, and, talk about hiring, and also getting hired. So you've worked with many product leaders over the years, and I know you've, you've been extraordinarily intentional about the leaders you hire. Just one fact for the audience. I don't think I've ever shared it or, but, the way Rahul and I met was in a hiring context, I believe, which was, Rahul was hiring for a role at Superhuman, and, at the time, I was kinda looking for what's next. And so I don't know how we got connected, but, somehow we got connected. We we ended up having, you know, I remember many, many conversations, on so I've seen up close, that you've been just extraordinarily intentional about the leaders you hire and what you are looking for in the leaders you hire. So my question, Rahul, is, like, if you were talking to another founder who's having a like, a senior product leader, what would you advise them about, you know, what type of product leader to look for and what makes mistakes to try and avoid? Well, here is the fundamental dialogue. We actually need, usually, to work with the opposite types. Otherwise, we won't get things done. But that itself massively increases the communication burden, and there is this art like you had in your table, what what the what the various types need to see. There is this art in effective communication and getting things done across the boundaries of these types. So, for example, if I identify as primarily craftsperson and then a bit visionary and really bad, frankly, at being an operator. Let's say I work with another craftsperson products leader, we're gonna have some amazing conversations. Right? We'll be seeing eye to eye on quality. We'll stay up all night tweaking pixels and crafting the product's messaging and and making beautiful videos and probably spend forever iterating and tweaking the the messaging and the emails that we send to our users and the blog posts and all of that. And, honestly, it'll be really fun. Together, we'll obsess over the tiniest details. But I have to ask myself the question, will this partnership be making up for my weaknesses? Probably not. Will we be running a well oiled organization and and shipping on time? Probably not. Now what that means is, it doesn't mean don't hire those people. Of course, you need to scale and we'll need people of all kinds. But over time, we have to build teams that have all three competencies. And as we reach that point, what we're probably going to have to do is partner with people who have the other type of competency. And what we need at any given time is going to change. It also depends on the stage of the company. So, for example, let's say your pre product market fit and your any one of those three archetypes, as your, depending on what your archetype is, you may actually not need to hire a product person. If if you are a craftsperson, for example, you may be able to lean on the operational skills of your engineering leader and bring something to market and get to post product market fit. Then as you're scaling the company, what you'll probably need is an operator to manage the two, three, four product managers that you have and to to help put in place processes and to make sort of things that are shipping on time and, your quality bar is being upheld. But then eventually, you'll be a multiproduct company, and you'll go back to building product zero to one again. And and guess what? Now you need a bunch of in this hypothetical scenario, you. You'll need some, plenty actually of craftspeople and one or two visionaries to sort of set the direction and and figure out where things are going. So there is this tendency, of course, to want to work with people like ourselves. If it's fun, we feel validated, and we feel seen, But it usually doesn't lead to the best outcomes, and my encouragement to everyone would be to think about what does the organization need at this moment in time, and how does that help bring us to the next level? Yep. I will strong plus one on that, and I'll observe that, one of the challenges I've seen I've talked to more than a 100 founders at this point who are looking for a head of product or CPO, VP product, whatever. Something that both told us, hey. You need to go hire this person. And, what I find is, you know, somehow they'll find me and they'll reach out to me. Hey. Like, you know, maybe you can talk. So I I usually take those calls, from founders. And, you know, what's interesting is, usually, the first question I get from them is, well, they say this is the role I'm hiring for. And, like, do you know any great product leaders? Right? Like, that's the first question. And can you introduce me to them? And so then I have to kinda, like, say, okay. Hold on. Like, it's like, yes. I do know some great product leaders, fortunately, but that is not where we should be going right now. Right? So, like, let's first figure out what it what it is that you want and what it is and whether it is even the right time to hire a code head of product. Because as you said, like, in some cases, you don't want to, yet hire a head of product. The very problems you're trying to solve could be solved by, like, many other means, including empowering your engineers or lead engineer or your product focus engineer model, or, like, hiring, you know, not a head of product, but, like, a perhaps, like, you know, mid career, early career kind of product manager. Right? You're gonna tackle some of the operational work that is now very much needed within your product. And, oftentimes, when I talk to the founder and I realized that this founder, their superpower is literally product. Right? Like, they're just excellent at it, and they've not yet hit, like, very clear, scaling. Right? My suggestion is, like, you're gonna invite more problems, by hiring someone to lead product and then delegating everything to them. And, and even if you kinda, like, decide to hire one anyway, make sure you're very clear about what it is that you're still going to continue to own as the founder whose superpower is product. Like, you're world class at it. And that's when there's some confusion, as well. Because from a management philosophy perspective, they they will imply, like but, well, if I hire a CTO type person, like, should I not just delegate product strategy and other things to them? And that's where we have that conversation. No. Actually, upfront during the interview process itself, if you can clarify that there are certain aspects of the product that you will continue to primarily own. Right now, they can co own it with you, but you will continue to primarily own. You will save yourself a lot of hassle downstream, like, a year, year and a half afterwards, where the VP product is frustrated because they're like, oh, the CEO is too precious about the some products and design and some details. And the founder is frustrated because the bar is no longer being maintained, and now there's, like, challenges. Have you, like, have you encountered these situations, with, like I know you're an angel investor as well. So I'm just curious have if you encountered these types of situations with start ups. Absolutely. And that that last one is personally very familiar. I I think it's also a product, not just of different archetypes, but but, frankly, different roles. You know, the founder is the only person usually who's thinking about the five to ten year time scale, and executives are, depending on the size of the company, thinking about the the one, two, three year time scale. And so there's this, there's this, for example, I'll put this into a saying form. There is this saying that no one cares more about the brand of the company than the founder, and that's true even more than your marketing leaders because the marketing leaders have other responsibilities like group growth and and so forth. And, again, with with design, with products, it's probably the case that if you are a product founder, no one cares more about the precision of the pixels and how it all feels than the founder. And other people are accountable to deadlines. The founder has unusual authority to be able to say, you know what? I don't care. This has to be right. We're gonna ship this when this is right. No one else can say that. Because on the flip side, if someone else says that, the founder is usually the first person to say, what the heck is going on? I'm gonna hold you accountable to this deadline. So there's there's very sort of special place that the the founder is in, and I I hope that everyone who is a founder realizes and sees that. The answer isn't to shy away from that. So I'm agreeing with you. The answer isn't just to give, in this scenario, the CPO, all the things and say, okay. You decide. I think the answer is to use that, what what's the word? It's it's not dichotomy. It's, I guess, contradiction, but but this paradox usefully to be able to press on quality when it needs to be pressed on, but also press on time lines and delivery when that needs to be pressed on, even if you happen to be good at one or the other. Yeah. For sure. Alright. So one other topic I want to cover, and we've kinda, like, you know, touched on it a bit already in the conversation, but I wanna make it explicit mainly because there's a lot of talk these days about taste, and taste as being a very valuable skill and trade in the AI age. Now, like, I think I would observe that, like, it's always been very valuable. Perhaps it's even more valuable. Perhaps peep more people are paying attention to it. Whatever it is, I feel like the current discourse around taste, doesn't sufficiently touch on how it works in practice in a team setting, where in a collaborative setting, in a collaborative environment. Like, so while, you know, I'm glad that we are having more conversation about this topic. It's sort of, like, more in the abstract rather than what it means in practice, and, like, you know, what it means to gonna apply it in practice. So one thing I'll observe is, like, as an organization gets very, like, much larger, it is impossible for one person to be the only one applying this. Now they can still be the primary tastemaker, but they they cannot be the only one applying this because just there's too much. There's too much. And so, you know, I think a large part of taste is, in practice again, is, like, how your team members themselves can kinda, like, understand, what your particular version of taste means. So, Rahul, can you speak more to what you learned about taste, as a leader as you build products at Superhuman? For sure. I agree. Taste is one of the hardest things to hire for. I think it's one of the rarest things to find as well. It's it's about as rare to find in my opinion as, visionary thinkers. It is trainable. It is very, very hard to train, but it is trainable. It takes time. The way I would think about training taste is more of an apprenticeship rather than, you know, you can go to a school or a class and and come back with taste. It just doesn't work like that. You need many, many repetitions. You have to ship many, many features, many products. And and not just ship features and products, you have to, whilst doing so, be extremely deliberate about your thinking and your self development, and that's why you it's so helpful to be in an organization where taste is is considered valuable and is going to be, upheld and taught. I think the biggest challenge is is not just people being able to reliably hit the bar. It's people knowing where the bar is. And I have a definition of taste that I think is a little unusual, but it's quite simple. It helps shine a light on what I mean by that. It's not just the decisions you take, although, of course, those are important. And and by that, I mean the skill, like, really simple example. What what color should this thing be, or or how does the typography feel here? It's how many of those decisions you take. So take any particular feature or any particular product, a truly amazing designer might see and take a thousand decisions. Good designers might see and take 500 decisions. A newbie designer or PM might only see or or take 10 decisions. And so, again, it's not just the quality of the decision, although that's really important. It's how many decisions are being taken. And the challenge for most people is actually spotting the decisions are even there. Yeah. It's, so important to like, for everyone to sort of really process what you just said, which is one of the things I've noticed is that the designers, you know, product managers, founders, who see that oh, actually, there isn't 20 decisions here that you walked me through. There's actually a 100 that were implicitly made, and that perhaps some of those could have been explicit. I think those individuals have a very sharp sense of, like and this is gonna sound like a cliche, but this is what I've observed in practice all the time is they have a very sharp sense of what is it that we're really trying to do here. Right? Like, what is what is the main thing? Right? Like, what is the, completely nonnegotiable objective here with the screen or with this flow or with this email copy? Whatever it is. Right? Like, they have a very keen sense of, like, correctly identifying what that is. Right? And it it's a it's from that identification that truly this is the main thing. And then, yes, there are other things we can trade off. Right? And also understanding all of those other things that we are trading off and why we are choosing for this to be the main thing and why we are, you know, why we might be okay with these trade offs but with making these trade offs, it's that view that then informs their sometimes very strong perspective, of well, you know, but this doesn't really address, like, you know, this objective or this other objective. Yeah. I I agree. It's in addition to knowing what the main thing is, I think it you need one more thing, probably, which is to see what all the variables are. For example, let's say you're, you you know, we we have a we have a rule of thumb at the I've got I'll give a very simple design example at Superhuman, which is if you're going to make a a block of grayish color because you wanna make a container, for example, it should never be neutral gray. And, designers on the call will know why that kind of creates a, sort of a sad, boring affectation to an interface. Typically, what you want to do is tint or shade it very slightly in one one direction or another. If you for example, if your primary color the superhuman primary color is is a purple, that is a slight purple to the grays, and suddenly, the user interface will pop and feel like it has life as opposed to to something that feels drab and gray. Early in career PM slash designer might not even know that that variable exists. So, yes, you have to have the goal, the main thing, but then you also need to know every single possible lever that you can pull. And for me, one of the most fun things about developing my own sense of taste and and teaching and training others is amassing an unusually large collection of levers. It's it's really fun to say, well, what if we tweak this? What if we tweak that? I see we we implemented this particular thing in that way, but that also seems like the default decision. What if we change that decision? And it is surprising how many things you can do that for. Yeah. Yeah. Yeah. Yeah. And, you know, Rahul, I feel like we can probably talk for several hours on, again, the various threads, that have come up. At this point, I'm seeing there are lots of questions, and I don't think we'll be able to get to all of those questions. So I'll say two things. One, folks, please put, you know, please share in the Zoom chat if you, you know, would like to request the Grammarly team to do other, such as sessions where we go deeper into any of these topics, just as a way of, giving feedback. I'm sure there'll be some official feedback as well in the future. But other than that, I wanted to suggest that folks, look at, the q and a, tab, and I wanted to invite Rocky, back, over to the stage, so we can go through a few questions. I'm over here waving and my video is not even on. Hey, y'all. Wow. That was awesome. I know nobody else can hear, but a round of applause for you too. Thank you so much for that conversation. Yeah. We actually have a poll, and I think we have somebody throwing it up on the screen right now, Shreyas, to your question of, like, if you want more of this stuff or if you wanna connect with us, there's a polls tab in the top. Chats, polls, docs. So definitely jump in and add that, if you if you wanna have some more. And then in that doc section, one last shameless plug for our q and a doc. If you click on that, you can actually add some questions to the q and a. And more importantly or equally importantly, you can upload this question. So we have a few in here right now, and I'm gonna get started with with the top one, which is one of my favorites for you all. It looks like Meg has for us. It would be amazing if there was a Cosmo style or, like, BuzzFeed style quiz that quiz that leads you to identify your archetype. Anybody know about that? Did y'all create one? What do you think, Shreyas? Do you have a quiz for your archetype? Yes. So, so the good news is that, we, we just, like, and by we, I mean, you know, mainly the Grammarly Coda team, have worked on, a Coda doc, particularly, to sort of, you know, take a lot of what, I have shared with them about these three archetypes. And, along with some members of my team, that that quota doc is accompanied, with, an actual, like, questionnaire. I believe there's, like, 12 or 13 questions that you can go through, to sort of identify your primary archetype. Okay? So that doc will be shared with you. It looks like it's already in the chat. So take a look at that. Start with the doc, and then there's you'll see a call to action for a, questionnaire, that you can go through as well. And, only thing I would say is, like, you know, there's a bunch of resources in there, and and we can email you more resources as well as you complete the questionnaire. The main thing I would say is, like, answer those questions as honestly and directly as you can. Nobody else is looking at your answers. So answer them in, you know, in ways that feel authentic rather than, well, what should be the answer I should provide? Right? Because you are all very, very sharp, and so I'm sure if you want to be identified as an x archetype, you will figure out, like, what options to select to be identified as that. But, like, then what's the point? There's no point of doing that. So as you go through the questionnaire, the questions are very meticulously, sort of worded. Try to make sure that you're answering what's authentic. So that's a resource that's available to you as part of, joining, this session. Awesome. Thanks, Shreyas. Also, I promise that wasn't a plant. Legit question. So, that that's great. The next question that I have on here just got uploaded to the top from Tim. When meeting a new executive in a meeting, what are some good shorthand ways to determine which archetype they are and hence what they will respond to? And maybe, Rahul, if you want to give us, like, what you from, like, a CEO founder, like, meeting a new executive venture hire, your perspective, and then Shreyas, maybe, from, like, a product leader perspective, meeting either a peer or someone who you could be reporting to. Oh, wow. I I don't think that I have thoughts about this too hard because I have I've always felt like I've just known that this is, you know, it's it's similar to, like, spotting a good founder and and figuring out who to invest in. You you kind of just know after you've met enough people. So it's not that I'm processing this consciously anymore, which I know is the most frustrating answer to give, so I apologize for that. I I suspect Shreyas has a much more useful answer about traits to look for. But I I just tend to know whether I'm dealing with an operator or a craft person or a visionary. You can tell them the kinds of things they they say and what they care about. Yeah. I I would, I would very much, like, plus one the it's what they say. Mhmm. And that provides, like, really useful signals. We we have to understand one thing about human nature. Like, you know, no matter, like, what you might read or hear elsewhere. Like, I'll say, like, we can't help being who we are, and we can't help but saying things and doing things that feel good to us. Right? So that manifests in all interactions that people have with others in a workplace setting. Right? So, like and by the way, this is not like that's that's kind of the the philosophy behind, the answer. But the answer is very practical. Right? Like, which is well, when you're dealing with an operator right? Like, let's take an interview setting. Right? Like, you're interviewing someone. Right? Someone senior. Well, what's gonna happen is, at some point in the interview, you're gonna say, do you have any questions for me? Watch for the questions they ask you. Right? So I tell this to founders as well. Like, I tell founders that, like, if the individual starts in the very first conversation, if their first several questions are about, tell me about the, structure and topology of the organization. Right? Tell me about, you know, what are your, sort of, what are the near term goals and OKRs? Right? What is the division of responsibilities, between various executives on your team? Right? If those are the types of questions that a candidate asks upfront in in an interview, well, folks, please put in this chat what archetype are they likely to be? What is and, again, most of us embody all archetypes. But what is their primary yeah. Of course, operator. Right? On the other hand on the other hand, if the prospective product leader asks questions about, you know, well, so, you know, I'm looking at the market and it looks like you're meeting these user needs, but you're kinda quite deficient on these other user needs. So is this an explicit choice? Like, walk me through the thinking around it. Or it seems like you're targeting these segments, but I would have thought these other segments are, you know, much bigger opportunities. So, again, walk me through the thinking around this. Or maybe they point out some, like, bugs or flaws on your website or in your documentation. Like, okay. Tell me what archetype that person is likely to be. Yeah. A crash person. Right? So so, like, again, the point is, like, people reveal a lot just by what they say. And all you need to do is to pay close attention and authentically listen. I really like that a lot, and that that I think you did a great job of building on there from, from a whole. But I I think what I'm hearing too is make yourself really familiar with, with those archetypes. Because the more familiar are the archetypes and the kind of things that they're gonna talk about, the easier it is to just kind of organically know when they're coming in. Yeah. That's great. Awesome. Alright. Next question that we have here, and this might be the last one. Maybe a little bit too more, but I really like this one a lot. This one here comes from, Piyush. I believe I'm saying that right. I'm probably butchering it, so my apologies there. What do you do when you're being evaluated on an archetype which is not natural to you? So I think we had some conversations in the chat about, I have to perform the role of an operator right now, but really I'm a craft person at heart or or vice versa. If you're being evaluated on that archetype and it's not the one that really, like, you sit well in, how do you how do you handle that? Any advice? So I'm I'm happy to share my perspective, but I'm also very curious. This is a great question. I'm very curious about kinda hearing Rahul's perspective as well, particularly, again, as founder CEO, where you kinda have to do various things. And you would think that a founder CEO is not getting evaluated, but you would be wrong because a founder CEO is getting evaluated by their employees. Right? Like, is this even a capable person to lead us as well as by their board and other stakeholders and by the market. Right? So there is that. Okay. So my quick answer, is, look, I think we it is exceedingly rare for people to entirely change who they are at their core. It's just extremely rare. Right? And then we cannot bank on it. So I think the way to go about it is to, like, actually be honest. Like you heard Rahul b, which is like, okay. Well, like, you know, I I don't I'm only a mediocre operator. Right? So it's kinda like that honesty that kinda comes first. And then, making sure that you convey to all the right people that this is a deficiency. This is not your happy place. Right? And and to make sure that, like, you know, by this time, you've built enough trust that the individual say it fits your boss. Like, they don't think you're incompetent. In fact, like, it's the opposite. Right? Like, they're so competent that you wanna make sure that, they understand that there are some deficiencies. And some of them can be fixed, but others are just programmatic. Like, you can't fix it because, like, if you fix that, it'll cause problems elsewhere. So, like, I think it's gonna, first, establishing trust through your execution and then being clear, to others is, I think, the key. Rahul, any thoughts, from your perspective? 100% agree. The the only thing I was thinking on top of that is, if you truly are being evaluated against a type that is not your type, then you may simply be in the wrong role or even in the wrong company. And, I I think that it it can often be a hard realization, but that is is often the case. Yeah. Speaking hard truths today. I'm loving it. Thank you. Thank you so much for being with us today. We're gonna jump off here in just a minute. I wanted to quickly drop the, Coda doc in again. This is not the question doc. This is the one, the product leader archetype stock that Shreyas has published. It's also the place about halfway down where you can take that assessment to see, you know, what what archetype you're fit in if you're still trying to figure it out yourself. But, yeah, with that being said, I just thank you. Again, I wish we could, like, all come off mute and give you all a ring of applause. This was absolutely amazing. I thoroughly enjoyed it. Yeah. And I'm seeing a lot of things in the chat as well. Feel free to drop those in. Wonderful. Thank you everyone for joining. This is this is great. Yeah. Thank you everyone. Thank you, Rocky. Thank you, Shreyas. Thanks. Bye. Oh, pleasure. Thank you.