<?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 Viktor Müller on Medium]]></title>
        <description><![CDATA[Stories by Viktor Müller on Medium]]></description>
        <link>https://medium.com/@viktormuller?source=rss-7df8b4215bbf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*v3INMWxGMHt8NPwa.jpg</url>
            <title>Stories by Viktor Müller on Medium</title>
            <link>https://medium.com/@viktormuller?source=rss-7df8b4215bbf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:38:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@viktormuller/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[Requirements]]></title>
            <link>https://medium.com/@viktormuller/requirements-2f851e50fce3?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f851e50fce3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[press-release]]></category>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 10:50:15 GMT</pubDate>
            <atom:updated>2023-03-21T10:50:15.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxQb8so2T8jjGN_I-BjQcg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@sxoxm?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sven Mieke</a> on <a href="https://unsplash.com/s/photos/blueprint?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This document is part of a <a href="https://medium.com/@viktormuller/introduction-766dbb30a6e7">series</a> that tries to describe a starting point for a product management organization in a Series A startup.</p><p>This chapter covers:</p><ul><li>Initiatives to requirements</li><li>The Press release</li><li>The Product requirements document</li><li>UX design and testing</li></ul><h3>Initiatives to requirements</h3><p>Product managers drive the execution of initiatives defined in the <a href="https://medium.com/@viktormuller/quarterly-planning-and-okrs-a7dae2b1be90">quarterly plan</a> for their respective teams. They need to <strong>detail the solution from a user (customer) perspective</strong>. They need to refine these with designers and engineers, leveraging their expertise. When they are finished, everyone should be aligned within the team on what the solution should look like for the users. Often some of the key design choices are also made at this point as they influence the requirements and vice-versa.</p><p>They start with detailing what is to be built by writing Press releases (PR FAQ) and Product requirements documents (PRD). <strong>Press releases (PR FAQ) are used for new product launches,</strong> major, stand alone new value propositions. <strong>PRDs are used for smaller individual features </strong>which reinforce existing value propositions. A PR FAQ for a new product can be followed by a few PRDs detailing some key, non-trivial features.</p><p>PR FAQs and PRDs should be <strong>widely circulated from early draft stages</strong> to leverage all the skills and experiences available in the organization. The more important, the more people should review it. They should be reviewed with:</p><ul><li>Tech lead</li><li>Designer</li><li>VP of product</li><li>In the weekly / fortnightly PM meeting (we will cover this in a future chapter)</li><li>[Optional] any domain expert</li><li>[Optional] CEO, CTO</li></ul><p>The purpose of these reviews is to <strong>help the PM with a diverse set of perspectives</strong> early on. These are not necessarily approval gates but resources that are available to improve the proposal. PMs do not need to incorporate all recommendations but they should use them as food for thought to improve their documents. Furthermore PMs will find it much easier to execute initiatives if they generate broad organizational alignment early on.</p><p>These reviews can be offline by commenting on the document or in a meeting or video call. Often it is best to send the latest draft 24 hours before the meeting to reviewers. If not everyone has read the document beforehand then take 5–10 mins at the beginning for everyone to (re)read it.</p><p>Stereotypically <strong>PMs should be in charge of finalizing the document </strong>(responsible in <a href="https://en.wikipedia.org/wiki/Responsibility_assignment_matrix">RACI terms</a>) and they would need to get <strong>approval from the VP of product</strong>. The approval step should be delegated further down in the organization for smaller scopes and as the organization and the individuals in it grow. In early stage startups, often the individual PMs are relatively junior and hence such a formal approval and close oversight from the VP of product is helpful.</p><p>Typically these documents benefit greatly from multiple people thinking about them over a few days and even weeks. Hence it is ideal to <strong>start drafting them several weeks before engineering</strong> is expected to start work.</p><h3>The Press release</h3><p>Amazon (and others, like Twilio) uses Press releases (PRs or PR FAQs) as part of their “<strong>working backwards</strong>” approach to product management. It suggests starting by describing the product from a customer’s perspective and working backwards to define the incremental versions and implementation details.</p><p>It is helpful to start from a standard layout for PR FAQs to make sure all key questions are answered. A version of that is nicely documented by <a href="https://medium.com/bluesoft-labs/try-an-internal-press-release-before-starting-new-products-867703682934">Andre Faria’s (CEO, Bluesoft) blog post</a>:</p><p><em>“Heading — Name the product in a way the reader (i.e. your target customers) will understand.</em></p><p><em>Sub-Heading — Describe who the market for the product is and what benefit they get. One sentence only underneath the title.</em></p><p><em>Summary — Give a summary of the product and the benefit. Assume the reader will not read anything else to make this paragraph good.</em></p><p><em>Problem — Describe the problem your product solves.</em></p><p><em>Solution — Describe how your product elegantly solves the problem.</em></p><p><em>Quote from You — A quote from a spokesperson in your company. Often a good way to talk about secondary benefits or future ideas</em></p><p><em>How to Get Started — Describe how easy it is to get started.</em></p><p><em>Customer Quote — Provide a quote from a hypothetical customer that describes how they experienced the benefit.</em></p><p><em>Closing and Call to Action — Wrap it up and give pointers where the reader should go next.”</em></p><p>Here is what it may look like in practice: <a href="https://medium.com/@viktormuller/press-release-example-6edd16c6c3a4">Financial planner — PR</a></p><p>It is often very helpful to add <strong>Frequently Asked Questions</strong> (FAQs) to PRs to help address the many questions that arise from it. Often these are split into <strong>External FAQs and Internal FAQs</strong>. The former targets customers and answers their potential questions about detailed product behavior, pricing, access or anything else that may not fit into the constraints of the PR. The latter targets engineers, designers and other employees and clarifies key questions about implementation details, internal processes and sometimes key alternatives considered.</p><p>Generally FAQs are useful to complement the PR and answer the first round of questions, clarify the value proposition and show its general feasibility. But it is <strong>not a good replacement for a PRD or UX / UI design </strong>to detail requirements.</p><h3>The Product requirement document</h3><p>Product requirement documents (PRDs) come in many shapes and sizes but they should always try to capture the following information.</p><ul><li><strong>Customer problem </strong>— Describe the customer segment and persona. What are they trying to achieve and why? How are they doing it now and what is their challenge? Refer to specific customers.</li><li><strong>High-level solution</strong> — Describe how the new solution is solving the problem differently and its key benefit for the customer.</li><li><strong>Functional requirements</strong> — Detail all the key behaviors of the solution.</li><li><strong>Non-functional requirements</strong> — See details below</li><li><strong>Success criteria</strong> — Describe how you will determine (often through a metric) whether the feature has been successful or if further adjustment is needed.</li></ul><p>For functional requirements, it is often helpful to start with <strong>user stories</strong> that describe particular actions, specific user personas are trying to complete to achieve specific goals. This helps <strong>describe intent</strong> in detail <strong>without restricting designers and engineers</strong> to come up with innovative solutions.</p><p>In a typical SaaS product usually there are three potentially important non-functional requirements that PMs should think about:</p><ul><li><strong>Scalability</strong>: How many users, data, transactions, etc. need to be supported in this version?</li><li><strong>Performance</strong>: How fast the users should receive responses? (especially from long running, non-interactive processes)</li><li><strong>Availability</strong>: How much of the time (99% or 99.999%) the system or the features needs to be available?</li></ul><p>Security and Maintainability can also be quite important but are typically the domain of tech leads. However if there is a disconnect in the team’s estimate for the size of the task and the expectations of the PM then misalignment on these or the other non-functional requirements can often be the culprit. A simple feature can become a lot more complex if it needs to scale to 10m users instead of 10k users.</p><h3>UX design and testing</h3><p>If the feature in question requires (non-trivial) changes to the UI of the application then it is useful to produce the necessary designs prior to commencing front-end development. Stereotypically this process is driven by the team’s designer based on the PRDs and support from the PM.</p><p>Depending on the nature and extent of the change, some <strong>user testing is usually more cost efficient than fixing issues once the software is built</strong>. Larger changes, net new experiences require more exhaustive testing, with more users and often multiple rounds. If the user experience is novel, e.g. a new way of finding restaurants then that also will result in longer, iterative user testing. On the other hand, standard functionality (e.g. log in / sign up) and small changes (especially if already based on user feedback) may require very little or even no testing.</p><p>Furthermore — especially when working on new or complex experiences — UX design and testing<strong> can often influence requirements</strong> resulting in more of an iterative process than a simple one-way one. It is important to keep in mind that the <strong>goal is to set the best requirements and develop great designs, not to finish the task within some arbitrary deadline</strong>.</p><p>From a CEO or CPO perspective, the most important thing is to be aware of the long term cost and time saving opportunity of user testing (especially major changes and novel UX) and <strong>anticipate the time needed to complete it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f851e50fce3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Press release example]]></title>
            <link>https://medium.com/@viktormuller/press-release-example-6edd16c6c3a4?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/6edd16c6c3a4</guid>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Tue, 21 Mar 2023 10:34:10 GMT</pubDate>
            <atom:updated>2023-03-21T10:50:31.421Z</atom:updated>
            <content:encoded><![CDATA[<p>This is an example of a Press release used for illustration in the <a href="https://medium.com/@viktormuller/requirements-2f851e50fce3">Requirements chapter</a> of a series on product management organization in a Series A startup.</p><p>Although it may not describe a great product, it has all the key elements of a Press release and hence can be used as a template for new ideas. In hindsight, it is probably a bit too long.</p><h3>Introducing Financial Planner</h3><p><em>The new app that helps millennials plan their future with confidence</em></p><p>LONDON — July 1st, 2021 — Starting today Financial planner is available in the UK for young people to help them gain control of their financial future. With the new app, millennials for the first time can easily understand how their choices today influence their lifestyle in 20, 30 or even 50 years in the future. They can start making more conscious decisions about how much they want to spend now and how much in the future.</p><p>Young professionals often struggle to assess whether they are saving enough. We earn more than we need for subsistence but not enough to fulfill all our wants. We see exciting lifestyles and experiences on social media but we do not know how others’ really live off-Instagram. Owning a home seems almost unachievable, and we know we will need to pay for our own retirement. But how much saving is enough? Should I just save every penny and not enjoy life while I am young or should I just YOLO it? These are key questions our generation struggles with.</p><p>Financial planner allows users to look decades into the future and see how their decisions today influence their life when they have kids or when they retire. They can start with median assumptions of having 2 kids and buying a family home and a car and retiring at 67 and see what lifestyle they will be able to afford when they retire. They can then play with assumptions, adjust their current lifestyle and see how their choices today translate into outcomes in decades. They also get to see how they are doing against their peers, they are told how their savings or income compare to the typical values of their age group, now or in 30 years.</p><p>The app is available to everyone in the UK for free starting from today. Anyone can build their own plan without registering. If someone wants to keep their results or track their progress against their plan, they can create an account and start their journey to financial confidence.</p><p>“We wanted to help young people become confident about their future. I have seen many of my talented, highly educated friends struggle to manage their finances. They did not know how to get started, it was too intimidating. And let’s be honest the financial planning services today are designed for baby boomers. We wanted to build something that is easy to use but helps you get realistic about your options, and hence lets you make smart choices today.” — said Viktor Muller, co-founder of Financial planner.</p><p>“I was already making decent money but I still had some student loans left. I wanted to start thinking about having a family, buying a home but I was just too afraid to look at the numbers, I did not know where to start so I just kept putting it off. The Financial planner app allowed me to get started. Because it gave me a plan instantly, I knew I could do this. I just needed to tweak a few parameters, to make it fit my life, the whole thing took like 5 minutes. When I saw that I am doing better than most in my cohort, it just lifted a massive weight off my shoulder. That got me interested, I realized, I could actually get smarter about my spendings now and retire 10 years earlier. Those five minutes genuinely changed my and my family’s life.” — Jessica, 32, global marketing director.</p><p>If you want to get confident about your future and find out how you are doing relative to your age group visit financialplanner.com and start your journey to financial security now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6edd16c6c3a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quarterly planning and OKRs]]></title>
            <link>https://medium.com/@viktormuller/quarterly-planning-and-okrs-a7dae2b1be90?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7dae2b1be90</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 09:23:49 GMT</pubDate>
            <atom:updated>2023-03-10T11:29:56.103Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product management in a Series A startup — Quarterly planning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFTEwi0bDad-rMOMEkGZlA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@airfocus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">airfocus</a> on <a href="https://unsplash.com/s/photos/planning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This document is part of a <a href="https://medium.com/@viktormuller/introduction-766dbb30a6e7">series</a> that tries to describe a starting point for a product management organization in a Series A startup.</p><p>This chapter covers:</p><ul><li>Why planning?</li><li>Outputs of planning</li><li>The planning process</li></ul><h3>Why planning?</h3><p>Planning tries to solve <strong>strategy, communication and alignment problems</strong>. It forces leadership to pause, internalize recent learnings and make adjustments to the priorities of the organization if necessary.</p><p>It creates an opportunity for leadership to <strong>communicate new priorities</strong> to the teams or reinforce existing ones. At the same time it also gives teams a chance to <strong>communicate challenges</strong> in operating products or further developing them (e.g. tech debt). Teams should also use planning to <strong>share their best ideas</strong> on how to work towards the priorities and what <strong>resources</strong> it would take (money, people, management attention, etc.).</p><p>Finally, at the end of the process <strong>teams and leadership should be aligned</strong> on who is working on what priorities and why and how they plan to solve for them. They agree that these plans are <strong>ambitious but realistic</strong> and they all commit to their necessary contributions.</p><p>That said, the resulting plan should be considered a “plan of record”. <strong>A plan valid until further change</strong>. Critical new learnings should be incorporated as soon as possible, even between planning cycles.</p><h3>Outputs of planning</h3><p>There are many different ways to structure and standardize the output of the planning process (OKRs, OMGs, V2MOMs, etc.). In this document, we use Objectives, Key results (OKRs) and Initiatives but as long as the planning process achieves the outcomes described above any format can be used. OKRs were originally “invented” at Intel in the ’70s and got popularized by Google.</p><p><strong>Objectives</strong></p><p>Objectives are high-level, typically qualitative goals that may take several quarters to accomplish. E.g. become the lowest cost provider or have the highest customer satisfaction in the industry. These can be set at each organizational hierarchical level. Obviously lower level objectives should contribute to their parent level and can only be more specific and narrower in scope.</p><p><strong>Key results</strong></p><p>Key results (KRs) are measurable outcomes (e.g. improve a KPI from X to Y or create a new capability X) that measure progress towards Objectives. They allow setting interim targets and tracking progress towards an Objective. Don’t be afraid of KRs shared by multiple teams, it encourages cooperation among them. (See Six Simple Rules by Yves Morieux)</p><p><strong>Initiatives</strong></p><p>Finally the quarterly plan is a sequence of Initiatives that the team will undertake in the quarter to achieve the KRs and move towards the Objectives. For example: build the new onboarding flow (Initiative), to improve conversion from X to Y (Key result) and accelerate growth (Objective). The initiatives form a more detailed plan than the overall Roadmap. It includes high-level resource requirements, dependencies and any risks already identified. The teams and the executive team should have relatively high confidence that they can accomplish the plan.</p><p>As a result OKRs and the Initiatives work together to ensure teams are clear on <strong>what is expected of them and how to get started</strong>. Plans should be ambitious but realistic. Organizations should <strong>aim for 80% KR achievement</strong>. Consistent 100%+ KR achievement indicates that the plans are not sufficiently ambitious and do not push the teams outside of their comfort zone. If KRs are calibrated for &lt;100% achievement that should be communicated to the teams.</p><p><strong>Team-level deliverable template</strong></p><p>These quarterly OKRs and Initiatives can have a very simple format. The focus should be on the discussion not creating dozens of slides or thousands of words.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kbgs9UdgRZI42cZCtoPyw.png" /><figcaption>OKRs and Initiatives template for teams</figcaption></figure><p>Stereotypically a small team of 4–7 engineers, should not have more than 1–3 objectives, 1–2 key results per objective and 1–4 initiatives for a quarter. A lot more than that and the planning is too granular wasting everyone’s time or the team is overcommitting.</p><h3>The planning process</h3><p>A series A company should<strong> </strong>regularly revisit its roadmap, especially the next 2–3 months to <strong>reflect the latest learnings</strong>. Ideally this happens naturally whenever major learnings occur however it is hard to stay on top of that in the day to day hustle.</p><p>Therefore companies (and teams) often adopt a quarterly planning cycle as a <strong>forcing function </strong>to revisit priorities and set new targets. Other parts of the organization (e.g. sales and marketing) are more naturally driven by quarterly objectives and hence this also helps align with those as well as board updates.</p><p>Generally quarterly planning should not take a full quarter of its own. Ideally it should be completed in <strong>2–3 weeks at the end of the previous quarter</strong>.</p><p>The planning is ideally a <strong>V shaped process</strong>, starting and ending with leadership decisions with teams contributing in the middle:</p><ol><li>Leadership sets Objectives and Key results for the whole organization</li><li>Objectives are aligned to teams who translate them to Key results and Initiatives</li><li>Executive team reviews the team-level Objectives, Key results and Initiatives.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/0*vdLR5wu3I7VM6JGS" /><figcaption>Most of planning is about sharing ideas across the organization</figcaption></figure><p>Step 1 is about the <strong>leadership </strong>(executives and board) agreeing among themselves on the most important <strong>priorities for the next quarter</strong> and communicating it to the organization. This can be as simple as “reduce churn”. There is no need to create new objectives for each quarter, actually it creates predictability and hence efficiency if the organization can work towards the same objective for a few quarters. Key results however should be updated to reflect the progress made last quarter and the new ambition.</p><p>In Step 2 the VP of product (and other executives in their respective organizations) works with the PMs to <strong>align the Objectives to each team</strong>. At this point it should become clear which team is going to contribute to which Objective. Teams should also <strong>surface any critical priorities that are not aligned to company Objectives</strong> but cannot be solved as a small task within the team’s discretionary maintenance capacity (we will cover maintenance in a future chapter). These could for example be left over work from the prior quarter or critical tech debt (e.g. security issues).</p><p>As Objectives are aligned on a team level, the VP of product continues to work with the PMs to <strong>set KRs</strong> for these and <strong>define the initiatives</strong>. More senior PMs are expected to drive the process independently and consult the VP of product once or twice before finalizing it. Junior PMs will work closely with the VP, including common brainstorming sessions and even daily reviews.</p><p>Each PM should also <strong>review and align the proposed OKRs and initiatives with their teams</strong> prior to discussing it with the executive team. Especially important that the initiatives are <strong>checked against available capacity</strong> by at least the tech lead. All estimations (especially such high-level ones) are always going to be highly inaccurate but at least obvious excesses can be identified and trust can be built within the teams.</p><p>In Step 3, the team leadership (PM, tech lead and design lead) <strong>discuss</strong> their proposed OKRs and Initiatives<strong> with the executive team</strong>. They should highlight any<strong> risks, resource shortfalls or cross-functional dependencies</strong> (e.g. a marketing support needed for a launch). The goal is for everyone to agree that</p><ul><li>the plan is ambitious but realistic</li><li>they believe if the plan is completed the OKRs will be achieved and</li><li>they will commit the resources necessary from their respective organizations.</li></ul><p>Once all the OKRs and initiatives are established it is important to <strong>share them across the organization</strong>. This helps coordination across teams and functions as people become more aware of the key initiatives happening in the organization. It will also serve as the basis of reporting progress (tracking progress will be covered in a future chapter).</p><p>In summary, this process is designed such that <strong>everyone is doing what they are best at</strong>. The leadership sets top down priorities. Teams develop solutions and detailed plans to deliver against those priorities, identifying risks and asking for help where they need it. Finally, leadership helps with their experience to judge the feasibility of those plans and reallocate resources or adjust expectations when necessary.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7dae2b1be90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product management in a Series A startup — Product strategy & Roadmap]]></title>
            <link>https://medium.com/@viktormuller/product-management-in-a-series-a-startup-product-strategy-roadmap-cef4227e6098?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/cef4227e6098</guid>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[roadmaps]]></category>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Mon, 20 Feb 2023 12:59:55 GMT</pubDate>
            <atom:updated>2023-02-20T13:05:26.016Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product management in a Series A startup — Product strategy &amp; roadmap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jP355NETmYhwc4Hja6KMeQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/ja/@slidebean?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Slidebean</a> on <a href="https://unsplash.com/s/photos/product-roadmap?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This document is <a href="https://medium.com/@viktormuller/introduction-766dbb30a6e7">part of a series</a> that tries to describe a starting point for a product management organization in a Series A startup.</p><p>This chapter covers:</p><ul><li>Product strategy: Choosing the problem to focus on</li><li>Product vision: Defining the solution to the problem</li><li>Concept design: Validating the solution</li><li>Product roadmap: Sequencing the solution</li><li>Maintaining these artifacts</li><li>Suggested reading</li></ul><h3>Product strategy</h3><p>The goal of product strategy is to focus the organization towards a common direction. It defines</p><ul><li>the target customer segment (often called the ideal customer profile),</li><li>their unmet need that the company is going to solve.</li></ul><p>Often there are many competing options and the company may have had some success with solving multiple problems for multiple segments by the time it raises a series A round. At this stage the company has typically built some unique capabilities and gained some proprietary customer insights but <strong>does not yet have the resources to compete directly with incumbent corporations</strong> in mainstream markets.</p><p>Therefore the strategy needs to <strong>narrow its focus to a single segment with an unmet need</strong>. Often these are <strong>smaller, less profitable, harder to serve segments</strong> than the mainstream. For example, at Steward we chose to focus our financial advice on mass affluent customers in their 30s and 40s even though they were much less profitable and a smaller segment than the mainstream high-networth (&gt;$1m in savings) retirees all the while having vastly different needs. But that is exactly why very few companies were targeting them, giving us an opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*i2IVvTrG4D4hG9jOeQw1FA.png" /></figure><p>When it comes to choosing target segments traditional (corporate) wisdom prefers large and fast growing segments. Given Series A companies are still small ($1–5m revenue) they do not yet need multi-billion dollar markets to achieve impressive growth. Therefore <strong>market size is only a pass / fail criteria. </strong>Markets with <strong>$50–100m potential are usually sufficient</strong> to reach series A revenue targets ($3–10m). Segment growth however is more relevant, no company wants to invest into a shrinking opportunity.</p><p>Another important consideration is to focus on problems that the company is <strong>uniquely positioned to solve</strong>. At this stage, this typically comes from the <strong>founders’ unique talent or experiences</strong>. Going back to the financial advisory example, at Steward we found a brand persona that resonated with this segment and proven that we can turn daunting financial questions into simple, personalized answers with high-level of automation to reduce cost.</p><p>When looking for unique strengths, a good place to start from is<strong> where the company has had success so far</strong>. What type of customers are most enthusiastic about the product, who is it easiest to sell to, who adopts it most easily? What are they using it for and how? Why is it so valuable to them? What did they do before? What convinced them to switch to your product?</p><h3>Product vision</h3><p>The vision describes the company’s <strong>plan of what the future solution to that problem looks like</strong> and its role in it.</p><p>Having a clear product vision helps <strong>align the whole organization and other stakeholders</strong> (investors, customers, suppliers, etc.) towards the common direction. It helps PMs, designers and engineers to anticipate future features and choose solutions that enable those. It helps creating and communicating roadmaps as they now have a clear destination and the stops along the way make more sense once we know the destination.</p><p>A good vision describes a solution <strong>10x better </strong>than the current solution. When it comes to vision, less is more. Visions that rely on accumulating features are usually the sign of insufficient customer insight. The vision should be based on<strong> 1–2 killer features</strong>. These can be then complemented by features that increase the value for the customer and make it harder for others to compete.</p><p>For example, a sustainability data provider for investment funds, built their initial success on the quality of their data. For them the killer feature was click to source transparency that made the data quality tangible to customers. They then defined a vision that layered additional data sets and a webapp to access it aligned with the various analysis tasks that their customers used the data for. They topped it off with some experimental ideas to create network effects between sustainable companies and investors by facilitating communication and data sharing. The vision wasn’t dependent on the latter two sets of features. Those were used to further increase value and create barriers to entry (especially via network effects).</p><p>Product vision documents can come in many shapes but it should answer <strong>how the product is solving the customer’s problem?</strong></p><ul><li>How is the customer onboarded?</li><li>How do they activate the product (what they need to do prior to getting value)?</li><li>How do they gain and perceive value from the product?</li><li>How do they keep using the product and getting more value out of it?</li><li>When and how do they pay for the product (or more generally how is it monetized)?</li></ul><h3>Concept design</h3><p>Often it is valuable to <strong>visualize the most critical elements of the vision with mockups </strong>or concept design. This helps communicate the vision to a wide spectrum of audience, especially to customers but also to employees who were not deeply involved in its creation.</p><p>The concept design is typically 20–30 screens that can demonstrate the user experience end to end. It should focus on <strong>key differentiated features in the main success scenario</strong> and can ignore standard functionality (e.g. log in) and error and edge cases. Often the focus is on the onboarding experience through activation and first value delivery. This is because customer acquisition is most critical at this early stage of a startup.</p><p>A key use of these mockups is to be <strong>validated with target customers</strong>. This should allow identifying the most valued features and prioritize those. It also allows tweaking or dropping any ideas that are not validated even at this early stage.</p><p>The validation can be planned by the in-house designers if they have the skills but it can also be worth contracting a specialist researcher for it. Validating someone else’s designs is often easier than your own. In either case the <strong>VP of product needs to ensure the quality</strong> of the process for the best outcomes hence below are some criteria for that.</p><p>Even a small sample of <strong>5–10 users</strong> generally provides an indication of which features are most valuable and if anything in the vision is highly unlikely to work in practice. A good test will <strong>establish objectives up front</strong> and even <strong>define a template to record the outcomes </strong>from each session. These should directly inform feature prioritization. There should also be a <strong>clear guide for the facilitator</strong>. This should ensure non-leading questions are asked (if any) and asked consistently from all participants.</p><p>Besides the good practices, there two main pitfalls of concept validation. The first is l<strong>ow stakes.</strong> When potential users are presented with solutions that come at no cost to them, there is a high chance of getting unduly positive feedback. Combine this with the fact that most people bias towards affirmation in interview settings, it is important to understand whether users are actually willing to endure the friction of using your product instead of their current next-best alternative.</p><p>In a B2B context, it is often helpful to pursue a <strong>letter of intent</strong> (LOI) to raise the stakes and establish a more realistic feedback scenario. In B2C settings <strong>comparing unbranded versions</strong> of your solution vs. established offerings can be a way to elicit honest preferences.</p><p>In B2B companies a second pitfall can be when the <strong>user is not the buyer</strong>. Therefore, it is important to perform validation with <strong>all relevant decision maker personas</strong> to fully understand the value of the concepts to the customer and the value proposition that is needed to drive adoption</p><h3>Product roadmap</h3><p>Given a clear and validated vision, the VP of product should lead the organization to define a high-level roadmap that leads to the vision. It is a<strong> sequencing of the key components</strong> that can be clearly communicated internally and externally (e.g. to customers).</p><p>Besides the vision there are two other (often overlapping) sources of ideas for the roadmap:</p><ul><li>company objectives (churn reduction, adoption increase, etc.)</li><li>improvements of previously launched components.</li></ul><p>While the vision drives net new offerings these other sources typically include <strong>incremental improvements </strong>on existing ones. As such they <strong>typically take precedence</strong> because it is much better to have one great offering than many mediocre ones.</p><p>Therefore as the roadmap is defined it is important to <strong>budget for these, especially after new launches</strong>, anticipating that they will arise even if we do not yet know their exact nature.</p><p>After a major launch <strong>1–2 quarters of refinement is the minimum to expect</strong>. For whole new products or propositions it is not unreasonable to assume that there will be valuable ways to improve it for multiple years. In that case, it can be assumed that additional offerings in the roadmap will require standing up new teams. Recognizing and <strong>budgeting for these follow-on needs forces the roadmap to be more realistic</strong> with fewer launches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/0*yXS0MafVkVchDVGC" /></figure><p>Given the uncertainty (e.g. of follow-on needs), the focus of the roadmap should be on sequencing not on hard commitments to specific solutions many years into the future.</p><p><strong>The next quarter should be most detailed and debated</strong>. Beyond that the roadmap could be defined in looser terms. When looking beyond 6 months, it is often helpful to just refer to the (sub)problems and customer segments that will be addressed rather than specific solutions.</p><p>Key considerations that are taken into account when creating the company-wide roadmap are:</p><ul><li>Impact on company-wide goals (e.g. growth vs. customer satisfaction vs. churn)</li><li>Confidence (how certain are we in the impact)</li><li>Effort</li><li>Dependencies</li><li>Bandwidth of the company (i.e. number of squads, how many topics can be worked on in parallel).</li></ul><p>Confidence is an important element as often the potentially <strong>most impactful ideas are of lowest confidence</strong>. The solution to this is not to deprioritize these but to define the next step as a low effort validation that increases confidence (e.g. conduct customer research, build a waitlist, run user tests, etc.). This will unlock prioritizing a greater investment later on. The roadmap should include (and often prioritize) <strong>validation of critical assumptions of the strategy and vision</strong>.</p><p>In practice, <strong>rigid scoring systems rarely work </strong>because much of the scores and weights are subjective anyway hence they become a distraction from the real conversation of sequencing. Instead it is more useful to lay out an assessment of these factors, have the <strong>key decision makers (e.g. executive team) create their own sequencing and discuss the disagreements</strong>. Often the top and bottom choices can easily be agreed on and the ones in the middle are less consequential as they can be reviewed once more before execution is ramped up.</p><p>In B2B companies, it is often helpful to have a <strong>less specific version of the roadmap for customers. </strong>This saves time for sales executives and helps<strong> </strong>avoid overcommitment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/0*Slqa8oZLNtzBaUFm" /></figure><p>In these B2B companies, the <strong>product organization needs to own the customer facing roadmap</strong> and regularly share it with other functions such as marketing, sales, customer success and support. It should always be kept up-to-date to avoid the need for other functions to fill the void and create their own versions.</p><p>Product managers should also <strong>seek out opportunities to discuss the roadmap with customers</strong> and take it as a chance to learn customer needs and manage expectations. Many B2B companies hold <strong>customer advisory board</strong> meetings on a regular (quarterly, annual) basis to deep-dive on the roadmap with select customers.</p><h3>Maintaining these artifacts</h3><p>In an ideal world all decisions that are taken in the creation of these artifacts (e.g. segment and problem selection, key feature choices, etc.) are backed by rigorous analysis and data. In practice there is <strong>never enough data and time </strong>to back all the decisions perfectly. However it is still much<strong> </strong>better to <strong>write down a draft and call out the unproven assumptions</strong> than to not have them. A key focus of the roadmap then can be validating those assumptions.</p><p>Finally, these are expensive documents to create and update as it requires synthesizing a lot of analysis and insights but it does not directly lead to immediate value for customers. Therefore it is not worth trying to constantly update them. Typically it is sufficient to <strong>revisit the strategy and vision once a year</strong>, updating it based on major learnings. The roadmap is often naturally updated as part of the <strong>quarterly planning </strong>exercise (covered in the next chapter).</p><p>That said, if a learning during the year forces the company to <strong>pivot </strong>(i.e. significantly change its strategy or vision) then <strong>these documents should be updated.</strong> They should be the main tools to align everyone towards that new direction. Having articulated the key assumptions before, should help communicate which one of those were proven wrong and how the new direction responds to that learning.</p><h3>Suggested reading</h3><p>Given product strategy, vision and roadmapping are so critical for the success of any product company there has been a lot written on this. The above is informed by at least the following amazing books:</p><ul><li>The Lean Startup — Eric Ries</li><li>The Innovator’s Dilemma — Clayton M. Christensen.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cef4227e6098" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product mangement in a Series A startup — Organization structure]]></title>
            <link>https://medium.com/@viktormuller/organization-structure-3b28e0c3d1b2?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b28e0c3d1b2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Mon, 06 Feb 2023 10:52:23 GMT</pubDate>
            <atom:updated>2023-02-06T11:01:24.854Z</atom:updated>
            <content:encoded><![CDATA[<p>This document is part of a <a href="https://medium.com/@viktormuller/introduction-766dbb30a6e7">series that describes a starting point for a product management organization</a> in a Series A startup.</p><p>This chapter covers:</p><ul><li>Roles</li><li>Responsibilities</li><li>Reporting lines</li><li>Squad structure</li><li>Squad scope</li><li>Scaling a squad</li></ul><h3>Roles</h3><p>There are three main roles in a typical Series A product development organization:</p><ul><li><strong>Product managers</strong>: setting the product priorities and aligning all functions to that direction (engineering, design, marketing, and sales)</li><li><strong>Designers</strong>: researching customer needs, designing UX and UI, validating product and design ideas</li><li><strong>Engineers</strong>: implementing product priorities in software and operating the software.</li></ul><p>As engineers make up most of the team (~80%) there needs to be additional leadership roles within engineering:</p><ul><li><strong>Engineering manager</strong>: People management, Team composition, Architecture</li><li><strong>Tech lead</strong>: Architectural and technology leadership on team level, Day to day task assignment, Hard skills development</li></ul><p>A company needs at least three distinct capabilities that are grouped under design in this document: Research, UX design and UI design. However as we saw in the <a href="https://medium.com/@viktormuller/introduction-766dbb30a6e7">Introduction</a>, our hypothetical Series A firm does not have the budget for a dedicated headcount for each. Therefore it is assumed that 1–2 great, experienced generalists are hired. One could be biased towards UX design and one towards UI and visual design. They can then be supported by a research consultant for critical research projects.</p><h3>Responsibilities</h3><p><a href="https://en.wikipedia.org/wiki/Responsibility_assignment_matrix">RACI</a> is a good framework to clearly describe who does what in an organization. Here is a quick introduction if you are not familiar with it.</p><p>A — Accountable: Makes final decision, career progression is tied to the quality of the decision</p><p>R — Responsible: Executes the necessary tasks</p><p>C — Consult: Consulted before final decision is made</p><p>I — Informed: Informed of the final decision</p><p>R implies C and C implies I. A does not imply R although ideally they are not separated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*rI5F2tM1S1nyAKJvAHzm0w.png" /></figure><p>Note that <strong>no one on the squad level is accountable for outcomes </strong>(or key results) like growth or churn in a series A company. That is because all the strategic decisions influencing those are reviewed and approved by the executive team and hence accountability for those lies with them. However PMs, designers and tech leads are each very much accountable for their own parts in executing against those plans as described above.</p><p>Despite not being accountable teams should still have OKRs and care about them. They should track them, identify risks to achieve them and communicate the issue to leadership so that they can help adjust course if necessary. This is expressed by the Measure results row above.</p><p>Furthermore there is <strong>no shared accountability</strong>. Shared accountability results in decisions by committee and consensus which does not just slow things down but also makes the decisions based on politics rather than merit. Therefore it is important that everyone knows who is accountable for what and they make those decisions, knowing they will be held accountable for them. This means that the accountable role does not need to achieve consensus and be blocked by disagreement of consulted roles. This requires a disciplined application of the <a href="https://en.wikipedia.org/wiki/Disagree_and_commit">disagree and commit</a> principle from everyone involved.</p><p>Finally the chart indicates a <strong>very high degree of collaboration</strong>.<strong> </strong>Almost all tasks involve multiple parties either as being responsible for contributing or to be consulted.</p><h3>Reporting lines</h3><p>Typically product managers and designers report to the VP of product in a Series A company. Usually there is no budget for a dedicated VP of Design</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*3JtxCr6kjJ1bKyy7-syOBQ.png" /><figcaption>PMs and the first 1–2 designers can report to the VP of product</figcaption></figure><p>Although not strictly on topic, it is worth mentioning how typically the engineering reporting hierarchy works out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*_WWMdobLNTLZ2NygUmrz5g.png" /><figcaption>Over 15–20 engineers often an additional layer of Engineering managers are added</figcaption></figure><h3>Squad structure</h3><p>The budget (25 FTEs) would allow for 3–4 squads. <strong>A typical squad is organized as a cross functional team </strong>as depicted below. It is led by a trio of PM, Designer and Tech lead. The best PMs make decisions in unison with their fellow leads and leverage the team as well.</p><p><strong>All engineers in a squad preferably report to the same EM</strong> so that the EM can provide effective oversight and support to those squads and be familiar with the day to day activities of the engineers. When EMs are not responsible for specific squads, they have a hard time evaluating their direct reports’ performance or effectively coaching them. They also end up being less effective at supporting the tech leads in key technical decisions.</p><p><strong>Designers can typically support 1–2 squads</strong> unless the squads are highly backend focused.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*o_wpo1kcBIcrip_OxIPDjA.png" /><figcaption>Typical squads lead by trio of PM, Tech lead and designer</figcaption></figure><p>Not depicted but sometimes a product marketer is also assigned to the team part time, especially around major launches. Similarly support may assign a contact person (single point of contact or SPC) to each product. However these roles usually do not partake in the day to day product development process.</p><h3>Squad scope</h3><p>Once an organization grows beyond 6–7 engineers, it needs to be split into multiple squads and decide how to scope each squad. Typically Series A organizations still want to prioritize moving fast over avoiding rework in the future. Therefore they benefit from <strong>aligning squads to customer problems</strong> and allow them to <strong>cut across technology layers</strong>. This typically means preferring full stack squads over separate front end and back end squads.</p><p>It is still preferable to have each component be worked on by a single squad (typically the one that is most reliant on it). If multiple squads work on a shared component then they should at least inform each other of intended changes or if that proves to be insufficient one of the squads can be assigned owner and can be required to approve any changes.</p><h3>Scaling a squad</h3><p>There are two typical reasons for starting a new squad:</p><ol><li>a squads scope became too large (&gt;6–7 engineers)</li><li>a large new problem is identified.</li></ol><p>In 1) the squad will need to be split into two squads staffed with a combination of existing and newly hired members. The problem space and the components also need to be split between the squads. Often both problem spaces will be reasonably well understood and an initial backlog and plan can be quickly drawn up for both squads. Depending on seniority the original PM (as well as the designer and EM) may be able to cover both squads and provide continuity. In this case the squad can be scaled as fast as hiring allows.</p><p>However in case 2) the squad is typically stood up more slowly and deliberately. <strong>The bottleneck initially is customer insight not engineering capacity. First the PM needs to be hired or assigned</strong>. They need to <strong>conduct the necessary research</strong> and layout the product vision, roadmap and draft an initial MVP scope.</p><p>As they progress <strong>a designer can be hired or assigned</strong> to help with research and <strong>validation via mockups</strong>. As the product takes shape, <strong>a tech lead can be hired or assigned to help planning technical aspects</strong> (architecture, technology risks). <strong>Finally engineers can be onboarded </strong>starting with more senior ones and adding junior ones later. Typically a first MVP can be built by ~3 senior engineers allowing further testing of the idea (see private and public beta launches) before investing further.</p><p>This process of building out an initial team of 1 PM + designer + 3 engineers could take 3–6 months with another 6 months to mature it to a fully staffed 5–6 engineer squad.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b28e0c3d1b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product management in a Series A startup — Introduction]]></title>
            <link>https://medium.com/@viktormuller/introduction-766dbb30a6e7?source=rss-7df8b4215bbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/766dbb30a6e7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Viktor Müller]]></dc:creator>
            <pubDate>Thu, 02 Feb 2023 11:47:15 GMT</pubDate>
            <atom:updated>2023-04-20T09:47:21.444Z</atom:updated>
            <content:encoded><![CDATA[<h3>Objective of this series</h3><p>This series is intended to serve as a starting point to set up a product management organization in a Series A company. It is just that, a starting point and each company should tailor it to their needs.</p><p>It reflects my opinion but has been reviewed by amazing product leaders from startups to big tech firms from four continents to whom I am hugely grateful. It being just an opinion, any and all feedback, comments and questions are welcome as I would like to consider it a living document.</p><p>The series is primarily intended for VPs of product, CTOs and CEOs who want to start their organizational design from a set of good practices. Secondarily senior product managers and anyone else wanting to have a better understanding of how to organize product management in a startup can benefit from it.</p><p>This series is <strong>not intended to be</strong>:</p><ul><li>product management 101</li><li>collection of all good product management practices</li><li>the perfect organizational design for all companies.</li></ul><p>The series assumes the reader is familiar with the basic concepts of product management and building software in agile, cross-functional teams.</p><h3>Assumptions</h3><ul><li>Typical SaaS business</li><li>B2B or B2C (where difference is relevant it is noted)</li><li>Raised £10m ($12m) for a 24 month runway</li><li>Product market fit in one niche</li><li>Commercial CEO, not personally leading product management</li><li>Current team: 10 engineers, 0 PM, part time contractor UX designer</li><li>Target team: 20 engineers, 1-2 EMs, 2–3 PMs, 1–2 designers</li></ul><h3>Chapters</h3><p>This series is made up of the following chapters:</p><ol><li><a href="https://medium.com/@viktormuller/organization-structure-3b28e0c3d1b2">Organization structure</a></li><li><a href="https://medium.com/@viktormuller/product-management-in-a-series-a-startup-product-strategy-roadmap-cef4227e6098">Product strategy &amp; roadmap</a></li><li><a href="https://medium.com/@viktormuller/quarterly-planning-and-okrs-a7dae2b1be90">Quarterly planning and OKRs</a></li><li><a href="https://medium.com/@viktormuller/requirements-2f851e50fce3">Requirements</a></li><li>Sprint planning</li><li>Maintenance and customer requests</li><li>Reporting progress</li><li>Launching &amp; tracking performance</li><li>Hiring and onboarding</li><li>Career ladder and professional development</li><li>Tools and technology</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=766dbb30a6e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>