<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by James Wang on Medium]]></title>
        <description><![CDATA[Stories by James Wang on Medium]]></description>
        <link>https://medium.com/@james-wang-product?source=rss-e2662e0710ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LCCCPV3TVfYEh6nz64vDRA.png</url>
            <title>Stories by James Wang on Medium</title>
            <link>https://medium.com/@james-wang-product?source=rss-e2662e0710ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:13:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@james-wang-product/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Breaking Into Product Management — Doing the Work]]></title>
            <link>https://medium.productcoalition.com/breaking-into-product-management-doing-the-work-7c46598558cc?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c46598558cc</guid>
            <category><![CDATA[interview-preparation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 09:19:56 GMT</pubDate>
            <atom:updated>2021-09-22T15:59:28.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9LaiDGi_PLdK7ZDH8Cehow.png" /><figcaption><a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Photo</a> by <a href="https://unsplash.com/@marcojodoin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marc-Olivier Jodoin</a></figcaption></figure><h3>Breaking Into Product Management — Doing the Work</h3><p>For working professionals who are trying to break into Product Management, I have a piece of advice that I always come back to.</p><p>Just do the work.</p><p>Easy to say, right? Let me help you understand what that can look like.</p><h3>Doing Product Work</h3><p>I have worked with and mentored technical and non-technical professionals interested in becoming Product Managers, many of whom have gone on to become full time PMs. There’s a long list of advice I’ll give, including to do their own homework on how to break in.</p><p>But the number one piece of advice I give them is to partner with a PM and pick up actual product work and projects.</p><p>Most people I talk to are absolutely on board with this idea, but struggle to understand what it means, how to do it, or where to even begin. In my career, I’ve carved out initiatives for aspiring PMs to own, providing guidance and direction to help them lead effectively. And I’ve had a lot of satisfaction in watching many of these people learn and grow and become PMs through their hard work.</p><p>In this article, I break down how individuals can find and tackle product work to get product jobs:</p><ul><li>Getting clear on your goals</li><li>Taking work from Product Managers</li><li>Picking your projects</li><li>Working effectively with your PM mentor</li><li>Leveraging your experience</li></ul><h3>Getting Clear On Your Goals</h3><p>The core of product management is leading a team to build things. So for most individuals, your goal should be building experience to demonstrate that you can do the job. This means building real competence in the work, and proving to others that you know what you’re doing.</p><p>Your background and experience can help you set a realistic target (level of PM, type of PM, industry, etc.) and determine what kinds of projects make sense to pick up.</p><p>Whatever the case, be clear on your goals for doing product work. What skills you want to build, confidence to gain, stories to tell.</p><h3>Taking On Product Work</h3><p>Many PMs will gleefully hand over work to others, both to take work off their plates, but also for the personal and professional benefits of mentoring someone.</p><p>But there are several considerations before you start asking PMs to unload on you.</p><h4>Be ready to hustle</h4><p>You will be expected to continue doing your current job, and doing it well. If you aren’t seen as a solid performer, people may not trust you to pick up additional work. And you want people to believe you’ll be a high performing, successful Product Manager. Past performance may not be a guarantee of future results, but it sure as hell is an indicator.</p><p>And expect to put in extra work, because it is extra work. Becoming a Product Manager is now your side hustle. That means either finding time or putting in extra effort to do your product work. It’s a real challenge, but PMs are expected to effectively manage their time and energy while delivering results.</p><h4>Get your manager on board</h4><p>If you’re going to be picking up work that isn’t related to your primary responsibilities, you ought to get this cleared with your manager. Assuming they’re a decent manager who cares about you and your career, they will be supportive. Additionally, they can help you carve out more time to focus on PM initiatives. They can advocate for you as you seek opportunities to pick up work or even when you start applying for roles.</p><p>You really want this to all be above board so that if and when an opportunity arises internally, you’ll be in a position to capitalize on all the hard work you’ve put in.</p><p>If you can’t trust them, that’s really unfortunate. And you’ll have to weigh the risks and consequences of trying to do this anyway, or picking another route to becoming a PM.</p><h4>Find PMs who will be great mentors</h4><p>Not all PMs are equal as mentors. And your own situation impacts the kind of PM that can best help you. Reach out to several people and let them know you’re interested in becoming a Product Manager. Ask advice on who would be good mentors or might have projects that you could assist on.</p><ul><li>Find PMs who are genuinely interested in helping you and who have strengths in areas you want to develop.</li><li>Aim to have multiple PM mentors. Find folks who you can partner with on projects, as well as those who can offer perspective, guidance, and coaching in your career journey. Look across a range of experiences — mid-level PMs who are in the thick of honing their product execution, Senior PMs who are exploring product strategy and driving larger initiatives, Product Leaders who make organizational and hiring decisions.</li><li>Have your goals clear and up front so you can describe where you want to grow and what you bring to the table.</li><li>Be humble. You’ve built up a good amount of skill and experience in your function, and are possibly a high performer. But any time you move into another function, you’re learning a lot of things from scratch. Hold onto a beginner’s mindset and accept that there are many things you do not know.</li><li>Have good answers for why you want to be a Product Manager, and be able to show your determination. I’ll chat for 30 minutes with almost anyone who’s looking for advice, but I only invest in people who demonstrate that they’re serious about their career.</li></ul><h4>Asking for work</h4><p>Once you’ve done your homework and have started chatting with PMs, it really is as easy as asking for work. Not all of your potential mentors will have work available, but they’ll all be motivated to help you find opportunities. Then it becomes a question of picking projects to build out the right experience and start your journey towards Product Management.</p><h3>Picking Your Projects — Covering the Product Development Cycle</h3><p>Ideally you will be able to work on multiple projects of varying scope that provide end to end experiences across the Product Development Cycle.</p><h4>A quick primer on the Product Development Cycle</h4><p>I’ve <a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">discussed the Product Development Cycle previously</a>, but I’ll go over this briefly. As a Product Manager, you are responsible for ensuring your team is spending their time well. The Product Development Cycle is fundamentally about validation of your company’s investment (of time, resources, money) at each step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QCrLdLzlXmXzUQKw.png" /><figcaption>The Product Development Cycle</figcaption></figure><p>A simplified breakdown:</p><ul><li>Discovery: Is this the right problem to work on right now?</li><li>Definition: Is this approach the right solution given the constraints?</li><li>Execution: Is the team building according to the requirements identified? Is the feature maintaining a level of quality that your users expect?</li><li>Launch: Is the feature being released, marketed, and supported in a way to ensure it will succeed?</li><li>Analysis: Did we succeed in our goals? What should we do next?</li></ul><p>Each step can go quite deep, especially as you <a href="https://productcoalition.com/driving-business-outcomes-and-impact-part-2-of-becoming-a-product-leader-60a8d893a83a">tackle bigger initiatives</a> or work on different stages of the product lifecycle.</p><h4>Covering the cycle: build on strengths and close gaps</h4><p>Given your own background and experience, you likely have a place in the Cycle that you are more comfortable with. Perhaps you executed as a developer, gathered requirements in customer support or success, or partnered on launches and performed competitive analyses in marketing. In any case, you can capitalize on your existing strengths and dovetail that into a product initiative to close gaps.</p><p>For developers, picking up an initiative a step ahead of execution is a great start. You can take a well understood problem and properly scope it and define it for execution in collaboration with the designer, lead that initiative through the sprint process, and then work with the marketing partner to release and launch it. Following up after with analysis and feedback is a nice way to cap off the initiative.</p><p>Ideally you’ll have the opportunity to pick up initiatives and run them through the whole cycle, from discovery to analysis and follow up. But taking multiple projects for pieces of the cycle still enables you to experience and understand the process.</p><p>At Evernote, I worked with a technical support representative who was interested in becoming a Product Manager. I had her lead an initiative for our first integration with Siri Shortcuts. I provided high level guidance and direction, but allowed her and the team to define the shortcuts themselves and how they would be implemented. She worked directly with one of the developers and our QA lead to build the feature as part of our sprint cycle. And she was responsible for the release of the feature, while I assisted on the marketing launch. She later was able to move into a full time PM position.</p><h3>Working Effectively With Your Mentors</h3><p>Aim to maximize the effectiveness of each opportunity. Working effectively with your mentors is key. Foremost is ensuring you’re executing well. You should be able to work with a degree of autonomy, but check in with your PM mentor on the decisions you’re making and any concerns you have along the way.</p><p>Additionally, seek to learn best practices, frameworks, and the underlying principles behind each thing you’re doing. If you’re observing user interviews, debrief afterward on how the interviewer led the process. If you’re drafting a PRD based on a template, dig into how the template had been created.</p><p>Talk to multiple PMs to hear how they’ve done similar things. For guidance on how to execute it better, but also to learn the different ways people can approach the same problem.</p><p>And finally, build rapport and gain trust from your PM mentors. They will be your strongest advocates, especially for internal opportunities.</p><h3>Leveraging Your Experience to Make the Move</h3><p>You can leverage your product experience when transferring or interviewing for a PM position.</p><h4>Moving internally into a PM position</h4><p>Internal moves are a great way to break into Product Management. You’ll have built up a reputation and will be considered a much more known quantity than an external hire. Having done real product work will be proof of both your ability to do the job and the ability to go above and beyond to achieve results.</p><p>Your mentors, peers, and even manager can be invaluable advocates for you. The hiring manager will be chatting with them, and they can talk you up. If you’ve been following my advice, you’ll have already networked heavily throughout the PM team.</p><p>Do the work of leading projects and meeting with PMs, and you will be the obvious candidate for any PM opening.</p><h4>Interviewing for PM positions</h4><p>There are many articles and books about prepping for interviews, crafting your resume, etc. Your product experience will be an invaluable asset in your interview process. Having worked across the Product Development Cycle, you should have real examples to call out when asked about your experience — how you collaborate, how you would measure success for a feature, etc. Likewise, having done the work, you won’t be answering in purely hypothetical terms when tackling a product sense interview.</p><p>Take the time to review the work you’ve done. Really think about what you did and why. Practice the <a href="https://jackiebo.medium.com/interview-tips-for-senior-pms-2424f7b7c967">STAR or PEARL</a> method for describing your projects.This will help you tell better stories in your interviews, and make your use of frameworks like <a href="https://www.impactinterview.com/2016/06/circles-method-product-design-framework/">CIRCLES</a> much more natural and fluid during your interviews.</p><h3>Closing Thoughts</h3><p>A lot of people say they want to become a Product Manager. Be one of the few who puts in the effort to make it happen. Find people who will invest in you and help you grow. Be bold in your asks and humble in your learning.</p><p>Remember that this process takes time. Great Product Management comes from years of intentional practice. Doing the work, and learning from the work. Focus on the journey and take pride in the preparation you are making. Because you want to be ready when that opportunity arises.</p><p><em>Thanks for reading, and I hope this article was helpful. Please share your thoughts in the comments, and follow me if you’d like to see more about growing your career in Product Management.</em></p><ul><li><a href="https://productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Becoming a Product Leader — Part 1: Thinking Like a Leader</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c46598558cc" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/breaking-into-product-management-doing-the-work-7c46598558cc">Breaking Into Product Management — Doing the Work</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring as an Individual Contributor — Part 4 of Becoming a Product Leader]]></title>
            <link>https://medium.productcoalition.com/hiring-as-an-individual-contributor-part-4-of-becoming-a-product-leader-c0b6c3857cd1?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0b6c3857cd1</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Mon, 21 Jun 2021 23:17:38 GMT</pubDate>
            <atom:updated>2021-06-22T04:11:13.714Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gOO5WzGA_JSkhFFWBYf6g.png" /></figure><h3>Hiring as an Individual Contributor — Part 4 of Becoming a Product Leader</h3><p>The strength of any organization stems from its people. As a Product Leader, you are responsible for growing and strengthening the product team by hiring talented Product Managers. In this article, I discuss how individual contributors can become effective interviewers and demonstrate leadership skills in improving their hiring process.</p><p>This is Part 4 of the “<a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader</a>” series. In this series, I’m tackling different outcomes and traits that individual contributor Product Managers can practice and cultivate to move towards becoming a Product Leader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUd55ZWBlZvrVUu6jeR7qg.png" /></figure><h3>Hiring Matters</h3><p>Who you hire matters. Especially Product Managers. More than most individual contributor roles, Product Managers can have massive impact on the success of a business. PMs are leaders of their teams. How they work with the dev team influences the speed and quality of execution. Their guidance and oversight impacts user experience and feature engagement. Their leadership in the vision, strategy, and roadmap drives customer and business outcomes.</p><p>Additionally, product managers can greatly impact the culture of the wider organization. Their attitude and mindset create an atmosphere for everyone around them. Strong positive personalities can help to forge bonds, build trust, and drive collaboration between Product Managers and other stakeholders. Strong negative personalities can raise walls, close communication, and even turn a great team toxic.</p><p>A great Product Manager on the right team can be a multiplying force for impact across the organization. A bad hire can be a dividing one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*T1zQp3UtbWuKRLNL4qwftg.png" /></figure><h3>Hiring as an Individual Contributor</h3><p>As an individual contributor, you won’t be making the final call on whether a candidate is getting an offer. But you can greatly influence this decision when you’re part of the hiring process. A good hiring manager listens to all voices in the written feedback and in the debrief meeting. As a member of the interview panel, you should aim to provide a valuable perspective to the hiring decision. Ideally, you can build up enough experience as an IC so that by the time you’re hiring for your own team, you know exactly how to make a great hire.</p><h4>Start Interviewing</h4><p>Getting into the interview process is generally pretty easy. If you’re in a company with a structured training program — great! Just get in there. But most companies won’t have a structured program. So it may not be obvious how to get involved interviews, there may not be any actual training, and perhaps not even interview guides or evaluation criteria for any given interview. All of which can be opportunities to <a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">drive improvements for the product team</a>.</p><p>If there isn’t an official process for getting involved in hiring, just ask. Talk to your manager and other hiring managers to let them know you’d like to get involved. Most folks are happy to bring in more interviewers. Hiring is a time consuming process, and being able to spread responsibility out across more individuals can limit the impact to productivity.</p><h4>Become an Effective Interviewer</h4><p>Good interviewing doesn’t happen by accident. Like any skill, it requires intention and practice. There are a lot of great <a href="https://www.wired.com/2015/04/hire-like-google/">books</a> and articles for interviewing techniques, questions, and processes. But there are a few key concepts I wanted to call out:</p><ul><li><a href="https://whothebook.com/">Know who you’re looking for</a>. You should be very clear on what is needed in the role. What does this PM need to achieve in the next 6–12 months to be successful in this role? What skills, traits, and experience does this person need to achieve those goals? If the hiring manager hasn’t explicitly stated these things, talk to them to find out.</li><li>Know the purpose of your interview. Each interview throughout the process serves a purpose. You should be clear in what aspects of the person you’re trying to tease out. It’s a waste of time for every interview to be trying to answer the same questions about the candidate.</li><li>Your gut is unreliable, so <a href="https://hbr.org/2017/06/7-practical-ways-to-reduce-bias-in-your-hiring-process">be consistent</a>. Asking the same questions ensures consistency in the process, which is critical to mitigating biases and effectively evaluating candidates.</li><li>Have evaluation criteria. Know how you can grade answers to questions or how the candidate performed on a product skills assessment interview. This provides more structure to your interview, and has the added benefit of being more useful to the hiring manager. If an evaluation rubric doesn’t exist, consider making one.</li><li>Talk to other hiring managers and interviewers on how they interview, what they look for, and how they guide candidates through the interview.</li><li>Shadow on as many interviews as you can manage. Take the time to chat with your partner after each interview. Dig into how they managed the flow of the interview. What their thinking process was. What responses or statements were worth flagging or following up on.</li><li>Once you learn how to run the interview, switch roles and reverse shadow, with the primary interviewer sitting back and observing. Again, take the time to debrief after interviews. Ask for feedback on your interview. What they thought you handled well. What they might have done differently.</li></ul><h4>Give Great Feedback</h4><p>The hiring manager won’t be present in most of the interviews, so providing effective feedback is critical to aiding their decision. A lot of interviewers just rely on their gut to make decisions and give barebones feedback based on their feelings. Gut based hiring leads to biased outcomes, and feedback from the interviewers is generally useless to the hiring manager. Your feedback should be like any other analysis you perform in your job as a Product Manager: an outcome oriented opinion backed by evidence.</p><ul><li>Write down your feedback in detail. Don’t just rely on passing a general recommendation over to the hiring manager. A well written, comprehensive evaluation is invaluable for the hiring manager when making hard judgment calls. Take 15–20 minutes to summarize your thoughts. This can have the additional benefit of helping you identify any gaps in your evaluation.</li><li>Give your overall recommendation, and ground it based on the overall needs for the position. If the position requires strong UX instincts, but they’re strong on data, be clear on why they’re a “no hire” for this role but could be a “strong hire” for another.</li><li>Provide specific examples to justify your evaluations. What made them a great communicator? What details did they provide that suggested they’d be a great collaborator with their team? How did they demonstrate strong analytical thinking?</li><li>Be clear about where you still have gaps in your understanding, especially if there is a good chance that these gaps should be covered in another interview.</li></ul><h4>Leverage the Debrief</h4><p>In the debrief session, you’ll have the opportunity to reiterate your feedback and to hear other people’s feedback. This is an opportunity both to further hone your hiring skills, and also to meaningfully influence the decision whether to extend an offer to the candidate.</p><p>Pay attention to how others provide feedback and how they talk about their interview. This is a great opportunity to see who is particularly skilled at interviewing and who you could learn from. Try to discern what makes feedback helpful. As a hiring manager, you don’t want to make decisions based on whether a team member liked the candidate or not. You want to make decisions based on the specific evaluation criteria each interviewer was measuring.</p><p>Upon listening to all the feedback, you should be able to form your own opinion about whether this would be a good fit for the role. This is good practice for when you’ll be the one making the hiring decision, but also a good opportunity in practicing influencing another’s decision.</p><p>If you have a strong opinion about the candidate, you should consider how you can provide this opinion. It isn’t your decision, but a well formed opinion can be valuable input for the hiring manager. Rather than just baldly stating your opinion, call out the specific aspect about the role and the candidate that either raised concerns or suggested greatness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*hQ6CoCFIp0Vg2FEdh7Hp_w.png" /></figure><h3>Becoming a Leader in the Hiring Process</h3><p>Many organizations do not have a particularly rigorous interview process. In these cases, there is an <a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">opportunity level up your product org</a>. Establish a shadowing program if one didn’t exist. Create evaluation rubrics, especially for product skill interview sessions. <a href="https://www.indeed.com/career-advice/interviewing/who-interview">Find or create a framework</a> for documenting the expectations for each role.</p><p>I recognized the value of good hiring early on in my career, and I made it a goal to become an effective interviewer and hiring manager. In addition to reading books and articles on hiring and interviewing best practices, I always made an effort to get involved in the hiring process wherever I worked. At Autodesk, I requested to take on multiple interviews in our PM hiring process, particularly the product sense phone screen and the on-site case study.</p><p>We didn’t have a proper training program for our interview process, and our interview guides were pretty light. So I met with every PM who ran either of these interviews. I asked them how they ran the interviews, what they looked for in candidates, and how they measured success. I was provided the opportunity to participate in and then run the interviews fairly quickly.</p><p>After a few sessions with the product sense phone screen, I started coalescing on a few key criteria to evaluate each candidate. I created an evaluation rubric, getting feedback from other interviewers and testing it out in my evaluations. After a few iterations, I had a solid interview and evaluation guide that enabled other PMs to quickly ramp up and run them on their own.</p><p>Interviewing this many candidates enabled me to hone my own skills and identify best practices and opportunities for improvement in our process. So when I moved into a management position and started hiring for my team, I was able to immediately leverage all the knowledge I had gained. I set expectations for the role to ensure each member of the interview panel knew what to look for. I centralized interview guides and resources to ensure consistency in our process. And I set up a shadow program so more Senior PMs would have the opportunity to start interviewing.</p><h3>Summary</h3><p>Hiring PMs matters. Great Product Leaders take the time to ensure their organization will make great hires. As an aspiring people manager, you should prepare yourself for the next level. Invest the time to become a great interviewer and hiring manager. And find opportunities to level up and improve your hiring process.</p><p>Next in the series, I discuss another fundamental people manager responsibility: Coaching and Mentoring Product Managers.</p><p><em>Thanks again for reading this articles series. Please share your thoughts in the comments! And be sure to follow me to stay updated on future articles.</em></p><ul><li><a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0b6c3857cd1" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/hiring-as-an-individual-contributor-part-4-of-becoming-a-product-leader-c0b6c3857cd1">Hiring as an Individual Contributor — Part 4 of Becoming a Product Leader</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader]]></title>
            <link>https://medium.productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/bee8bf9b2011</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 08:10:57 GMT</pubDate>
            <atom:updated>2021-06-22T15:49:50.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qKe1EiujN-SNHs452tzY4w.png" /></figure><h3>Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</h3><p>Great Product Leaders raise the bar for product management across an organization. They consistently strive to improve how product management is practiced, ensuring better outcomes over time. In this article, I discuss how individual contributor Product Managers can demonstrate leadership by establishing excellence in product management themselves and across their organization.</p><p>This is Part 3 of the “<a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader</a>” series. In this series, I am tackling different outcomes and traits that individual contributor Product Managers can practice and cultivate to become a Product Leader.</p><p>As an IC PM working to become a Product Leader, you need to convince other leaders to trust that you can raise the bar of product management in your organization. This trust is earned through:</p><ul><li>Demonstrating your ability to manage product initiatives of significant scope and complexity, and</li><li>Driving real improvements in product management processes across your organization.</li></ul><h3>Demonstrating Excellence in Product Management</h3><p>Your leadership team relies on Product Leaders to bring a depth of product expertise to the organization. Demonstrating that expertise and earning their trust means:</p><ul><li>Experiencing the product development cycle multiple times on initiatives of significant scope and complexity, and</li><li>Effectively communicating with senior leaders and stakeholders</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*tZi6nl_Rgx6bh1NMUa2aaw.png" /></figure><h4>Mastering the Product Development Cycle</h4><p>As a Product Leader, you will be responsible for business outcomes across a wide swath of product areas. As an IC, you should aim to understand the Product Development Cycle well enough to guide and coach other PMs to success. That means running through the cycle multiple times on projects across a range of scope and complexity.</p><p>There are a lot of variations on the definition of the Product Development Cycle. But the core principles are the same. Discover and validate what you’re supposed to build and what it looks like. Deliver a high quality experience. Release and market appropriately. Measure impact and gather feedback to determine what to do next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CVmvEJVijWXM4FVVkODTrQ.png" /><figcaption>The simple Product Development Cycle</figcaption></figure><p>The details of each step vary dramatically depending on the scope of the project. For a minor feature improvement, each step can be relatively straightforward. Minimal conversation needed with customers or collaboration with stakeholders. Discovery might be as simple as deciding to build out feature parity across a platform. Definition as simple as modifying designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5QV1rIzxP8TLgxf3tFPVA.png" /><figcaption>Major feature launches require more validation and collaboration with stakeholders.</figcaption></figure><p>For a major launch, discovery can require in depth conversations with customers and internal experts. Definition requires plenty of concept testing and idea validation. Execution requires phased milestones and coordination with other teams. Go to market is an entire project in and of itself to get all the material together, align stakeholders, and get buy in from leadership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F2x2k78kR4ASTXEE6cGH0w.png" /><figcaption>Large, ambiguous initiatives require consistent validation and approval throughout the cycle.</figcaption></figure><p>For really big bets, each step can become its own miniature cycle. Discovery and validation become inherent principles behind every step. Approvals from leadership can be required to move forward between steps in order to justify the expenditure of resources or to ensure the brand isn’t damaged or revenue put at risk.</p><p>As a Product Leader, your familiarity with each step across a wide range of scopes is critical to successfully leading a team of PMs. You will be guiding them through new experiences and watching their work to ensure they don’t make irreparable mistakes.</p><p>That said, not every company expects equal depth of experience across the entire cycle, nor is the scope of products the same. The key is taking on the widest potential scope a Product Manager can own in your organization.</p><p>I built up a range of experience across my career. Working on a variety of products and business models helped to create depths of skill in areas that I otherwise might not have. Gaming required deep data analysis, down to minutes and even seconds of user behavior. Game launches meant collaborating on creative ad campaigns and hard CPI / LTV optimizations. Growth at Evernote taught me growth loops, clarifying hypotheses, and rapid experimentation. Working on zero to one products at both <a href="https://evernote.com/features/tasks">Evernote</a> and Autodesk meant countless hours of user research and validation and complex release plans.</p><p>Whatever your background, seek a range of opportunities to broaden and deepen your own experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*XoOL0wui2NQXd3D3Q00__g.png" /></figure><h4>Avoiding the Execution Trap</h4><p>Most Product Managers get their start in the execution step of the product cycle. PMs can get stuck on this step. It’s comfortable, it’s often the only explicit expectation, and there’s always more to be done.</p><p>Additionally, owning too much of the execution process can prevent the team itself from growing and improving. Having to answer every minor UI or requirements question makes you a bottleneck. Being the only person who know how the whole release process works makes you a single point of failure. Driving all improvements from the sprint retro deprives individuals from taking on leadership opportunities.</p><p><a href="https://productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Your goal should be to enable your team to execute effectively with as little of your involvement as possible</a>. As a Senior Product Manager, you should be able to provide guidance to the team to make them self sufficient. You should know what good and bad execution looks like. You should be familiar with multiple frameworks and methods. You should have developed an understanding of the underlying principles behind those practices.</p><p>This knowledge should make it straightforward to train a less experienced team. You won’t impose your idea of best practices; you’ll work with your team to discover what works best for the team. You know what you can expect, and so you can negotiate and delegate responsibilities. You’ll empower each team member to be responsible for the quality and effectiveness of each part of the process they touch.</p><p>As a result, your team will deliver better product outcomes. Your engineering lead and developers will have more ownership over the process and product. And you will be able to spend more time on the rest of the cycle, or increasing the scope of the initiatives you tackle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zAdDrc19J3wQPSOf7D109g.png" /></figure><h4>Earning Trust Through Communication</h4><p>It isn’t enough to do the work. You need to be communicating what you do and how you do it, in order to build trust that you can <a href="https://jackiebo.medium.com/the-surprising-skills-that-help-you-succeed-in-your-product-management-career-as-you-get-more-3a1fcff40f8e">autonomously lead initiatives of significant scope and impact</a>.</p><p>A key thing to consider is “autonomy.” Having autonomy means being able to choose goals and the means of achieving them. But having that freedom doesn’t mean being able to work in complete isolation. Great leadership is bringing everyone along the journey, including senior stakeholders and leadership.</p><p>A major facet of communication with leadership is understanding their needs. Your leadership team is looking for confidence. Confidence in the direction you’re heading, the approach you’re taking, the timelines you’ve committed to, and that the right people are being included throughout the process.</p><p>You should be clear in your needs as well. Asking for ongoing resources and support. Help on pushing against or even changing systems that put your projects at risk. And continuous buy-in on direction and approach.</p><p>By addressing their needs and clearly articulating and justifying your own, you will earn their confidence. And you will be demonstrating the degree of scope and complexity you can manage autonomously.</p><p>A mistake I made early in my career was trying to solve problems quietly and only communicate good news and wins whenever possible. I thought that instilling confidence was about never showing weakness. This worked for a while — I solved a lot of problems, had some good wins, and made my way up the career ladder. But as I moved into bigger initiatives, the problems became far beyond what any one team or individual could hope to contain. Trying to quietly manage everything stressed me out, which stressed my team out. And failures became surprises to leadership and stakeholders.</p><p>I started communicating risks early. I walked through the situation, what the team and I were doing to address it, and whether we needed any assistance. Most of the time, nothing changed in what we would do — I was just being transparent about it. And by doing so, it took a lot of the pressure off in the case of failure, and it actually increased confidence that the team and I were doing well.</p><p>I learned that while winning is important, bringing people along the way defines success. By walking with your stakeholders and leaders through each step, they become collaborators in the process. Decisions and outcomes are made together, win or lose.</p><h4>Ideas Into Action</h4><p>When communicating to your senior leaders stakeholders, there are several key areas to cover: conflicts between people, the plans for complex projects, risks to plans, insights on direction, and high impact emergencies. You should seek to provide transparency into challenges and risks, but emphasize that you and your team are taking appropriate actions.</p><p>Examples of the kinds of topics worth communicating:</p><ul><li>Unique insights from customer conversations</li><li>Last minute emergencies that you managed and resolved</li><li>Overcoming logistical hurdles, such as legal blockers or creating an operational plan with customer success</li><li>Disagreements with partner teams on priorities, approaches, or resources and how you plan to resolve them</li><li>Presenting a research plan — goals, hypotheses, methods</li><li>Managing an angry client or frustrated sales rep, or requesting assistance in those conversations</li></ul><p>Look for opportunities to communicate what you and the team have managed. Take advantage of presentations on major launches or research findings. Leverage periodic check-ins with the leadership team. 1:1s with your manager can be an effective time to demonstrate excellence. A good manager can be your strongest advocate. Providing them specific evidence of your good work can be critical to your future opportunities.</p><p>With my reports, I ask them to keep me updated on the many initiatives they’re working on. I ask them to emphasize the challenges they’re facing and how they’re approaching them. For complex projects that are a bit beyond their experience, this ensures I can evaluate their approach and provide feedback. For problems that they are resolving on their own, I have awareness of what they’ve accomplished, and I can then broadcast their successes to other leaders in the organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qX1JiJ5dl6va-EOVs_zjOg.png" /></figure><h3>Leveling Up the Product Team</h3><p>Beyond establishing excellence in one’s own abilities, Product Leaders level up the craft of product management across the entire organization. Part of this is in coaching and mentoring other PMs. But an important aspect is driving improvements in product practices in your organization.</p><p>As an individual contributor, you have opportunities to make meaningful improvements to how your product team operates. <a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Taking the initiative</a> to collaborate with other Product Managers and drive improvements is an <a href="https://productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">important part of leadership</a>.</p><p>There are many ways to level up your product organization. It comes down to a few key ideas. Improve tools or processes to make it easier for PMs to do their jobs well. Identify and share out best practices across the product development cycle. Knock down barriers in communication with other functions, partner teams, or leadership.</p><p>Some examples of what this looks like:</p><ul><li>Product Development Cycle improvements. Every aspect of the cycle is rife with opportunities to drive improvements. Running kickoffs, product spec reviews, analysis templates, release checklists, customer research methods, etc.</li><li>Unblocking barriers with partners. Getting approvals with legal, setting up a new beta process, or getting access to analytics tools can be opaque if clear processes haven’t been defined. Working with partners and documenting processes can go a long way to making other PMs’ lives easier and more effective.</li><li>Product planning. The org-wide planning process is extremely high impact and often quite a mess. I’ve never seen a company with a bullet proof planning process. But I’ve worked places that put in a lot of effort to continuously improve the process. Being part of the solution and helping to make the org-wide planning process more effective is a great way to invest your time.</li><li>Communication with stakeholders and leadership. Do you have recurring meetings with key partners? Do you have channels for passing direction and insights down from senior leaders from other functions? Any best practices when presenting updates to the leadership team? Communication out of the team is critical to success for the team, PMs, and the organization as a whole.</li><li>Team culture. Does your team foster an attitude of positivity and proactiveness? Do you share ideas and collaborate, or are you mostly siloed into your teams? Do your product team meetings include time to get to know each other, how you think, and what you value? Do you have recurring product team meetings? Fostering a healthy product team culture can spur improvements across every aspect of product management.</li></ul><p>Finding areas that need improvement is usually quite easy. Prioritizing your time and energy effectively is important. Talk to your manager, skip level manager, or even your head of product to hear about high priority areas that need attention and improvement. Volunteer your time to assist other leaders in ongoing initiatives.</p><p>You can also take any improvements you’ve made for your own team or paths you’ve trail-blazed and share those with the rest of the product team. This can be as simple as documenting steps in a confluence page and talking about it during your biweekly PM meeting. Or as robust as frequent presentations and helping your team to become evangelists.</p><p>When I joined the Growth team at Evernote, we had the opportunity to redefine what Growth meant at Evernote. We revamped our experimentation process: clearer hypotheses, automated dashboards, new testing frameworks. And we began to see some real impact. We shared our results and learnings throughout the organization. Biweekly emails with upcoming tests and previous results and learnings went out to the entire organization. We presented to leadership on major wins, explaining the data and psychology we used to define hypotheses. And on demo days, our developers presented their experiments. They walked through the full process of hypothesis generation, implementation, results, and findings.</p><p>We consistently messaged what we were doing, how we did it, what we learned, and what the impact was. And we shifted attitudes and perspective on what growth could mean for our business and organization. By sharing knowledge and democratizing the process, we brought more product and marketing teams into adopting experimentation and growth concepts, pushing the entire org to more data driven decision making.</p><h3>Summary</h3><p>Product Management is a function without obvious answers and no guarantees. But the frameworks, practices, and processes we apply to our craft can determine the long term success or failure of an organization. Becoming a Product Leader means establishing excellence in Product Management in oneself and throughout the organization. Moving up from an IC position means taking steps to demonstrate that excellence to senior leaders and to take real action to drive improvements beyond your individual team.</p><p>And this process is never ending. A great Product Leader is always striving to improve themselves and the organization.</p><p>Next in the series, <a href="https://productcoalition.com/hiring-as-an-individual-contributor-part-4-of-becoming-a-product-leader-c0b6c3857cd1">Hiring as an Individual Contributor</a> — Part 4 of the <a href="https://productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader</a> series.</p><p><em>Please share your thoughts in the comments! And be sure to follow me if you want to stay updated on future articles.</em></p><ul><li><a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Becoming a Product Leader — Part 1: Thinking Like a Leader</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bee8bf9b2011" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader]]></title>
            <link>https://medium.productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/60a8d893a83a</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Tue, 01 Jun 2021 01:12:30 GMT</pubDate>
            <atom:updated>2021-06-10T15:40:44.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LlDi5vQL1aeqBRwpoZ58ng.png" /></figure><h3>Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader</h3><p>Product Leaders drive impact for the business by taking on complex initiatives and defining strategy across multiple teams. This is Part 2 of the “<a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader</a>” series. In this series, I’m tackling different outcomes and traits that individual contributor Product Managers can practice and cultivate to move towards becoming a Product Leader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*zmh14wicae9Ngm6nel_W-A.png" /></figure><h3>Leading Complex Initiatives</h3><p>As a Product Leader, you will be expected to lead and drive initiatives that span across an organization. So the potential impact you can have on the business— either positive or negative — increase commensurately. Your leadership team, stakeholders, and individuals doing the work all need to trust that your influence will result in better outcomes.</p><p>And nothing proves the ability to drive major business impact like past success. So it’s important for individual contributor PMs seeking to become Product Leaders to take opportunities to drive complex initiatives.</p><p>What this looks like varies a lot by the company and organization you’re in. But initiatives and projects led by Product Leaders tend to need major coordination and alignment. They’ll work with more leaders and more stakeholders than what’s expected at the team level.</p><p>Examples of scope for a team level Product Manager vs. a Product Leader:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vxO9ovG34piowALUmjLLA.png" /></figure><p>Look at what other product leaders are responsible for compared to team level PMs at your company. Within Autodesk Construction Solutions (ACS), PMs are responsible for their individual product areas. There’s still a lot of cross-organizational collaboration, but they tend to stay relatively focused. Group PMs or Directors will lead initiatives that need delivery from many teams or even the entire organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kky--s45PmBXOnDg6bdf7g.png" /></figure><h4>Big scary initiatives and the fear of failure</h4><p>I took on the responsibility to define a strategy for an initiative with complex technical tradeoffs and without clarity on the exact customer needs. I’m going to be a bit vague, so I apologize if this isn’t perfectly clear. But essentially, we realized that within next couple planning cycles, we were going to face serious sales and development challenges if we didn’t come up with a compelling story and proper solution.</p><p>A fully built solution would require months of development effort from almost every team in our organization. No one else wanted to even look at this; we were all still busy just grinding away at our immediate goals. But we needed a plan.</p><p>I hesitated to take this on. This initiative had the potential to get very complicated, very quickly. There was little data available, and no good way to talk to customers about it at the time. Getting involved could mean staying involved for a long time. And at any step in this process, I’d run a risk of failure or embarrassment.</p><p>But it needed to be done, and it was exactly the kind of complex, ambiguous problems that other Product Leaders in my organization were facing. And it was a really interesting problem to solve. So I decided to take on the responsibility.</p><p>In leading this initiative, I was able to collaborate with leaders across R&amp;D and GTM teams that I would never have otherwise worked with. I learned a lot about our products and the customer and business needs driving this initiative. And I continuously presented our evolving approach and our plans to the leadership team, eventually getting buy in on a strategy.</p><p>Together, we were able to formulate a phased approach that allowed us to build incrementally towards a full solution, while having time to evaluate and make changes to the plan as we progressed. This plan is actually still evolving and ongoing, and code is starting to be shipped.</p><p>One of the key things I learned from this experience was that with big, scary, complicated initiatives, people appreciate someone stepping up to try and make sense of things. It didn’t matter that I didn’t have the best experience or that I was learning as I went.</p><p>Another takeaway was that with large enough initiatives, even just creating alignment on a plan is a major outcome. Shipping code and impacting customers is still the goal, but the challenge to get so many folks pointed in the same direction is significant, and other leaders recognize it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*kHD43jIuntKdmbhgPqc68g.png" /></figure><h4>Ideas into action</h4><p>As an individual Product Manager, look for opportunities to tackle complex initiatives outside of your immediate team level responsibilities.</p><p>If you’re working on an existing product that’s stable, are there big new market opportunities that you could extend towards? Building a strong business case is a great project. You collaborate with other product managers, marketing, sales, and research and data. Best case scenario, you get approval, build it, and drive a huge win for the business. Worst case, you learn a lot, build relationships, and demonstrate bigger picture thinking and impact.</p><p>Or is there a big gap between product visions that needs a coherent narrative? You can help create a powerful story that unites the organization and builds excitement with leadership and stakeholders. And in driving that alignment, you can create better business outcomes.</p><p>Look for opportunities to step outside of your individual team and work. Talk to your manager, the leadership team, and even senior stakeholders to learn about what kinds of problems are looming and need a leader to champion. Yes, it’s more work, and no it’s not required. It may not go anywhere outside of a document or presentation. But that’s the work of a Product Leader — lots of exploration, alignment, and bets that sometimes pay off and often don’t.</p><h3>Organization-Wide Strategy</h3><p>Product strategy drives business outcomes. As a Product Leader, you will be expected to define, align, and drive strategy across an organization. Product Managers are often thinking about strategy and prioritization for their team’s backlog. Whether in planning cycles or in grooming the backlog, they should always be able to explain why the team is doing what they’re doing. Yet PMs often don’t take the time to articulate a clear strategy when making their plans.</p><p>So, two questions to discuss: “how does one define product strategy?” and “how does one lead strategy across an organization?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*LdFi1MsYW745c6fq9jxJ0w.png" /></figure><h4>Defining Product Strategy</h4><p>Jackie Bavaro and Gayle Laakmann in <a href="https://www.crackingthepmcareer.com/"><em>Cracking the PM Career</em></a> did a fantastic job defining strategy. To briefly summarize their thinking, product strategy has three components:</p><ul><li>Product vision</li><li>Strategic framework</li><li>Roadmap</li></ul><p>Most Product Managers are familiar with selling a vision and creating a roadmap. A lot of PMs skip the strategic framework.</p><p>The product vision is the high level, inspiring description for where the product can go. It’s often aspirational and excites folks with what the future holds. PMs don’t always spend a lot of time building a grand vision, but they can usually explain where the product is going over the next 2–3 years.</p><p>The roadmap is just a list of things you say you’ll be working on. Whether a high level backlog, or a rough timeline of initiatives. It’s what most stakeholders are asking for. When are we going to satisfy this customer request? What’s going in our big quarterly marketing push? But a roadmap by itself doesn’t say anything much about meaningful goals and outcomes.</p><p>The strategic framework is the missing piece in most PM’s plans. It answers the questions of “why this list of initiatives,” and “how are we going to achieve our vision?”</p><p>Key considerations for your strategic framework:</p><ul><li>What are the major goals you are trying to achieve?</li><li>What customers are you targeting with your goals?</li><li>What business impact do you believe these goals will have?</li><li>How do the goals align with the broader organizational strategy?</li><li>How do the goals tie into your broader vision?</li></ul><p>The goals should explain the building blocks that form the vision, as well as the business outcomes that justify the investment over time.</p><p>However you create the framework, the key is that the strategic framework answers questions on why work is worth doing.</p><p>I have a simple template that I’ve shared with the PMs in my group. It’s designed to drive alignment with other teams, and explain the prioritization of our roadmap. This is helpful, as we have a lot of dependencies with other teams, and work often gets delayed. When push comes to shove, our framework makes it clear what work can or can’t get cut.</p><ul><li>Goals: What do we plan to accomplish this half? How will things be different for our customers or our organization as a result of what we do this half? How are we aligning with or supporting broader organization wide goals and direction?</li><li>Strategy: How will we do the above? Who are we focusing on? What are we prioritizing as a must have, a nice to have, a won’t do?</li><li>Milestones: Are there incremental wins we can deliver along the way? What types of initiatives and timeline would enable these incremental goals?</li></ul><p>Each initiative in our roadmap can be tied to a specific goals, milestone, and strategic priority.</p><p>I’ve found this framework to be very helpful when presenting to our leadership team and to stakeholders. A vision by itself is an empty promise. A list of initiatives by itself explains nothing. The framework provides a meaningful plan and creates context for what we’re building. It sells the <em>why</em>, the story behind what we plan to build and where we’re going.</p><h4>Driving Strategy Across an Organization</h4><p>Product leadership in strategy is about defining, aligning, and selling a broader strategy across an organization. An organization wide strategy should instill confidence that everyone is working together towards bigger outcomes. It should empower teams to define their own strategies, aligning with organization-wide outcomes.</p><p>Two major considerations:</p><ul><li>Driving alignment with other leaders and stakeholders</li><li>Providing the right level of guidance to teams</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZw9O4dLnde1kJ31WK_LZQ.png" /></figure><h4><strong>Aligning with other leaders and stakeholders</strong></h4><p>This is a common thread with any kind of Product Leadership activity. You’re impacting a broader scope, and more people and teams are impacted and have opinions. Likewise, you’re interacting with and dependent on more outside teams. Driving this alignment needs to happen constantly, not just during planning cycles.</p><p>Building alignment and excitement early on increases the likelihood that your plan will be supported and resourced and your vision realized.</p><p>I was leading a team to discover a new product opportunity. We wanted to start small — focus on a single step in a larger workflow, and build a case to expand. But it was clear that customers were going to want more connections with other products in ACS. My initial instinct was to hand-wave the longer term opportunity so I could focus on the hard work of validating the immediate MVP. But I realized — with advice from others — that this was an opportunity. I could build more excitement for the opportunity and demonstrate leadership across a broad product area.</p><p>Over several months I collaborated with many other team leads to build a shared understanding of our products and visions. We brainstormed long term opportunities to create more powerful workflows for customers. This culminated in stories we could tell in product specs and presentation. Driving and engaging in these conversations built a lot of excitement. Leadership and our sales and marketing partners saw the opportunity, and our MVP proposal was green-lit. And I learned a lot about collaborating on a broader vision with other leaders.</p><h4><strong>Providing guidance to teams</strong></h4><p>Good strategic guidance aligns teams toward shared goals. By aligning teams towards specific goals and outcomes, you can drive greater business impact. Crushing three goals will have a lot more impact than barely touching ten goals. Effective guidance clarifies priorities. It answers questions for an organization that teams can’t easily answer for themselves. But it leaves space for teams to define their own problems and solutions.</p><p>In a recent planning process, I worked with several other leads to form a coherent strategy for our part of the business unit. We discussed what made our product area unique and what we saw as long term opportunities for our products, within the broader context of the Autodesk Construction Cloud. With this, we were able to agree on a high level vision for our product area.</p><p>We defined strategic pillars that supported our vision, aligning directly to each of the organizational goals set by our leadership team. Each of these pillars was a long term opportunity of investment, with increasing maturity levels. We defined maturity levels on an axis of manual effort to automation and insights. Essentially, does this work flow exist, how easy is it to complete this workflow, can steps in this workflow happen automatically, and can we predict steps or provide insights for this workflow?</p><p>A key insight was realizing that over-investment in one pillar’s maturity at the expense of another could create an unbalanced experience that didn’t satisfy a significant portion of customers. Every pillar mattered, and we wanted to make continuous, meaningful progress along the maturity axis for each pillar.</p><p>Each team in our broader group is responsible for specific features and pieces of each workflow that we own holistically. By creating this framework, we were able to provide more transparency across the group as to how far along each team was for each pillar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*-hMuXpjl8CRtpjU2VXAi1g.png" /></figure><p>This made it easier to identify strengths and gaps to be closed, in order to create a more consistent approach across our portfolio of products.</p><p>With this high level framework, we left a lot of room for teams to define how they’d achieve these goals. But they also had clarity on how to define team level strategies that would align across our group and with the broader organizational goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*kHD43jIuntKdmbhgPqc68g.png" /></figure><h4>Ideas into Actions</h4><p>If you haven’t yet, define a clear product strategy for your team. You should be able to articulate how each initiative ties to your product goals. Each product goal should serve a higher level organizational or business goal. You should be clear on who you’re building for, and why you’re prioritizing them over other customers or users. You should be able to quickly determine what work must get completed this half and what can be pushed out. Answer the questions listed above, and answer any questions that your team and stakeholders ask.</p><p>Once you’ve defined a compelling strategy for your team, start looking outward. Look for broader strategic narratives that you can create with other teams. Help your product leaders craft the broader strategies by coming with data or research insights. Go and talk to other teams about what they’re building towards, and raise awareness of misalignments or opportunities.</p><h3>Summary</h3><p>Being a product leader requires driving bigger product and business outcomes. Individual team level focus isn’t enough. Find opportunities to take on initiatives that impact multiple teams. Collaborate with others on strategy and vision beyond your own product area. Find ways to prove that you can work with others to move the business.</p><p>Remember that the goal isn’t do everything or to do it all perfectly. It’s about learning how to increase the scope and impact of your actions. Working across a broader section of your organization and with more leaders will provide you with new challenges and problems to overcome. Maintaining a good attitude and focusing on learning will carry you a long way.</p><p><strong>Next in the series —</strong> <a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Part 3: Establishing Excellence in Product Management</a>.</p><p><em>Please share your thoughts in the comments! And be sure to follow me if you want to stay updated on future articles.</em></p><ul><li><a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</a></li><li><a href="https://james-wang-product.medium.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a></li><li><a href="https://james-wang-product.medium.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Becoming a Product Leader — Part 1: Thinking Like a Leader</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60a8d893a83a" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a Product Leader — Part 1: Thinking Like a Leader]]></title>
            <link>https://medium.productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38e1d4bccd7</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Thu, 20 May 2021 22:00:40 GMT</pubDate>
            <atom:updated>2021-06-10T15:41:55.354Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hfg376eCnaMWyWbZ6thL7g.png" /></figure><h3>Thinking Like a Leader — Part 1 of Becoming a Product Leader</h3><p>This is Part 1 of the “<a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader</a>” series. In this series, I’m tackling different outcomes and traits that individual contributor Product Managers can practice and cultivate to become a Product Leader. This article focuses on shifting one’s perspective from a team level Product Manager to an organization wide Product Leader.</p><p>The biggest obstacle I faced when trying to move from Product Manager to Product Leader was my own mindset. I had a number of attitudes and beliefs that were counterproductive and held me back:</p><ul><li>Leadership is responsible for solving organizational problems and strategy. I’ll take on these kinds of initiatives when it’s my job to do so, or if it means I’ll get promoted.</li><li>How am I supposed to drive these initiatives as an IC? There’s so much uncertainty and I don’t have the authority to change things.</li><li>I can’t focus on organizational initiatives, I have a responsibility first to my team.</li></ul><p>You may or may not suffer from any of these misconceptions. But I’ve seen other experienced individual contributors making the same mistakes, banging their heads against the ceiling of management and leadership.</p><p>Changing my perspective was difficult and is an ongoing struggle. But pushing myself to a new mindset has made all the difference in my ability to be a leader.</p><blockquote>Leadership is responsible for solving organizational problems and strategy. I’ll take on these kinds of initiatives when it’s my job to do so, or if it means I’ll get promoted.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OSsjJuFf0YLqAUofDApYZw.png" /></figure><h3>Don’t Wait to Be Invited</h3><p>People can hold themselves back by thinking it’s not their place to take on organizational initiatives. Whether they think it’s not their responsibility or not in their authority, they can find reasons not to try to tackle large problems.</p><p>For a while, I had a pretty rigid hierarchical view of how organizations worked. I believed that each role had a specific area of responsibility and authority, and operating outside of those bounds wasn’t appropriate. So when I saw problems in organization wide strategy or gaps in major processes, I’d complain to my manager or leadership.</p><p>And I got frustrated, because the problems would generally persist, and it felt like nothing that I said mattered.</p><p>More than anything, my beliefs about having the <em>authority</em> to drive large initiatives was holding me back. I had no problems driving changes for my team or even working with my peers to make small changes in our process. But larger, organizational changes felt outside of the authority of a simple team-level Product Manager.</p><p>Talking to my manager and other leaders helped me to challenge this thinking. Yes, there were some decisions that would be difficult to involve myself in. But there were countless other initiatives and problems that needed driving that any individual could take on.</p><p>And there wasn’t any magical authority that came with moving up to a higher level that suddenly changed how things needed to get done. I wanted to be in a position where people would have to listen to me. But being a great leader isn’t about relying on your title to ram changes through; it’s about building trust through effective collaboration and swaying hearts and minds to align on goals and a direction.</p><p>It was obvious in hindsight, but it was helpful having someone point it out to me: I didn’t need the title to do the work.</p><p>But why should I take on all this extra work if I couldn’t be certain it would mean a promotion?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TuPGcKTA2DNhEYGZkiu_8w.png" /></figure><h3>Don’t Look For Guarantees</h3><p>Moving into a leadership position can require taking on a number of responsibilities above and beyond your day to day role. And few people embrace the idea of doing extra work without some kind of compensation and recognition. I often looked at it from a transactional perspective: if I did this work, was I going to get promoted? How many features did I need to launch? How many initiatives did I need to drive? How many people did I need to mentor?</p><p>It usually doesn’t work like that. Your manager and senior leaders won’t make such promises, because 1) these roles are filled based on business needs, and 2) just because you checked some boxes doesn’t mean you&#39;ve proven you can thrive in the new position.</p><p>People need to trust that you have the attitude, aptitude, and capacity to be great at the next level. They need to believe that they should continue to invest in you. There are a lot qualities that your leadership team is looking for. Many of which they won’t or don’t know how to articulate. Doing the work provides an opportunity for you to actually discover, practice, and demonstrate those qualities.</p><p>And if you really want to be in the role, you should want to do the work. If your only interest in taking on a complex cross-organizational initiative is to have the title, then you’re going about this backwards. Moving into the role makes those kinds of challenges your job. If you don’t enjoy mentoring and coaching other PMs, why do you want to be a manager? If you don’t embrace the value and impact of driving alignment with multiple leaders, why do you want to make that your day to day responsibility?</p><p>If you want to do the work, you should do the work.</p><blockquote>How am I supposed to drive these initiatives as an IC? There’s so much uncertainty and I don’t have the authority to change things.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zY9m8k8qs4Y17q2VTUqq2g.png" /></figure><h3>Embrace the Uncertainty</h3><p>The <a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">initiatives and problems you drive as a Product Leader are much more complex</a>, much less certain. Building confidence and alignment across an organization in the face of such uncertainty is difficult. But it’s all the more important because of that uncertainty.</p><p>When taking on larger initiatives — whether new product discovery, a major operational shift, or a change in strategy — there is not going to be an obvious right answer. You may never know the correct answer. No one will. But a plan needs to be made, and the job is creating and selling it in a way that folks will believe in it.</p><p>On larger organizational initiatives, you will rarely be able to get to the same level of confidence as you were able to reach at the team level. There are too many variables. Once you involve multiple products and multiple teams, the complexities increase exponentially. Greater dependencies between teams means reduced confidence in technical approaches and delivery dates. Making a change to your product offerings can have ripple effects on customer purchasing decisions.</p><p>Driving bigger changes means accepting you won’t have the perfect data to justify a decision. Instead, it increases the need to build confidence in that decision across an organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CU8EWiyjstDHq2qEZwqKdg.png" /></figure><h4>Collaborate to Build Confidence</h4><p>Collaborating with more leaders reduces uncertainty. It increases the likelihood that a plan will succeed. And critically, it increases other people’s confidence in the plan.</p><p>As a seasoned Product Manager, you should have honed your product instincts to identify major opportunities and risks. Other leaders across your organization likewise will have built up their own instincts that you should leverage.</p><p>Their instincts and experience can help fill gaps in your knowledge or identify risks that you didn’t see. They’ll connect you with data or individuals who can answer critical questions. And they’ll help you build a stronger case to get buy in from other stakeholders and the leadership team.</p><p>Effective collaboration is the foundation for the success of any major initiative. And the bigger the initiative, the more important that collaboration is.</p><blockquote>I can’t focus on organizational initiatives, I have a responsibility first to my team.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJSuvj6kiP05gvNXr_H5uw.png" /></figure><h3>Prioritizing the Team and the Organization</h3><p>Leaders often have to make hard prioritization decisions that impact multiple teams. Sometimes one team’s goals has to be deprioritized in favor of a more critical organizational goal. It’s not pretty, and it can hurt morale— but it sometimes needs to be done.</p><p>Learning how to balance the needs of the organization against the needs of your immediate team can be a difficult challenge. But your job isn’t just to be a great Product Manager for your team; it’s to be a great Product Manager for your organization. As a Product Leader, you need to prioritize your time and your teams’ time wisely to ensure the highest impact for the business and your customers.</p><p>There are two key challenges here:</p><ul><li>Putting the organization’s objectives ahead of an individual team’s objectives.</li><li>Balancing your time and effort between serving the organization vs. serving the team.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yeVVdAzet8iyrUWO-gI2Bg.png" /></figure><h4>Prioritizing the Roadmap to Serve the Organization</h4><p>There are often opportunities to support goals that don’t directly benefit your team, or slows your team down from achieving its goals. But taking these opportunities can drive better outcomes for the business, rather than if every team operated selfishly towards their own goals.</p><p>My team was working on a brand new product area, while most of the rest of the organization was working on <a href="https://construction.autodesk.com/">unifying our core products</a>. Our project was new and shiny, serving the goals of exciting our customers and driving new business opportunities. By contrast, the rest of the org’s work was less glamorous, but absolutely essential to the overall success of the business.</p><p>One of the teams we were partnering with — and were heavily dependent on — was falling behind on its roadmap. This team’s product area was a foundational piece of the unified offering, and a platform on which many other teams would be developing.</p><p>We could have protected our own goals and roadmap — eating down other features in our backlog while we waited for them to catch up, or building on their platform with narrowly scoped solutions that worked only for us. Instead we collaborated with them to take on several initiatives that unblocked our team but would also serve to expand their platform for other teams.</p><p>We cost ourselves some of our velocity towards our own goals, but we accelerated adoption across the organization. And we demonstrated that we could put the good of the organization ahead of ourselves.</p><p>An important part of making this kind of decision is being highly visible. Your manager and leaders should have insight into the decision making process to ensure that this is the best course of action for the business. And your leaders should be fully aware that you’ve put the needs of the organization first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TN9JaWFVY4k-gx2ObfL82A.png" /></figure><h4>Prioritizing Your Time to Serve the Organization</h4><p>As a Product Manager, it can be difficult to move your focus away from the team and towards side projects. But your time is a valuable resource and prioritizing that time ruthlessly is a necessary part of being a Product Leader. Over-investing in a single team becomes a waste of your skills as you grow more seasoned and capable of impacting an organization.</p><p>I had to find my own balance in taking on side projects for the organization and doing the work for my team. As the PM on a team, you need to continue to deliver results and ensure progress and challenges are communicated up to leadership. But a lot of the invisible work that PMs do to ensure the success of the team can become unnecessary or even counterproductive. In my past, I’ve pulled a lot of teams together through grit and duct tape. I’ve been the definer, driver, and maintainer of processes that kept the team moving fast. I’ve done a lot of QA to ensure features were delivered with high quality. I’ve pulled data to make decisions on minor interactions. At a certain point, all the extra work starts to have diminishing returns.</p><p>Additionally, taking on too much responsibility can actually hamper the team’s ability to succeed. You don’t want to be the bottleneck for every minor UI decision, or not be able to trust your devs to make sure that their work meets the design and acceptance criteria. You don’t want a release to become chaos just because you were out sick. You can infantilize a team by taking away all responsibility outside of committing code. Instead, aim to find a balance that ensures the whole team is responsible for the success of the team and the product.</p><p>When my team shifted from product discovery and prototyping to production of a beta MVP, I made a decision to be less involved in the details. This meant putting the responsibility of defining and maintaining processes on the developers. I set high level expectations and provided feedback, but left it to the team to work out how they wanted to operate. This resulted in a lot more sprint iterations to find the best way forward, but it empowered the individuals to own the process and the improvements. Likewise, I tried to find a balance in the detail of my specs and in answering questions vs. ensuring everyone understood the customer problems we were trying to solve and trusting them to come up with good answers on their own.</p><p>This is an entire topic of itself, but I sought an approach of “minimum viable product management” for day to day execution. I did enough to ensure that the team and product would be successful, without chasing the last 10% of optimal product execution. It wasn’t easy to find a balance, but my team was understanding. They respected and appreciated that I was trying to drive larger improvements across the organization, and many of the devs on my team appreciated the opportunity to take more ownership.</p><h3>Summary</h3><p>I had to shift my perspective in a number of ways before I embodied the qualities of the kind of leader I wanted to be. And it’s still a struggle. I can fall back on bad habits and negative mindsets. But I have a constant intention to live these values — to be more empathetic and collaborative; to embrace uncertainty; to take on the challenges that need solving. And this intention has changed the way that others see me and how I see myself.</p><p>Each individual will face their own internal struggles in becoming a leader; these were mine.</p><p>Next in the series, I start digging into the actual outcomes and impact you should aim for as you transition to Product Leadership. Next up, <a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Driving Business Outcomes and Impact</a> — Part 2 of the Becoming a Product Leader series.</p><p><em>Do you have similar stories in shifting your perspective to be more effective as a leader? Are there are other mindsets that you think are worth calling out? Please share them in the comments! And be sure to follow me if you want to stay updated on future articles.</em></p><ul><li><a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader</a></li><li><a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38e1d4bccd7" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Becoming a Product Leader — Part 1: Thinking Like a Leader</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a Product Leader — Introduction]]></title>
            <link>https://medium.productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce?source=rss-e2662e0710ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/3410931eb7ce</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[James Wang]]></dc:creator>
            <pubDate>Thu, 20 May 2021 21:57:03 GMT</pubDate>
            <atom:updated>2021-06-22T15:48:17.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ncmE-ERfaRFUo7B2cDod5Q.png" /></figure><h3>Becoming a Product Leader — Introduction</h3><p>This is an article series on moving from individual contributor Product Manager to people manager and Product Leader.</p><p>This is something that I’ve personally struggled with, and witnessed brilliant, hardworking, rockstar PMs struggle with. There are some solid articles on this already, as well as great guidance from the recent <a href="https://www.crackingthepmcareer.com/"><em>Cracking the PM Career </em></a>book. But I still feel like there isn’t enough information out there on how to make this leap. It pains me to watch amazing PMs become jaded or even toxic as they find that they can’t seem to break into the next level.</p><p>So I wanted to break down my understanding of the kinds of outcomes and behaviors necessary in moving from IC to people manager. In this series, I’ll be sharing my own experiences in struggling with understanding and demonstrating these outcomes and building these skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*EKscy_jnSe7VQIrq5AOQnw.png" /></figure><h3>A Big Leap</h3><p>The hardest gap to cross in the Product Management career (other than breaking into PM at all) is moving from individual contributor to people manager and Product Leader.</p><p>Others have expressed this quite well, but it’s worth reiterating: <a href="https://www.reforge.com/blog/crossing-the-canyon-product-manager-to-product-leader"><strong>what got you here won’t get you there</strong></a>.</p><p>As an individual contributor Product Manager, you can spend years honing your craft and focusing on doing your job better. You’ll see steady increases in scope and salary, moving from a junior PM, to mid-level, to Senior.</p><p>But at a certain point, all your hard work stops resulting in forward progress. You hit a point where you keep improving your skills, but you get passed over when that Group role that opens up. Or you max out on your capacity to drive initiatives, and you aren’t getting recognized for doing all the hard work. You get vague feedback on why you didn’t get the promotion, or unclear guidance on what you can do to position yourself for the next one. It seems like nothing you’re doing matters in making the leap to a Product Leader role (Lead Product Manager, Group Product Manager, Director, etc.).</p><p>Quite likely, you’re going about it wrong.</p><p>Just like breaking into Product Management, moving from an individual contributor PM into a managing PM is a role change. There are different responsibilities, different outcomes, different skills. Understanding this distinction is critical to successfully making the transition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*03yjoV9CFSVTwoP2oEIPxA.png" /></figure><h3>Product Leader vs. Product Manager</h3><p>Every good Product Manager is a leader. They lead their teams, building excitement on a product vision, roadmap, and features. They lead key projects and initiatives, driving collaboration across a myriad of stakeholders. They lead meetings, brainstorming sessions, customer research calls, and a multitude of interactions.</p><p>But being a Product Leader means more than being a great Product Manager. PMs tend to operate within a limited scope of responsibility, limited to one or two teams. And PMs tend to be the primary driver for those teams.</p><p>Being a Product Leader is about inspiring and leading other PMs and leaders in the org and across the company, far beyond the outcomes of a single team. It’s about stepping away from being the individual driver, and guiding others to drive big parts of an even bigger problem.</p><p>Additionally, managing other PMs is a unique challenge, and one that PMs might think they’ve experienced as a result of having led teams. The reality is that great hiring and recruiting is time consuming and challenging. Coaching and mentoring other PMs is not as simple as knowing the answer and making sure they do it. Fostering growth in your team and creating a positive team culture requires thought and intention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*QRmC9htM0gGaXgNMeaQjfA.png" /></figure><h3>It’s All About Trust</h3><p>Most great Product Managers could do a good job — even a great job — as a Product Leader. Eventually. If they got the opportunity, they could practice, get coaching, read books, do the work, and eventually become great. But getting that opportunity is where the challenge lies for a lot of PMs. Senior leaders don’t want to risk the harm a premature promotion can cause.</p><p>Having the potential to do the work is not the same as having done the work. Having the ability to shift mindset and focus is not the same as having already made that change.</p><p>You need to build trust with your manager, their manager, their peers, and with senior leadership that you can do the work and you can do it well.</p><p>So, what does this all look like?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*niiuFNEuNp-Ol20Ia_CrvA.png" /></figure><h3>What You Do and How You Do It</h3><p>Demonstrating product leadership is about driving major <strong>outcomes and impact</strong> and the <strong>skills and traits</strong> of doing it well. It’s about impact at the organizational and business level, instead of the team level. And how you collaborate, the attitude you display, and the atmosphere you create determine whether other leaders trust you to lead.</p><p>This is a five part series. In each article, I’ll provide guidance and perspective on what matters and why, and share personal examples on how I made these changes.</p><h4>Shifting Perspective:</h4><ul><li><a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Part 1: Thinking Like a Leader</a></li></ul><p>The first step of any journey is internal. The biggest obstacle I faced in making the transition from Product Manager to Product Leader was my own mindset and attitude. Shifting this perspective was fundamental to unblocking my progress.</p><h4>Driving Impact:</h4><ul><li><a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Part 2: Driving Business Outcomes and Impact</a></li><li><a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Part 3: Establishing Excellence in Product Management</a></li><li><a href="https://productcoalition.com/hiring-as-an-individual-contributor-part-4-of-becoming-a-product-leader-c0b6c3857cd1">Part 4: Hiring as an Individual Contributor</a></li></ul><p>This section covers the kinds of impact you should strive to achieve as a growing Product Leader. It’s about growing the organization and business via taking on larger initiatives, driving improvements in product processes, and leveling up the PM team.</p><h4>Collaborative Leadership:</h4><ul><li>Part 5: Influencing an Organization</li></ul><p>Collaborating with other leaders to influence and effect change across an organization is an ever evolving challenge and the cornerstone of great leadership. While individual initiatives may succeed or fail, how you worked with people along the way indicates whether you and your organization will be successful over the long run.</p><h3>About Me</h3><p>I wanted to mention a bit about my background to provide context for these articles.</p><p>I got my start as a Product Manager about eight years ago, in mobile free to play gaming. I spent about three and a half years in gaming, launching multiple titles and leading multinational teams. I built up expertise in data analysis, economic modeling, monetization design, and live operations and optimization. I directly managed multidisciplinary teams and led projects with up to 50 developers. I left my position as a Director in 2017 when I decided to switch to more traditional software products.</p><p>I worked at Evernote for just under two years. My first year I spent working on the Growth Experimentation team as Product Lead, where I worked with my peers to learn and define what Growth meant at Evernote. We found new success with this team, expanding to three full scrum teams. I spent my next year working on the iOS platform and in new product discovery, building a case and defining an MVP for <a href="https://evernote.com/features/tasks">Tasks</a>. This product was developed and released after I left, but it was based on the designs that my team defined and validated.</p><p>I moved to Autodesk in 2018, by way of the acquisition of PlanGrid, a construction productivity software solution. At PlanGrid / Autodesk, I managed one of our top used features across our entire construction software suite, while engaging in new product discovery for a feature that is now in beta. I applied and was promoted to Group Product Manager after a year and a half with Autodesk, after having built a case for a new product, coached and mentored several PMs, drove improvements to our hiring process, and led strategy on a large cross-organizational initiative. I now manage a team of three product managers, overseeing multiple product lines.</p><h3>Summary</h3><p>Becoming a Product Leader isn’t just about getting a promotion, a title change, or a new position. It’s about becoming the kind of person that can lead organizations and who other leaders want to follow. It’s a journey of many steps — from shifting your internal perspective, to taking on new and challenging initiatives, to practicing new ways of working with others. And each step on this journey will move you closer to being the kind of leader that you want to be.</p><p>When it comes to getting a title or promotion, there are no guarantees. This will not likely be a transaction in which you can negotiate, “if I do these three things, you will give me a promotion.” Instead, focus on becoming the person you want to be, and the opportunities will eventually align with your hard work and preparation.</p><p>With each article in this series, I’ll be sharing my perspective and personal experiences on the changes I made and the actions I took. I hope that the frameworks and examples help and guide you in your own journey towards becoming a Product Leader.</p><p>Next in the series, Part 1 of Becoming a Product Leader: <a href="https://medium.com/@James_Wang-Product/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Thinking Like a Leader</a>.</p><p><em>Thanks for reading! Let me know your thoughts in the comments, and be sure to follow me to keep up with each update.</em></p><ul><li><a href="https://productcoalition.com/becoming-a-product-leader-part-1-thinking-like-a-leader-b38e1d4bccd7">Becoming a Product Leader — Part 1: Thinking Like a Leader</a></li><li><a href="https://productcoalition.com/becoming-a-product-leader-part-2-driving-business-outcomes-and-impact-60a8d893a83a">Driving Business Outcomes and Impact — Part 2 of Becoming a Product Leader</a></li><li><a href="https://productcoalition.com/establishing-excellence-in-product-management-part-3-of-becoming-a-product-leader-bee8bf9b2011">Establishing Excellence in Product Management — Part 3 of Becoming a Product Leader</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3410931eb7ce" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/becoming-a-product-leader-introduction-3410931eb7ce">Becoming a Product Leader — Introduction</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>