<?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 Nina Leis Klein on Medium]]></title>
        <description><![CDATA[Stories by Nina Leis Klein on Medium]]></description>
        <link>https://medium.com/@ninaleisklein?source=rss-2cd8ab4f0659------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wa-eHpB6AUApvHiiTZRz6g.jpeg</url>
            <title>Stories by Nina Leis Klein on Medium</title>
            <link>https://medium.com/@ninaleisklein?source=rss-2cd8ab4f0659------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:21:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ninaleisklein/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[Interviewing startups: A product manager’s guide]]></title>
            <link>https://medium.com/@ninaleisklein/interviewing-startups-a-product-managers-guide-dfc3a8ecc110?source=rss-2cd8ab4f0659------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfc3a8ecc110</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Nina Leis Klein]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 03:35:13 GMT</pubDate>
            <atom:updated>2019-02-13T03:35:13.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1YximM0za-wsrmBaOB7xg.jpeg" /></figure><p>There is a lot of information out there intended to prepare people for interviews. And there are some awesome articles and books specifically for PMs (some links below). Many of these resources provide sample questions that interviewees should practice answering or provide tips on how to speak about your experience and how to position yourself and the skills you bring to the table, etc. Lots of great stuff, for sure!</p><p>But, as someone who has been on both sides of the hiring table in the startup world, I wanted to focus on a lesser discussed area of interview prep: preparing to interview the startup.</p><p>I want to start by making two statements:</p><ol><li>As an interviewer, there is almost nothing more impressive than interviewing a candidate who you <em>know</em> has done their homework.</li><li>As a candidate, because of the nature of startups, you really need to make sure that <em>this</em> startup is as much of a good fit for you as you are for it.</li></ol><p>These points are, of course, interdependent. You have to do your homework in order to understand if the startup is a good fit for you and in doing so you’ll be showing your interviewer that you’ve done your homework.</p><p>Startups need people who care. The stats for success are not in a startups favor, so startups need people who are not only good at their job but who care a lot about what the company is trying to accomplish and will go above and beyond because they believe in what they are doing.</p><p>In a startup environment, you want to make sure you can see (and share) the vision as laid out by the founder and that you like the people you’ll be working with. The company may not currently be making (a lot of) money, so you want to understand and believe in the direction they are headed. And, if you’re going to be stressed or working long hours, you want to make sure it’ll be around people you enjoy.</p><p>So, let’s get you ready!</p><p><strong>Do you homework</strong> — while this tip isn’t unique to startups, the biggest difference here is that there may be very little information publicly available on the company.</p><ul><li>If the company has a website, thoroughly explore it. If you have to register for an account to explore deeper, do it! (I’ll be honest, as a hiring manager, if someone I was interviewing hadn’t created an account, it felt a little lazy.)</li><li>Review the FAQs (if available) and jot down notes and questions.</li><li>Search for and read any press or customer reviews the company has received. Do customers seem happy with the product or service?</li><li>Check out Crunchbase to understand what investors, if any, the company has and Glassdoor (if they have a profile) to see what current or former employees have to say about the company.</li><li>Do a quick google search for the company or the service/product they offer — see what competitors pop up and give them a quick once over too.</li><li>For B2B sites, sign up for a demo of the product; read the training or help materials</li><li>For consumer sites, review the site, jot down anything that seems confusing or you think could be improved. Really like some design, functionality or feature? Jot that down too!</li><li>If the founders or other members of the team have Linkedin profiles, read up on them and their experience.</li></ul><p><strong>Come prepared with real questions.</strong> Write them down ahead of time and don’t forget to bring them with you. Coming with a list of thoughtfully prepared questions showcases your enthusiasm and genuine curiosity.</p><p>So, what should you be trying to figure out?</p><ul><li>Ask probing questions about the company vision and the problems they are trying solve. Again, when you work at a startup, it’s really important to believe in the vision.</li><li>Ask about the current business/revenue model and strive to understand any future revenue models. Though some people may disagree with me on this point, I think it’s important for you to get an idea as to how the company plans on making money in the future. Also, try to figure out how product and technology fits into the larger business. Does it feel more like a side project or the foundation for everything else?</li><li>Who does the company view as their competition? (Side note here, in my experience, if the company says they have no competition, they are wrong/not being honest with themselves and that should be a red flag for you.)</li><li>Ask about team structure — which players are already in place? How do they work together? What’s the company’s hiring plan? The answers to these questions will give you a little more insight into what your job will be now and in the future.</li><li>If you are the first product hire for the company, I always find it interesting to ask whether people have worked with a product manager before. You’ll want to understand the company’s understanding of the role or what experience they have had with it in the past.</li><li>What are the expectations for the role you are applying to? What will you really be responsible for in your day-to-day? Ask the hiring manager what skills they think a person who will succeed in this role should have.</li><li>Does the company already have a product roadmap? If so, what are some key items on it? How did those items make it onto the roadmap?</li><li>Ask the founder directly (but also others on the team) what he or she is like working for. What’s their management style? How do they deal with a scenario when someone disagrees with them? Are they more of an idea person or more of an operations person? (The product/CEO relationship in small startups is an important one — ideally, you are able to provide balance to one another. If both people are “idea people”, you may have trouble actually executing; if both people are more ops oriented, you may struggle a little with innovation. Ask questions to help you understand the CEO’s strengths and how you may be able to compliment them.)</li></ul><p><strong>Meet with as many people as you can, not just the hiring manager.</strong> Make sure you meet with someone (if not multiple people) from engineering, marketing and customer support (assuming they have people in these positions). As I mentioned earlier, you want to make sure you have work chemistry with those around you because you’ll likely be spending a good amount of time together. Tailor your questions to each persons specific area within the company but feel free to ask broader questions as well. Ideally, everyone in the organization should be able to speak to the vision and business model and understand how their role plays into that.</p><p>Approaching interviews with startups with genuine curiosity will not only set you apart from “the competition” but will also provide you with valuable insights to help you determine if this startup is the right one for you. Good luck!</p><p>Additional resources to help you prepare for an interview:</p><p><a href="https://hackernoon.com/how-to-prepare-for-a-product-manager-interview-6204b1ba5d6d">“How to prepare for a PM interview” by Vishal Sood</a> — thorough article that also contains lots of additional resource links at the end</p><p><a href="https://medium.com/pminsider/preparing-for-pm-interviews-how-to-get-there-in-15-20-hours-193f6fcbf606">“Preparing for PM interviews” by Fernando Delgado</a> — provides solid advice, broken down into hours, for preparing for your interview in 15–20 hours.</p><p><a href="https://www.amazon.com/Cracking-PM-Interview-Product-Technology/dp/0984782818/">Cracking the PM Interview</a> by <a href="https://www.amazon.com/Gayle-Laakmann-McDowell/e/B004BI1ZUQ/ref=dp_byline_cont_book_1">Gayle Laakmann McDowell</a> — a very popular resource for PMs; includes resume and cover letter help, sample interview questions, etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfc3a8ecc110" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The product role in early stage startups]]></title>
            <link>https://medium.com/@ninaleisklein/the-product-role-in-early-stage-startups-30e0569d5090?source=rss-2cd8ab4f0659------2</link>
            <guid isPermaLink="false">https://medium.com/p/30e0569d5090</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Nina Leis Klein]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 20:34:52 GMT</pubDate>
            <atom:updated>2019-02-04T20:34:52.636Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ueO5sJ-E0P2rLSHJtoq6xQ.jpeg" /></figure><p><strong>So you want to work as a PM at an early stage startup?</strong></p><p>That’s awesome! I love startup environments — they are exciting and energizing, fast and chaotic, stressful and rewarding. Opportunities and challenges are around every corner and because things move so fast, you can see how your contributions create real value for the business in a much shorter timeframe. As a PM considering entering this environment, here are some tips I’ve learned along the way to prepare you for your startup adventure…</p><p><strong>Be prepared to be a generalist.</strong> There are a lot of tasks that product managers should try <em>not</em> to spend their time on: project management, QA, product design, customer support or sales demo-er, technical copywriter, etc. In an early stage startup environment, however, its very possible you will be asked and should be prepared to incorporate these additional tasks into your workload. Start ups are “all hands on deck” environments — you do what needs to be done and must maintain a positive attitude about it.</p><p>If you find yourself so consumed with tasks unrelated to what you really need to be doing and what you were hired for, it’s definitely time to talk to your supervisor (a lot of time the CEO or founder). Involve them in brainstorming ways to shift things around so you can focus more on what you feel is most important. Don’t be afraid to talk about the organization’s hiring needs — while it may not be something that the company can accommodate in that moment, they should at some point in the future and having that discussion can be beneficial for everyone involved.</p><p><strong>As your company grows, be prepared for your role to “shrink”.</strong> But this is a good thing! Embrace the opportunity to give up some of the above tasks in favor of the things you really should be focused on as a PM (an incomplete and un-prioritized list to follow) ie. talking to and understanding your customer, finding solutions to business problems, looking at data, testing your ideas via prototypes, compiling requirements, working with your tech teams/designers, communicating, listening, strategizing, prioritizing, etc.</p><p>I’ll be honest, this can be hard at first — you’ve gotten used to being involved in everything and it can be difficult to let go. I’ve seen this happen not just with product managers but with a lot of early employees, across functions. If you start to feel FOMO (fear of missing out), give yourself a little pep-talk to get excited for all the product-y things you now get to do that you weren’t able to before. You’ll soon start to feel much more productive and that’s a wonderful feeling!</p><p><strong>If you’re the company’s first PM hire, be prepared for a little bit of ‘process’ friction.</strong> Very early stage companies don’t have a lot of process or structure in place which is beneficial in a lot of ways as it allows them to move, adjust and adapt very quickly. It’s survival of the fittest out there! However, as a PM, people will be depending on you to help set up some process and structure — while everyone will benefit from this in the long run, it can feel uncomfortable at the beginning. Be empathetic, realize the organization is in an adjustment period. Be super communicative about any new processes and why its important.</p><p>Personal anecdote to illustrate this point: I joined a very small (like 10 people) startup a few years ago, as the company’s first PM. The company had a vision but no roadmap and no processes in place for their development team. People would literally just shout across the room for a developer to come over for everything from “can you fix this bug?” to “it’d be great if we had this feature” to “why can’t I find this email??”…As you can imagine, this was pretty disruptive to the team and the features they were suppose to be working on. Setting up a process for reporting bugs and collecting ideas drastically improved the engineers productivity and benefited everyone in the company in more ways than one even though, at first, it felt more tedious to follow the new bug/idea reporting process vs. shouting. (I am not sure I ever really got people to understand software engineers and IT support were in fact different but my dev teams were always very helpful people and would give computer problems a shot!)</p><p><strong>Embrace evolution. </strong>As new information is gathered and as the company narrows in on product-market fit, your product strategy will likely evolve. Be open to this evolution and embrace the new challenges and opportunities it brings. I hear people in startups comment a lot about how quickly things change; change can be exhausting, frustrating and uncomfortable. But a lot of times, it is a necessary part of a startup’s life. Ideally your company knows its true north, sometimes it just need to shake the compass a little bit to re-find it. <em>(Side note, if your org is struggling with this, have people take a read through “Who Moved My Cheese” by Spencer Johnson — while from the late 90’s I still think its relevant when it comes to dealing with change in life and work.)</em></p><p>With this likely for change in mind, understand that the timeframe for your product roadmap will likely be in weeks and months vs. quarters or years. As the company grows and your product-market fit is established, the timeframe within which you can accurately plan your roadmap should increase. Trying to plan too far out when the environment is volatile can result in a lot of wasted effort. (Another side note, this <em>does not</em> mean to not establish a vision, you should <em>absolutely</em> do that. Just don’t try to plan out a multi-year roadmap — focus your energy and thoughts on other things.)</p><p><strong>Be prepared to set the stage for your future teammates.</strong> You may have the opportunity/responsibility to establish your company’s product management process and culture. Whether you have years of experience under your belt or this will be a first for you, plan to invest some real time and thought here. Read books and blogs, talk with other PMs, attend product management conferences or events, etc. Invest in learning about different methods and approaches; don’t be afraid to test things out and make adjustments as necessary.</p><p>Every so often my Tech Lead and I would want to try out something new we thought might be more efficient or somehow beneficial to our teams; we’d give it a try for a defined time period, then do a retrospective on it at the end of the time period, gathering our team’s feedback, and making changes as needed. Much like with the products we build, our processes need iteration and, in my experience, its good practice to include those that the processes impact, into the conversation. And while this doesn’t mean everyone always gets what they want, a team that feels empowered, that their ideas matter, and they can help own the solution, will be a happier, more productive team.</p><p>Read the above and ready to roll? Coming soon, some tips for preparing for a PM interview with a startup!</p><p>Worked in product for a startup? What else should new comers know? Share your thoughts and tips in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30e0569d5090" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best practices for onboarding your new Product Manager]]></title>
            <link>https://medium.com/@ninaleisklein/best-practices-for-onboarding-your-new-product-manager-df73dbf246fc?source=rss-2cd8ab4f0659------2</link>
            <guid isPermaLink="false">https://medium.com/p/df73dbf246fc</guid>
            <category><![CDATA[new-hire-onboarding]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nina Leis Klein]]></dc:creator>
            <pubDate>Tue, 29 Jan 2019 20:01:00 GMT</pubDate>
            <atom:updated>2019-01-29T20:01:00.972Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*986Q8Grkk-iKHYYk8fqEeQ.jpeg" /></figure><p>Starting a new job comes with lots of emotions: excitement, anticipation, and fear, to name a few. For both new team members and supervisors, it can all be a bit overwhelming. As a supervisor, you are probably really excited to have another set of hands joining your team, but getting someone new up to speed can take a lot of thought, time, and energy. Here are some best practices to help you create a great onboarding experience for your newest team member.</p><p><strong>Pre-schedule meetings/meet &amp; greets with all relevant departments</strong></p><p>Product managers must interface and build relationships with a lot of departments and people. Help kickstart these relationships by pre-scheduling meetings on behalf of your new hire. Once you know the person’s start date, get their email set up so you can schedule short (20–30 minute) ‘meet &amp; greet’ type meetings with key departments/people. (If you wait till your new hires first day, you may have a hard time getting time on other people’s calendars.) In the calendar invite, be sure to write a little intro about both the new hire and the person they will be meeting with in order to provide a bit of context for both parties.</p><p>Have reoccurring meetings with departments in place? Don’t forget to add your new PM to the calendar invites, as needed.</p><p><em>(As a side note, I like to print out the person’s schedule — with their name on it — for the week and place it on their desk/workstation. I know that seems kind of old school but I’m telling you, new employees love it.)</em></p><p><strong>Provide a checklist of action items for your PM to complete</strong></p><p>Let’s be honest, PM’s love checklists. And there is no better way to help your new hire feel both organized and accomplished than by providing them with a checklist of tools to explore (make sure you include sign in credentials if they already exist), documentation to review, initial assignments to complete, etc. It’s also a great exercise to have your newest hire be responsible for going back through this doc and adding/updating/revising for future hires.</p><p><strong>Product Walkthrough</strong></p><p>This is a crucial piece of onboarding and, depending on the complexity of your product or products, may span multiple meetings with multiple people. At the very least, have the user facing product walkthrough be led by your previously most recent product hire — if that makes sense in your organization — and let your newest hire know they will have the opportunity to lead the product walkthrough for a future hire.</p><p>It is also crucial that your new PM sit down and do a product architecture walkthrough with a tech lead. The focus of this walkthrough will, again, depend on your product and architecture but ideally your new PM will come away with a high-level understanding of what systems are in place and how they are connected.</p><p>If possible, for both of these meetings, have your new PM come away with a diagram or other documentation they can revisit later on; if this type of documentation doesn’t exist yet, have your new PM be the person to put it together (the walkthrough leads can serve as mentors here too).</p><p><strong>Add a team lunch to the agenda</strong></p><p>Getting everyone together for a laid-back lunch is a great way to introduce your newest member to the team and allow them to take a little breather. If your team is really big, choose a handful of people (4 to 5); a smaller group will make conversations easier, more informative and less overwhelming.</p><p><strong>Day 1 meeting with supervisor</strong></p><p>Take this opportunity to provide a high-level overview of the product vision/strategy/roadmap. This provides context for your new PM and will help them understand how they fit into the broader vision. Also be sure to discuss expectations for the person in this role (and how this role plays with the other roles on the team). The PM role and team structures can vary significantly between companies, so taking the time to make this clear from the get-go will benefit everyone.</p><p><strong>End of week meeting with supervisor</strong></p><p>Your new PM has just completed their first week! Hurray! Be sure to get time with them before the end of day to do a recap of the week, answer questions, review any assignments, and discuss the plan for the following week (what he or she will be working on, etc.). In my experience, it’s nice to end your first week knowing what’s coming up next.</p><p><strong>A little pre-planning goes a long way</strong></p><p>Investing the thought, time, and energy in your new product manager’s on boarding experience will pay dividends in the long run. Not only will he or she be able to hit the ground running faster and more competently, they will feel like a valued member of the team right out the gates, which, in turn, helps create a happier, more productive team member for years to come.</p><p>What else makes for a great onboarding experience? Share your thoughts in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df73dbf246fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>