<?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 Stephanie Kazalac on Medium]]></title>
        <description><![CDATA[Stories by Stephanie Kazalac on Medium]]></description>
        <link>https://medium.com/@stephanie.kazalac?source=rss-7cc599623a51------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tHZN6xWhPGaDBiEOjhHtqw@2x.jpeg</url>
            <title>Stories by Stephanie Kazalac on Medium</title>
            <link>https://medium.com/@stephanie.kazalac?source=rss-7cc599623a51------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:02:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@stephanie.kazalac/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[Why I like using ProductBoard for Product Roadmaps?]]></title>
            <link>https://medium.com/@stephanie.kazalac/why-i-like-using-productboard-for-product-roadmaps-fe0e807a0ddc?source=rss-7cc599623a51------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe0e807a0ddc</guid>
            <category><![CDATA[productboard]]></category>
            <category><![CDATA[product-roadmap]]></category>
            <dc:creator><![CDATA[Stephanie Kazalac]]></dc:creator>
            <pubDate>Fri, 24 Apr 2020 10:24:20 GMT</pubDate>
            <atom:updated>2020-04-30T06:05:58.249Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why I like using ProductBoard for Product Roadmaps</h3><p>I wanted to share my experience and learnings with <a href="https://medium.com/u/b8dbd5ecb655">productboard</a> as we recently moved to this new tool to create and manage Product Roadmaps at Delivery Hero.</p><p>Initially, I wasn’t convinced as I had concerns to have one more additional tool to maintain but it turns out that ProductBoard has been quite handy especially in this new virtual world.</p><p><strong>1. At first, I found ProductBoard overwhelming</strong> <strong>to use</strong>. I had to reach out to the support team multiple times (who has by the way been very responsive and helpful) to figure out how to configure the board and understand the concept of view. A small suggestion, it would be useful to share some templates to give some inspiration and a step-by-step onboarding.</p><p>2. We used ProductBoard to c<strong>ommunicate our product initiatives for our Q2 product roadmap to our stakeholders</strong>. It was a great way to give full transparency and set expectations. For instance, we created a dedicated column for product initiatives that will not happen in Q2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9abIQxSxqHl9MeokfFui3A.png" /></figure><p>3. We have experimented with some <strong>cool features to let our stakeholders score our product initiatives</strong>, such as “Critical”, “Important”, “Nice-to-have”, &quot;Not Important&quot;. I personally found that it was a great way to give a voice to our stakeholders and involve them in the product roadmap process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GbqUxFbmxSI4XdQyylt9lg.png" /></figure><p>4. We also <strong>use ProductBoard internally within our Product team</strong> to go through each of our product initiatives, to not only share status updates and exchange product ideas but also highlight potential dependencies and blockers.</p><p>5. There’s <strong>a “Dependency” feature coming very soon</strong>. I personally tested it as a beta tester but in my opinion, needs some additional improvements. For instance, I haven’t found ways to flag dependencies from other views/tribes.</p><p>6. I think <strong>overall ProductBoard fosters better cross-functional collaboration</strong>, gives a very clear picture of the product roadmap and helps to communicate it in an easy way.</p><p>7. The <strong>look and feel makes you want to use ProductBoard </strong>and I believe this makes the difference compared to some other product roadmap tools.</p><p>8. Our <strong>next steps with ProductBoard</strong> is to integrate it with JIRA to avoid redundant work and link our product initiatives to our OKRs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Kf-Ou8E5gn1xynGnMmPRw.png" /></figure><p>I would love to hear anyone’s experience with ProductBoard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe0e807a0ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The lessons I’ve learned in my first 3 years as a Product Manager]]></title>
            <link>https://medium.com/@stephanie.kazalac/identify-relevant-issues-and-build-valuable-products-as-a-product-manager-29b50ea08391?source=rss-7cc599623a51------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b50ea08391</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[problems]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Stephanie Kazalac]]></dc:creator>
            <pubDate>Tue, 21 Mar 2017 07:49:05 GMT</pubDate>
            <atom:updated>2020-04-22T20:46:45.261Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*N8s5XYST0J6rK54DFMTBmQ.jpeg" /></figure><p>I remember my first time building a product “I had butterflies in my stomach”. My head was full of questions on how to build a successful product experience, what product decisions to make, how to deal with business stakeholders and, the list went on!</p><p>This is my first post on Medium. I wanted to share the lessons I’ve learned about building products, features, identifying relevant problems, and driving better product decisions.</p><h3>1. Listen to your users!</h3><p>You’ll be surprised at the number of companies neglecting customers’ feedback and missing out on important opportunities. That is why I am bringing this up here!</p><p>This is your role to identify what’s needed, what’s missing, what’s failing in your product to make your users happy and your product successful. You are the voice of the customer, thus do so!</p><h4>Don’t ignore qualitative feedback</h4><p>I realized that is way too often ignored by companies but crucial in the discovery phase. Come up with a prototype or an MVP (minimum viable product) and speak with users to gain some early feedback. You need to ensure you solve a real problem. Is the problem that you are trying to solve painful enough?</p><h4>Gather quantitative feedback</h4><p>Firstly, always ensure to collect data in a structured way so that you can get the most out of them. Find out for instance what are the reasons behind hosts declining a reservation. These are the reasons you will need to collect through your product.</p><p>Also pass as much data as you can to your product analytics tools (e.g. Google Analytics, Firebase, etc.) to have a better understanding of your users’ behaviour. Once you have data to analyze, you can start making assumptions and do some correlation.</p><p>For instance, x% of declined reservations are due to inaccurate calendars (hosts not updating calendars), which will then ruin the traveller experience. Do you actually give your hosts the proper tools to manage their calendar? Do they sync their calendar? Do they actually know how to sync their calendar? These are the questions you will need to ask yourself.</p><p>Dig into your data even more if you have a worldwide audience, you might be surprised how they can vary from one country to another one.</p><h4>Your Customer Service is here for you!</h4><p>Your customer service is the perfect team to get insights from to identify product weaknesses and improve the overall customer experience. You have very powerful customer service software like Zendesk that allow you to record cases in such a way that you can pull out very insightful reports and get an overview of your customers’ pain points.</p><h4>Check out your NPS results on a regular basis</h4><p>This will also help you validate your assumptions and obviously measure your customer satisfaction. Work closely with the team conducting the NPS (Net Promoter Score) and don’t hesitate to add questions, only relevant ones! I would highly recommend <a href="https://medium.com/u/f9ec0e0e5d0">Typeform</a> to create and send out NPS surveys (I do not work for them but I am a big fan of their product, I found it very handy!).</p><p>To sum it up<strong>, </strong>I am spending more and more time analysing data and digging into them to understand and find the right problems to focus on so that I can build features that would not only make sense but improve the <strong>metrics</strong> that matter.</p><p>Understand and identify customers’ needs and problems will help you stay ahead and build a successful product experience. Always keep in mind, what customers need so that you can anticipate their needs.</p><h3>2. Don’t raise your voice but make some noise!</h3><p>I’ve often had pressure to launch x amount of features that were supposed to improve conversion by x%, acquire thousand hundred of users, increase supply by x%, reduce churn rate by x times, and at the end didn’t improve any of these metrics requiring us to kill these so-called amazing features.</p><p>Looking back now, I realized this is where I failed. I knew this was the wrong feature to build back at the time but I prefer to let it go to avoid dealing with difficult stakeholders.</p><p>As a product manager, there are a number of soft skills that you need to master to be effective at your role and one of them is <strong>Influence</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*bZ88l6j3O3cFRV6Zl9aoWw.jpeg" /></figure><p>Remember you are the one who knows what’s best for your product and your users. If you don’t, maybe Product Management is not the right dfor you.</p><p>If you feel this is the wrong decision, you should bring it up and back it up with data! This is how you’ll move your product to the next level!</p><h3>3. Estimate and prioritize accordingly</h3><p>Measuring will not only give you an idea of how successful is your feature or product but will also motivate, engage your team and bring the best out of them.</p><p>I’ve learned to come up with rough estimations to figure out how this feature could potentially bring to the business. There is no point to apply this to small features but this can be a great way to justify the revamp of a page for instance. Do you know how many users are dropping off at this step, do you have ideas to improve the product funnel? Come up with some observations, a hypothesis and a rough estimation. This will make a huge difference within your team. Remember the bottom line is to bring value.</p><p>Once done, size your features with your engineering team to have a better understanding of the effort. Break it down into small parts and #gethingsdone. Once you have a rough idea of the business value and the effort, you can prioritize.</p><p>That brings me to the end of my post: my background!</p><h3>4. Product Management doesn’t require to have an engineering background!</h3><p>In the beginning, I felt uncomfortable not having a strong technical background and people with an engineering background actually made me feel worse at times but I quickly realized that <strong>it wasn’t and it isn’t required to make a product successful.</strong> I have a business background, in e-commerce, so I got to learn some basic coding but I can tell and certify that it is better to be good at analyzing and interpreting data than at coding.</p><p>Your job is firstly to understand your users, identify problems and needs so that you can define a product vision and make the right product decisions to bring value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*quZUXqACfP_eFAThU9rgdA.jpeg" /></figure><p>Your job is NOT to code, if you do so, then you should maybe consider a software engineer career.</p><p>The only technical skill that is actually I wouldn’t say required but very useful would be able to run SQL queries to get the data you want and avoid dependencies on engineers or business analysts.</p><p>Don’t get me wrong, product management still means understanding product development so you need to understand how your systems talk to each other, how the release process works, how to interpret API documentation, etc.</p><p>To sum up this post in a few words, I see product management as a multi-disciplinary role requiring various skills, knowledge and some confidence to influence!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*oPR4-BL4lMUOhw9rGMv65w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b50ea08391" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>