<?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 Chloé Rozenbaum on Medium]]></title>
        <description><![CDATA[Stories by Chloé Rozenbaum on Medium]]></description>
        <link>https://medium.com/@chloe-rozenbaum?source=rss-c9185aeb2dcf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*-iPJjudzai6gqBCFhvjCFw.jpeg</url>
            <title>Stories by Chloé Rozenbaum on Medium</title>
            <link>https://medium.com/@chloe-rozenbaum?source=rss-c9185aeb2dcf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:02:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chloe-rozenbaum/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[How to Tackle Breaking Down a Monolith]]></title>
            <link>https://medium.com/bitsrc/how-to-tackle-breaking-down-a-monolith-1686baff4ea4?source=rss-c9185aeb2dcf------2</link>
            <guid isPermaLink="false">https://medium.com/p/1686baff4ea4</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[monolith]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Chloé Rozenbaum]]></dc:creator>
            <pubDate>Fri, 06 Jan 2023 15:21:25 GMT</pubDate>
            <atom:updated>2023-01-24T16:10:00.151Z</atom:updated>
            <content:encoded><![CDATA[<p>As a PM, a lot of us have experienced asking engineers for a new fancy feature and getting the infamous answer “We can do it, but <strong>it will take ages</strong>: <strong>it is in the monolith</strong>”.</p><p>We would spend a lot of time trying to figure out how to be the most efficient, touching this monolith as little as we could, and still delivering a bit of value. We tried to split it into micro services, but eventually, we got to the end of the low hanging fruits, and the value was not there any more. So we needed more. We needed to break it down, and for that, we needed a plan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*OB5k9G1WdWISwMNgNSOHMQ.png" /></figure><h3>Planning to plan</h3><p>Quite a few times, PMs tried to gather the tech leads in a 1 or 2-hour long workshop. The outcome was always the same. We needed to <strong>break down the monolith into micro services</strong>. But no tech lead had a good understanding of <strong>the full scope</strong>, we couldn’t agree on <strong>what to tackle first</strong> and why, <strong>how to split the work. </strong>The one thing we knew is that<strong> </strong>it would be <strong>impossible to block a full year </strong>or so of development to do it all. After these workshops, no follow up was done, months went on, and we still didn’t have a plan.</p><p>So we decided to make time for it. For <strong>two weeks</strong>, all tech leads would be dedicating at least <strong>90% of their time</strong> to that task, as well as two engineers who had been there since the creation of the company and had core knowledge of the monolith. As a product manager with good technical knowledge, I was picked to join the group. The outcome would be <strong>technical</strong>, but had to take into account <strong>business priorities</strong>. We planned these two weeks to be in a quiet sprint, as everyone was to ditch meetings and regular sprint work, to focus on this project.</p><p><em>We decided to do it over two weeks and have 90% of the time dedicated, but it could very well be adapted to be 50% of the time for a month, or half a day for a few weeks/months. That is up to you, and mostly depends on your priorities.</em></p><p>Once that was decided, and before those two weeks, we did a little bit of preparation:</p><ul><li>We agreed on the <strong>goal </strong>for those 2 weeks of workshops. We wanted to achieve a <strong>mapping of the current status</strong>, define what would be a <strong>good micro service state</strong>, and advise on <strong>how to get there</strong>.</li><li>We agreed to dedicate our time and effort to do it.</li><li>We agreed I would be the one driving the workshops. Retrospectively, definitely pick the most methodical person for this task. It doesn’t have to be a product manager.</li></ul><h3>The current status of our world</h3><p>The first milestone was to make sure everyone had a good understanding of <strong>where we were at</strong>. To facilitate our conversations, we worked on <strong>Miro</strong>. It is probably worth mentionning this work happened during the Covid lock down, so we were all remote. In an ideal world we would have done that<strong> in person</strong>, but still in Miro to make no transcription post-session would be needed.</p><p>One week before the workshop, I asked to our group for a <strong>list of the domains </strong>we had in our company. I then added them as Frames in Miro. The two weeks would follow a simple cadence: <strong>some homework </strong>for everyone, and then <strong>a common session</strong> to discuss, sometimes with some <strong>debates</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YKZvEUEFonSo5wnm67HjTg.png" /><figcaption>Domains in Miro</figcaption></figure><p>On the Monday morning we assigned people to be <strong>domain owners</strong>, as the one(s) who had the best technical knowledge about it. One engineer could be the owner of one or more domains. Then, I asked them to take some time, offline, to <strong>add all functionalities in their domain</strong>, and to try to be as user oriented as possible in the naming. We then reviewed them all together for a couple hours. One would think that would be faster, but a lot of challenging was done, to properly define where were things. We ended up with a <strong>mapping of the domains and their features</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nn07uEqqlqPwhz_1AoVomw.png" /><figcaption>Domains and features</figcaption></figure><p>The next step, was to <strong>define the dependencies</strong>. To make sure they were not forgetting any, I asked them to <strong>add the depencies per feature</strong>. The domain owners worked on it on their own, and we gathered again to review, and agree. We made sure that each dependency was marked in both domains. The session together took a bit longer, and few more dependencies that had been forgotten were added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AWeXxuwbS9QJ3ma2cn0GxQ.png" /><figcaption>Domains, features &amp; dependencies</figcaption></figure><p>The last step before starting to discuss our vision, was to understand <strong>what works well</strong> in the current architecture, and <strong>what doesn’t</strong>. For this step, as a product manager, I participated and added my own post its from a business/user point of view. Sometimes they were at the level of the domain, sometimes at the feature level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lDLV_sxfDfnLN44qkyQew.png" /><figcaption>Domains &amp; pros &amp; cons of the current architecture</figcaption></figure><p>At this point, we already had a very good <strong>view of our current system</strong>. As we were reviewing at every single step, all the group got to have a very good knowledge of domains they were originally not used to. Zooming out on the Miro board, it was also very easy to see which domains looked good (=very green) and which ones required a bit of work (=very red). The next steps were to discuss where we wanted to go.</p><h3>Our ideal world</h3><p>Before even starting about thinking design, architecture and drawing it on Miro, we needed to pin point <strong>what required changes</strong>. Again, we took a round of “homework”, led by all tech leads, before reviewing as a group and discussing together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NrU2ul1W2KFU9e2HYBxreA.png" /><figcaption>Things to change based on what didn’t work well</figcaption></figure><p>Having already listed cons, adding desired changes was a quick thing. However, we had two sessions of a few hours of conversation following this, to understand which domains had to stay as is, be extracted, divided, or merged into others.</p><p>At this point, we reached the design milestone.<strong> Techleads and specialists had a clear list of what to change in their domains</strong>. The next step was to draw what would be the future system, based on these changes.</p><p>To do this, they took some time on their own again to do this. Some of them had to <strong>meet and discuss in smaller groups</strong>, to make sure their<strong> new domains’ designs were coordinated</strong>. Then, we synchronised all together, and again, that session generated quite a few debates and took some time for everyone to align.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rFM9i3OUyBVa5Z_a0YXTUA.png" /><figcaption>Architecture before/after</figcaption></figure><p>That was it, we knew where we wanted to go, we had our desired architecture. Having the final results, it was now obvious that the<strong> total amount of work</strong> represented way <strong>more than a year of work, probably closer to two</strong>. There was no way we could afford to put all development work on standy to focus on those changes.</p><h3>Making a plan</h3><p>In order to prioritise changes we wanted to make, we extracted all the ones already present in the domains, and made sure we were not missing any required to achieve the desired architecture. We copied them to another frame in the Miro. To then be able to order them in time, we needed to know if there was<strong> any advised order, for architectural or efficiency reasons</strong>. We simply linked those post its with arrows, then ordered them a little bit.</p><p><em>For a real system, you will likely obtain a diagram way more complex than the following one.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*IEm0-LZNSXpv8BmklsD4LA.png" /><figcaption>Changes, and advised order</figcaption></figure><p>At this point, it was my turn to do some homework. I went to <strong>all the product managers and the CPO</strong> of the company, and together we discussed what plans did they have for the upcoming 2 years.<strong> What were the priorities</strong>? Which main feature did they foresee improving? I built a very global roadmap, not going into more details than at the quarter level, and then presented it to our tech leads and specialists group. That insight was very important to take into account. A technically prioritised order would not make sense. We then spent some time to discuss, and voted on what should be tackled first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*hyrj9fsxaQAVeapOE4DdfA.png" /><figcaption>Votes on priorities</figcaption></figure><p>From this vote, the next step was to position changes onto a timeline. But to do that, we needed to have an idea of how complex they would be. We used T-shirt sizes to estimate everything (S, M, and L), then we started to position the changes onto <strong>a roadmap</strong>. That was a collaborative work done in a call as we wanted to take into account both<strong> business priorities and technical recommendations</strong>. We made a <strong>split by teams</strong> based on domain knowledge, to better understand how to coordinate the work amongst ourselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7DYXZ_qjRCsouXtiaGFAJw.png" /><figcaption>A roadmap of the domain changes, by team</figcaption></figure><h3><strong>What next?</strong></h3><p>We presented our work to <strong>the rest of the engineers and the product managers</strong>. The <strong>map of the domains</strong> could be kept and adapted, with the upcoming changes. The<strong> desired state</strong> could evolve as the business needs were evolving. And then the <strong>mapping of the orders</strong> could be used, when encountering a business need, to pick what extraction to a microservice would be possible, and what would be the dependencies: the <strong>roadmap</strong> was a tool to guide a team, but always to be adapted to stay agile. (See <a href="https://medium.com/p/f7df0fe606">how-to-build-an-agile-roadmap- article</a>). If it was true at the time, it would then evolve with the business and the priorities.</p><p>Overall, these two weeks of work gave to the whole team a very good understanding of the ecosystem we were working with, and all the challenges we’d have to face to upgrade it. That on its own, was already a very good starting point for the upcoming months.</p><p><em>Disclaimer: this article was made from memory on a previous experience. It is a tool suggestion, and does not pretend to be the only approach to carve a monolith</em></p><h3>Break down monoliths with reusable components</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/0*MtCGotmqmBDp0Oev.png" /></figure><p><a href="https://bit.cloud/"><strong>Bit</strong></a><strong>’s open-source tool </strong>help 250,000+ devs to build apps with components.</p><p>Turn any UI, feature, or page into a <strong>reusable component</strong> — and share it across your applications. It’s easier to collaborate and build faster.</p><p><strong>→ </strong><a href="https://bit.dev/"><strong>Learn more</strong></a></p><p>Split apps into components to make app development easier, and enjoy the best experience for the workflows you want:</p><h4>→ <a href="https://blog.bitsrc.io/how-we-build-micro-front-ends-d3eeeac0acfc">Micro-Frontends</a></h4><h4>→ <a href="https://blog.bitsrc.io/how-we-build-our-design-system-15713a1f1833">Design System</a></h4><h4>→ <a href="https://bit.cloud/blog/how-to-reuse-react-components-across-your-projects-l4pz83f4">Code-Sharing and reuse</a></h4><h4>→ <a href="https://www.youtube.com/watch?v=5wxyDLXRho4&amp;t=2041s">Monorepo</a></h4><h3>Learn more</h3><ul><li><a href="https://blog.bitsrc.io/how-we-build-micro-front-ends-d3eeeac0acfc">How We Build Micro Frontends</a></li><li><a href="https://blog.bitsrc.io/how-we-build-our-design-system-15713a1f1833">How we Build a Component Design System</a></li><li><a href="https://bit.dev/index.html">Bit - Component driven development</a></li><li><a href="https://blog.bitsrc.io/5-ways-to-build-a-react-monorepo-a294b6c5b0ac">5 Ways to Build a React Monorepo</a></li><li><a href="https://bit.dev/blog/how-to-create-a-composable-react-app-with-bit-l7ejpfhc/">How to Create a Composable React App with Bit</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1686baff4ea4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitsrc/how-to-tackle-breaking-down-a-monolith-1686baff4ea4">How to Tackle Breaking Down a Monolith</a> was originally published in <a href="https://medium.com/bitsrc">Bits and Pieces</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 Work With Customer Support for Better Product Management]]></title>
            <link>https://medium.com/swlh/how-to-work-with-customer-support-for-better-product-management-48b70ec77e15?source=rss-c9185aeb2dcf------2</link>
            <guid isPermaLink="false">https://medium.com/p/48b70ec77e15</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[user-feedback]]></category>
            <dc:creator><![CDATA[Chloé Rozenbaum]]></dc:creator>
            <pubDate>Mon, 11 Jan 2021 13:05:21 GMT</pubDate>
            <atom:updated>2021-01-13T09:52:03.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*ytMsT5QO9-8u_sAgCXoZaw.png" /></figure><p>As a product manager, one of the challenge is to be aware of your users’ needs, and to collect feedback. One doesn’t always have the time or skills to run proper user testing sessions, and then analyse the data. A simple thing that many companies have is a customer support team. It is an asset that is often under estimated in product management.</p><h3><strong>Build a relationship with the CS team</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*77pZKIzoec1W2an850KrdQ.jpeg" /></figure><p>In companies, the CS team is the team in touch with users. They gather the feedback, both feature requests and issues to fix. They will often ask product managers for some new features, sometimes quite a lot. Then, being a PM is about taking their feedback into account and managing their expectations.</p><p>In order to do so, include them in your routine. One easy thing to do is setting up a weekly or biweekly session with the head of customer support. That will allow them to keep you up to date with upcoming issues, or suggestions. On the other side, you will be able to present upcoming projects or insights you have.</p><p>It will also push the CS team to centralise their requests through one person, and thus only push further the ones that are really valuable.</p><p>Don’t hesitate to discuss your roadmap, to present how projects succeed to each other and where their requests could fit or not. Don’t forget to mention trade-offs. The more transparent you are, the less pressure you’ll get from them to get things through.</p><p>Overall, the important piece is to get used to include the CS team and have an open conversation with them, rather than consulting them or being consulted on demand.</p><h3><strong>Gather CS data</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*shxyJ4MWc9dbd2wOGNuh2w.jpeg" /></figure><p>A lot of the quantitative data is very insightful. For example, a pie chart showing the split between the main contact reasons is great. Such a categorisation can further be applied to direct contacts (phone, email, chats), or even to reviews you get on app stores. You can then break down each subject with the CS team. For example the parent subject “Transaction status” could be broken down into “When will the transaction be done”, “I don’t understand the status of my transaction”, “My transaction is delayed”, etc. Knowing the split between high level categories, and their sub-categories is helpful. <br> <br>Every time you release a feature that impacts the user experience heavily, another good metric to track is the contact rate. If users encounter issues, they will contact the team to get help. If you want to see the impact of your feature even more clearly, try to look at the contact rate specifically for the topic of your feature. For example if you are adding some promotion, you can filter out anything unrelated to prices or to the business model.</p><p><em>Tip: when looking at contact rates, look the number of tickets in comparison to users activity. Don’t forget to divide it by the number of active users, or by the number of purchases (whichever is the most relevant).</em></p><p>Knowing how many tickets or requests can be solved with one-answer-only is another good metric. Those tickets are usually easy to close. It can be from the CS team itself through a macro generating answers, by adding some self-service in the product, or through a bot that would pick up the information the user needs or process the request internally, as a CS agent would do. Then prioritise. If it is easy to group answers using a macro, but the automation is heavy, maybe the work on such a feature can be delayed for now? Such data informs well on projects’ impact.</p><p>It is great to have all this data to identify issues, but you will need to follow up with the CS to adjust with qualitative data, and go beyond.</p><h3><strong>Include the team in your process</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*bEFK2oGaMwOdcljC8rszMA.png" /></figure><p>A lot of the ceremonies a PM runs would benefit from the CS team input.</p><p>A good session to invite them to is your sprint demo, they will give very good recommendations for your next iterations. You can even go beyond, and present them wireframes or designs before you bring them to engineers. They will be able to confirm whether the experience matches the need, and might raise important edge cases.</p><p>In a past experience, we had some monthly presentation to the C-levels about our progress. We were talking about issues identified, the solutions implemented, and impact on KPIs. We ended up including the CS team as presenters for some parts of the session. Having them was consolidating our message on user satisfaction, and united us a lot. We were feeling more like squad with one goal, rather than multiple teams working in parallel to try and make it happen.</p><p>For example, when brainstorming a problem, to try to find a solution within a range of many solutions, definitely include the CS team. They will add some options that might be very relevant. But beyond that, they will help you identify the solutions that match your users’ mind set. <br> <br> Before we had proper quantitative data to prioritise everything, I went through this process:</p><ul><li>Give your group a problem. Good to have a bit of CS, design, product, 1–2 engineers in there. Ask them to breakdown your problem into smaller chunks.</li><li>For each chunk, ask them to brainstorm potential solutions</li><li>Last round is voting. Give them (for example) 2 votes each, and make them vote on the problem chunk that is the most important, then 2 votes each again for solutions.</li></ul><p>Such an exercise will trigger very good cross team conversations. We ended up with an ordered list of action items, quite driven by the CS insights. When the quantitative data came up, it confirmed the prioritisation we had from the brainstorming. You can trust your CS team.</p><p>To summarise, working with the CS team can only bring you some more awareness on your users. Don’t take their requests as a burden, include them in your work routine as much as possible. They will understand your constraints, you will save a huge amount of time, and it will make your reasoning more solid.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48b70ec77e15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-work-with-customer-support-for-better-product-management-48b70ec77e15">How to Work With Customer Support for Better Product Management</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four tips that will make you a more efficient product manager]]></title>
            <link>https://medium.com/azimolabs/four-tips-that-will-make-you-a-more-efficient-product-manager-9435998ebe17?source=rss-c9185aeb2dcf------2</link>
            <guid isPermaLink="false">https://medium.com/p/9435998ebe17</guid>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[time-management]]></category>
            <dc:creator><![CDATA[Chloé Rozenbaum]]></dc:creator>
            <pubDate>Wed, 22 May 2019 10:25:22 GMT</pubDate>
            <atom:updated>2022-03-16T14:09:44.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6vN55VxNDgs08pbPjEunGA.png" /></figure><p>Product management attracts people from a wide variety of backgrounds. Some are business specialists, others are former designers or engineers. Some are charismatic communicators, others are process ninjas.</p><p>Finding a middle ground between these skills is difficult but essential. Here are four things that helped me to become a more efficient and effective product manager.</p><p><strong>Push back and ask stakeholders to do the maths</strong></p><p>Product managers have to say no all the time, but knowing when and how to say no is tricky. A good way to improve the quality of your stakeholder requests is to push back and ask for more data. Don’t demand in-depth analysis — that’s your job — but some questions are broad enough to be answered by stakeholders without too much effort. Encourage them to bring some key information that will help you make a faster decision. Things like:</p><ul><li>How many users might this affect?</li><li>What are the basic use cases?</li><li>What problems does this issue cause for customers or the business?</li></ul><p>These simple questions will encourage the stakeholder to think the request through before firing off an email, saving both of you time in the long run. Your conversations will become more productive as stakeholders grow to understand how you decide priorities.</p><p>Senior managers will sometimes look at your roadmap and ask you to prioritise a shiny feature that they want delivered. Occasionally a stakeholder might even speak to an engineer and bring you a request that they know is small: “The engineer said it’s only a few hours work — can’t you just work in parallel on feature A and feature B?”</p><p>The best response is to explain that delivery is a zero sum game. If you switch resources to the stakeholder’s priority, feature B will be delayed. Concrete examples are the best way to show the consequences of tradeoffs.</p><p><strong>Have smarter meetings</strong></p><p>Meetings are like rabbits — they breed fast and soon overrun your territory. Whenever a calendar invite drops into your inbox, make sure to establish a few basic facts:</p><p><em>Does this need to happen now?</em></p><p>If a stakeholder wants to talk about a feature that you won’t work on for several months, don’t have a meeting for the sake of it. You will likely forget the decisions you made, or they will be unclear by the time you execute them. Worse, many decisions will become obsolete as circumstances change.</p><p>If your stakeholder insists, agree to a high level discovery meeting with a strict agenda and time limit. Explain your reasons politely and a good stakeholder will understand.</p><p><em>Who really needs to be present?</em></p><p>Only invite essential participants to a meeting. While it’s important to keep people in the loop, it’s far more efficient to have short meetings with a few participants than long ones with 10. That way everyone is heard and results/decisions are clear.</p><p>Requirements gathering meetings are a good example. Try grouping technical people into one meeting and operational people into another. It is then easier to have a global session to make sure everybody is on the same page. Try not to have catch-up meetings unless strictly necessary.</p><p><em>Is the agenda simple?</em></p><p>I used to waste time writing a long agenda for every meeting invite that I sent. As my meetings became more concise and efficient, I began to add a one-line description of the expected outcome to the title of the event. That was enough.</p><p><strong>Have clear, achievable weekly and daily goals</strong></p><p>To run smart meetings, you need to know your weekly and daily priorities. At the beginning of each week, make a list of your weekly goals. At the beginning of each day, make a list of what you want to achieve by close of business. Your daily goals should not be a copy and paste of your weekly goals. They should contain the specific tasks that allow you to meet the broader weekly goal.</p><p>Don’t spend too long on this task: add just enough detail to show you what is on your plate so that you won’t forget things.</p><p>Here is an example of my goals for this week:</p><blockquote>Continue the recruitment for JTBD</blockquote><blockquote>Start preparing the scope for transaction flow work. Look at data and funnels</blockquote><blockquote>Look at the competitors analysis and put findings into a document</blockquote><blockquote>Write my article</blockquote><p>And my to-do list for a given day of this week:</p><blockquote>Do research for my article and write the skeleton</blockquote><blockquote>Look at the transaction funnels</blockquote><p>Keep your list personal. If your team is about to release a project, don’t write “Release project A”. It’s too broad and covers the rest of the team’s work. Instead, write something like: “Make sure everything is ready for the release — handle internal and external communications.”</p><p>If your goals are personal and achievable, you own them and can tick them off without too many dependencies. Seeing your progress throughout the week will also boost your motivation and sense of achievement.</p><p>With a good list of priorities, it will be easier to figure out which meetings are necessary, who you need to talk to and what can be postponed to another week.</p><p><strong>Communicate more efficiently</strong></p><p>Product managers must communicate with a lot of stakeholders, often in different time zones.</p><p>At Azimo, we don’t use email very often. It’s usually reserved for official things, such as a decision or the outcome of a meeting that needs to be shared broadly and followed up. The more direct the communication is, the more efficient it will be. Chat is better than email, a call is better than chat.</p><p>But chat brings its own challenges. Most PMs will be subscribed to at least 20 chat channels, not including private messages. In general, messages are best responded to straight away. If you can’t, Slack reminders are a great way to catch up later.</p><p>It’s better to have a private message conversation with multiple participants than to rely on a public channel. People often mute public channels or your conversation gets lost in somebody else’s conversation. It’s much easier to get a reaction or decision from a private message.</p><p>Finally, do not make decisions on Slack. They are easily lost and there is no single source of truth among all the competing channels and conversations. Use a proper tool to document and share your decisions, such as Confluence or Google Drive.</p><p>Ultimately, voice or video calls are the easiest and fastest way to communicate when it matters. Few people like conference calls, but a short meeting is better than a chat conversation because:</p><ul><li>Answers are more accurate</li><li>Decisions are clearer</li><li>Fewer assumptions are made</li><li>Messages aren’t ignored or forgotten</li></ul><p>These tips helped me in my early career as a product manager. What lessons would you pass on to the next generation of product managers? Let me know in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9435998ebe17" width="1" height="1" alt=""><hr><p><a href="https://medium.com/azimolabs/four-tips-that-will-make-you-a-more-efficient-product-manager-9435998ebe17">Four tips that will make you a more efficient product manager</a> was originally published in <a href="https://medium.com/azimolabs">AzimoLabs</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 build an agile roadmap?]]></title>
            <link>https://medium.com/azimolabs/how-to-build-an-agile-roadmap-f7df0fe606?source=rss-c9185aeb2dcf------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7df0fe606</guid>
            <category><![CDATA[product-roadmap]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Chloé Rozenbaum]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 09:13:20 GMT</pubDate>
            <atom:updated>2021-03-10T12:12:14.932Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to build an agile product roadmap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*ITlKBTv9liQMerlpg4Be1w.png" /></figure><p>The roadmap is an essential part of a product manager’s toolbox. It shows the company the road ahead, it shows my manager whether I’m building the right thing and it shows other teams potential dependencies. The better a roadmap is defined, the clearer things are for everyone.</p><p>But how can a roadmap both plan for the future and stay agile? How do we compromise between business needs and the ability to build, test, iterate and stay lean?</p><h3><strong>What is a roadmap?</strong></h3><p>“A plan for the future, usually with a particular goal.”<br><a href="https://www.oxfordlearnersdictionaries.com/definition/english/road-map"><em>The Oxford Learner’s Dictionary</em></a></p><p>At its simplest, a product roadmap is a chronological list of what you’re going to build next, with individual features listed in varying levels of detail. It looks similar to a Gantt chart, though in practice it is a much more flexible document, with fewer details.</p><p>So, the roadmap is a visualisation tool. Simple enough. The tricky part is working out how to define, prioritise and build the features that you’ve listed, which is why a roadmap cannot exist by itself. Three things are needed to build one: scope, complexity and priority.</p><h3><strong>How do you define a roadmap?</strong></h3><p><em>Scope<br></em>Defining scope is the core of a PMs job. User testing, user interviews, analytics, research, business vision and other tools help you to define the problem, explore solutions and back up your decision with data. If there is no measurable business or customer value, a good manager will rightly kill your feature. Good PMs and good managers don’t chase shiny, complex features, they focus on where the value lies.</p><p>The most common approach is to build an MVP and then follow up with further releases. However, never build an MVP that doesn’t provide value on its own. If priorities change you can be left with a product that doesn’t bring any value to the business or its customers.</p><p><em>Complexity<br></em>Estimating complexity is notoriously tricky. I learned very early in my career not to make promises based on my own assumptions. Ask your engineers: they are the technical specialists, they know best. Your job is to give them as much context as possible so that they can understand the problem, advise on the solution and define the architecture. They will often find use cases that you never considered.</p><p>Next up is sizing. It’s safe to assume that the bigger a project is, the more surprises you will receive. The complexity of user stories is estimated using the Fibonacci sequence because risk does not grow in parallel with size. The same method can be used to estimate project complexity, though the following factors should be taken into account:</p><ul><li>The project’s complexity</li><li>The team’s knowledge of the codebase</li><li>Technical debt</li><li>Distractions</li></ul><p>A good approach is to split the MVP into smaller pieces, estimate the size of each piece with engineers and repeat as necessary. Adding a margin of error to the total estimate will give you an idea of timeframe.</p><p><em>Priority<br></em>If you have scoped the project and estimated complexity properly, priority should be easy to decide. Ideally you will build the features that offer the highest business and customer value for the lowest effort first. But what happens when a high value feature is highly complex and has to be prioritised against a simple, easily-built lower value feature? Quick win or big win?</p><p>One method is to calculate the cost of delaying release, which works well to compare features that solve different problems. This technique can be used to evaluate a feature that decreases churn versus a feature that increases acquisition. If you have enough resources, you could also run two queues of work in parallel: one for large features and one for small. That way you can put, for instance, 20% of the team’s effort into small features or technical debt.</p><p>Regardless of how you tackle prioritisation, you have to do your homework. Don’t prioritise anything without scope and complexity.</p><h3>… <strong>and here’s how you make it agile</strong></h3><p>So, you’ve done the hard work. You have your scope, complexity and priority. Surely now you just have to draw the roadmap and get on with it? Not really, no. If a roadmap is just a visualisation tool, it must adapt to the data, research and circumstances that it visualises. New features appear, customer desires change, technical debt is fixed and architecture is updated. Scope and complexity also change as projects progress. To be agile, your roadmap must evolve with your business and the needs of your customers.</p><p>But why do we even need a roadmap? Why spend so much time and effort on something that keeps changing? The answer is simple: because nobody wants to read a 30-page waterfall document, and 30-page documents are hard to update with the new research, testing results, hypotheses, scope, metrics etc. that your build-test-iterate model will bring.</p><p>A roadmap should be rigid enough to show a plan but flexible enough to respond to new developments. You don’t have to waste time going into detail for features that are months away, but you should be more precise about features that are coming soon. Offer just enough precision for each step of the journey.</p><p>Finally, remind your team and the business that the roadmap will change over time<em>.</em> It’s just a tool to visualise your work and communicate your plans. The roadmap is definitely a living document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*pagm7ooXu-XokowSn49TBQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*z_7AZoKHk7uAHVmRA1fOSg.png" /><figcaption>Old roadmap — Updated roadmap</figcaption></figure><h3>Towards financial services available to all</h3><p>We’re working throughout the company to create faster, cheaper, and more available financial services all over the world, and here are some of the techniques that we’re utilizing. There’s still a long way ahead of us, and if you’d like to be part of that journey, check out our <a href="http://bit.ly/3vajnu6">careers page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7df0fe606" width="1" height="1" alt=""><hr><p><a href="https://medium.com/azimolabs/how-to-build-an-agile-roadmap-f7df0fe606">How to build an agile roadmap?</a> was originally published in <a href="https://medium.com/azimolabs">AzimoLabs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>