<?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 Product Queen on Medium]]></title>
        <description><![CDATA[Stories by Product Queen on Medium]]></description>
        <link>https://medium.com/@cindyadem?source=rss-29340f9b7515------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QYEjzJyx-JSM2SZt2mU9XQ.png</url>
            <title>Stories by Product Queen on Medium</title>
            <link>https://medium.com/@cindyadem?source=rss-29340f9b7515------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:41:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cindyadem/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[Road to Release: Your step-by-step guide to beta-testing in 2023]]></title>
            <link>https://medium.com/is-that-product-management/road-to-release-your-step-by-step-guide-to-beta-testing-in-2023-e88c9bd3bcf7?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/e88c9bd3bcf7</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[beta-testing]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Sun, 18 Jan 2026 02:32:51 GMT</pubDate>
            <atom:updated>2026-01-18T02:32:51.962Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to avoid crashing on take-off by testing your product with real users</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8H9sTQA1ZVttjtGB" /><figcaption>Photo by <a href="https://unsplash.com/@mbuiux?utm_source=medium&amp;utm_medium=referral">Mohamed Boumaiza</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>You want to ensure your product doesn’t suck</strong></p><p>Have you ever visited a website and you were left wondering whether it was built by a chaotic bat; or downloaded an app you were excited about but soon after aborted mission because, <em>“who built this thing and what were they thinking?”</em></p><p>No?</p><p>Okay, at the very least you have encountered a situation where an app you like or need was inconvenient in specific ways. Either it takes forever to send an OTP, or a button hides a key component you want to use, or for the life of you, you cannot remember where you need to click to do a specific key task because its hidden under several vague menus.</p><p>Such scenarios are key indicators of ineffecient or insufficient user testing exercises; where the product or QA team failed to catch bugs or ask the right questions to test users- if at all they tested with actual users.</p><blockquote><em>Alpha and Beta tests are part of the user acceptance testing (UAT) process. UAT is designed to help the product team investigate whether the software developed meets business and end user needs and works as anticipated.</em></blockquote><h3>User acceptance testing is important because:</h3><ul><li>It helps in the <strong>detection of bugs</strong> so they’re quickly fixed before they annoy mass users.</li><li>It’s part of the <strong>quality assurance</strong> process that ensures you sort out any issues that could prevent your app from being blocked by app stores.</li><li><strong>Usability testing</strong> that ensures the app or website works in predictable and similar ways regardless of the device being used to access it.</li><li>It helps you <strong>test the performance</strong> of your software when it’s being accessed by multiple people; things like loading speed, errors and seamlessness are critical to check.</li><li>It helps in <strong>spreading product awareness</strong> since it can be used as a marketing strategy with your targeted end users. A well organized test process can help you acquire and retain your first group of real users.</li></ul><p>There are a few fundamental differences between Alpha and Beta tests. In this article, we’ll focus on how to plan and execute beta testing like the boss you are.</p><p>But first;</p><h3>Differences between Alpha and Beta testing:</h3><p><strong>Alpha Tests</strong></p><ol><li>​Usually performed by internal employees</li></ol><p>2. Often perfomed in an internal testing environment (deveoper’s site)</p><p>3. Minimal or no focus on security and reliability</p><p>4. Critical issues are directly fixed and addressed by developers.</p><p>5. Ensures the quality of the product before moving to beta testing</p><p><strong>Beta Tests</strong></p><ol><li>Usually performed by end users who are not part of the company/org.</li></ol><p>2. Performed in a real-time environment that’s available to the public</p><p>3. Testing is focused on reliability, security, seamlessness and robustness</p><p>4. Also focuses on product quality, but with user’s feedback to ensure readiness for mass real-time users.</p><p>5. Feedback is collected and can be addressed immediately or on a rolling basis based on urgency and product roadmap.</p><h3>Three Beta testing tools you can leverage:</h3><ol><li><a href="https://developer.apple.com/testflight/">TestFlight</a>: You can invite up to 10,000 testers using just their email address or by sharing a public link. Testers can download it from the AppStore. Up to 100 apps can be tested at a time. TestFlight supports apps for iOS, iPadOS, macOS, tvOS, watchOS, and iMessage.</li><li><a href="https://firebase.google.com/products/crashlytics/">Firebase Crashlytics:</a> This is a real time crash reporting tool, helps you prioritize and fix your most pervasive crashes based on the impact on real users. Crashlytics also easily integrates into your Android, iOS, macOS, tvOS, and watchOS apps.</li><li><a href="https://testfairy.com/">TestFairy</a>: Works on both iOs and Android and allows users to report bugs by shaking their device or just clicking on a button and sketching on the screen. TestFairy includes an enterprise-grade app distribution platform for iOS and Android that is highly configurable, tightly secured and can sync with your corporate Single Sign-on.</li></ol><h3>How to map out your beta-testing roadmap:</h3><h3>Stage 1: Getting Launch Ready</h3><ol><li><strong>Key Features Developed: </strong>There needs to be something to be tested. And you want the critical features ready to be brought to the test group.</li><li><strong>Acceptance criteria well defined: </strong>ACs guide the testers to measure whether the feature meets the specified expectation. Well defined criteria can be answered using a yes or a no.</li><li><strong>Software/App Pushed to Test Environment: </strong>The initial test environment for Alpha testers is usually a sandbox or a developer’s site. The App/Sotware should be available in that environment to allow for testing.</li><li><strong>Alpha testers added to sandbox/test environment: </strong>Alpha testing is done in a closed environment with limited access. The testers (usually internal team members) have to be added into the environment so they can access the app/software for testing.</li><li><strong>Internal Alpha-testing of App completed: </strong>Internal alpha testers mark yes or no on the acceptance criteria of specific features to indicate whether they work as stipulated or not.</li><li><strong>App pushed to production:</strong> Once the alpha test is done and changes made, the developers push the app/software to production (ie AppStore/Playstore) or soft-launch the website so it can be accessed by the public/beta testers.</li></ol><h3>Stage 2: Beta-Planning</h3><ol><li>​<strong>Create beta- test SMART goals and tasks: </strong>Specify the tasks you want to test through the beta-test expercise, and the goals you want to achieve with the exercise. Some key goal-setting questions could include: What do you want from this beta program? Will you be engaging these users on a weekly, monthly, or quarterly basis? How will you be engaging them? Will it be simply for new features or innovation and new product releases? How often will you require them to give feedback?</li><li><strong>Finalise on the testing strategy to be used: </strong>This could include specifying whether it’s virtual, in-person or both; how long the testing period will last, what rewards (if any) will be offered to the testers, and where the testers will be found.</li><li><strong>Assign team responsibility in the testing process: </strong>Ensure every stakeholder knows their role and the associated deadlines; this includes any review or approval processes (such as budgetary approvals)</li><li><strong>Narrow down specific dates and deadlines: </strong>You want to be have a limited window so that testers stay engaged and prioritize the process.</li><li><strong>Decide on any beta-testing tools needed, where appropriate: </strong>​Test your new software on multiple platforms and beta-testing tools. Depending on the software, this could involve testing it on both MAC and PC computers, both iOS and Android mobile device, and Chrome, Edge, and Safari internet browsers. The software could behave differently across different platforms. Different testing tools/platforms allow you to test for specific things, so choose approriately.</li><li><strong>Create a communications plan/strategy for the beta-testing exercise: </strong>Timely, clear and targeted cross-functional and external communication makes for a seamless testing exercise</li></ol><h3>Stage 3: Legalities and Shortlisting</h3><ol><li><strong>Prepare an NDA and Participation Agreement for testers to sign: </strong>You don’t want your idea stolen before it makes it to the market; or to get sued because you processed a tester’s personal information without express permission.</li><li><strong>Create ideal test-user persona: </strong>You want your target market to make a significant part of your test user group, so you know that you’re building something YOUR users want.</li><li><strong>Coordinate with internal teams to help shortlist potential test users: </strong>Customer success, social media team and sales team can help curate targeted, precise list of users who fit your test group persona.</li><li><strong>Reach out to communities where test users are likley to be: </strong>You want to let people know you’re ready for launch and keep them excited to receive a solution to a problem they’re facing. Excellent marketing</li><li><strong>Settle on dates and locations or virtual rooms for the beta-testing: </strong>You want to communicate, well in advance to your test users the logistics around the exercise.</li></ol><h3>Stage 4: Beta-testing</h3><ol><li><strong>Specify internal team members to beta-test and their locations (if in-person):</strong> Relevant team members need to own specific parts of the testing exercise; and team can map out availability.</li><li><strong>Organize logistics for team members (digital or physical): </strong>Prior preperation helps everyone feel in control and prepared to do their best work.</li><li><strong>Organize logistics for testers, if necessary (internet, location, transportation and meals; if in-person): </strong>Users should feel that you care about their convenience.</li><li><strong>Communicate relevant information with beta-testers consistently: </strong>You want as many shortlisted participants as possible to show up for the testing exercise.</li><li><strong>Conduct the testing over the specified range of dates: </strong>Time to know whether you’ve built something worth having.</li></ol><h3>Stage 5: Beta Feedback</h3><ol><li><strong>Bug reports:</strong> Fix them before they annoy and frustrate everyone else.</li><li><strong>Submit Feature requests or improvements</strong>: You know what your users want more of; add it to your backlog and you’ll refine it later.</li><li><strong>Journal/Note-take: </strong>Take real-time notes of your observations and insights you gather as you carry out your exercise</li><li><strong>Evaluate Feedback:</strong> Ensure you come up with the correct POV when you look at the feedback in toto.</li><li><strong>Map required changes where necessary</strong>: ​Groom the backlog of feedback into <em>now, next and never</em> columns of changes to be made.</li></ol><h3>Stage 6: To the Moon!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*6Kp1hvJMjMUOL60x" /></figure><h3>Beta testing as a beginner:</h3><p>As a PM, you’ll encounter your very first user testing exercise. Or, an opportunity to stop limping through the process and do it well.</p><p><strong>I’ve created a user-testing playbook that helped me facilitate cross-country testing exercises, leading to my promotion just 8 months into my first product role. This playbook is now available on Gumroad and is filled with Notion templates that will help you plan the logistics, communicate with users effectively, and record their feedback.</strong></p><p>With this playbook which includes other resources that are helpful for a new PM, you can take the guesswork out of user testing and ensure that your products are designed to meet the needs of your users. Don’t miss out on this opportunity to take your product strategy to the next level.</p><p><a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">You can get the Testing Textbook here</a></p><p>My name is Cindy aka Product Queen. I’m a non-coder of a PM who got promoted 8 months into my first ever official product role because of my capacity to create processes from scratch and collaborate like a boss.</p><p>Find my portfolio <a href="https://www.productqueen.co/">here</a> where I also take product newbies through specific ways to kick ass as a new PM.</p><p>You can check out the PQ Kickstart Kit for brand new PMs <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e88c9bd3bcf7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/road-to-release-your-step-by-step-guide-to-beta-testing-in-2023-e88c9bd3bcf7">Road to Release: Your step-by-step guide to beta-testing in 2023</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting to Product-Market Fit (1)]]></title>
            <link>https://medium.com/@cindyadem/getting-to-product-market-fit-1-1346c455e022?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/1346c455e022</guid>
            <category><![CDATA[product-market-fit]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Wed, 17 Jul 2024 19:01:05 GMT</pubDate>
            <atom:updated>2024-07-17T19:01:05.567Z</atom:updated>
            <content:encoded><![CDATA[<h3>If you have to ask if you got it, you likely don’t. Here’s how to get there.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Unr1fxhrBVBpJ2UG" /><figcaption>Photo by <a href="https://unsplash.com/@powwpic?utm_source=medium&amp;utm_medium=referral">Inés Álvarez Fdez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><em>Product-Market-Fit is mostly like skiing downhill. Exhilarating, demanding, and with ‘gravity’ doing most of the work. Understanding the section of the terrain you’re working with helps you pull out the best tools and skills so you land safely.</em></blockquote><p>Consider me Exhibit A of a product person who once erreneously claimed PMF. Earlier in my career as a founder, once we got to 20–30 paying and enthusiastic users, I made the mistake of thinking we had gotten to the promised land. Newsflash: we had not. And so we optimised too soon. Spent a bunch of bootstrapped funds in campaigns and features that were premature and disconnected us from what the market needed from us at that time.</p><p>Yep. We landed on our faces. But not before we put in effort equivalent to skiing uphill- doable but unsustainable.</p><h4>Today, we’ll talk about the 4 stages of Product-Market-Fit and what the first stage requires from you as a PM of a new-to-the-market product.</h4><p>First things first, let’s break down the PMF spectrum. According to our friends at First Round Capital, there are four general stages of PMF:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_tZURHJplRr_1MMMCRuOg.png" /></figure><p>1. <strong>Nascent</strong>: You’ve got a handful of somewhat engaged and happy initial customers, but things still feel early and messy. (Spoiler alert: This is our focus today!)</p><p>2. <strong>Developing</strong>: You’re making progress, but not quite there yet. Lots of iteration still needed in your product or marketing efforts. Likely navigating lots of complaints from users.</p><p>3. <strong>Strong</strong>: You’re onto something big! You can handle the demand but you’re beginning to feel stretched out.</p><p>4. <strong>Extreme</strong>: Skiing downhill. The momentum of demand has an energy of its own. In some ways, things feel out of control. Your product may not be perfect (is it ever?), but people want a piece of what you’re selling faster than you can service them. Scary but exhilarating.</p><blockquote><em>Now, the speed with which you can get from Nascent to Extreme PMF largely depends on how big of a problem you’re solving, and how fast you can get your users to decide that its a problem they want solved.</em></blockquote><p>If you’re ChatGPT, then it’s taking you 5 days post-launch to get to 1 million users (must be nice). If you’re not, then you’re likely going to go through the 4 stages of PMF like the rest of us mere mortals.</p><p><strong>Note: Products can go from ‘Extreme’ PMF to any of the earlier stages when market forces change, and there’s need to restrategize on how to adapt to that change. eg. Clubhouse after Twitter created Spaces.</strong></p><h3>Nascent PMF: Early Romance</h3><p>So, what exactly does Nascent PMF look like? Picture this: You’ve got 3–5 customers in B2B who are actually paying you money. I know, it doesn’t sound like much, but trust me, it’s enough to get those early signals of Product-Market Fit. It’s like the first spark in a relationship — small, but potentially explosive.</p><p>What’s Your Product at This Stage?</p><p>Here’s a fun fact: Your “product” at the Nascent PMF stage doesn’t have to be a fully-fledged app or platform. It could also be:</p><p>- A humble spreadsheet</p><p>- A rough prototype you’ve put together in Figma or similar</p><p>- A snazzy presentation on Miro/Canva</p><p>- Or even just a service you’re providing</p><p>Remember, we’re in the early days here. It’s all about proving the concept and getting that initial validation.</p><h4>Finding Your First Customers: The Hunt Begins</h4><p>Now, you’re probably wondering, “Cool, but how do I find these elusive first customers?” There’s a couple of ways:</p><p>1. Dust off that phonebook (yes, cold call- literally)</p><p>2. Dive into social media and online groups (try not to be spammy)</p><p>3. Leverage warm intros (time to call in those favors)</p><p>4. Tap into VCs, advisors, and mentors (they’re not just for funding, you know)</p><p><em>Pro tip: Get yourself a Market-Problem Map. It’s like a treasure map, but instead of gold, you’re finding your way to product-market fit. Here’s a </em><a href="https://miro.com/miroverse/market-problem-map/"><em>Miro template</em></a><em> you can use.</em></p><h4>The Sweet Spot of Nascent PMF</h4><p>Alright, so you’ve got a few customers. But what does success in Nascent PMF actually look like? Here’s the breakdown:</p><p>1. <strong><em>Mission Critical</em></strong>: They pay you. Yes, it’s that simple. If they’re willing to part with their hard-earned cash for your product, you’re onto something.</p><p>2. <strong><em>The Optimization Stage</em></strong>: Focus on increasing satisfaction with your product. Happy customers lead to more customers.</p><p>3. <strong><em>The Venn Diagram of Success:</em></strong> You want to hit that sweet spot where Willingness to Pay (WTP), Minimum Viable Product (MVP), and Minimum Viable Segment (MVS) all overlap. It’s like the holy trinity of product development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aX28z8tyJDiYMf-YA544Lw.png" /><figcaption>When MVP, MVS and WTP intersect, you know you’re killing it at the nascent PMF stage</figcaption></figure><h4>Yellow Flags: When Trouble’s Brewing</h4><p>Paying customers are great!! However, while you’re on the right track, there’s still a risk of being run over. Here are some yellow flags to keep an eye out for in the next 9–12 months:</p><p>- Nobody would be really sad if your product disappeared (ouch!)</p><p>- Your customers can’t fully articulate what they love most (or dislike) about your product (indecisive much?)</p><p>- It’s incredibly hard to find new customers (like rolling a boulder uphill)</p><p>- Usage is lower than a snake’s belly (red alert)</p><p>If you spot these warning signs, don’t panic! It’s time to change at least one of the 4Ps of Product-Market Fit: Persona, Problem, Promise, or Product. Think of it like a product remix — sometimes you need to change the beat to get people dancing.</p><p>So, how do we then navigate the testy nascent stage? Go-To-Market Strategy Options</p><p><em>1. Understand where you are currently positioned with relation to ‘The Chasm’.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*u1LBOdvCWsawptJY8ldO1w.png" /><figcaption>From Crossing the Chasm: Geoffrey Moore</figcaption></figure><p>Nascent stage by default means you’re either still at the early adopters stage or in the chasm figuring out how to cross it. The chasm has been a Bermuda Triangle for many startups or products which have struggled with how to get to the other side.</p><p>For this, check out ‘<a href="https://www.amazon.com/Crossing-Chasm-3rd-Disruptive-Mainstream/dp/0062356852">Crossing the Chasm</a>’ book by Geoffrey Moore. A key strategy for product folks on how to cross this chasm is to focus on one key user profile before going to the next. Leveraging product-led growth can also give you extra insight into what kind of users are most drawn to your product and optimizing for this target group should you see sustained interest.</p><p><em>2. Clarify your Early Customer Profile (ECP) vs your Ideal Customer Profile (ICP).</em></p><p>Know the difference. Your early customers might not be your ideal long-term customers, and that’s okay! However, when you’re able to gain clarity on who your ICP is, then you can build a product with those user stories in mind. Skipping this step, in the long run, will likley result in having dissatisfied customers or being stuck servicing a group that doesn’t fit the vision of the product or company.</p><p>For instance if you were a B2B SaaS and you want to position yourself for the high-end client base, you could slowly start introducing credit card requirements for free trial signups for users who may not meet your ICP checklist. This self-selects the ideal group that will take you from <em>Nascent</em> to <em>Developing</em>.</p><p>Remember, finding Product-Market Fit is like solving a complex puzzle. It takes time, patience, and a whole lot of trial and error. But with these insights in your PM toolkit, you’re well on your way to cracking the code.</p><p>Until next time, keep innovating, keep iterating, and most importantly, keep having fun with your product journey!</p><p>Heya! I am a PM, and you can check out my blog <a href="https://www.product-queen.com/product-blog">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1346c455e022" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 skills you need to supercharge your performance as a non-technical product manager]]></title>
            <link>https://medium.com/is-that-product-management/4-skills-you-need-to-supercharge-your-performance-as-a-non-technical-product-manager-7ab76e1930d4?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ab76e1930d4</guid>
            <category><![CDATA[product-management-skills]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 10:42:23 GMT</pubDate>
            <atom:updated>2026-01-18T02:31:44.305Z</atom:updated>
            <content:encoded><![CDATA[<h3>Here’s where you can start in your journey to Upskill as a non-technical product manager</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1nRndOKuZpRwdEpo" /><figcaption>Photo by <a href="https://unsplash.com/@cookiethepom?utm_source=medium&amp;utm_medium=referral">Cookie the Pom</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4><strong>Just because you can’t code, doesn’t mean you can’t be ‘technical’:</strong></h4><p>You do not need to be the CR7 of your product, your superpower should be more focused on how you bring in the Ronaldos, Serenas and Beyoncès in your immediate team and greater org to play together. Still, for you to know how to orchestrate like the pro you are, you have to know your keyboard.</p><blockquote>As a product manager, if you’re not growing, you’re wilting. Your basket of skills needs to keep expanding with tools, insights and techniques that you can leverage for the eagle’s view that PMs are expected to have. -PQ</blockquote><p>Here’s some skills you need to learn so you can serve your team well:</p><h3>Data Analytics</h3><p>You need to be able to follow what’s happening in your product. What are the key metrics you’re optimising for and how’s the movement looking? Are your users dropping off like flies or should you be thinking about a glorious IPO and that hidden island you’ve been fantasising about.</p><p>You need to be able to segment your users, relate different datasets to pull out specific insight and more than that, you need to be able to communicate the key take-aways from those numbers and what it means for the next strategic steps.</p><p>Some great starting points to your data journey is SQL, Excel, Tableau and PowerBI. If you’d like to play around with code, dip your feet into Python and see what magic it can do for you.</p><p>You can learn these skills very affordably (or close to free) from DataCamp, LinkedIn Learning, Coursera and Udemy.</p><h3>Project Management</h3><p>Yes, yes… we know product management is different from project management. In an ideal world, there would be a surgically clean delineation between what you do in product and what project managers should do. However, a lot of times, you could be required to pull out some project skills to perform well.</p><p>Your ability to make product-adjacent plans with specific timelines, your knowledge of collaboration tools like Asana, Jira and Trello, budgeting resources, etc will come in handy when you have a product to run and sometimes people to manage.</p><p>You do not need a PMP certification, just arm yourself with a one-day online course that will teach you what you need to know.</p><h3>User Experience Management</h3><p>As a PM, your heartbeat needs to align with that of your user. You always want to build for the people who power your product. This means that as much as is possible, you need to consistently aim for excellence in the <a href="https://uxplanet.org/characteristics-of-a-good-user-experience-bce6fdbeaacb">four-part User Experience test</a>: Usable, Enjoyable, Equitable (or accessible) and useful.</p><p>While being great at this skill could include being able to wireframe user journeys on tools like Figma or Miro (or a piece of paper), a big chunk of it is your ability to talk to your users, to observe how they’re using your product (sometimes in person), to actually <a href="https://www.productqueen.co/product-discovery-as-a-product-manager">source for complaints about your product</a> and to do your darnedest to polish it up into something that is delightful to use.</p><p>Google has an excellent course on User Experience Design. <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwj94YrBv8j6AhUthP0HHQsvAkcQFnoECAkQAQ&amp;url=https%3A%2F%2Fgrow.google%2Fcertificates%2Fux-design%2F&amp;usg=AOvVaw3v1FThOxJXKdry6UX8A7g4">Check it out</a>.</p><h3>Design Thinking</h3><p>I once heard a story where some non-profit went to dig a borehole in a remote desert in an African country so that they could save the women from having to walk 5km to and fro the river. Sounds really altruistic, impactful and thoughtful, innit? Except a week or so later, the brand new borehole was poisoned and the women resumed their daily 5km treks to the original water source. Wild.</p><p>Thing is, had the good non-profit folks actually talked to the women, they would know that the daily trek was their daily break. They could get together, talk girl stuff, provide emotional and social support to each other and only focus on themselves. Taking away this experience from them was not a favour. It was detrimental to their well being.</p><blockquote>Design thinking is the process you would use to co-create solutions with your end users. It begins with empathising with your user’s needs. This could sometimes look like spending time, physically with them in their natural environment and observing how they go about their daily lives, what problems they face and how they solve them, and having non-leading conversations with them.</blockquote><p>As a P.M, a design thinking mindset will help you build something people want, and not get your brand new well poisoned. If you have the budget, you can learn it from <a href="https://online.hbs.edu/courses/design-thinking-innovation/">Harvard Online here</a>. Or you could take this workshop from the <a href="https://www.wickedproblemsolver.com/?s_kwcid=AL!8620!3!524622092552!e!!g!!design%20thinking%20course&amp;utm_job_number=125&amp;utm_region_name=safrica&amp;utm_funnel_stage=customer_acquisition&amp;utm_marketing_channel=paid_media&amp;utm_marketing_subchannel=search_ppc_branded&amp;utm_start_date=05122022&amp;utm_end_date=12312022&amp;utm_source=google&amp;utm_custom_field_one=wps_safrica&amp;utm_custom_field_two=design_thinking&amp;utm_custom_field_three=524622092552&amp;utm_custom_field_four=design%20thinking%20course&amp;utm_custom_field_five=e&amp;gclid=EAIaIQobChMI943u_sHI-gIViOhRCh3p9wdrEAAYASAAEgJCePD_BwE">Project Management Institute.</a></p><p>Remember:</p><blockquote><em>Learning and Innovation go hand-in hand. The arrogance of success is to think that what you did yesterday will be sufficient for tomorrow- William Pollard.</em></blockquote><p>Now, go forth and prosper :)</p><p>My name is Cindy aka <a href="https://www.productqueen.co/">Product Queen</a>. I’m a non-coder of a PM who got promoted 8 months into my first ever official product role because of my capacity to create processes from scratch and collaborate like a boss.</p><p>Find my portfolio <a href="https://www.productqueen.co/">here</a> where I also take product newbies through specific ways to kick ass as a new PM.</p><p>You can check out the PQ Kickstart Kit for brand new PMs <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ab76e1930d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/4-skills-you-need-to-supercharge-your-performance-as-a-non-technical-product-manager-7ab76e1930d4">4 skills you need to supercharge your performance as a non-technical product manager</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Road to Release: Your step-by-step guide to beta-testing in 2023]]></title>
            <link>https://medium.com/@cindyadem/road-to-release-your-step-by-step-guide-to-beta-testing-in-2023-d06bc81fcc1b?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/d06bc81fcc1b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[beta-testing]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 10:32:39 GMT</pubDate>
            <atom:updated>2023-02-22T10:32:39.963Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to avoid crashing on take-off by testing your product with real users</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*99sOKsETTpLo2eny" /><figcaption>Photo by <a href="https://unsplash.com/@mbuiux?utm_source=medium&amp;utm_medium=referral">Mohamed Boumaiza</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>You want to ensure your product doesn’t suck</strong></p><p>Have you ever visited a website and you were left wondering whether it was built by a chaotic bat; or downloaded an app you were excited about but soon after aborted mission because, <em>“who built this thing and what were they thinking?”</em></p><p>No?</p><p>Okay, at the very least you have encountered a situation where an app you like or need was inconvenient in specific ways. Either it takes forever to send an OTP, or a button hides a key component you want to use, or for the life of you, you cannot remember where you need to click to do a specific key task because its hidden under several vague menus.</p><p>Such scenarios are key indicators of ineffecient or insufficient user testing exercises; where the product or QA team failed to catch bugs or ask the right questions to test users- if at all they tested with actual users.</p><blockquote><em>Alpha and Beta tests are part of the user acceptance testing (UAT) process. UAT is designed to help the product team investigate whether the software developed meets business and end user needs and works as anticipated.</em></blockquote><h3>User acceptance testing is important because:</h3><ul><li>It helps in the <strong>detection of bugs</strong> so they’re quickly fixed before they annoy mass users.</li><li>It’s part of the <strong>quality assurance</strong> process that ensures you sort out any issues that could prevent your app from being blocked by app stores.</li><li><strong>Usability testing</strong> that ensures the app or website works in predictable and similar ways regardless of the device being used to access it.</li><li>It helps you <strong>test the performance</strong> of your software when it’s being accessed by multiple people; things like loading speed, errors and seamlessness are critical to check.</li><li>It helps in <strong>spreading product awareness</strong> since it can be used as a marketing strategy with your targeted end users. A well organized test process can help you acquire and retain your first group of real users.</li></ul><p>There are a few fundamental differences between Alpha and Beta tests. In this article, we’ll focus on how to plan and execute beta testing like the boss you are.</p><p>But first;</p><h3>Differences between Alpha and Beta testing:</h3><p><strong>Alpha Tests</strong></p><ol><li>​Usually performed by internal employees</li></ol><p>2. Often perfomed in an internal testing environment (deveoper’s site)</p><p>3. Minimal or no focus on security and reliability</p><p>4. Critical issues are directly fixed and addressed by developers.</p><p>5. Ensures the quality of the product before moving to beta testing</p><p><strong>Beta Tests</strong></p><ol><li>Usually performed by end users who are not part of the company/org.</li></ol><p>2. Performed in a real-time environment that’s available to the public</p><p>3. Testing is focused on reliability, security, seamlessness and robustness</p><p>4. Also focuses on product quality, but with user’s feedback to ensure readiness for mass real-time users.</p><p>5. Feedback is collected and can be addressed immediately or on a rolling basis based on urgency and product roadmap.</p><h3>Three Beta testing tools you can leverage:</h3><ol><li><a href="https://developer.apple.com/testflight/">TestFlight</a>: You can invite up to 10,000 testers using just their email address or by sharing a public link. Testers can download it from the AppStore. Up to 100 apps can be tested at a time. TestFlight supports apps for iOS, iPadOS, macOS, tvOS, watchOS, and iMessage.</li><li><a href="https://firebase.google.com/products/crashlytics/">Firebase Crashlytics:</a> This is a real time crash reporting tool, helps you prioritize and fix your most pervasive crashes based on the impact on real users. Crashlytics also easily integrates into your Android, iOS, macOS, tvOS, and watchOS apps.</li><li><a href="https://testfairy.com/">TestFairy</a>: Works on both iOs and Android and allows users to report bugs by shaking their device or just clicking on a button and sketching on the screen. TestFairy includes an enterprise-grade app distribution platform for iOS and Android that is highly configurable, tightly secured and can sync with your corporate Single Sign-on.</li></ol><h3>How to map out your beta-testing roadmap:</h3><h3>Stage 1: Getting Launch Ready</h3><ol><li><strong>Key Features Developed: </strong>There needs to be something to be tested. And you want the critical features ready to be brought to the test group.</li><li><strong>Acceptance criteria well defined: </strong>ACs guide the testers to measure whether the feature meets the specified expectation. Well defined criteria can be answered using a yes or a no.</li><li><strong>Software/App Pushed to Test Environment: </strong>The initial test environment for Alpha testers is usually a sandbox or a developer’s site. The App/Sotware should be available in that environment to allow for testing.</li><li><strong>Alpha testers added to sandbox/test environment: </strong>Alpha testing is done in a closed environment with limited access. The testers (usually internal team members) have to be added into the environment so they can access the app/software for testing.</li><li><strong>Internal Alpha-testing of App completed: </strong>Internal alpha testers mark yes or no on the acceptance criteria of specific features to indicate whether they work as stipulated or not.</li><li><strong>App pushed to production:</strong> Once the alpha test is done and changes made, the developers push the app/software to production (ie AppStore/Playstore) or soft-launch the website so it can be accessed by the public/beta testers.</li></ol><h3>Stage 2: Beta-Planning</h3><ol><li>​<strong>Create beta- test SMART goals and tasks: </strong>Specify the tasks you want to test through the beta-test expercise, and the goals you want to achieve with the exercise. Some key goal-setting questions could include: What do you want from this beta program? Will you be engaging these users on a weekly, monthly, or quarterly basis? How will you be engaging them? Will it be simply for new features or innovation and new product releases? How often will you require them to give feedback?</li><li><strong>Finalise on the testing strategy to be used: </strong>This could include specifying whether it’s virtual, in-person or both; how long the testing period will last, what rewards (if any) will be offered to the testers, and where the testers will be found.</li><li><strong>Assign team responsibility in the testing process: </strong>Ensure every stakeholder knows their role and the associated deadlines; this includes any review or approval processes (such as budgetary approvals)</li><li><strong>Narrow down specific dates and deadlines: </strong>You want to be have a limited window so that testers stay engaged and prioritize the process.</li><li><strong>Decide on any beta-testing tools needed, where appropriate: </strong>​Test your new software on multiple platforms and beta-testing tools. Depending on the software, this could involve testing it on both MAC and PC computers, both iOS and Android mobile device, and Chrome, Edge, and Safari internet browsers. The software could behave differently across different platforms. Different testing tools/platforms allow you to test for specific things, so choose approriately.</li><li><strong>Create a communications plan/strategy for the beta-testing exercise: </strong>Timely, clear and targeted cross-functional and external communication makes for a seamless testing exercise</li></ol><h3>Stage 3: Legalities and Shortlisting</h3><ol><li><strong>Prepare an NDA and Participation Agreement for testers to sign: </strong>You don’t want your idea stolen before it makes it to the market; or to get sued because you processed a tester’s personal information without express permission.</li><li><strong>Create ideal test-user persona: </strong>You want your target market to make a significant part of your test user group, so you know that you’re building something YOUR users want.</li><li><strong>Coordinate with internal teams to help shortlist potential test users: </strong>Customer success, social media team and sales team can help curate targeted, precise list of users who fit your test group persona.</li><li><strong>Reach out to communities where test users are likley to be: </strong>You want to let people know you’re ready for launch and keep them excited to receive a solution to a problem they’re facing. Excellent marketing</li><li><strong>Settle on dates and locations or virtual rooms for the beta-testing: </strong>You want to communicate, well in advance to your test users the logistics around the exercise.</li></ol><h3>Stage 4: Beta-testing</h3><ol><li><strong>Specify internal team members to beta-test and their locations (if in-person):</strong> Relevant team members need to own specific parts of the testing exercise; and team can map out availability.</li><li><strong>Organize logistics for team members (digital or physical): </strong>Prior preperation helps everyone feel in control and prepared to do their best work.</li><li><strong>Organize logistics for testers, if necessary (internet, location, transportation and meals; if in-person): </strong>Users should feel that you care about their convenience.</li><li><strong>Communicate relevant information with beta-testers consistently: </strong>You want as many shortlisted participants as possible to show up for the testing exercise.</li><li><strong>Conduct the testing over the specified range of dates: </strong>Time to know whether you’ve built something worth having.</li></ol><h3>Stage 5: Beta Feedback</h3><ol><li><strong>Bug reports:</strong> Fix them before they annoy and frustrate everyone else.</li><li><strong>Submit Feature requests or improvements</strong>: You know what your users want more of; add it to your backlog and you’ll refine it later.</li><li><strong>Journal/Note-take: </strong>Take real-time notes of your observations and insights you gather as you carry out your exercise</li><li><strong>Evaluate Feedback:</strong> Ensure you come up with the correct POV when you look at the feedback in toto.</li><li><strong>Map required changes where necessary</strong>: ​Groom the backlog of feedback into <em>now, next and never</em> columns of changes to be made.</li></ol><h3>Stage 6: To the Moon!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*6Kp1hvJMjMUOL60x" /></figure><h3>Beta testing as a beginner:</h3><p>As a PM, you’ll encounter your very first user testing exercise. Or, an opportunity to stop limping through the process and do it well.</p><p><strong>I’ve created a user-testing playbook that helped me facilitate cross-country testing exercises, leading to my promotion just 8 months into my first product role. This playbook is now available on Gumroad and is filled with Notion templates that will help you plan the logistics, communicate with users effectively, and record their feedback.</strong></p><p>With this playbook which includes other resources that are helpful for a new PM, you can take the guesswork out of user testing and ensure that your products are designed to meet the needs of your users. Don’t miss out on this opportunity to take your product strategy to the next level.</p><p><a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">You can get the Testing Textbook here</a></p><p>My name is Cindy aka Product Queen. I’m a non-coder of a PM who got promoted 8 months into my first ever official product role because of my capacity to create processes from scratch and collaborate like a boss.</p><p>Find my portfolio <a href="https://www.productqueen.co/">here</a> where I also take product newbies through specific ways to kick ass as a new PM.</p><p>You can check out the PQ Kickstart Kit for brand new PMs <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d06bc81fcc1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sample questions to ask during user interviews as product manager]]></title>
            <link>https://medium.com/is-that-product-management/sample-questions-to-ask-during-user-interviews-as-product-manager-b1990499907f?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1990499907f</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-testing]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 06:25:24 GMT</pubDate>
            <atom:updated>2026-01-18T02:32:36.530Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to fight your own confirmation bias and your panelists unwillingness to be ‘bad’.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HZWfOBs_t86J2jOh" /><figcaption>Photo by <a href="https://unsplash.com/@uxindo?utm_source=medium&amp;utm_medium=referral">UX Indonesia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><em>The №1 challenge you have to navigate during user interviews is people’s inability (or unwillingness) to disappoint you. They will want to first assume THEY are the problem, that THEY are the ones clicking on the wrong button, or misunderstanding something, before the realisation dawns on them that what you’ve brought to them is umm… full of friction.</em></blockquote><p>Most panelists (i.e users who will be testing your product) will want to inundate you with reasons why they like what you’re showing them and how it’s ‘such a good idea’. Testers tend to be a bunch of ‘mums’ who think every idea is a good idea, but you’ve got to take them through ‘<a href="https://www.momtestbook.com/">The Mum Test</a>’. It is YOUR job to fight the unmerited glee to settle for untested positive feedback.</p><p>Before I get to the list of questions below, there are <strong>a couple of things that can help you tease out what your panelists true opinions are:</strong></p><ol><li>If it’s prototype testing, let them know that YOU did not design the thing, you hired a ‘guy’ or someone else in a different team did it and you want to find out if they’re doing a good job or not and that you hope your panelist can help you assess that. You want to remove the fear of offending you from your panelist.</li><li>If it’s an in-person test, reward anyone who finds a bug or a friction point with sweets (surprisingly, adults like these) or a dollar or a badge for the top bug-finder; anything that incentivizes your panelists to notice things that are not quite right. You want to normalise the experience of delivering bad news that your product kind of sucks. That’s the only way you’ll know what to fix.</li><li>You make it explicit at the beginning of the session that the goal is to find out what ‘issues’ exist so you can solve it for them; the more direct and honest they are, the more helpful their feedback will be. Everyone likes to be helpful.</li></ol><p>The questions you ask will depend on what kind of user interview you’re doing and obviously the product you’re testing. Usually, there’s 4 testing exercises you do before launch, <a href="https://www.productqueen.co/four-types-of-product-testing-before-launch">you can read more about them here</a>.</p><h3>Questions you might ask during a discovery exercise:</h3><ul><li>What are your current pain points or challenges in relation to the product or service category we are offering?</li><li>What do you like/dislike about similar products or services currently on the market?</li><li>What features or functionality are most important to you in a product or service like ours?</li><li>What would you be willing to pay for our product or service?</li><li>How often do you envision using our product or service?</li><li>What are your top priorities when considering a purchase in this category?</li><li>What would make you choose our product or service over competitors?</li><li>Can you think of any potential drawbacks or drawbacks of our product or service?</li><li>Are there any additional features or functionality you would like to see in our product or service?</li><li>How likely are you to recommend our product or service to friends or colleagues?</li></ul><h3>My favourite questions to ask during prototype testing:</h3><ul><li>Bad news only, what don’t you like about product/feature/functionality/process/look?</li><li>What has been the most confusing part of this experience for you?</li><li>What would you add or remove from this design or process?</li><li>What do you think we might be forgetting?</li><li>What do you understand by X on this page?</li><li>What would prevent you from enjoying this product?</li><li>If you could add one feature to the product, what would it be?</li><li>How likely are you to recommend this product to a friend or colleague?</li></ul><h3>Questions during performance testing and beta launch:</h3><ul><li>Are you able to create an account? Did the OTP arrive on time?</li><li>Are all images loading correctly? Are buttons working?</li><li>If you put your phone on landscape mode, are you still able to scroll up and down?</li><li>How’s the loading speed on your device?</li><li>Are you able to navigate through key tasks with relative ease?</li><li>How seamless is it for you to navigate through the pages as you need to?</li><li>Can you easily find (a button, a feature, a page) that you’re looking for?</li></ul><p>When facilitating user interviews as part of focus groups, user testing or just a good old ‘talk-to-your-users’ session, you might need to learn how to ask questions like a therapist would. You want to capture the emotions and the mental journey your user is going through when looking to answer your questions or test your product. These are great follow-up questions when a user responds a specific way or chooses a specific button over another.</p><h3>Examples of things a Therapist would Say:</h3><p>1. Something happens that seems to surprise them. For instance, they click on a link and say “Oh” or “Hmmm” when the new page appears. You could ask: “Is that what you expected to happen?”</p><p>2. The participant makes a comment, and you’re not sure what triggered it. You could ask: “Was there something in particular that made you think that?”</p><p>3. The participant suggests concern that he’s not giving you what you need.“No, this is very helpful.” “This is exactly what we need.”</p><p>You can read more about it Things a Therapist would Say <a href="https://sensible.com/download-files/">here</a>.</p><h3>User testing as a beginner:</h3><p>As a PM, you’ll encounter your very first user testing exercise. Or, an opportunity to stop limping through the process and do it well.</p><p><strong>I’ve created a user-testing playbook that helped me facilitate cross-country testing exercises, leading to my promotion just 8 months into my first product role. This playbook is now available on Gumroad and is filled with Notion templates that will help you plan the logistics, communicate with users effectively, and record their feedback.</strong></p><p>With this playbook which includes other resources that are helpful for a new PM, you can take the guesswork out of user testing and ensure that your products are designed to meet the needs of your users. Don’t miss out on this opportunity to take your product strategy to the next level.</p><p>You can get the Testing Textbook <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><p>My name is Cindy aka <a href="https://www.productqueen.co/">Product Queen</a>. I’m a non-coder of a PM who got promoted 8 months into my first ever official product role because of my capacity to create processes from scratch and collaborate like a boss.</p><p>Find my portfolio <a href="https://www.productqueen.co/">here</a> where I also take product newbies through specific ways to kick ass as a new PM.</p><p>You can check out the PQ Kickstart Kit for brand new PMs <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1990499907f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/sample-questions-to-ask-during-user-interviews-as-product-manager-b1990499907f">Sample questions to ask during user interviews as product manager</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four types of product testing you should do before launch]]></title>
            <link>https://medium.com/is-that-product-management/four-types-of-product-testing-you-should-do-before-launch-50052c2ada27?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/50052c2ada27</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Mon, 20 Feb 2023 08:53:14 GMT</pubDate>
            <atom:updated>2026-01-18T02:32:23.595Z</atom:updated>
            <content:encoded><![CDATA[<h3>Efficient product testing lets you build something people want</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q8x5cI64ikh4JT00" /><figcaption>Photo by <a href="https://unsplash.com/@dtravisphd?utm_source=medium&amp;utm_medium=referral">David Travis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>User testing involves gathering feedback from users on a product or service before its release to the market. The insights gathered from this process can help businesses make necessary improvements and adjustments to enhance the user experience.</em></p><p>There are many different types of product testing that can be beneficial before launching a new product.</p><p><strong>Here are four common types of product testing that can help ensure a successful launch:</strong></p><ol><li>Discovery research</li><li>Prototype testing</li><li>Performance testing</li><li>User experience testing</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IFGnFTrGVpe2d4KI" /><figcaption>Photo by <a href="https://unsplash.com/@freestocks?utm_source=medium&amp;utm_medium=referral">freestocks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>1) Discovery: Let your users tell you what they want</h3><p>This type of testing involves surveying potential customers to gauge their interest in and willingness to purchase the product. This can help identify potential customer segments and their needs, as well as any potential barriers to purchase.</p><p>Some of the ways you can pull this off is through:</p><ul><li>Focus group sessions with specific segments of your users,</li><li>Going through user feedback to find out what their pain-points are,</li><li>Looking at what the competitive market is offering and how you can leverage your areas of strength to provide better service to your users.</li></ul><p>Unless you’re looking to build the first car as an upgrade from using horses, your users will tell you want they want; perhaps not as eloquently, but vocally all the same. <a href="https://www.productqueen.co/product-discovery-as-a-product-manager">Read this</a> if you’d like to learn more about how to approach discovery as a PM.</p><h3>2) Prototype testing</h3><p>Before launching the final product, it is important to create a prototype and test it with a small group of customers or potential customers. This can help identify any design or functionality issues, and allow for necessary adjustments to be made.</p><p>Prototype testing can be a bit of a hustle. For software products, you’re technically asking a bunch of your users to sit through a simulation of what the final product will look like and then answer a bunch of qualitative questions. The hardest part about this process isn’t about the exercise itself, it’s getting users in the room in the first place.</p><p>You will need to properly incentivise them (whatever that looks like), get them to show up hopefully excited and engaged, share with them a link to the prototype which sometimes is just hosted on Figma preview and tease out honest responses from them. People will NOT want to ‘offend’ you so they will try their best to dilly-dally around something they think is frankly s*it.</p><p>You can do this online, in-person, through a WhatsApp call or phone call; whatever gets you user feedback.</p><p>Don’t panic, I’ve learnt how to do this swimmingly well and I created an end-to-end playbook you might appreciate. <a href="https://t.co/gV6tmcPMzK">You can find it here.</a></p><h3>3) Performance testing</h3><p>You want to know that your product works as intended on the devices and within the context your users will typically use it in. This is why we have alpha testing exercises.</p><p>If a majority of your users are in a location with minimal internet connection, or use devices with limited storage or operating capacity, you want to make sure that they can seamlessly use what you’ve built for them or they will get frustrated and move on to their own devices (*wink wink, get the pun?)</p><p>This type of testing involves putting the product through various scenarios and conditions to ensure it performs as intended and meets all relevant quality and safety standards. This can include testing for durability, reliability, and other key performance metrics.</p><p>Sometimes, performance testing also includes compatibility testing. Compatibility testing ensures that the product is compatible with a range of different devices, operating systems, and other software. This can help ensure that the product works seamlessly across different environments and platforms.</p><p>Again, <a href="https://t.co/gV6tmcPMzK">here’s a playbook</a> that you can use when planning out your testing exercises.</p><h3>4) User experience testing after you launch your product.</h3><p>You will typically do this with a wider group after doing the performance testing above through beta testing programs. This is when it’ll be in the hands of your actual users, randomised and segmented.</p><p>This type of testing evaluates the performance of the product under different conditions, such as different workloads or user scenarios. This can help identify any performance bottlenecks or issues and ensure that the product can handle expected levels of usage.</p><p>User experience testing also involves observing how users interact with the product, and collecting feedback on their experience. This can help identify any usability issues or user frustration, and allow for necessary improvements to be made. It involves evaluating how easy it is for users to navigate the product and complete common tasks. This can help identify any usability issues and make improvements before the product is launched.</p><h3>User testing as a beginner:</h3><p>As a PM, you’ll encounter your very first user testing exercise. Or, an opportunity to stop limping through the process and do it well.</p><p><strong>I’ve created a user-testing playbook that helped me facilitate cross-country testing exercises, leading to my promotion just 8 months into my first product role. This playbook is now available on Gumroad and is filled with Notion templates that will help you plan the logistics, communicate with users effectively, and record their feedback.</strong></p><p>With this playbook which includes other resources that are helpful for a new PM, you can take the guesswork out of user testing and ensure that your products are designed to meet the needs of your users. Don’t miss out on this opportunity to take your product strategy to the next level.</p><p><a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">You can get the Testing Textbook here</a>.</p><p>My name is Cindy aka Product Queen. I’m a non-coder of a PM who got promoted 8 months into my first ever official product role because of my capacity to create processes from scratch and collaborate like a boss.</p><p>Find my portfolio <a href="https://www.productqueen.co/">here</a> where I also take product newbies through specific ways to kick ass as a new PM.</p><p>You can check out the PQ Kickstart Kit for brand new PMs <a href="https://productqueen.gumroad.com/l/pm-kickstart-kit">here</a>.</p><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50052c2ada27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/four-types-of-product-testing-you-should-do-before-launch-50052c2ada27">Four types of product testing you should do before launch</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 tech tools you need to be good at as a non-technical product manager]]></title>
            <link>https://medium.com/is-that-product-management/5-tech-tools-you-need-to-be-good-at-as-a-non-technical-product-manager-9b8b98f01e1d?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b8b98f01e1d</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Tue, 04 Oct 2022 17:30:34 GMT</pubDate>
            <atom:updated>2026-01-18T02:32:10.665Z</atom:updated>
            <content:encoded><![CDATA[<h4>You can learn these product management tools on the job, but it’s the ‘why’ mindset that will determine how well you can leverage them and become a badass product manager</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zOzBtgdKCol7T0BY.jpg" /></figure><p>A sharp knife doesn’t make a great chef, but it sure turns cooking into an absolute delight.</p><p>As a product manager, having the right tools at your disposal will determine whether you operate blind as a bat or brilliant as Einstein. For non-technical product managers, just because you cannot code doesn’t mean you cannot leverage technical tools that help you develop and share new insights with devs, designers and leadership.</p><p>Good news is, it is not rocket science and you do not need to be the world’s no 1 expert at these. All you need to do is know what they do, why you need them and how to use them to achieve your specific goals.</p><p>Let’s jump right in:</p><h3>Tech tool #1 — Wireframing, Prototyping and Design tools.</h3><p>This could be <a href="https://www.figma.com/wireframe-tool/">Figma</a>, <a href="https://balsamiq.com/">Balsamic</a> or <a href="https://www.mockflow.com/">Mockflow</a>.</p><p>It could also be a blank sheet of paper where you can map out screen flows, draw out <a href="https://tendocom.com/blog/content-architecture-what-it-is-and-why-it-matters/">content architecture </a>and essentially take yourself through the journey your end user would follow if you developed the feature or product.</p><p>Knowing how to put your ideas to paper helps you communicate your ideas to the engineers and even designers. Having your designs or ideas look pretty is a nice-to-have; not completely essential. But it will give you the opportunity to think and communicate like the powerful product manager you are. A good communicator is a good leader.</p><h3>Tech tool #2- Roadmapping tools</h3><p>These could be <a href="https://clickup.com/product-planning?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=gs_cpc_t4_nnc_nb_trial_all-devices_cpc_lp_x_all-departments_beta_kd-roadmap-t4-20220804&amp;utm_content=all-countries_kw-target_text_all-industries_all-features_all-use-cases_tool_phrase&amp;utm_term=p_roadmapping%20tools&amp;gclid=EAIaIQobChMIrP6R95rG-gIVjO7tCh0KkQV0EAAYASAAEgIUfvD_BwE">ClickUp</a>, <a href="https://roadmunk.com/">Roadmunk</a>, <a href="https://www.productplan.com/learn/roadmap-tools/">ProductPlan</a> or <a href="https://www.productboard.com/">ProductBoard.</a></p><p>Even good, old Excel could work here.</p><p>Roadmapping helps you visualise the journey your product will take from Point A to Point B. This usually includes new features introduced, new markets you’ll enter into and sometimes even what you’ll be discontinuing because of a changing business or regulatory landscape.</p><blockquote><em>Roadmaps are more of a communication tool than a strategy tool. They help you tell different stakeholders what to anticipate over the coming months. Ideally, roadmaps shouldn’t stretch more than 4 quarters or they risk becoming redundant and less agile.</em></blockquote><p>As a product manager, you’ll usually create different roadmaps for different stakeholders. For instance, what investors and the management is keen to see is different from what developers want to know. Again, roadmaps are communication tools.</p><p><a href="https://www.productqueen.co/template-how-to-write-a-tips-blog-post-8">Here’s where you can read more about creating a roadmap.</a></p><h3>Tech tool #3- Analytics tools</h3><p>These could be <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwivw4aj_Mb6AhUZQfEDHT3UD-YQFnoECAgQAQ&amp;url=https%3A%2F%2Fanalytics.google.com%2Fanalytics%2Fweb%2F&amp;usg=AOvVaw095EntAfOjiijSk290zWyQ">Google Analytics</a>, <a href="https://mixpanel.com/">Mixpanel</a> or <a href="https://www.hotjar.com/">Hotjar</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tb8QeBMOA8yVTPol.jpg" /></figure><p>A good product manager knows numbers that matter</p><p>As a product manager, one of your key tasks will be to determine how your product is performing based on the goals you set for it. You cannot improve what you cannot measure. And knowing what to measure is 70% of the battle.</p><p>The metrics you set that would be the key growth indicators would inform what you will measure and the analytics tools you will use. Some analytics tools (such as Hotjar) only work on websites but not mobile apps. Others provide an overview of traffic sources but don’t go granular.</p><p>Once you decide what metrics you are optimising for, you will then choose what tool can help you measure movement. Acquainting yourself with how to read the data is expected, the ability to draw insights from that data is good, but a real MVP Product manager knows how to perform A/B tests, question the data and adjust strategy based on the insights gained from the data.</p><p>It sounds heavy now if these terms are new to you, but the more you expose yourself to these tools and processes the more your muscles grow as a result.</p><h3>Tech tool #4- Agile Project/Product Management Collaboration tools</h3><p>These could be <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwjP6rfkgcf6AhVPXfEDHd5DBIMQFnoECBYQAQ&amp;url=https%3A%2F%2Fasana.com%2F&amp;usg=AOvVaw28oQVgcd5_aDDNlqNosTUB">Asana</a>, <a href="https://www.googleadservices.com/pagead/aclk?sa=L&amp;ai=DChcSEwiV7OzRgcf6AhUUCYsKHYo0BmMYABABGgJlZg&amp;ohost=www.google.com&amp;cid=CAASJORoOuuwcF0pSFdtclLqmWLPzb9a_yyLLNqZ5M5W-hFDINtXHg&amp;sig=AOD64_0a9mzEpJbumAqbgUpcEZyKznWH_w&amp;q&amp;adurl&amp;ved=2ahUKEwiQiOXRgcf6AhVM_rsIHUPMAMsQ0Qx6BAgFEAE">JIRA</a> or <a href="https://trello.com/">Trello</a></p><p>Collaboration tools give visibility to what everyone in the team is doing which helps avoid duplication of tasks and allow you to track progress on specific outputs. Most give you the option of prioritising tasks in terms of urgency while visualising dependencies. By default, a lot of tech tools have a collaborative aspect, but these specific ones are made to empower teams to work together.</p><p>Most times, you will find that your needs as the product team evolve as your product evolves. This could mean that you could start off with the simple free version of Trello and then graduate to JIRA’s premium version as your needs become more complex and all encompassing.</p><p>You will also realise that some of these tools play well with others; like Trello and JIRA are made by the same company and have adjacent use-cases (depending on what you need) so you will likely use them together. A lot of them also allow for cross-integration that enables you to embed one tool onto another so you can have all your items in one overarching tidy place.</p><p>Sometimes, you will be required to onboard onto the tool all other teams in the company are using, alongside the tools your product team uses. Again, none of these require a specialised degree to learn, but knowing their capacities and their use-cases allow you to empower your team to leverage them in ways that unlock your potential to communicate, prioritise and collaborate.</p><h3>Tech tool #5 — Content repository</h3><p>This could be <a href="https://www.notion.so/">Notion</a>, <a href="https://www.googleadservices.com/pagead/aclk?sa=L&amp;ai=DChcSEwikh6XDhcf6AhVN8ncKHVkLBA4YABAAGgJlZg&amp;ohost=www.google.com&amp;cid=CAASJORolmPTa0dQDqyviFg4Nwx1tHY4BQBiaP2ataQUPxqmBREWyg&amp;sig=AOD64_3H1P_Uv3bKTFMDZi0ev5tPp3_foA&amp;q&amp;adurl&amp;ved=2ahUKEwjt5pzDhcf6AhW2gv0HHYM7CIAQ0Qx6BAgDEAE">Confluence</a> or <a href="https://www.googleadservices.com/pagead/aclk?sa=L&amp;ai=DChcSEwjOr63Ohcf6AhXV-FEKHe2XCnkYABAAGgJ3cw&amp;ohost=www.google.com&amp;cid=CAASJORoTksnu0loDsKyf6M7qqFVkZRGGsy6-c8uHw9CUFoA6syqRg&amp;sig=AOD64_3vkf3-rNyyT7g7gkwrADzP2Da-mw&amp;q&amp;adurl&amp;ved=2ahUKEwjhyaTOhcf6AhXQXvEDHSYNC_EQ0Qx6BAgDEAE">Google Workspace</a>.</p><p>One thing you’re guaranteed of doing a lot of as a product manager is writing, reviewing writing or editing writing. Think of documentation as the kidney of the product. When it’s healthy, it filters out the junk and keeps the good stuff in. Because it’s easy to take for granted, you will not notice when there’s a problem until your oedematous product is full of unnecessary features no one wants.</p><p>A phenomenal product manager keeps their <a href="https://www.productqueen.co/documentation-for-new-product-managers">product documentation in order</a>. It’s easy for whichever stakeholder to trace what they’re looking for, the information is easy to read and up to date, and the language is reflective of the audience the writing was intended for.</p><p>Tools that help you house your documentation ideally allow you to easily link pages, create sub-pages, add files of different formats and share the repository with different relevant folks. Again, different organisations will use different tools depending on the pre-existing or evolving needs.</p><p>If you’d like to learn how to create your repository as a new PM, you can read about it <a href="https://www.productqueen.co/documentation-for-new-product-managers">here</a>.</p><h3>It’s not the ‘what’, it’s the ‘why’ that matters</h3><p>As a new PM, you may not always have a choice on what tools will be used in your role; that’s okay. However, it’s on you to figure out why the tool is being used and if you encounter limitations that exist with the current tool stack, you’ll have to present a case as to ‘why’ a different tool will be a better fit.</p><p>But first, learn your tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/0*I6RZCgWS-T1xEPsA.jpg" /></figure><p>Product Queen™ is launching a robust, editable manual that contains templates, checklists, planners and lists that you can leverage to either land your first job as a P.M, or thrive in your current role.</p><p>​You can expect templates such as:</p><ul><li>The 30/60/90 day new PM checklist that got me ‘employee of the month’ in month four.</li><li>Six product document templates you will need as a P.M [helped me create 2 years worth of scattered documents in one beautiful repository]</li><li>How-to-guides to help you perform product-critical tasks such as doing user interviews, planning for user acceptance testing, developing the quarterly roadmap and prioritising feature requests.​</li></ul><h3>Do you want these P.M goodies from Product Queen™?</h3><h4>Join the Waitlist: <a href="https://www.productqueen.co/wait-list">https://www.productqueen.co/wait-list</a></h4><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b8b98f01e1d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/5-tech-tools-you-need-to-be-good-at-as-a-non-technical-product-manager-9b8b98f01e1d">5 tech tools you need to be good at as a non-technical product manager</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a Roadmap as a Product Manager (with examples)]]></title>
            <link>https://medium.com/@cindyadem/how-to-create-a-roadmap-as-a-product-manager-with-examples-b5222f63d2d1?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5222f63d2d1</guid>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[product-development-plan]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Tue, 04 Oct 2022 17:23:20 GMT</pubDate>
            <atom:updated>2022-10-04T17:23:20.162Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>A great roadmap is less of a strategy tool and more of a means of communication; and yet, good communication signals good strategy.</em></h4><figure><img alt="A calendar with a clock on it" src="https://cdn-images-1.medium.com/max/1024/0*xbWxL3_l1m7EPJNZ.jpg" /></figure><p>As a product manager, roadmapping has been a way to journal out my thoughts on what the next stint of development should focus on. I look at the stats, consider user requests and opinions and check out what competitors are doing to rough-draft what makes sense to build now, next and never. I then fold out the paper and store it out of sight then go work it out with my team.</p><blockquote><em>Roadmapping is not a solo activity. It’s as cross-functional as it gets; encompassing getting data from the sales team, user complaints from customer success, metrics from our analytics tool and pulling up reviews from socials and PlayStore.</em></blockquote><p>You want to build something people want. And if you’re listening, your users are telling you exactly want they want. This is what the product discovery process is about.</p><h3>A great roadmap is based on:</h3><ul><li>Qualitative and quantitative data on user needs and feedback</li><li>Analysis of usage data to inform areas of high and low customer focus</li><li>Data around points of friction and affected customers to help prioritise roadmap plans.</li><li>Research into market opportunities and competitor content</li></ul><p>A roadmap should also reflect internal stakeholder needs aligned with customer value.</p><p>A strategic roadmap balances larger complex dev projects with smaller iterative user needs.</p><p>This balance allows dev teams to build for current users while exploring potential for new market growth opportunities.</p><p>This process is augmented when PMs make data-driven decisions.</p><h3>Here’s a sample of how to map out what you need in order to prioritize feature requests:</h3><figure><img alt="A table showing requested features, the stakeholder making the request and the data supporting the request" src="https://cdn-images-1.medium.com/max/1024/1*CE1tKeJrQ2mjvBUaMFzOOA.png" /><figcaption><a href="https://productschool.teachable.com/courses/enrolled/1696269">A sample scenario borrowed from Product School</a></figcaption></figure><p>And here’s how you might prioritize the above feature requests:</p><figure><img alt="A gantt chart showing how the items in the first table might be prioritized based on the data and the urgency associated with the requests." src="https://cdn-images-1.medium.com/max/1024/1*4ED1Kcfad_jeZg1hnErADA.png" /><figcaption>An example of how the features prior could be prioritized.</figcaption></figure><p>Example of a roadmap borrowed from Product School</p><h3>Examples of Public Roadmaps:</h3><h4><a href="https://www.notion.so/NALA-Roadmap-057eef46825944f298233c316f24f6e9">1. Nala Money</a></h4><p>Nala is a money transfer service on a mission to increase economic opportunity for Africans worldwide. In specific, they facilitate Africans in diaspora to send money back into the continent at affordable rates. Their roadmap and feature request tool is hosted on Notion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PrEKcd56NxowPiYUkxU4lw.png" /></figure><h4>2 -<a href="https://github.com/orgs/github/projects/4247/views/1">GitHub</a></h4><p>GitHub has a very detailed roadmap with items that look more like Jira development tickets. What they’re working on has been mapped out to several months in advance, with appropriate tags. This way, they’re able to communicate to their users what to expect when which has a way of building brand trustworthiness and loyalty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6oBX2DY_LBZOsp12siMJ_A.png" /><figcaption>GitHub lets their community know what to anticipate for the next couple of quarters</figcaption></figure><h4>3 — <a href="https://trello.com/b/PDIV7XW3/buffer-transparent-product-roadmap">Buffer</a></h4><p>Buffer hosts their roadmap on Trello and they’re not shy about why they make it public. Apart from wanting users to comment and upvote on features they’re eager to use, they claim that they’re building it for their competitors as well since they <a href="https://buffer.com/resources/transparent-product-roadmap/">believe that</a>: <em>“There’s plenty of opportunity for everyone to be successful! All in all, we think this could raise the bar for all of us, and challenge Buffer to build the best, most valuable features possible.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3J8uV744Lu2Md2pvS2Kag.png" /><figcaption>Buffer creates their roadmap for their users and competitors to know what they’re working on.</figcaption></figure><p>As you can see, there are several roadmapping tools that can come in handy when creating a roadmap that works for you. Tools like Notion, Trello, Roadmunk, Click-Up and Jira all work well with varying levels of colour and complexity.</p><blockquote>A Product Roadmap is as personal as a journal but can be as public as a newspaper;</blockquote><p>There is no universal template on what a perfect roadmap looks like for you and your organization. As long as you marry the needs of the user, with that of the business, bearing in mind the business and competitive landscape, you can create a map that works for you, and change it up as frequently as is appropriate.</p><p>Should you decide that you want your users to directly influence it, publishing it has it’s advantages.</p><p><a href="https://www.productqueen.co/how-to-train-colleagues-on-new-tech-tools">Your checklist for training team members on new tech [downloadable template included]</a></p><p><a href="https://www.productqueen.co/beta-testing-roadmap">Road to Release: Your step-by-step guide to beta-testing in 2022</a></p><p><a href="https://www.productqueen.co/product-discovery-as-a-product-manager">6 ways you can approach product discovery as a product manager</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5222f63d2d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learnt about Product-Led Growth]]></title>
            <link>https://medium.com/@cindyadem/what-i-learnt-about-product-led-growth-e35292e67c46?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35292e67c46</guid>
            <category><![CDATA[product-school]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Mon, 15 Aug 2022 15:17:05 GMT</pubDate>
            <atom:updated>2022-08-15T15:17:05.429Z</atom:updated>
            <content:encoded><![CDATA[<h4>And why you should also take the FREE Product School Course.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OoAZSwiEYqxFIvDgAFswAQ.png" /></figure><p>This is a summary of my notes taken from the FREE Product School Course that you can find <a href="https://productschool.teachable.com/courses/enrolled/1696269">here</a>.</p><h3>PLG Steps</h3><p><strong>Acquire</strong>: Getting users into the product eg through freemiums or free trials. They sign up and create an account or activate their trial accounts.</p><p><strong>Adopt:</strong> The users/trial users fully onboard and become paying customers. Sticky features and driving regular usage make this phase successful.</p><p><strong>Retain:</strong> Users renew their subscriptions as they continue to realise value from the product. The overall user experience is seamless and intuitive.</p><p><strong>Expand</strong>: Users either upgrade to a higher-tier version of the product or drive additional revenue in other ways. It puts my product at the center of our revenue growth strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muOhGtmk0ypt66eZiKk_3A.png" /><figcaption>You can find this in the Product School Free course <a href="https://productschool.teachable.com/courses/enrolled/1696269">here</a>.</figcaption></figure><h3>Making a PLG Plan:</h3><ol><li>Define what metrics I’ll use to measure success</li></ol><ul><li>Deciding on what areas I’ll focus on to improve the metric</li><li>Determining how I’ll track each metric.</li></ul><p>2. Understand how I’ll close the value gap; the difference between the perceived value of the product and the what my product can ACTUALLY deliver.</p><ul><li>See why my users are acting as planned and where they’re not getting the full value from my product</li><li>Notice in what ways my users are not fully understanding what our product can actually deliver.</li></ul><p>3. Identify what I’ll need to keep users engaged</p><ul><li>Provide contextual and relevant content to users to promote additional and continued value.</li><li>This could be through in-app engagements that connect with my customers right within our product.</li></ul><p>4. Game plan on how I’ll continually measure, learn and iterate on our product experience.</p><ul><li>Create plans centered on real user data and feedback</li><li>A/B test different in-app strategies to best engage with users’ changing needs.</li></ul><h3>Free Trial Strategy:</h3><ol><li>Reduce friction when signing up; do not require payment information</li><li>Showcase a digital onboarding guide from day 1, demonstrate core basic functionality to drive quick wins for the user</li><li>Allow users to access all areas of the product in order to make it as sticky as possible, as quickly as possible.</li><li>Allow time to deploy product. 30 days is a good measure, but 7–14 days work as well depending on the type of product it is.</li></ol><p>Free trials measure interests and improve sales outcomes by leveraging product-qualified leads who have demonstrated purchasing intent.</p><h3>Assessing Value Gaps:</h3><p>We want to ensure users derive as much value as possible from our product. Here’s some questions that can help with that:</p><ul><li>Where are users coming from and where do they use the product most?</li><li>How often are they using our product daily/weekly/monthly?</li><li>Once they’re in our product, what’s their typical user pathway?</li><li>What features are getting the most use/time?</li><li>What features are being overlooked?</li><li>Are there points where users are dropping off (logging out, going back to the dashboard, etc)</li><li>Does usage vary by user persona?</li></ul><h3>NRR and Customer Retention:</h3><p>NRR (Net Recurring Revenue) is the percentage of revenue retained from existing customers within a specific period, including expanded revenue, downgrades and cancellations.</p><p>Formula for calculating NRR is:</p><blockquote><strong>[Total Revenue (including expansion) — Churn (cancellations and Downgrades)] divided by Total Revenue</strong></blockquote><p><strong>Improving retention:</strong></p><p><strong>Nurture user journeys through in-app engagements</strong>. Why?</p><ul><li>They personalise the product experience while providing a prescribed action path leading to adoption</li><li>They can build longer-term retention through adoption of more complex features after onboarding</li><li>They could be applied to new releases, to point out feature enhancements or simply drive awareness of new tools.</li></ul><p><strong>Proactively communicating to users</strong>. Re-engaging and retaining inactive users can be done through triggered communications. You can send timely messages such as:</p><ul><li>Email reminders that guide inactive users back to the product if inactive for a specific amount of time</li><li>A pop-up message that anticipates a user’s next steps based on a previous action</li><li>Well-timed ‘pro-tips’ that expand on initial value realisation.</li></ul><p><strong>Providing deeper self-service knowledge</strong> to users who have adopted the basic features. A self-service help center bot powered by a searchable wiki can guide continued engagement in a scalable way.</p><p>Help bots are:</p><ul><li>Key resources for complex products</li><li>Can serve as a buffer to support questions or tickets with FAQs.</li><li>Helpful to centralise info that improve user experience.</li></ul><p><strong>Long-term retention requires leveraging roadmaps.</strong> This is done by analysing and incorporating user sentiment and data to inform roadmaps and make appropriate engineering resource allocations that focus on key customer needs.</p><p><strong>Prioritising Retention Plan to Drive Revenue:</strong></p><ul><li>Focus on highlighting one feature at a time and avoid bombarding users with multiple in-app guides.</li><li>Determine which features (especially low-usage ones) that are most critical to driving revenue through retention.</li><li>Features tied to retention are typically sticky features, and provide the most value to your customers.</li><li>Only once users have successfully adopted the feature you’ve chosen to promote should additional features be promoted.</li><li>If low-adoption persists, <strong>iterate</strong> on your first solution before shifting to address another feature.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E-5ybMCcgYDZdgdFEDwmiw.png" /></figure><h3>Maximizing Customer Lifetime Value</h3><h3>1. Expand revenue from existing customers</h3><ul><li>Measure, learn and iterate on all the processes already in place such as product features, onboarding guides, customer surveys and data analysis to improve the overall business.</li><li>Specifically, experiment with new features or UX tweaks and see if changes move the needle.</li><li>Drive existing users to increase their spend by upgrading to higher tiers or adding new paid features to their packages.</li><li>Expose users to more features that are paid or come with a higher costs (i.e higher tier) to maximize on CLV.</li></ul><blockquote>💡 <em>One of the main barriers to customer growth and expansion is that users may leave due to lack of product adoption. Before focusing on maximizing user value, make sure adoption rates of your core features are strong.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vDsr4tpPw9cUhd6Tm7blA.png" /></figure><p><strong>Expanding Customer Lifetime Value could look like:</strong></p><ul><li>Continuously iterating and releasing product enhancements to address usability and growth challenges.</li><li>Adding new paywall features that upsell current customers</li><li>Identifying when customer actions might lead to opportunities for larger accounts (for example: adding more users could mean their company is growing and they need to upgrade their subscription package)</li><li>Identifying referral opportunities as users change roles and companies</li></ul><h3>2. Capturing new revenue opportunities:</h3><p>This usually means capturing new types of users or market segments.</p><p>To do this well, create a dedicated process to turn insights into action steps and development tasks on your product roadmap. Expansion should be powered by how much users are consuming your product.</p><p>New product capabilities allow you to attract new user segments and iterate on friction points that will reduce drop-offs.</p><p>Once you leverage your existing paying users and build for new potential users, the potential for sustained growth becomes exponential.</p><h3>Create a Winning Roadmap</h3><p>Effective roadmaps are based on:</p><ul><li>Qualitative and quantitative data on user needs and feedback</li><li>Analysis of usage data to inform areas of high and low customer focus</li><li>Data around points of friction and affected customers to help prioritise roadmap plans.</li><li>Research into market opportunities and competitor content</li></ul><p>A roadmap should also reflect internal stakeholder needs aligned with customer value.</p><p>Roadmaps should also balance larger complex dev projects with smaller iterative user needs.</p><p>This balance allows dev teams to build for current users while exploring potential for new market growth opportunities.</p><p>This process is augmented when PMs make data-driven decisions.</p><p><strong>Here’s a sample of how to map out what you need in order to prioritize feature requests:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pgaeZuS16qc-j8Qp_oN0SQ.png" /></figure><p><strong>And here’s how you might prioritize them:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URmcxgzYauYwv9apg8wUyA.png" /></figure><h3>Key PLG Take-aways:</h3><ol><li>Define your <strong>cross-functional metrics</strong> and tie these to <strong>key performance indicators</strong></li><li><strong>Close the value gap</strong> for users to realize your product’s full potential</li><li>Keep users engaged through <strong>sticky features</strong> and <strong>new value</strong>, and ultimately generate <strong>renewals</strong></li><li><strong>Measure</strong>, <strong>learn</strong>, and continually <strong>iterate</strong> on your product to grow revenue</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35292e67c46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guide to creating your first documentation as a new Product Manager. Part 1]]></title>
            <link>https://medium.com/is-that-product-management/guide-to-creating-your-first-documentation-as-a-new-product-manager-part-1-b8923a6caf8e?source=rss-29340f9b7515------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8923a6caf8e</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Product Queen]]></dc:creator>
            <pubDate>Sat, 06 Aug 2022 10:56:24 GMT</pubDate>
            <atom:updated>2026-01-18T02:31:53.582Z</atom:updated>
            <content:encoded><![CDATA[<h4>A ‘<em>don’t panic, you’ve got this</em>’ strategy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MwpSTIjdMHMGkZ-uf9d9Dg.png" /><figcaption>Documentation doesn’t have to freak you out. You’ve got this.</figcaption></figure><p>My first official PM gig came after a 5-year stint running an EdTech startup that ran out of funds. While I was the de-facto Head of Product and was a master generalist, one of the key tasks that I had never gotten around to actively engaging myself with was creating product documentation on Confluence (or whatever other tool) and linking it to Jira.</p><p>So, I am writing this for the version of myself who felt overwhelmed by all the new terms and tools, who had to learn fast under the watchful eye of an overeager micro-manager who was keen to see me fail, and create the most beautiful repository of ‘main source of truth’ for the product we were building.</p><p>So, this article is meant for the PM who’s been tasked with creating and/or managing documentation, with or without the help of a Product Owner.</p><h4>It all begins with the Owner’s mindset.</h4><ol><li><em>Are you starting from scratch or do you have an existing repository that you are starting with?</em></li></ol><p>More likely than not, when you take on your new role, unless it’s a brand new startup, there’s documentation somewhere. It’s likely spread between obscurely-named spreadsheets and google docs, some rough notes in a book, and some lo-fi/hi-fi designs on Figma. If you’re lucky, your predecessor did a great job of organizing the information in a useful, easy-to-follow way and you can use that as ‘inspiration’ to prepare yours; no need to reinvent a perfect wheel.</p><p>Most of us are not that lucky. We’ll inherit a mountain akin to a pseudo-abandoned, dusty library that hides a lot of useful books.</p><h4>Here’s how you’ll build a monument out of a documentation ruin:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iT15kM84-6h2kcevCsNMEA.png" /><figcaption>Great documentation is a sign of organization, competence, and good taste.</figcaption></figure><p>a. <strong>Collect all the documentation</strong> that’s been shared with you and go through it one by one. This may sound boring, but it will help you in two main ways: you get to understand where your product came from and what it’s transitioning into. You also get to see the vision your company is looking to achieve and how you should be thinking about the place of your product in achieving that vision. A PM needs to be as close to a human manifestation of a ‘source of truth’ as possible.</p><p>b. If the documents are not properly labeled in a way that’s easy to identify and follow, <strong>create your own naming convention</strong> and save them in a private folder for now. If your company is a stickler for ‘this is how we’ve done naming before’ and it’s not (yet) understandable for you, duplicate the docs and save them with your preferred names in your own folder.</p><p>c. <strong>Determine which documents are ‘outdated’,</strong> which ones you’re not too certain are relevant, and which ones are obviously recent and up to date. One way to establish this is to check the last date it was edited/published. Another way is to check how relevant the content is to what you know is currently being built. You can then save them in three different folders. If they’re all in a Confluence or Notion Space or different spaces, you can create your own single space, add pages and subpages and separate them that way. You will confirm later with your manager whether your categorization is accurate.</p><p>d. <strong>Meet with different stakeholders</strong> within your company and outside of it. Prepare any list of questions you had after reading through the documents. Clarify things like context, competitive landscape, and current sprint and roadmap. Take copious amounts of notes; you’ll need these when creating or updating the documentation you already have. This step is important even if you were an internal transfer or hire; this time, you’ll be thinking like the world-class PM you’re becoming.</p><p><em>2. Who are you targeting with this documentation?</em></p><p>How you’ll write for investors and partners will be different from how you’ll write for developers or end users. A great PM knows their audience. For instance, main pages can contain a summary with links to pages that have more granular information. Dev tracking tools like Jira tend to go even deeper and more technical. Depending on whether or not you’re a technical PM, you’ll be focusing on ensuring your devs understand ‘<strong>what</strong>’ to build, and the techies will take care of breaking down the ‘<strong>how</strong>’.</p><blockquote>Regardless of who you’re writing to, a rule of thumb is this: write to express NOT to impress. Fancy language is good for the ego but bad for building understanding. Make your writing simple, crisp and targeted.</blockquote><p>Filter out the language and granularity of your writing against two main factors:</p><p>a. Who is most likely to read it (influenced by where you’ll share it or store it)</p><p>b. What key message you’d like to pass (influenced by what the specific product documentation it is)</p><p>For instance, a general roadmap meant to be shared with management will be high-level and highlight key milestone markers, while acceptance criteria to be shared with devs will have granular details on what the expected dev outcomes will be.</p><p><em>3. Do you have an internal source of truth, and how do you funnel information in and out of it?</em></p><p>A <a href="https://backlog.com/blog/single-source-of-truth-what-is-it-and-why-do-you-need-it/">Source of Truth</a> is a digital location that contains the most updated, most relevant information regarding a project. It’s the one place anyone can go and be confident that what&#39;s there is an accurate representation of what is current.</p><p>Most companies will have a place where a majority of their documentation lives. This could be a shared Google drive, DropBox, Notion or Confluence. For most organizations, you’ll trace even more documents distributed in other spaces like Slack, Asana, Miro, etc.</p><p>Your main first task as a potential world-class PM is ensuring that there’s reliable, updated information in a reliable location where anyone interested can find what they’re looking for, clearly labeled.</p><p>If there already is a ‘Source of Truth’, use your advantage as a new PM to test how easy to navigate and search for info is. If YOU find it hard or confusing to trace what you need or understand what a specific document is, it’s likely even more challenging for someone with less technical chops to do the same. Notice this and make improvement plans.</p><p>Find a way to have all documents feed into the Source of Truth through links, screenshots, and embeds. Everyone should know that if they find something in the Source of Truth, then it is the most updated, most relevant piece of information on that specific subject.</p><p>If there is none, work with your team to find out what is the most friction-free location that will suit the team’s needs regarding a document or information repository and get to work creating the most useful wiki that could ever be created by man.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3uvu90SLr4PoEy82vNaUlA.png" /><figcaption>Great documentation is a manifestation of incredible communication skills.</figcaption></figure><blockquote>A great PM treats whatever they’re in charge of as a product; this includes the documentation repository. Incremental improvements, over perfection is the goal here.</blockquote><p>Next, we’ll talk about how to create and populate info in one of the most popular documentation software: Confluence.</p><p>So, what are some of the things you wish you knew when handling documentation as a first-time PM?</p><p>→ Follow Product Playbook on X: <a href="https://x.com/intent/user?screen_name=jakebarlo">https://x.com/intent/user?screen_name=jakebarlo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8923a6caf8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-that-product-management/guide-to-creating-your-first-documentation-as-a-new-product-manager-part-1-b8923a6caf8e">Guide to creating your first documentation as a new Product Manager. Part 1</a> was originally published in <a href="https://medium.com/is-that-product-management">The Product Playbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>