<?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 Alla Kopylova on Medium]]></title>
        <description><![CDATA[Stories by Alla Kopylova on Medium]]></description>
        <link>https://medium.com/@allakopylova?source=rss-bacb15609f31------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_e7UGhQRoS2Thz3H3qq7ig.jpeg</url>
            <title>Stories by Alla Kopylova on Medium</title>
            <link>https://medium.com/@allakopylova?source=rss-bacb15609f31------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:41:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@allakopylova/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[Product Manager’s End-to-End AI Workflow: From Customer Interviews to Launch]]></title>
            <link>https://allakopylova.medium.com/product-managers-end-to-end-ai-workflow-from-customer-interviews-to-launch-d68e0b79e663?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/d68e0b79e663</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sat, 13 Sep 2025 14:37:26 GMT</pubDate>
            <atom:updated>2025-09-13T14:37:26.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FqzwB5j8ByVf-dKjVM8gtQ.png" /></figure><p>For years, being a PM meant exhausting processing of manual notes from customer interviews, hours of consolidating feedback, and putting together prototypes with just enough code — or pulling in engineers for proof-of-concepts that took weeks. Low-code tools helped, but anything that felt “live” still required coding, and each validation cycle stretched into weeks.</p><p>Today, AI tools shrink those cycles to days. More importantly, they free PMs to focus on what matters most: insights, decisions, strategy, and revenue enablement. The result is faster shipping, smarter de-risking, and products that start generating revenue sooner instead of burning time and budget on dead ends.</p><p>Here’s how I use AI across the four classic stages of product development: <strong>Discovery, Validation, Development, and Communication/Launch.</strong></p><h3>Stage 1: Discovery — From notes to insights</h3><p>Everything in product starts with a deep understanding of user problems and a clear framing of opportunities.</p><p><strong>Before AI</strong> customer interviews left you with messy notes scattered across docs or trapped in people’s heads. Desk research meant hours of Googling and manual synthesis. If you didn’t process notes immediately, valuable context slipped away. Time was always tight, and insights rarely got reused.</p><p>After incorporating AI into my daily life these workflows and tools I use look like this:</p><ul><li><strong>Granola</strong> — an AI-enhanced note-taking for live conversations — automatically captures every customer interview or internal meeting, highlights themes and contradictions, does synthesis of the the meeting and adds your notes to the transcript. Think of it as your AI meeting assistant and interviewer’s notepad.</li><li><strong>Perplexity</strong> and <strong>ChatGPT</strong> are my go-to tools for desk research, competitor benchmarking, and synthesis of insights.</li><li><strong>Dovetail</strong> — a centralised research repository with AI insights — I use it to organise and reuse insights from interviews, surveys, support tickets, or any qualitative data.</li></ul><p>All discovery activities I start with the definition of a research question and most risky assumptions. After this I select the group of users to validate these insights with and run 3 to 5 user interviews and record them in <strong>Granola</strong>. All my transcripts then go to <strong>Dovetail</strong> which generates a one-page insight brief.</p><p>Prompts that help me do do the analysis:</p><p><em>Capture Jobs To Be Done</em></p><blockquote>“Based on these interview transcripts, identify the top 3 Jobs To Be Done. For each job, write:</blockquote><blockquote><strong>Job statement</strong> (using the JTBD format: <em>When [situation], I want to [motivation], so I can [outcome]</em>)</blockquote><blockquote><strong>Evidence quotes</strong> from users that illustrate the job</blockquote><blockquote><strong>Pain points</strong> users face when trying to accomplish the job.”</blockquote><p><em>Translate Jobs To Be Done into Opportunities</em></p><blockquote>“Turn these Jobs To Be Done statements into opportunity statements. Reframe them as unmet needs, pains, or desires from the user’s perspective.”</blockquote><p><em>Cluster Opportunities under a Business/Product Outcome</em></p><blockquote>“From this set of customer interviews, cluster the Jobs To Be Done into themes. Rank them by:</blockquote><blockquote>- Frequency (how often users mentioned them)</blockquote><blockquote>- Importance (how critical they are to the user’s success).</blockquote><blockquote>Provide a short paragraph explaining why each job matters and how users currently try to solve it.</blockquote><blockquote>Explain context for each opportunity:</blockquote><blockquote>- Why this job matters to users.</blockquote><blockquote>- How users currently try to solve it (hacks, tools, workarounds).</blockquote><blockquote>Link to business outcomes:</blockquote><blockquote>- Propose a business/product outcome that these opportunities support.</blockquote><blockquote>- If multiple clusters support different outcomes, map each cluster to the most relevant outcome.”</blockquote><p>When I am done with the list of all opportunities and their business outcome I go to the next stage and run a quick <strong>Perplexity/ChatGPT</strong> scan for competitor/market context which can be appended to the opportunity statement brief. Some prompts that help here:</p><p><em>Competitor Analysis</em></p><blockquote><em>“Give me a competitor analysis for products solving [problem]. Highlight differentiators, pricing, and gaps</em>.”</blockquote><p><em>Industry and Trends</em></p><blockquote><em>“What are the top 5 trends in [industry] that could influence how users solve [problem]?”</em></blockquote><p>The result of the Discovery Stage is clear opportunity statements related to business outcomes and understanding or user problems with Jobs To Be Done map. Faster synthesis of user problems means fewer misaligned bets and more confidence that we’re solving the right, monetisable problems.</p><h3>Stage 2: Validation — From static mockups to live prototypes</h3><p>Now that we have clear opportunity statement definition, it is time to generate solutions and experiments to validate the three main hypothesis — usability, value, and feasibility.</p><p><strong>Before AI</strong> it took time to create static wireframes or clickable Figma prototypes. Getting something even “semi-working” meant waiting for design and engineering time. Validation took weeks, and often you are already attached to the results.</p><p>Now my workflow looks the following way: I am a huge fan of <strong>Lovable</strong> that generates working application prototypes from prompts in hours, and users can even interact with something that feels real and provides instant feedback.</p><p>We start with brainstorming solutions for opportunities and for every solution we can generate a prototype in Lovable with a prompt. Then this prototype can be put in front of 5 users to collect reactions and check task completion. Depending on the feedback you decide to kill, pivot, or invest into the idea. Some prompts that help here:</p><p><em>Brainstorm Solutions for Opportunities</em></p><blockquote>For each opportunity, propose <strong>3–5 possible solutions</strong>.</blockquote><blockquote>For each solution, suggest <strong>1–2 lightweight experiments</strong> to validate quickly.</blockquote><p><em>Generate a Prototype</em></p><blockquote>Build a simple web app for… Include signup/login, dashboard, etc… and dummy data. Users should be able to…”</blockquote><p>As a result of this stage you have clickable prototype, validation results report, and first gateway to proceed or to kill the idea. You avoid shipping features customer’s won’t pay for and keep investment focused on what drives adoption.</p><h3>Stage 3: Development — From prototypes to automated flows</h3><p>After successful validation the next step is to deliver the smallest functional version that delivers value to users or to build MVP. The goal here is to validate your product in the real market, to test viability and feasibility.</p><p><strong>Before AI</strong> you were completely dependent on engineers for every integration and data sync. Analytics is usually not setup on this step or is manual. Automations lived in spreadsheets or never got built.</p><p>What I use now is <strong>n8n</strong> that helps to connect tools and orchestrate workflows, and <strong>Amplitude</strong> to provide AI-suggested funnels, cohorts, and anomalies, providing insights after launch. Amplitude can be connected directly to n8n, and n8n connects with the help of webhooks to Lovable.</p><p>Analysing usage in Amplitude you can already make a recommendation about feasibility of the solution implementation, which is backed up with data. Building MVPs with automation tools accelerates time-to-market. Every week saved is a week earlier you can test pricing, onboard paying users, and prove ROI.</p><h3>Stage 4: Communication — From slides to narratives</h3><p>The last step covers product communication and presentation of the results or opportunity validation.</p><p><strong>Before AI c</strong>reating decks meant hours in PowerPoint/Slides, fine-tuning formatting instead of sharpening the story.</p><p>My absolute favourite is Gamma, which turns a PRD into a polished deck in minutes. You can draft your launch narrative in Gamma (<em>problem → solution → proof → CTA</em>) and create decks for different target audiences be it leadership, sales, marketing in minutes. Sharper positioning and faster narrative-building help sales and marketing teams close deals earlier, while giving leadership confidence to greenlight growth bets. Some useful prompts here:</p><p><em>Create Narrative</em></p><blockquote>“Turn this product requirements doc into a 10-slide launch story: problem, target audience, solution demo, social proof, next step. Keep it concise and visual.”</blockquote><p><em>Generate Decks</em></p><blockquote>“Create a one-pager for the sales team from this PRD. Focus on pain points, solution, and three key differentiators.”</blockquote><h3>Final thought</h3><p>The biggest unlock of AI isn’t speed alone — it’s focus. Instead of drowning in logistics, you can double down on what matters: discovering real problems, shaping strategy, and guiding the team to outcomes. Granola, Perplexity/ChatGPT, Dovetail, Lovable, n8n, Gamma, and Amplitude form a stack help you to save you most precious resource — time — and get the results faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d68e0b79e663" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Product Org: Balancing Discovery, Delivery and Outcomes]]></title>
            <link>https://allakopylova.medium.com/building-a-product-org-balancing-discovery-delivery-and-outcomes-8227a7798369?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/8227a7798369</guid>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 10:48:56 GMT</pubDate>
            <atom:updated>2025-07-14T10:48:56.605Z</atom:updated>
            <content:encoded><![CDATA[<p>High-performing product orgs aren’t built through rituals or frameworks alone — they’re built through clarity: knowing what to optimise, when to move fast, and when to minimise risk. That clarity comes from how we structure teams and align work — whether through delivery focus, discovery speed, or outcome ownership via OKRs. Let’s explore how to structure your product org across three critical dimensions: discovery, delivery, and outcome ownership — and how OKRs can align these modes to real business value.</p><h3>Discovery vs. Delivery Mindset</h3><p>Distinction between Discovery and Delivery is often misunderstood. Many people think of discovery and delivery as sequential <em>phases</em> in a linear product process (first you discover, then you deliver). But in a mature product org, they’re better understood as parallel, continuous operational modes — each with its own goals, rhythms, and teams.</p><p>If you treat Discovery as “just a phase” within Delivery:</p><ul><li>You compress it into sprint 0 (or ignore it entirely)</li><li>Engineers become feature factories</li><li>Product-market fit risks go unchecked</li></ul><p>But if you treat them as modes, you can:</p><ul><li>Run discovery on future bets while delivery ships roadmap items</li><li>Build dual-track teams to scale speed and insight</li><li>Make better, faster decisions with real user data</li><li>Avoid costly rework and misaligned launches</li></ul><p><strong>Discovery and Delivery aren’t just phases in a process — they are continuous operational modes</strong>. The next question is: how do we steer them effectively? Let’s look at how OKRs can help guide each mode without slowing them down.</p><h3>OKRs and Where They Belong</h3><p>OKRs is a powerful tool for alignment and it seems that is employed almost by every company. But they are not universal — and that is also fine. Not every team needs an OKR to be aligned. Sometimes, clear goals and speed of iteration are more powerful.</p><p>Another problem is that companies jump on the bandwagon and create OKRs empty of any context. OKRs alone do not explain:</p><ul><li>what your vision is</li><li>what the strategy is going to be</li><li>why you have chosen that specific objective</li><li>how does this particular OKR connect to the vision</li></ul><p><strong>OKRs aren’t your strategy</strong> <strong>— they’re your chosen levers to make progress toward it. </strong>Here’s how they fit into the strategic stack:</p><ul><li><em>Product vision </em>— the future you want to create with the horizon of 5–10 years</li><li><em>Product strategy</em> — where to play and how to win with the horizon of 1–2 years</li><li><em>OKRs</em> — your strategic options for 3–4 month</li><li><em>Roadmap</em></li></ul><p>Now that we are clear on what we would like to achieve let’s see how a functioning product organisation can be created without trying to invent OKR for every company initiative.</p><h3>Where OKRs Add Clarity in Product Org</h3><p>OKRs were designed to align teams around outcomes that move the business forward — not to describe every task a team is doing.</p><p>That’s why OKRs shine when the team:</p><ul><li>Has a clear line of sight to a business metric (like revenue, churn, NPS)</li><li>Can influence user/customer behaviour</li><li>Operates in a cross-functional setup with shared ownership</li></ul><p><strong>OKRs work well in GTM-aligned and outcome driven product teams.</strong></p><p>Product teams driving measurable customer or business outcomes — like conversion, retention, monetisation — should absolutely have OKRs. These OKRs help focus priorities, align cross-functionally, and create accountability for outcomes (not just output). For example:</p><p><em>Objective: Improve self-serve activation</em></p><ul><li><em>Key result: Increase activation rate from 25% → 40%</em></li><li><em>Key result: Reduce onboarding time from 10 min → 5 min</em></li></ul><p><strong>OKRs can be applied to Strategic bets as well.</strong></p><p>Product work often supports broader company OKRs like <strong>revenue growth</strong>, <strong>expansion into new markets</strong>, or <strong>operational efficiency</strong>.</p><p>The nuance: product rarely owns business outcomes in isolation. Sales, operations, marketing — all play critical roles. Product enables the outcome by shipping the right thing, but the result often depends on others.</p><p>In these cases, product teams can (and should) track <strong>delivery milestones</strong> and <strong>impact hypotheses</strong>, but avoid being held solely accountable for lagging business results.</p><p>Important nuance here as well: strategic delivery ≠ immediate results.</p><p><strong>When product teams work on strategic initiatives — new platform capabilities, enterprise features — the delivery is often just the start.</strong> The actual business impact may be delayed by weeks or even quarters, depending on sales cycles, adoption curves, and GTM execution. This is where OKRs can mislead if they’re too tightly coupled to quarterly business outcomes.</p><p>Focus instead on:</p><ul><li>Milestone-based key results (“Launch X with feature set…”)</li><li>Leading indicators (“First 10 partners onboarded”)</li></ul><h3>Where OKRs Don’t Fit Well</h3><p><strong>Discovery teams</strong></p><p>In fast-moving discovery efforts, OKRs tend to slow things down. These teams need to learn fast, to track hypothesis and be able to align fast. In discovery not the metrics are optimised, but speed of getting to the insights.</p><p><strong>Core engineering &amp; infrastructure teams</strong></p><p>Foundational teams often deliver long-term value that’s not easily tracked via OKRs. Their work supports scale, stability, and dev velocity. Their success is reflected in fewer incidents, faster CI/CD, better infrastructure — not easily tied to quarterly business goals.</p><p>Don’t force OKRs where technical excellence and clear roadmaps are better indicators of progress.</p><h3>When Product Enables, Not Owns the Outcome</h3><p>In most cases, <strong>product is a key enabler of business OKRs — but not the sole driver</strong>. That distinction matters. This is very common in B2B product orgs where sales drives revenue or ops-heavy orgs where supporting workflows matter, not user acquisition.</p><p>Product doesn’t need OKRs to be strategic. Product needs <strong>clarity on impact</strong> — even if it’s indirect.</p><p>In these cases, <strong>tying product OKRs to business outcomes like revenue or churn is misleading or even counterproductive</strong>. Here’s how to reframe success and structure goals instead:</p><ul><li>Ship the right thing → <em>enable</em> GTM to succeed.</li><li>Build for scale → <em>enable</em> business growth.</li><li>Design for adoption → <em>enable</em> customer success.</li></ul><p>If your product team isn’t directly driving business results but is a <strong>critical enabler</strong>, then OKRs need to reflect <strong>influence</strong>, not <strong>ownership</strong>.</p><p><strong>Reframe OKRs Around Enablement</strong></p><p>Rather than forcing business key results, define success as <em>readiness</em>, <em>capability</em>, or <em>removal of friction</em>. For example,</p><p><em>Bad objective: “Increase revenue by 10%”</em></p><p><em>Better objective: “Enable self-serve sales motion by automating pricing configuration”</em></p><p><em>Key result: “Reduce time-to-quote from 5 days → 1 hour”</em></p><p><em>Key result: “Achieve 100% pricing accuracy in quote generation”</em></p><p>Here, you’re <strong>not promising revenue</strong> — you’re ensuring the systems are in place for sales to perform better.</p><p><strong>Use Leading Indicators</strong></p><p>If lagging business outcomes (like revenue) are outside your control, shift to leading indicators that show <strong>impact potential</strong>.</p><p><em>Examples:</em></p><ul><li><em>% of deals supported by new quoting tool</em></li><li><em>Uptime or NPS of internal tools</em></li><li><em>Ops time saved from automation</em></li><li><em>% of bugs in mission-critical flows reduced</em></li></ul><p><strong>Co-Define OKRs With Business Stakeholders</strong></p><p>OKRs can be shared — a product team can own the <em>platform</em>, while sales owns <em>the outcome</em>. For example:</p><p><em>Sales objective: Close $2M in mid-market with faster deals</em></p><p><em>Product key result: Launch CRM sync to auto-populate sales contracts</em></p><p><em>Sales key result: Reduce avg time-to-close from 30 → 15 days</em></p><p>This way, product plays a clear enabling role, with measurable contribution, <strong>without carrying false accountability.</strong></p><p><strong>Sometimes… Don’t Use OKRs at All</strong></p><p>For platform teams, infra, or technical debt work — a <strong>well-scoped roadmap + clear milestones</strong> often works better than OKRs.</p><p>Examples of better alternatives:</p><ul><li>Technical OKRs (stability, velocity, scalability)</li><li>Milestone-based goals (“Launch new billing API by Q2”)</li><li>Internal SLAs or DORA metrics for engineering health</li></ul><h3>How to Structure Your Product Org Around These Principles</h3><p>Now that we’ve unpacked the two key operational modes — Discovery and Delivery — and explored how OKRs can help align product work with business goals, the next question is: <strong>how should we structure our teams to support these modes effectively?</strong></p><p>To turn strategy into execution, we need more than capable individuals — we need the right team constructs that reflect how product work actually flows across the organisation. That’s where a three-squad model comes in:</p><ul><li><strong>Discovery Squads </strong>— lean, fast-moving, research-driven teams focused on reducing uncertainty and identifying new opportunities. They work without the pressure of delivery cycles, often moving outside of sprint cadence, and prioritize speed of learning over immediate output.</li><li><strong>Delivery Squads </strong>— cross-functional, execution-oriented teams focused on building, scaling, and maintaining core product functionality. Their strength lies in planning, coordination, engineering excellence, and reliable shipping.</li><li><strong>GTM/Outcome Squads</strong> — outcome-obsessed teams working closely with Sales, Marketing, and CS to drive adoption, retention, activation, and revenue. They’re aligned to business OKRs and feedback loops, ensuring that what’s built actually delivers measurable impact.</li></ul><p>This structure ensures that you’re not just building the product right — you’re also building the right product, and making sure it performs in the market. Each squad type plays a unique role in driving innovation, stability, and business growth.</p><h3>Discovery Squad</h3><p>Main focus is on exploring new opportunities, validate problems, prototype solutions quickly. Goal is <strong>learning</strong>, not shipping.</p><p>Typical activities Discovery squad is leading:</p><ul><li>User interviews and research, identification of pain points in new and existing segments</li><li>Prototype testing</li><li>Market scans and competitive analysis</li></ul><p>These teams fuel the roadmap with insight — not output. Speed and learning is much more important than outcomes.</p><p>What can be an objective for Discovery squad. Here is an example:</p><p><em>“Validate the most promising solution for our new onboarding experience.”</em></p><p><em>Key Results:</em></p><ul><li><em>Conduct 10 user interviews with new users within 2 weeks</em></li><li><em>Prototype 2 potential onboarding flows and test with at least 5 users each</em></li><li><em>Achieve at least 80% task success rate in usability tests</em></li><li><em>Decide on go/no-go for MVP build by end of quarter</em></li></ul><p>Ideal profile for your Discovery squad is strong design and PM pair to be able to cover research, hypothesis framing and rapid prototyping. With the rise of AI tools the need of engineering support becomes optional here. Engineering support can be required to validate feasibility of prototypes.</p><h3>Delivery Squad</h3><p>Main focus is to build and scale validated solutions. Goal is to <strong>ship high-quality product</strong> that solves real problems.</p><p>Typical activities Delivery squad is leading:</p><ul><li>Sprint delivery of features</li><li>Technical design &amp; backlog grooming</li><li>Integration with platform and infra</li></ul><p>These are the builders who execute on validated bets. Their outcomes are quality shipped products with real technical KPIs. Example of Delivery squad objectives:</p><p><em>“Launch the new invoicing engine with zero customer disruption.”</em></p><p><em>Key Results:</em></p><ul><li><em>Complete end-to-end system integration by MM/DD</em></li><li><em>Migrate 100% of active accounts to the new flow with no blocking issues</em></li><li><em>Reduce invoice generation time from 2 mins to &lt;10 seconds</em></li></ul><p>Ideal setup of your Delivery squad is well balanced on tech and product sides team with product manager owning roadmap and coordinating delivery, software engineers and QAs, product designer to polish end-to-end flows.</p><h3>GTM Squad</h3><p>These squads are a perfect fit to be guided with the help of OKRs. Their main goal is to drive measurable <strong>business outcomes</strong> — revenue, retention, conversion, adoption — through product work. Often work closely with <strong>Sales, Marketing, Customer Success, or Ops</strong>. However, they are NOT just “supporting CS.” They are actively solving business problems <strong>through the product</strong>.</p><p>Typical activities of GTM squad:</p><ul><li>Improving onboarding flows to increase activation</li><li>Shipping product-led upsell features (e.g., usage-based billing)</li><li>Creating self-serve paths to reduce sales-assisted effort</li><li>Running pricing tests or packaging changes</li><li>Reducing churn by addressing key drop-off patterns</li></ul><p>This squad model is particularly valuable if your product plays a direct role in monetisation, adoption, or retention — especially in PLG or self-serve motions. Example of objective for GTM squad:</p><p><em>“Increase trial-to-paid conversion in the self-serve flow.”</em></p><p><em>Key Results:</em></p><ul><li><em>Improve activation rate from 30% → 50%</em></li><li><em>Reduce drop-off in pricing step from 40% → 20%</em></li><li><em>Implement in-app upgrade prompt with &gt;5% CTR</em></li><li><em>Contribute to $100K in incremental MRR from self-serve channel</em></li></ul><h3>So How to Structure Your Product Org?</h3><p>Product vision and strategy along with North Star Metric creates overall product org alignment. And then it is different for every product squad:</p><ul><li><strong>Discovery Squad</strong> validates opportunities, performs research, prototyping, testing, interviews , utilises impact mapping directly tied to learning outcomes</li><li><strong>Delivery Squad</strong> ships and scales solutions, builds, QAs, integrates, maintains, improves, utilises roadmap and technical goals to track SLAs and milestones</li><li><strong>GTM Squad</strong> drives business outcomes, improves activation, reduces churn, increases expansion, utilises OKRs directly tied to user behavior or revenue metrics</li></ul><p>The real value of OKRs isn’t in tracking everything — it’s in creating focus where business outcomes are on the line. Product teams shouldn’t force OKRs when they’re enablers. They should define <strong>impact in their context</strong> — and let business teams carry business goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8227a7798369" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strategic Focus vs. Executive Requests]]></title>
            <link>https://allakopylova.medium.com/strategic-focus-vs-executive-requests-3deb163826d6?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/3deb163826d6</guid>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Wed, 02 Jul 2025 14:40:52 GMT</pubDate>
            <atom:updated>2025-07-02T14:40:52.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zqNOqhHn9TYb9hZRnF6f1g.png" /></figure><p>As product leaders, we live in the tension between long-term strategy and short-term opportunity. Sales wants a feature to close a deal. A big customer makes a promise-heavy request. The CEO forwards an email with the subject line: “Can we build this?”</p><p>The trap is to fall into stakeholder-driven roadmap process, where they basically are trying to find a way to “fairly” divide up the engineering capacity across scattered priorities.</p><p>The truth is: everything feels important, but not everything is <em>strategic</em>. And without a clear framework, product teams become reactive — shipping one-off features, piling on technical debt, and drifting from the roadmap.</p><p>Over the years, I’ve developed a simple four-question lens that helps me evaluate opportunities and say no with confidence. This helps deciding what to work on and pick the few things that can truly make an impact. Every good product strategy begins with focus and not prioritising, but focusing. Without clear focus product becomes reactive, and not strategic.</p><h3>The FARD Framework (Focus, ARR, Risk, Debt)</h3><p>I use FARD Framework to triage and prioritise opportunities. It is easy to recall in high-pressure conversations. You can apply it quickly in product reviews, exec check-ins, or backlog grooming. I find it particularly helpful when you need to evaluate requests quickly ****from execs, sales, or customers, or you need to defend roadmap decisions with business context.</p><h3>F — Focus</h3><p>We’ve all seen one-off features clog the roadmap and confuse the product. If we keep chasing every “important” request, we risk building a product that serves no one well.</p><p>Focus aligns with strategic vision and product principles.</p><ul><li><em>How well does this align with our current strategic priorities and product vision?</em></li><li>Is it in our current strategic “lane”? Or a distraction?</li></ul><h3>A — ARR Impact</h3><p>ARR addresses commercial impact.</p><ul><li><em>How much revenue (new or retained) is at stake?</em></li><li>Is this a €20K or €2M impact? Is it net new or expansion?</li></ul><p>If we’re talking about a large revenue impact (or retention risk), it deserves attention.</p><p>But ARR alone isn’t enough. Big deals can still be distractions.</p><h3>R — Risk &amp; Commitment</h3><p>Captures feasibility, timing, and commitment which is often overlooked.</p><ul><li><em>How fixed is the opportunity?</em></li><li>Is it prepaid, contractually committed, or speculative based on sales team’s optimism?</li><li>What is the risk if we do it? What’s the risk if we don’t?</li></ul><p>This question helps us avoid building on hope. I often push back by asking: <em>“Are they willing to sign now — before we build?”</em></p><h3>D — Debt Impact</h3><ul><li><em>Will this pay down or increase tech debt?</em></li><li>What’s the long-term cost of not doing it?</li></ul><p>Technical debt deserves a separate discussion as many companies focus on just business priorities completely disregarding that it is one of the silent killers of product velocity and quality. It is not enough to focus purely on features or revenue, especially becomes critical in the companies lacking technical leadership and just been business driven.</p><p>If technical debt is a frequent blocker or discussion point in your team, make it explicit.</p><p>I have it as a separate dimension included into the framework. Having it separate adds clarity and:</p><ul><li>helps you prioritize engineering work that doesn’t have a feature tied to it (e.g., refactors, migrations).</li><li>builds buy-in with non-technical stakeholders by treating tech debt as a first-class citizen.</li></ul><p>You might prioritize a refactor or platform investment <em>even with zero ARR</em>, because the Debt score is dangerously high. ARR can be “indirect impact” resulting in unlocking speed and preventing outages. ROI can be shown in terms of velocity regained or bug rate reduced.</p><p>For example,</p><blockquote><em>If it’s big ARR, prepaid, and strategically close — do it.</em></blockquote><h3>Drawbacks &amp; Limitations of the FARD Framework</h3><p>There are few thoughts on what to watch out while using this framework:</p><p><em>Subjectivity in Scoring</em></p><p>“Strategic focus” and “risk” can be interpreted differently by different stakeholders. Example: The CEO might see a deal as perfectly aligned; the product team might not. To use it right it requires shared alignment on the company’s strategy and priorities to score accurately.</p><p><em>ARR Bias</em></p><p>Usually innovation bets can suffer if we over-prioritise revenue. It may lead to short-term planning especially in sales-led environments. To mitigate this focus should be weighted higher.</p><p>Doesn’t Explicitly Include Customer Delight</p><p>The model lacks a “customer experience” or “usability” dimension. You might still ship something high ARR, low risk, but painful for the end-user. And it can be a frequent case in B2B environments. UX can be one of the factors your users stick to your solution.</p><h3>Application for different company stages</h3><p>FARD is applicable for both early-stage startups where ARR might be small but focus is critical and growth-stage where risk and misalignment becomes a problem.</p><p><em>For pre-product-market fit</em></p><p>What works:</p><ul><li>Focus (F) is <em>critical</em>. Early-stage teams are prone to distraction. This helps prevent chasing custom features for random customers that won’t scale.</li><li>Risk (R) is useful — but in a different sense. You’re not de-risking delivery, but validating assumptions. Risk = “How risky is this bet in terms of learning?”</li></ul><p>Where FARD falls short:</p><ul><li>ARR (A) often misleads at this stage as you do not have meaningful revenue yet. Early revenue can come from non-ideal customers who distort the product direction and can anchor you to a niche that won’t scale.</li></ul><p>ARR is better to be replaced with Learning Value</p><ul><li>Will this help us validate/invalidate a key hypothesis?</li><li>Does this represent a real, repeatable customer segment?</li></ul><p><em>For post-product-market fit</em></p><p>What works:</p><ul><li>Focus (F) remains critical: You now have a clearer vision, and must avoid fragmentation or “platform thrash.”</li><li>ARR (A) becomes central: Now you’re scaling, and prioritizing by commercial value makes sense.</li><li>Risk (R) matures into evaluating technical feasibility, support cost, and roadmap disruption — very relevant.</li><li>Debt (D) gets more focus as scalability and infrastructure load become important.</li></ul><p>Think of FARD as a core triage tool — adaptable to different company stages by tuning the definitions of each axis.</p><ul><li>Pre-PMF: use it to stay focused on learning and not chase vanity revenue.</li><li>Post-PMF: use it to scale responsibly, grow revenue, and avoid strategic drift.</li></ul><h3>Time to say “No”</h3><p>FARD helps you to communicate the decision on strategic level, keeps you data-driven and not emotional. I like it for the ease of application, speed of decision making and alignment it brings.</p><p>Saying no isn’t about rejecting ideas. It’s about protecting focus and building a system that helps protecting team’s focus is a strategic prioritisation muscle that builds over time.</p><p>So next time you’re under pressure to take on a shiny new request, ask:</p><p>“How big is it? How fixed is it? And how far does it take us from the strategy?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3deb163826d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slow down to speed up]]></title>
            <link>https://allakopylova.medium.com/slow-down-to-speed-up-483a3e1db2d7?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/483a3e1db2d7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 21:40:36 GMT</pubDate>
            <atom:updated>2023-01-16T21:40:36.579Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a successful product is not only investing in new features, but also maintaining and improving the existing product. There is a common misconception that in order to grow we need to deliver only new things. We can find perfect opportunities to enable delivering even more customer value by improving the existing product.</p><p>Here are some hints to look for these improvements:</p><p><strong>#1: usability of the existing product </strong>— customer expectations always evolve and not investing in continuous improvement of UX can degrade value of the product to your customers.</p><p>→ Perform regular audits of you features and user flows, analyse complaints of your users and see where you can prevent churn.</p><p><strong>#2: performance and scaling </strong>— can become huge issue when you grow as your product should not degrade with growing user base.</p><p>→ Benchmark your performance and do not forget about load tests for your product.</p><p><strong>#3: infrastructure and technical debt</strong> — the more features you pack into your product, the more it is to maintain, and this defines the speed you can in future.</p><p>→ Perform regular audit of your application code base and do not neglect prioritising topics that improve development experience.</p><p><strong>#4: invest in internal tooling and automation</strong> — the goal of PM’s daily life is to spend more time on experimenting with new things and understanding your customers better, that’s why the routine internal processes should be automated at max.</p><p>→ Tools like Zapier, Airtable, etc. can definitely solve some pains.</p><p>In general these are pains of “growing up”: for a startup it is easy to spend 90% of your time building new things, but as you grow the internal things get more importance. You need to slow down in order to move faster.</p><p>#productmanagement #prioritisation</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=483a3e1db2d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick “how to”: product strategy]]></title>
            <link>https://allakopylova.medium.com/quick-how-to-product-strategy-d560e09b446a?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/d560e09b446a</guid>
            <category><![CDATA[productstrategy101]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Tue, 23 Aug 2022 20:05:18 GMT</pubDate>
            <atom:updated>2022-08-23T20:05:18.702Z</atom:updated>
            <content:encoded><![CDATA[<p><em>One of the challenges for product people is to craft a roadmap that reflects your product strategy. It is not about including all possible feature requests on your roadmap and just distributing them in time or setting priorities without clear direction. Product strategy should guide you through this task and be your main reason to say “no”. How to define one? There is no secret formula to it, it is all about following the framework that guides you through the most important questions. Let’s go through it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dQH_0DBmrfW44D5gQKJ_hA.jpeg" /></figure><h3><strong>Core elements of product strategy</strong></h3><p>Shaping your product is not an easy task as you need to resist the temptation of adding new features from customer requests, and should be confident in sticking to vision and business goals. Good idea is to focus on the problem your product needs to solve or in other words why does your product exists. It is important to be clear on the <strong>problem statement</strong> from the very beginning and avoid resource burn. For this you need to analyse the following aspects of your problem space:</p><ul><li>problem-solution impact.</li><li>competitive landscape, what is working now and what is not.</li><li>target market, what are the constraints.</li><li>typical customer journey.</li></ul><p>To own your problem you need to be clear on who are your <strong>customers</strong> and what is your core differentiator for them, what are they ready to pay for. Your product needs to deliver something of value to your market that your competitors do not, and this is to become your product strategy. What can give you better understanding on how to approach this task is to research how customers solve the problem now. This can give you sense of problem urgency for users (how desperate are they to solve this problem and what are they ready to withstand), and will help you to understand which current blockers users might have. Day-to-day observation gives you opportunities to disrupt current ways of thinking. Analysis of jobs to be done or user journey mapping is powerful approach here.</p><p>The next important aspect is to analyse your <strong>market</strong> situation and how your product idea fits into the <strong>value</strong> <strong>chain</strong>. The following questions might help:</p><ul><li>Does your product deliver something of value your market/competitors do not?</li><li>How does a product fit into the daily user’s lives?</li><li>What are the trends or directions your market might adopt?</li><li>How does your industry, user expectations and technology evolve?</li></ul><p>You need to study your market well as depending on market conditions you might bet on different things, for example:</p><p><em>In a saturated market with multiple players </em>the focus should be on differentiation of your product idea, what is unique about your product) and becoming a market leader. The good thing is that you have a solid list of your potential customers. What to do:</p><ul><li>do a market research and collect potential use cases and needs for your product.</li><li>learn your target audience and understand what functionality they really need.</li><li>and measure product awareness here as well as sales conversion.</li></ul><p><em>In a market with one or several market leaders </em>strategy should be around price and focusing on lower-priced versions that include the same features as competition. Here the main focus is on understanding the key features, finding ways to reduce costs and experiment around pricing.</p><p><em>In underserved market</em> we are talking about niche market and underserved needs of it. You first need to identify these needs. What to measure is customer churn rate, CLV/CAC ratio.</p><p>Once you clear on customer, market and problem statement, the next step is to create a <strong>product vision</strong>. For this you need to be clear on what is the value you bring to your users today, how do you want to improve it near-term and what could that look like ten years out?</p><p>What is your <strong>core feature or defensibility </strong>is the next question to answer. What is the key feature your product is known for? This feature should be core for further improvement. It is common mistake to focus on new features instead. Focus on key features helps to prioritise and define your product strategy. It is beneficial to prioritise perfecting your killer feature over expanding your product. Listen to the users of your key feature and try to delight them instead of adding numerous features to your product.</p><p>After a product vision has been set we can start defining the <strong>success metrics</strong> and setting product goals. These metrics can be grouped around this:</p><ul><li>improve CSAT rate</li><li>increate LTV of a customer</li><li>reduce churn</li><li>increase adoption</li><li>enter new market and expand geographically</li><li>and so on.</li></ul><p>If you grow new business then metrics are usually picked up from MRR, ARR, ARU, LTV set. In case you need to protect revenue and sustain an existing business, then NPS, churn and retention can be something to address.</p><p>The next step is to focus on your <strong>roadmap</strong> that should represent you product strategy answering the questions “why are we doing it”, “what are we doing”, “how does this relate to our product goals”. The topics you can place on the roadmap are: customer core and delight features, customer requests, metric movers (features to improve engagement or revenue), technical debt or some strategic topics. The prioritisation is always done judging the vision fit, importance of this item to your users and business impact.</p><h3><strong>Examples of bad product strategy</strong></h3><p>After talking for a while about the product strategy framework, it is time to give some examples what is a bad strategy. Top three examples are:</p><ul><li>not focused on one target customer segment and trying to address every customer profile.</li><li>not following product vision.</li><li>no clear product differentiation.</li></ul><p>As an outcome fo a bad product strategy you have resource burn, legacy tech debt and feature factory that do not move key metrics.</p><h3><strong>Checklist to your product strategy</strong></h3><p>Crafting your product strategy is not a magic, it is iterative approach to find answers to the following questions:</p><ul><li>Why does your product exist or what problem does it solve?</li><li>Who are your customers and how important is this problem to your customers?</li><li>How are they currently solving it?</li><li>How is your solution better than the current solution? What is your key feature?</li><li>What is the market situation now? How your product idea fits into the value chain?</li><li>Do you have a product vision?</li><li>Are you clear on what are you trying to optimise? Do you have success metrics defined?</li></ul><p>As a result your roadmap will provide all the answers to questions above and guide efficient product development process resulting in the product your customers love.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d560e09b446a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering customer development in a structured way]]></title>
            <link>https://allakopylova.medium.com/mastering-customer-development-in-a-structured-way-183fb9b5676c?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/183fb9b5676c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-development]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[prodcut]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sat, 27 Nov 2021 07:31:25 GMT</pubDate>
            <atom:updated>2021-11-27T07:31:25.385Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every company exists with just one goal to become successful and to grow fast. The core of this success lies in how well you address the known or unknown problems of your target customers. You need to make sure, especially at the beginning, that your product is tuned to the needs of your target customers and provides real value to them, and the better it is done, the faster you can get traction and usage for your product. You can study market, competition, brainstorm trying to guess what might catch the attention of your target audience, but the only way to learn about the real problems and needs of your customers is through customer development, i.e. talking to them. Customer development is not a special skill that only extroverted people are blessed with, it is rather a structured framework that helps to understand your problem space, validate product hypothesis, and decide on who is the perfect customer for your product and what can be a business model behind this.</em></p><p><em>So let’s deep dive into the topic of customer development that is one of the mandatory skills of every product manager.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dwgL8hRDcWrmmR5_fhWeeg.jpeg" /></figure><h3>What is customer development?</h3><p>Customer development is a hypothesis-driven approach that serves to build your understanding of the following product aspects:</p><ul><li>who are your customers</li><li>what is the best way to reach your target audience</li><li>what problems and needs do your target users have that can become the core of your product’s functionality</li><li>based on which criteria does your audience decide to buy a product that can help you with the product positioning in the future</li><li>what are the solutions your target customers have already tried or are using</li></ul><p>These insights will help you to assess the value and feasibility behind your product idea and decide if you need to invest time and resources in building it further. The insights from customer development could be gathered leveraging two approaches:</p><ul><li>quantitative insights. This requires you to work with a big amount of data and do more indirect studies of your target audience. The ways to collect qualitative insights are, for example, surveys, A/B tests, statistics from Google Trends. As this method requires rather a huge set of data, it can be not always easily applicable to products in the initial stages, when you need to learn more about the “why” of your problem space.</li><li>qualitative insights. This is the heart of customer development that helps you learn about the needs of your target audience, how the product has been already used or is planned to be used, what can be your core differentiators, and what should be a part of your MVP. From now on we will be talking about gathering qualitative insights.</li></ul><p>However, before talking about the approach to collect qualitative insights, it is important to mention three main rules of customer development:</p><ul><li>it is all about your potential customers and their feedback, and you should focus not on selling your solution at this stage, but rather on understanding the problem space</li><li>the earlier you start building up the knowledge about your customers the better it is for the final product</li><li>you should never stop learning about your target audience and their problem space.</li></ul><h3>Structuring customer development efforts</h3><p>There is nothing complicated here to get your qualitative insights if you approach it in a structured way that could be described in the following four steps:</p><ol><li>Make a plan on what you are going to learn about or form your assumptions.</li><li>Find people from your target audience you can talk to validate your assumptions.</li><li>Prepare and execute interviews.</li><li>Evaluate the results and look for insights.</li></ol><p>Nothing complicated, but let’s cover each of the steps in detail.</p><p><em>Step 1: Set a goal for your customer development iteration.</em></p><p>To start with you need to identify the blind spots in your understanding of the problem space, to have a good understanding of which is a prerequisite of building a successful product. To build this knowledge you need first to formulate your assumptions about the problem space or hypothesis that will be validated or invalidated. To start with you can try to brainstorm different aspects from the following hypothesis groups:</p><ol><li>Value hypothesis: customer — problem — need. For example, what can be a specific problem customer might have. Or are they willing to invest resources into solving a particular problem?</li><li>Viability: distribution &amp; pricing — demand. For example, how are purchasing decisions made or what are they influenced by. What does it take to acquire X customers?</li></ol><p>In these two categories, you can write down things you believe to be true and would like to be clear on before starting building the product. Apart from brainstorming for these two categories, you can also check your business model canvas to see what are the blind spots for you there to validate and come up with hypotheses for all unknowns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aB0y4Rt3MDNmA3I5o9ZAeQ.png" /><figcaption>Image 1: Business model canvas</figcaption></figure><p>How you can apply business model canvas to come up with the hypothesis? Let’s take for example Value Proposition quadrant. The hypothesis you might need more clarification on is related to:</p><ul><li><em>What problem does my product/service solve?</em></li><li><em>What benefits does it deliver to my customers?</em></li></ul><p>For the Channels quadrant the hypothesis is:</p><ul><li><em>How are you going to sell/distribute the product?</em></li></ul><p>And so on. By answering these questions you will get the idea of what should be validated with your customers.</p><p><em>Step 2: Define your target customer profile</em></p><p>Define who is your target customer for the hypothesis list you’ve formulated. The target customer is the one who is experiencing the problem you believe to solve, and you should try to narrow down their profile description: What do they worry about? What might be their problems? How is the problem being solved now? Some demographics, level of tech-savviness, etc.</p><p>It is hard to segment customers at the beginning, and you can start dividing them based on their needs. It is not bad that you end up with multiple segments, every segment is also your hypothesis that needs to be validated by arranging several interviews with the representatives of these customer segments. To start with you can focus on the biggest segment with the most acute problem or where you know that they are using the solutions that are not good enough.</p><p>The next step is to understand where your target customer group can be found and how you can reach them to arrange an interview. If you are building an existing product, then most probably the easiest way is to reach out to the existing users. If you are working on something new, try to target people directly through social media, or connecting on the conferences, etc. You can also scout for help in your network, asking for introductions to your target audience (seek among your friends or co-workers). Do not be afraid to reach out as people usually love to share their experiences and to help others.</p><p>The last question you might have is how many people you should be interviewing? Start with at least five per every segment you have identified. If you find recurring patterns in answers, then there is no further need to proceed with the validation, otherwise, you need to interview the further participants until you reach this recurring pattern in answers.</p><p><em>Step 3: Prepare for the interview and execute it</em></p><p>After you are done with your hypothesis and focus of your customer study, as well are clear on the target group you’d like to approach first, you can come to the most interesting part of crafting the list of questions you’d like to build your conversations around. This list should not be a long one and fixed. Try to find the top five questions you’d like to use to steer the conversation, and let the customers talk. You will learn much more from listening.</p><p>To break the ice start with the questions that help to understand if an interviewee is a right person to interview. These can be the demographics related questions, as well as the following questions that give you more understanding of the person you are interviewing:</p><ul><li><em>“Tell me about the way you usually do ___?” </em>A customer should describe the way he does his usual job and you can observe if he complains about doing some part of it, or even the whole.</li><li><em>“What are the efficiencies and inefficiencies in the process can you spot?”</em></li><li><em>“What was the hardest thing doing __?” </em>This helps to understand if a problem is big enough which is a good characteristic of the problem.</li><li><em>“Why was it hard (doing this thing)?” </em>Helps to understand how to position the product.</li></ul><p>The next set of questions can help you to go deeper and let the customers “dream”:</p><ul><li><em>“Would you do anything differently?” </em>Here you need to communicate that a customer should use the full imagination to think about the task. Meanwhile, you can learn about the biggest pain point that can be your core feature and main differentiator.</li></ul><p>To understand where potentially can your product be positioned ask questions about the tools and the way a customer is solving the problem right now:</p><ul><li><em>“How did you do it the last time? Tell me the last time you faced the problem?” </em>Helps to understand a use case better.</li><li><em>“What did you do to solve the problem?” </em>This shows if a problem is real. If a user did not do anything, then the problem is not big enough and not relevant enough.</li><li><em>“Do you use any tools to complete this task?” </em>You can note what tools customer names, and what is category he will compare you to in the future.</li><li><em>“What did you not like in the solutions you’ve used?” </em>This is a potential feature list of your product.</li></ul><p>To get the urgency about the problem that can later be reflected in your business model, try to ask the following question:</p><ul><li><em>“How often do you have the problem?” The problem</em> should be frequent because it is directly connected to the LTV of your customers and shows how much you should be able to pay for the marketing budget.</li><li><em>“How much would you pay for this solution?” </em>This can be also a question that helps you to better understand the urgency of the problem.</li><li><em>“Do you know anyone who has the same problem?” </em>Shows if they often discuss this problem and you have a chance to get another contact to reach out to.</li></ul><p>Important is to keep in mind that you should avoid letting customers talk about features. Make them describe their problem and routine to the full extent so that you can come up with the proper way to solve this problem. And avoid them describing their ideal way of making things. It is important to understand what they are actually doing to complete the task. What helps here is if you can observe the way customers complete their tasks and observe their reactions/challenges. This is the best way to understand how customers are making decisions. Try to understand what motivates your customer that will help you tune your product better to the target group.</p><p><em>Step 4: Evaluate the results and look for insights.</em></p><p>This step requires rather a diligence in working with all the data you have generated in your interviews, looking for the commonalities and insights. To evaluate the results first we need to be clear on what a validated hypothesis is. A validated hypothesis means that your target customers confirm having a problem while doing a specific job and s/he is looking for the solution to solve this problem or has tried to solve the problem in another way. What also helps to evaluate a potential is understanding how severe the problem is and how often does it occur.</p><p>You should not be afraid to prove that your idea/hypothesis is not feasible. This is also a good sign and the only thing you need to do is to use the insights you’ve generated in the interview to adjust or pivot your business idea. No matter how hard you believe in it, if customers do not see value for them, you will not be successful.</p><p>To sum it up here is a template that might be used to structure customer development efforts. For every validation category that you find the riskiest for your product, a set of hypotheses should be identified with the profile of your target customers that should take part in your validation. This is your setup. Then we look at two dimensions: things to observe (or quantitative understanding of a problem) and questions to ask (qualitative understanding of a problem. For every category, you select the most appropriate method to study users: interviews, surveys, studying support feedback, usability testing, eye tracking, usage statistics. After getting the answers you can document insights and plan the next steps/actions. That is it, repeat it for every category you find risky for the success of your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8G-TlEwtnnH6JhnUorc8Q.png" /><figcaption>Customer development template</figcaption></figure><h3>Mistakes to avoid</h3><p>Last but not least let’s talk about the mistakes to avoid while doing customer development. I collected common <em>anti-patterns</em> you’d be better to avoid:</p><p><em>Talk about your product first.</em></p><p>Your main goal is to focus on the problem, otherwise, you will get the opinions on the features you need to introduce, and not a real validation of the viability or value behind your product.</p><p><em>Ask leading questions.</em></p><p>Your goal here is to get honest feedback, but not to confirm what you believe should be a problem. That’s why try to keep your questions as free from your own beliefs and assumptions as possible.</p><p><em>Focus on the ideal way of solving things or how it should be.</em></p><p>It is a big difference between what people do and what they say. That’s why the most relevant for your data will be in the past, what people actually did to solve the problem, but not what should be an ideal way to solve it.</p><p><em>Try to validate all the hypotheses you have in one customer interview.</em></p><p>Focus is a king, even in such unstructured on the first sight thing as an interview.</p><p><em>Do interviews only at the beginning.</em></p><p>Make it a habit to talk to your users constantly. Even if you have a mature product.</p><p><em>Go into the interview without any goal.</em></p><p>This is also about placing focus on everything you do.</p><p><em>In the end, what matters is if your product nails down the customer&#39;s pain point. This will define its success. The only way to achieve this is to introduce customer development as a constant practice, you should not be afraid of it, but rather approach it in a structured way. What I can recommend deepening the knowledge into this topic is checking up the following resources:</em></p><ul><li><em>Book “Lean customer development” by Cindy Alvarez</em></li><li><em>Book “The Mom Test: How to talk to customers &amp; learn if your business is a good idea when everyone is lying to you” by Rob Fitzpatrick</em></li><li><em>Video on how to talk to users: </em><a href="https://www.youtube.com/watch?v=MT4Ig2uqjTc&amp;t=1s"><em>https://www.youtube.com/watch?v=MT4Ig2uqjTc&amp;t=1s</em></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=183fb9b5676c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product challenge #1: navigating your strategy]]></title>
            <link>https://allakopylova.medium.com/product-challenge-1-navigating-your-strategy-2cddb1be91d6?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cddb1be91d6</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sun, 17 Oct 2021 16:57:59 GMT</pubDate>
            <atom:updated>2021-10-17T16:57:59.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RyAseByxXQKzGwJOj_o9VQ.jpeg" /></figure><p>There are different opinions on challenges in product management and my list starts with the ability to tell “no” to multiple product requests. Deciding what to build is an extremely difficult task, that should be aligned with the long-term perspective of your product and not just opportunistically focus on the short-term wins. The worst thing you can do is losing the long-term picture and focusing on one-off requests that serve one customer. In deciding what to build it is important not only to have a clear prioritisation approach but also a strong product vision and focus. The last one — focus — is unattainable without a clear product strategy.</p><h3><strong>What is a product strategy?</strong></h3><p>A product strategy is a balancing act between choosing the most rewarding problems and assigning resources to solve these problems. It is important while despite the size of the organization you are in, you will always be always short on resources. Two important aspects to keep in mind here: product strategy should be led by problems and not solutions (aka feature requests), and the most rewarding problem is reflected in the product vision fit, biggest customer reach, and hence impact on revenue.</p><p>The question to ask yourself: how to understand that you have a clear product strategy? The answer is simple: if you can say “no” much more often, than saying “yes” to a new opportunity, then you have the strategy. What can help you in making these decisions is having a clear understanding of:</p><ul><li>your business focus and the most important to be aligned on in the organization,</li><li>product data and trends related to your business model, acquisition funnel, retention. It provides you insights into which situation your product is used in and by which customer group,</li><li>qualitative insights from user research,</li><li>industry or technology trends.</li></ul><p>All these provide us with the characteristics of a good product strategy. A good product strategy is:</p><ul><li>… focused on one target market or one target persona (user group) at a time. Do not try to please all possible user groups at a time. This is the most important part of the whole product management — the ability to prioritize and to say “no”.</li><li>… aligned with a business strategy. If the goal of your business is to grow and acquire new users next year, then the product strategy should fully reflect it. This means that your product goals should also be structured around driving engagement and user growth. This is why before starting to work on your product strategy you need to understand if your goal as a business right now is to solve a specific user problem that leads to the increase in acquisition, engagement, or revenue; or to optimize an existing experience, or scaling to new markets and channels, or optimization of operational efficiency.</li><li>… clear across the whole organization and every department contributes to it.</li></ul><h3><strong>Why being clear on your product strategy is important?</strong></h3><p>It is all about focus. If you would like to succeed with the limited resources you need to target your solution to the specific needs of your customers, and it is rather challenging if you try to address all at once: be it every customer segment you might have or any opportunity you might face.</p><p>Clear product strategy is the bridge that connects your high-level product idea and vision to the specifics of how you reach the vision or your roadmap. It helps to laser-focus the efforts on product discovery and delivery, and provides you the answers to the following questions:</p><ul><li>which outcomes do we need to pursue to fulfill our vision or reach specific business outcomes?</li><li>which customers do we need to serve first to reach our vision/outcomes faster?</li><li>which opportunities do we need to address?</li></ul><p>It is easy to do a self-check to understand if you have a product strategy by answering the following questions:</p><ul><li>do you have a clear decision to focus on the specific customers right now and fully understand what are the pains and needs?</li><li>do you have a clear target of where you want to be in the future?</li><li>do you know your objectives and can measure them to evaluate if you are approaching your vision?</li></ul><h3><strong>How to align product vision, product strategy, and roadmap?</strong></h3><p>What if you face a situation where you do not have a clear product strategy and find it difficult to answer the questions above. Let’s use the following 7 steps to navigate the way to product strategy.</p><p><strong><em>1. Business goals</em></strong></p><p>The first thing is to start with understanding the context and collecting the macro perspective. This presumes collecting the information on the following aspects:</p><ul><li>business goals you set for your company,</li><li>market and competition insights,</li><li>what threats and opportunities do you see for your company and product,</li><li>what trends you might leverage, i.e. significant changes in technology, distribution, and innovation or any social trends.</li></ul><p>The outcome of this step is to be clear on the business goals or a high-level objective you are trying to achieve as a company and which macro-factors you can leverage (trends and market opportunities) or what you should mitigate/be aware of (your weaknesses or threats). The business goals can be focused on expansion into the new territories or increasing the revenue, for example, “5x growth in revenue by…”, “expand into five new countries in the first half of the year”. This will guide all your product strategy efforts and experiments you are planning.</p><p><strong><em>2. Product vision</em></strong></p><p>Then revisit your product vision. If you do not have one, then take time to define a product vision first. It should answer the “<em>Why?</em>” question behind your product and represents a high-level view of what you want to create in the future with your product. Sets the North star for every decision you make. It can take years to achieve it, but with every product goal reached you are getting closer.</p><p>The product vision should be customer-focused, otherwise what is the reason your product exists if you do not do it for your customers. Also, address differentiation aspects in your vision, why exactly you and why are you better. You should also keep in mind that product vision is not the same as a company vision. Your product strategy shows the way to reach your product vision which in its turn is linked to the business goals.</p><p><strong><em>3. Product goals</em></strong></p><p>Based on your business goals and the product vision the next step is to form your product goals or objectives that represent your targets to accomplish. These goals are measurable which you can use to evaluate your product efforts against and always exist in a particular period of time. For example, if we have as a business goal to “Increase revenue from sales”, your objectives can be: “Increase qualified leads by 30% by Q4 2021”, “Increase conversion by 15% from ‘interested’ to ‘purchase is done “. The first objective can be influenced by marketing/sales, but the second one is completely in the product’s responsibility and you can work with it breaking it down to actionable items — your roadmap.</p><p><strong><em>4. Target customer group</em></strong></p><p>The next important step is to know you are your customers. If you have multiple segments and are not sure what to start with, look always after the segment that has the most unmet needs that might be the “easy catch” for you, if the market is easily accessible (this means you can reach out to your customers easily to get the fast feedback and customers are helping you to co-create the product). These two aspects are much more important at the beginning to build up the product because it will make no good if you target a market with big customers, but to get the feedback you need to wait weeks if not months. The speed of iteration is everything at the beginning. Even if TAM does not look attractive, but you managed to build a strong core with the niche user group fast, it is much better as you can then adjust your product later to the needs of the other bigger group.</p><p><strong><em>5. Product opportunities</em></strong></p><p>Pain points of your customers along with the opportunities your market is presenting you or trends from your list of opportunities.</p><p>When talking about the pain points you need to evaluate how acute the problem is and what is the frequency of this problem to your target group. Here the good approach is to use an opportunity solution tree, where every opportunity is connected to the desired outcome you would like to reach. Every product opportunity gives you the list of hypotheses you have to validate before starting building the product.</p><p>While generating opportunities you might consider the following dimensions:</p><ul><li>solving a user problem,</li><li>optimizing and existing experience with the product,</li><li>scaling to the new channels or markets,</li><li>reducing an operational overhead.</li></ul><p>This is for example an approach employed by Google “70/20/10 rule”:</p><ul><li>70% goes on the core initiatives that help you to build the main defensible. e.g. addressing a core business need, improving the solutions that exist,</li><li>20% is for adjacent opportunities (maybe something fires there). E.g. new market entry or extending your product offering,</li><li>10% on the transformational projects — these are the risky projects.</li></ul><p><strong><em>6. Prioritization</em></strong></p><p>And every opportunity needs to be prioritized and for this is important to have a set of prioritization factors, like reach, impact, effort, etc. And then depending on the weights, you set for every opportunity you can plan the generation of solutions and experiments that back this solution up. This helps you to keep your focus on your product efforts.</p><p><strong><em>7. Roadmap</em></strong></p><p>Having the prioritized list of opportunities that focus on your target customers group and are traced back to your product and business goals represent your product strategy, which can be later on translated to the roadmap and answers the question “<em>What?</em>” of your product. A roadmap is a plan of your strategy that can be either objective-based or theme-based. An important thing to keep in mind is that your backlog is not your roadmap, it is one step above and needs to be easily communicated, so you should not include everything into your roadmap.</p><p>If your product roadmap is not based on a strategy then it is simply a series of tactical or reactive deliveries that do not necessarily lead to reaching goals or objectives.</p><p>These 7 steps are summarised below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Da_cBy-5AdqY6fJQNgzMPQ.png" /><figcaption>Aligning product vision, strategy, and roadmap</figcaption></figure><h3><strong>Conclusion</strong></h3><p>Though a product strategy might seem a challenging task, it is more about science than art. If you know your business, your customers well then finding out the critical path to reach the stated results is not that complicated. Hope that the framework above assists you with it, and also would like to refer to the resources that I find quite good inspiring:</p><ul><li><a href="https://productsthatcount.com/fmr-netflix-vp-of-pm-on-product-strategy/">GLE Framework</a></li><li><a href="https://www.easygenerator.com/en/blog/e-learning/70-20-10-business-innovation/">70–20–10 Rule for innovation</a></li><li><a href="https://www.nicolasrica.com/blog/what-is-product-strategy?utm_source=departmentofproduct_newsletter&amp;utm_medium=departmentofproduct_newsletter&amp;utm_campaign=departmentofproduct_newsletter#">On roadmaps and prioritisation</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cddb1be91d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Boosting your self-development]]></title>
            <link>https://allakopylova.medium.com/boosting-your-self-development-9b20d2b79e7?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b20d2b79e7</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sat, 21 Aug 2021 08:51:31 GMT</pubDate>
            <atom:updated>2021-08-21T10:03:14.257Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tn15hu1xAscWlkMmAfF96A.jpeg" /></figure><p>Self-development became the main topic of modern life. Just look at the never-ending stream of self-improvement books, programs, and various articles on the topic. However, what is the most efficient way to speed up your professional and personal development? In my example can say that books, articles, and conferences help you to get the required knowledge, but one of the most efficient ways here is to exchange with somebody who can either share their experience or listen and then ask good questions. Leveraging the experience of smart people around you is a tool that can bring you further in your career and personal life.</p><p>I cannot stop talking about the importance of mentoring both professional and personal life and let me start with mentioning the main benefits of mentoring:</p><ul><li>self-development and career progression. You are learning from the experience of the other person, be it a mentor or a mentee.</li><li>confidence. Mentees learn to speak up and talk about their problems, and for mentors seeing the success of the mentee reaffirms their abilities.</li><li>increased self-awareness. You need to realize your strengths, weaknesses and be clear on your values to engage in the mentorship relationship.</li><li>communication skills, ability to listen and deliver feedback.</li><li>problem-solving. Especially mentors are challenged to see the problem from a different perspective. It is worth mentioning that mentoring is a two-way street where mentors also learn a lot from mentoring.</li></ul><h3>First steps before looking for a mentor</h3><p>Mentors represent the supporting network that helps you to grow. And building up this supporting network is not possible without specific goals you set for yourself. You need to be clear on your vision first, what do you want to achieve, what are your challenges. Every decision you make should be guided by this vision of your future self. After setting a vision and goals, it is easier to understand which people do I need in my supporting network, who should be my role model.</p><blockquote>You dream about something, define your goals and define your vision, then find people who help you get there.</blockquote><h3>The importance of your supporting network</h3><p>It is all about self-development and getting better every day. It requires a huge effort from your side to maintain the order of your life, be it health, relationships, career, and skills. This constant battle for your focus and progression in the direction of goals is accompanied by friction. That’s why by placing yourself in the supporting environment you not only rely on internal motivation but get support and guidance from the outside.</p><p>Let’s imagine that you decided to become an artist. Hanging out with the people who neglect art will not bring you any good, you need to surround yourself with artists first, whom you can exchange ideas with and who will motivate you to keep going. The same with becoming an entrepreneur - you need to surround yourself with the role models that can inspire you.</p><p>Long story short: when you plan to invest in yourself you should invest in your circle first and carefully pick up people you spend the most of the time with. The people you can learn from can help you keep the focus on your goals and the most important increase interest in what you are doing and motivate for the new ways of exploring how things should be.</p><p>This supporting circle can also include people that you know virtually, who share their knowledge through social media, for example.</p><h3>On mentoring relationship types</h3><p>There can be different ways you engage with the people who support you. And here comes the classification of mentoring in three groups: advisor, coach, and mentor.</p><p><em>Advisor</em></p><p>If we talk about career or professional space this is the most common and the most beneficial type of relationship that can help you solving the existing problem. These are the people who have a similar experience to yours, you share the same domain and/or profession and are more experienced in this. They usually have achieved something that you set yourself as a goal now. The relationships with an advisor have some specific goals and are limited in time.</p><p>What are success factors in this relationship:</p><ul><li>you need to have a specific goal or problem you are trying to solve</li><li>you need to manage your relationship actively to get the best results</li></ul><p>The easiest way to find is to check precisely for the people in the area you are working in that achieved something you plan to (can be Linkedin, conferences, or postings on freelance platforms with the request to give a consultancy).</p><p><em>Coach</em></p><p>Compared to an advisor this is a type of mentorship role where a person not necessarily achieved what you are planning for, but can help to figure out the way to it.</p><p>As an example, you can think of an athlete and sports coach. As you know the best soccer players rarely end up being successful coaches. This is the main difference between coach and advisor. Advisor will give you answers to your problems from his experience, while the coach will help you figure out the way to solving your problem by asking the right questions.</p><p>The relationship with a coach is more long-term. This is the type of person you should fully trust and be sincere with.</p><p>A coach helps you to define a goal, helps you to work through your impediments in achieving this goal, be aware of your resources, support and motivate you in reaching your goals, but not as an active role, more as an observer.</p><p><em>Mentor</em></p><p>This is the most complex type of relationship that requires a lot of time and effort to build it and also special chemistry between you. The person who are your role model, but not only in one specific area, like career, but overall with the life attitude.</p><p>These relationships are deep and long-term and always assume no pre-defined schedule for meetings or no predefined problems to solve. You just exchange on some particular topics and a person shares his wisdom with you.</p><p>You can be from different professional domains, but need to share the same values when it comes to life attitude. This is a person you are comfortable with and who is to become your friend.</p><p>Depending on your current goals and situation, and also on your personality type you can decide what kind of support you are looking for and start searching for these people. The recipe for a mutually beneficial relationship with your advisor/coach/mentor is mainly commitment from both sides, sincerity, and open communication.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b20d2b79e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting MVP right]]></title>
            <link>https://allakopylova.medium.com/getting-mvp-right-a58b92cab627?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/a58b92cab627</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sat, 26 Jun 2021 06:52:06 GMT</pubDate>
            <atom:updated>2021-06-26T06:52:06.438Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why do most startups fail? One of the reasons is focusing on a wrong problem or lack of knowledge about the actual one. We need some tool that helps to study the problem space better and only then switch focus to building the final product. However, what usually happens is that the rear resources are spent on building the product, and only then learnings are collected. What is a better solution here is to utilize the MVP approach or a minimal viable product to collect validated learning.</em></p><p>Quite often MVP is associated with the first version of a final product built and delivered to customers. The misconception here is that MVP should not be treated as a product in its final form where half of the features are de-prioritized. MVP is more about establishing a <a href="https://www.ycombinator.com/library/4Q-a-minimum-viable-product-is-not-a-product-it-s-a-process">repeatable process</a> that helps to deliver value to customers and validate main product risks before any substantial investments.</p><blockquote>Validated learning is the one purpose of MVP.</blockquote><p>For example, instead of building a software piece that solves customer problems, focus on finding a way how to deliver services manually. This is not a scalable approach but gets you to the feedback from customers faster. Once you understand that users benefit from the service you provide and most important are ready to pay for it, you can start focusing on the product itself and how it can potentially evolve.</p><blockquote>The goal of MVP is to gather feedback and iterate over it. It is not the first increment of your final product and can be completely different from the product you will end up building. The main goal behind MVP is to communicate the way you solve the problem to your target users and get some traction on it.</blockquote><h3>Product risks</h3><p>Every product idea is followed by some risks that we should try to mitigate before starting any development effort. The most critical risks or unknowns are good candidates for applying MVP. But first, let’s see what are the main risks a product might have:</p><h4>Feasibility</h4><p>This relates mainly to the implementation risk or the evaluation of the product from a technical standpoint. However, this is one of the least important risks you might want to address at the beginning, as 90% of all the commercial products are more or less clear how to build, at least your engineers have had some similar cases before, otherwise we are in deep R&amp;D projects.</p><h4>Value and viability</h4><p>These are the most important aspects to validate before you start. They indicate if you have customers ready to pay for the product you are offering. Value alone is not enough if you decided to do a commercial product, as commitment from users to pay is the best indicator of the problem they have. And we should not forget that the goal of almost every company is to become profitable at some time. You should not optimize monetization from the very beginning, but you should be sure, that later on the value your product delivers is sufficient enough to monetize.</p><h4>Distribution</h4><p>Also, one of the risks indicating you can efficiently reach your customers, sell and deliver your product to them.</p><p>The wrong approach is to focus on technical feasibility first. In the beginning, the way a product should look, which features it should have, and which technologies to use, are not that important. It is the easiest to start with as you are not supposed to interact with the customer because getting harsh feedback is hard, however, negative validation is also a result that your idea does not match the problem space well and needs to be iterated.</p><p>Early feedback and engagement with customers help you to validate value and viability risks. By talking to people and presenting your idea, asking questions, you can already understand if your idea solves a problem and if you have potential buyers. You will be able to evaluate the following questions:</p><ul><li>Does your product solve users’ problems, and if there is enough demand from their side?</li><li>Are people ready to pay for it, and how much?</li><li>What features do they want to get in your product?</li></ul><p>The hardest part is to validate the market and if your product can deliver value and viability for your business. Business is built around the problems people are ready to pay. So, try to get deeper into these problems first and sell before you make.</p><h3>Validation of product ideas</h3><p>MVP is more about using the fewest time possible to validate a product idea and prove demand along with the ability to distribute your product. It is possible due to feedback loops you have built with your users. MVP helps you to build this feedback loop. Depending on the question you might have, there can be four types of MVP.</p><p><em>Group 1: Content-based MVPs</em></p><p>Applicable if you are validating if there is a real problem and would like to get an idea of your potential target audience in the early stage. It is one of the fastest ways to validate ideas and is a good choice for B2B products. For example, this can be content in blog posts, newsletters, free webinars on the topic related to your product.</p><p><em>Group 2: Demos</em></p><p>Help to prove demand for your product and also gather feedback from your target audience. You can rely on landing pages, demos, and doing presentations of your product idea to your customers. Also, crowdfunding campaigns are the approaches to gauge demand when you have no product in place.</p><p><em>Group 3: Prototypes</em></p><p>Help not only to validate your understanding of a problem but provide you with feedback on the way you are solving this problem. A couple of examples are click-dummies, paper prototypes, and any kinds of models that represent your product idea.</p><p><em>Group 4: Product imitation</em></p><p>A good choice for validation of your service value. It is also a good choice for B2B space. Some examples here are The Wizard of Oz and Concierge prototypes.</p><p>Two rules to keep in mind while building MVP:</p><ul><li>Your goal is not only to get feedback but also a commitment from your customers. It can be either signups or payment for your service or LOI if we are in B2B space. If you have proved demand and have a waitlist of hundreds of target users in the B2C space, and at least several LOIs in the B2B context, you can investing in building the first version of your product.</li><li>You should timebox your validation period. Timebox your validation efforts. The whole thing about MVP is that the validation should happen fast, so impose a hard deadline.</li></ul><blockquote><a href="https://www.youtube.com/watch?v=knNyCVcc5z0"><em>Take 48 hours, try to make people pay you, and you have an answer if you should move on further with the idea or not.</em></a></blockquote><h3>Designing MVPs</h3><p>How to start with MVP? Consider the following steps in the process:</p><ul><li><em>Who is your target customer?</em></li></ul><p>Be focused and specific here. It is easier to target a niche, validate your assumptions within it, and then grow out from it.</p><ul><li><em>What is their problem?</em></li></ul><p>The problem that you perceive as a problem might not be the same for your customers. Also, it is good to understand if this problem is worth solving.</p><ul><li><em>What is your value proposition for this target customer group that your future product can deliver?</em></li><li><em>What is my riskiest assumption?</em></li></ul><p>Understand your main potential risk here. Is it engagement from the user&#39;s side (value)? Is it possible to market and distribute the product (distribution)? Can you monetize your idea (viability)? Or is it some technological risk you might have (feasibility)?</p><ul><li><em>What experiment should I plan to test the riskiest assumption?</em></li></ul><p>Here select the most appropriate type of MVP. It depends on the risks you have identified at the previous step:</p><ul><li>If the goal of your MVP is to learn more about the problem and get the first interested people, then you can use content-based prototypes: s<em>ocial media and posts or blogs, newsletters, any kind of webinar.</em></li><li>If you try to understand if people will pay for your solution (viability), then you can try driving traffic to <em>a landing page</em> that communicates your value proposition or start a <em>crowdfunding campaign.</em></li><li>If you know that the problem is present and the user base is there, but are not sure about the way you should solve the problem, then you can pick up process-based prototypes — Wizard of Oz or Concierge. Even static prototypes can do their job here.</li></ul><p>After designing MVP, test it with your target customers and get early feedback. Try to understand their goals. The intent here is to make them commit to your product. Commitment means show readiness to pay. It is necessary because just liking your product is not a commitment and indication of future usage. After all, business exists to be profitable, and you need to be sure that your efforts would have a chance to be paid out.</p><p>What can be the typical problems to avoid while designing MVP:</p><ul><li>You have an idea of the product and decide on which features should be in MVP. The right approach here is that MVP is about learning more about your problem space. Only if you know the specifics of the problem, you craft the solution the users will use on a repeatable basis (product-customer fit). MVP is not about the initial version of your product with the trimmed feature set.</li><li>You plan just one MVP, and it is enough to have one experiment. The more diverse experiments you run to understand the problem space better, the more confident results you get.</li><li>Validation of the obvious things. Only the riskiest and critical problems should be part of the validation and MVP process.</li><li>No payment guarantee from your customers. Liking is not buying.</li></ul><p><em>To sum up the main takeaways on MVP:</em></p><p><em>1. MVPs is more about the process that helps to validate:</em></p><ul><li><em>your product idea with real users and collect insights for your future product initiatives;</em></li><li><em>your sales strategy, the way you attract your customers and deliver a product to them.</em></li></ul><p><em>Apart from the strong validation focus, MVP allows you to test and get as much feedback as possible before writing a single line of code. It also serves the purpose of attracting your first users.</em></p><p><em>2. Keep the focus and start with the riskiest hypothesis and validate it. Remember that the less is more, and you should not validate all possible things in one go.</em></p><p><em>3. Do not focus on features to build. Start with delivering the maximum of value and the process of value delivery.</em></p><p><em>4. Try to get some commitment from your customers, and do not forget about readiness to pay.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a58b92cab627" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Products that inspire: Peloton]]></title>
            <link>https://allakopylova.medium.com/products-that-inspire-peloton-f9aeef4ac475?source=rss-bacb15609f31------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9aeef4ac475</guid>
            <category><![CDATA[peloton]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[success-story]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Alla Kopylova]]></dc:creator>
            <pubDate>Sat, 10 Apr 2021 08:32:47 GMT</pubDate>
            <atom:updated>2021-04-10T08:32:47.768Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The best approach to learning how to build winning products is to analyze the companies that succeeded. I’d like to open up a series of posts exploring the products that inspire me. And the first in the line is Peloton.</em></p><p><em>If you have never heard of Peloton before 2020, then 2020 should’ve changed it. Peloton is all the rage in the fitness world right now. The investor reporting by the end of 2020 shows 232% of total revenue growth, driven by solid demand for Bike and Bike+, followed by 382% of digital subscription growth. Investing heavily in content remains the secret ingredient of Peloton’s business model and makes it hard to be reproduced by the other platforms.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6wpJlI0cG3OiLPVmndiWQ.jpeg" /><figcaption>Source: <a href="https://www.pinterest.de/pin/768426755155809445/">https://www.pinterest.de/pin/768426755155809445/</a></figcaption></figure><p>The trend marks the 2010s for a healthy lifestyle. Almost everyone tried if not attending a gym but exercising at home, buying different fitness equipment, and subscribing to various online classes. Bikes, treadmills, steppers, rowing machines are present in different configurations in the fitness equipment market, and it is tough to stand out in these product categories. But not for Peloton. A stylish bike that perfectly fits your apartment became one of the highlights of the past years. However, Peloton is not just a bike. It is more than that. It is your “gateway” to the world of connected fitness.</p><p>Developing such a product was a challenge, as the fitness market is an overcrowded category, and it has not seen much innovation recently. Before Peloton gained momentum, connected fitness was primarily associated with fitness trackers and fitness apps. Still, Peloton made the home workout experience complete by adding an indoor bike followed by a treadmill with a huge, really huge library of highly engaging and motivating content. How did they manage to innovate an already crowded market and, more than that, created a separate product category?</p><p>The story of Peloton gets us back to 2012 in New York, where the idea to remove the main obstacle on the way to attending your gym class was born. After eight years of developing a product, it now operates in four countries, having showrooms and studios for shooting workouts and an army of celebrity fitness trainers.</p><h3>Problem</h3><p>What separates us from a healthy future? The answer is a busy schedule, lack of motivation, long way to the gym, and you name it. As a result: <em>you are just not working out as much as you should.</em> And precisely here, Peloton found a huge opportunity to reinvent the way we work out.</p><p>Everyone strives for better health, better appearance. In pursuing these, we keep on buying gym memberships, attending different fitness classes, jogging outside, or working out at home. For most of us, group workouts are a preferred option as it helps boost motivation through the competition with your group mates. And this gave rise to the trend of boutique fitness experiences.</p><p>Boutique fitness classes are instead a niche part of the fitness industry, but they grow fast. Spinning, yoga, pilates, HIIT, and Crossfit studios differ from gyms in the way they provide smaller and more intimate fitness experiences and focus on a community of like-minded people. Boutique fitness also addresses one of the social trends and adapts to millennials and younger generations who look for more personalized experiences and a sense of community.</p><p>The only (major) drawback here is that you need to book classes on time, and the classes given by your favorite trainer can accommodate only a specific number of people and are usually booked out fast. The next complication is that you need to arrange it with your work schedule, which is not always possible, considering late meetings, rush hour, and traffic jams. And the significant thing about instructor-led classes is that you attend not a studio. Still, you abounded to a particular fitness coach, and if the coach leaves, then your motivation to get back to a studio can also decrease.</p><p>So, we’ve got this challenge:<em> how can we have a boutique fitness experience that fits my schedule and stick to it?</em></p><p>Back in 2013, Peloton answered this challenge in their <a href="https://www.kickstarter.com/projects/568069889/the-peloton-bike-bring-home-the-studio-cycling-exp">Kickstarter campaign</a> that also helped to validate the demand for boutique fitness experience at home. This campaign helped to raise $307,332 and validated the need for the new product that later becomes <em>“Apple of the fitness world” or “Netflix for gyms”.</em></p><h3>Product</h3><p>“<a href="https://www.businessinsider.com/peloton-ceo-sells-happiness-more-than-bikes-2019-8">Peloton sells happiness</a>”</p><p>Peloton started to revolutionize boutique fitness experiences by eliminating one of the main problems: <em>the complexity of accommodating workouts into a busy schedule and exercise regularly</em>. As a result, Peloton’s product offering appeals to one of the central core human drives: <em>drive to connect to others, feel valued and liked, become more attractive.</em></p><p>Peloton’s product line is represented by hardware (Bike, Bike+, Tread), software that provides access to a media content library, and apparel to round it up.</p><h4>Connected fitness</h4><p>Peloton’s original product as we know it is a bike with a touch screen on it and a massive library of media content. However, the hardware part — bike — was a risky step for a startup, as it implies higher costs and a complicated production cycle. The team first tried to start with the software part — the app with the content — that can be run on a tablet attached to the existing bikes. They quickly noticed that attaching the tablet to the bike, all those cords and connections did not look nice, so they took a risk to tackle a hardware part. This focus on holistic experience grants Peloton the name of “Apple of the fitness world”.</p><p>A stationary bike with a screen on it allows you to participate in classes and community workouts. You are not only buying a bike but access to the community and high-quality content. A treadmill that came next shares the same concept.</p><p>The way Peloton solves users’ paint points is quite remarkable. The people who seek boutique fitness experiences in the convenience of their homes offer a bike with a prominent touchscreen display that is rather stylish and fits perfectly in the interior.</p><p>The crucial part of the hardware design is the support of OTA (over the air) updates that help Peloton to innovate fast compared to their competitors and can react quickly and innovate not in years but months.</p><h4>Media content</h4><p>Product development of Peloton started with the hardware part — a bike that is an expensive item, and it makes the growth hard. That’s why the second pillar of Peloton’s growth is the Peloton workout app that became a massive piece of their growth strategy.</p><p>The app gives access to the exclusive sports content available on a subscription basis and includes not necessarily classes that require a bike. Classes on yoga, power training, stretching are also part of the content library. What makes these classes different from the other apps is that celebrity instructors lead them. These instructors’ contribution results in an extensive library of high-quality content that grows over time and builds up a community around it.</p><p>With the celeb instructors, Peloton nailed it. They exactly understood what drives most people to fitness classes. So much depends on who is teaching!</p><p>What Peloton does great is building a network around the content they produce. Users can attend live events that allow you to meet people you are taking classes with, leader boards, video chats, badges. Peloton quickly realized that music plays a considerable part in the workout experience that made them investing in B2B music streaming through the acquisition of <a href="https://techcrunch.com/2018/06/27/peloton-acquires-music-startup-neurotic-media/">Neurotic Media</a>. This acquisition made them even more independent when it comes to content delivery.</p><p>And all these resulted in a high user engagement rate: the average monthly workout in Q4 was <a href="https://investor.onepeloton.com/static-files/dd43f8b8-acc9-443a-bc51-fd26433ec549">24 times</a> that is entirely not bad if you compare it to the gym.</p><p>To sum it up: the hardware-plus-subscription business model is hard to create and to make successful. Peloton nailed it due to the focus on personalization, content, and community around it.</p><h4>Apparel</h4><p>Finally, Peloton offers the third pillar of products: sports clothes — T-Shirts, bags, leggings make up to 1% of revenue, and this completes the holistic experience from interacting with the brand.</p><h3>Business model</h3><p>The three product pillars that we talked about drive the monetization strategy of a company:</p><ul><li>Fitness app brings monetization through users’ memberships to access live streams and content library — a flat fee of $39 per month. Peloton has almost 93% retention, making this stream promising and scalable as this is the primary source of recurring revenue. High engagement of users and low churn that is around 2%, proves the subscription model’s success.</li><li>Hardware or “connected fitness products” come for a high price, as it might seem — treadmills for $4,295 and bikes for $2,245 <strong>— </strong>but result in 80% of a company’s whole turnover. An interesting approach here is to allow a financing option when users can pay out a bike cost for around $58/month, comparable to a standard gym membership or two classes of boutique fitness. It also creates lock-in for users for another couple of years, influencing the high retention rate of Peloton. If subscription business and content are the main focus for Peloton, why do they invest in hardware? As the company positions it, the hardware part covers marketing costs.</li><li>Exercise equipment and apparel take the rest of almost 2% of the total revenue share and complete the experience users get from Peloton.</li></ul><p>Peloton does incredibly well in keeping almost 93% retention, having 1.4 million users who completed around 60 million workouts in 2019. The clear indication about this product’s success is that users stick to using it for more than one year. Typically if you buy a bike, the likelihood of losing your intention to work out at home in a year is high. Why the Peloton retention is that high? It is due to the instructor-led classes and the creation of sticky experiences through the community where you compete with the others.</p><p>Below are some numbers shared by the company in the <a href="https://investor.onepeloton.com/static-files/75d1e429-dc1f-4264-b53e-6442e1b8c7bd">shareholders’ letter</a>. An average number of monthly workouts by 24 per subscription is a sign of sticky product experiences.</p><figure><img alt="Source: shareholders’ letter https://investor.onepeloton.com/static-files/75d1e429-dc1f-4264-b53e-6442e1b8c7bd" src="https://cdn-images-1.medium.com/max/1024/1*KeID2szljeNt1_gmRpoRkw.png" /><figcaption>Source: <a href="https://investor.onepeloton.com/static-files/75d1e429-dc1f-4264-b53e-6442e1b8c7bd">shareholders’ letter</a></figcaption></figure><h3>Key success factors</h3><p>What are the critical success factors of Peloton’s product and business model? Apart from a deep understanding of the problem space, there are a couple of additional items that are worth mentioning:</p><p><strong>1 — Urgency: how badly do people want or need it right now?</strong></p><p>One thing to tell here: a healthy lifestyle is something that will never become outdated. According to the statistics for the fitness industry, the prevailing <a href="https://www.wellnesscreatives.com/fitness-industry-statistics-growth/#overview">81% of millennials</a> have the highest goal to become and stay fit. The fast pace of our modern life and isolation will also add up on urgency for Peloton as you get a personalized fitness experience from the convenience of your home.</p><p><strong>2 — Market size: how many people are purchasing things like this?</strong></p><p>This item is tightly linked to urgency as well. Getting back to the health industry statistics: before the pandemics time, the world fitness industry experienced a growth of 2.9%, <a href="https://www.wellnesscreatives.com/fitness-industry-statistics-growth/#overview">with approximately 210,000 clubs globally and 184 million members</a>, excluding the boutique fitness experiences. The majority of these people turned their focus to home workouts.</p><p>Even if we imagine the everyday life where all gyms are open, in the markets where Peloton is active — UK, USA, Canada, and Germany — TAM is around 90 million people who buy fitness memberships and about 10 million people who opt for fitness subscriptions. The average number of treadmills sold is around 5M and bikes 3M pieces a year.</p><p><strong>3- Pricing potential: what is the highest price a typical buyer would be willing to spend for a solution?</strong></p><p>Taking into account the personalized nature of Peloton workouts and subscription-based model, we end up with a good range for pricing: on the one end are boutique fitness experiences with the price between 20 and 40 $ for a class, and on the other end are fitness apps with the price around 15 $ for a month. It all shapes the subscription price for the Peloton app.</p><p><strong>4- Marketing and cost of customer acquisition: how easy is it to acquire a new customer?</strong></p><p>When it comes to reaching the users, they rely on online marketing and TV commercials and provide offline experience for their customers. “If you try it, you want it” this slogan resulted in opening stores where you can experience the product before ordering it online and having it delivered to you. Peloton uses a TV channel to raise brand awareness, which proved itself the most efficient in pandemics time.</p><p>A strong community and network help grow through word of mouth and result in quite strong organic channel growth. The critical element that enables this organic growth is first-class content to create, which the company invests heavily in content partnerships collaborating with the stars.</p><p>It sounds like a lot of money. However, Peloton covers their marketing costs by the devices (Bikes and Treads) they sell.</p><p><strong>5 — Distribution: how can you reach your customer</strong></p><p>As for every big company with the ambition to provide the best customer experience, logistics is a king here.</p><p>From Shareholders’ Letter beginning of Q1 2021:</p><blockquote>“Also, as we rapidly scale our organization to meet the extraordinary demand for our products, we realize that some of our Members have faced extended delays associated with receiving our products or having support requests fulfilled.”</blockquote><p>To fix this problem, Peloton <a href="https://techcrunch.com/2021/02/04/peloton-will-pump-100m-into-delivery-logistics-to-ease-supply-concerns/">plans to invest $100M into delivery logistics</a> which also shows their focus on the efficient customer journey.</p><p>Peloton also leverages the power of multiplicators when it comes to distribution through cooperation with one of the more than 300 hotels offering private Peloton rooms where you get your bike and access to their network of classes.</p><p><strong>6- Uniqueness of offer: how unique is your offer versus competing offerings in the market, and how easy is it for potential competitors to copy you?</strong></p><p>When it comes to the differentiation from the hundreds of hardware and software fitness products, Peloton stands out due to the mix of hardware and software, providing the ecosystem for your workout. The main differentiator is the community and network that they managed to build up around the product.</p><p>Three product directions — hardware, software&amp;content, and apparel — might sound a little bit too much when it comes to focusing. However, this allows Peloton to move in any direction company decides, and due to the balance between the three directions, they managed to create a separate product category that already disrupted the fitness world.</p><p>The apps in the category “at-home workout platform” with the curated content keep on emerging, e.g., Apple Fitness+ and Centr. Apple Fitness+ is strong competition here, but you have the content paired only to your Apple Watch. At the same time, Peloton can always fall back to their devices (Bikes and Treads), which proves that the three directions Peloton addresses help and not only distort focus.</p><p>The rest of the applications in the category of home workouts target only one kind of workout, like SoulCycle (cycling), Asana Rebel (yoga), Athlagon (power training).</p><p>And also some emerging competitors, like Zwift, Tonal, or Mirror, try to bring interaction into your home workouts through their hardware.</p><p>To sum this up, at home fitness market is a blue ocean. There is enough competition out of there, but what helps Peloton to be unique is the mixture of content, hardware, and apparel.</p><p><strong>8- Upsell potential: are there related secondary offers?</strong></p><p>Here Peloton has a good position. All three products complement each other: you can start with the cheapest subscription for workouts, then purchase the hardware part and round it up with an apparel item.</p><h3>What can we learn from it?</h3><p><em>Peloton is one of the companies we can learn a lot from. The main takeaways that can be applied while building products:</em></p><ul><li><em>Good understanding of the problem, a high level of empathy to your target audience, and living the problem yourself help build a great product.</em></li><li><em>Rely heavily on prototyping to reduce technology risks as early as possible.</em></li><li><em>Invest in community creation and building engaging and sticky experiences in your product from day one.</em></li><li><em>Even if you are a startup and do not have enough funds, focus on the premium service and compete not based on price but based on the quality of everything you do.</em></li><li><em>And this all takes to the last point — do not take shortcuts. It does not matter how hard this can be. Prioritize quality and building loyalty.</em></li></ul><p>And here is the condensed version of the product breakdown:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G0H0ApmxNttF9SgTQLbRKw.png" /></figure><h3>Links</h3><p>If you are interested in investigating Peloton’s product further, check the following links that are quite informative:</p><p><a href="https://www.launchnotes.io/blog/how-they-launched-it-peloton?utm_source=convertkit&amp;utm_medium=email&amp;utm_campaign=How+they+launched+it%3A+Peloton%20-%205072153">https://www.launchnotes.io/blog/how-they-launched-it-peloton?utm_source=convertkit&amp;utm_medium=email&amp;utm_campaign=How+they+launched+it%3A+Peloton%20-%205072153</a></p><p><a href="https://blog.mywallst.com/how-does-peloton-make-money/">https://blog.mywallst.com/how-does-peloton-make-money/</a></p><p><a href="https://www.fool.com/investing/2020/10/29/why-peloton-stock-fell-sharply-on-thursday/">https://www.fool.com/investing/2020/10/29/why-peloton-stock-fell-sharply-on-thursday/</a></p><p><a href="https://www.purshology.com/2019/11/four-factors-behind-the-success-of-digital-fitness-brand-peloton-econsultancy/">https://www.purshology.com/2019/11/four-factors-behind-the-success-of-digital-fitness-brand-peloton-econsultancy/</a></p><p><a href="https://www.npr.org/2019/04/05/710439824/live-episode-peloton-john-foley?t=1607194323086">https://www.npr.org/2019/04/05/710439824/live-episode-peloton-john-foley?t=1607194323086</a></p><p><a href="https://www.toptal.com/finance/equity-research-analysts/fitness-boutiques">https://www.toptal.com/finance/equity-research-analysts/fitness-boutiques</a></p><p><a href="https://nogood.io/2019/10/16/peloton-growth-marketing-strategy/">https://nogood.io/2019/10/16/peloton-growth-marketing-strategy/</a></p><p><a href="https://www.similarweb.com/website/onepeloton.com/competitors/">https://www.similarweb.com/website/onepeloton.com/competitors/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9aeef4ac475" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>