<?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 Tanya Bragin on Medium]]></title>
        <description><![CDATA[Stories by Tanya Bragin on Medium]]></description>
        <link>https://medium.com/@tbragin?source=rss-83277fe57157------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Cqvq8HWjtMswbLjkHovx6Q.jpeg</url>
            <title>Stories by Tanya Bragin on Medium</title>
            <link>https://medium.com/@tbragin?source=rss-83277fe57157------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:11:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tbragin/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[Strategies for open source product management]]></title>
            <link>https://medium.com/design-bootcamp/strategies-for-open-source-product-management-f77f19372880?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77f19372880</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Thu, 02 Nov 2023 12:35:11 GMT</pubDate>
            <atom:updated>2023-11-04T17:05:31.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hiAd5EXyMpbY1GMdTNQ0NQ.png" /></figure><p>Having worked with several open source products as a product manager (PM), I sometimes get asked how being a PM focused on open source is different from traditional product management.</p><p>I started my PM career at a traditional B2B company, where we were not relying on the open source distribution model. At one point, we developed an integration with “the ELK stack” and that is how I learned about Elasticsearch, a popular open source search and analytics engine.</p><p>I was lucky enough to join <a href="https://www.elastic.co/">Elastic</a> on the ground floor as a PM for the logging use case, and it was a bit of an adjustment at first to figure out how to operate as a PM for an open source product. After 6 years at Elastic, I joined <a href="https://clickhouse.com/">ClickHouse</a>, a popular open source real-time analytics database, as a head of product.</p><p>This blog describes key concepts critical to understand when working with open source, as well as some of the things I learned as an open source PM and keep in mind to this date.</p><h3>Types of open source projects</h3><p>Open source projects are not all the same. They use different software licenses and governance models.</p><p><strong>Open source licenses</strong>: There are many <a href="https://en.wikipedia.org/wiki/Open-source_license">open source licenses</a> with different goals, restrictions, and implications for users. The main distinctions I think about are:</p><ul><li>(1) <em>How “permissive” is the license</em>, meaning can you just use it without any restrictions? An example of a commonly used permissive license is Apache 2.0.</li><li>(2) <em>How “viral” is the license</em>, meaning if you use it, does your software have to also be open sourced? An example of a license where that is the case is GPL.</li><li><em>(3) Is the license standardized (</em><a href="https://opensource.org/licenses/"><em>OSI approved</em></a><em>) or custom?</em> In recent years, many commercial open source companies (COSS), such as Elastic, Confluent, Hashicorp, stopped using OSI approved licenses and started using customized licenses to restrict competition with CSPs and other hosted providers of software.</li></ul><p><strong>Governance models</strong>: Open source projects can be <a href="https://www.redhat.com/en/resources/guide-to-open-source-project-governance-models-overview">governed in multiple ways</a>, but the main models I have seen adopted in the data space are:</p><ul><li><em>Founder-leader</em><strong>. </strong>This is how many open source projects get started. A creator of a project publishes it and at first supports it as a side-job. For example, Elasticsearch was built and open sourced by Shay Bannon in 2010 as an independent developer, and was supported solely by him until formation of Elastic in 2012.</li><li><em>Single-vendor</em>. As the name suggests, in this model, a single vendor chooses to distribute some of its intellectual property under an open source license. Sometimes, this project is not core to their business, and they simply look to attract collaboration around it (for example, the Facebook React project). Sometimes, the vendor exists specifically to support and build a business around the open source project (e.g. MongoDB, Elastic, ClickHouse).</li><li><em>Foundation-backed</em><strong>. </strong>A foundation is a non-profit organization managing an open source project on behalf of many interested parties. Popular foundations include Apache Foundation, CNCF, and Linux Foundation. A project can be donated to a foundation by a commercial entity or a solo creator. Many open source projects in the data space are managed by foundations, including Apache Kafka, Apache Spark, Prometheus, etc..</li></ul><h3>Open source community members</h3><p>In the context of open source, “community” refers to people that use, contribute to, and build businesses on top of the open source project.</p><p>If you are a product manager, you are likely working at a company responsible for extending the open source project and building a commercial business fueled in part by this project. Your role may differ depending on your company’s relationship to the open source project, its license, and governance model (see above).</p><p>For the rest of this blog, I will assume that your company is wholly or partially responsible for the open source project direction and roadmap. If that is the case, it is important that you know how to interact with the community of users and contributors and leverage these relationships positively toward the project success.</p><ul><li><strong>Users</strong> are individuals who adopt open source in some capacity, whether for personal use or production use in their organization. They typically evaluate it against other technology alternatives, and can be a great source of product feedback.</li><li><strong>Contributors</strong> are individuals that get actively involved in improving the project, typically by improving the code or documentation. There are one-time contributors (e.g. fix a specific bug, add one new feature — usually in the context of their own use), and consistent contributors (e.g. maintain an existing feature on an ongoing basis, or consistently contribute bug fixes and features — not only for themselves). Sometimes they are enthusiasts that contribute on their own time, and sometimes their contributions are sponsored by their employer.</li><li><strong>Customers</strong> of a commercial open-source company are individuals or organizations that pay money in exchange for a service (e.g. support, professional services) or an additional commercial product (e.g. commercial extension or hosted version of open source product).</li><li><strong>Ecosystem</strong> of integrations refers to open-source or commercial projects that extend the core capabilities of the product and allow it to interact with other software. This is especially critical in the infrastructure space, where a project does not exist in isolation, but is usually part of a technology stack that gets adopted together. Understanding what this stack is for each key use case will help you identify the right connectors to build, maintain, and nurture within the ecosystem.</li><li><strong>Partners</strong> of a commercial open-source company are individuals or organizations that provide products or services that do not directly compete with the core offering of your company. Usually, their activities broaden adoption of open source and thus the potential serviceable market, and they may be interested in joint go-to-market strategies and co-marketing activities.</li><li><strong>Competitors</strong> of a commercial open-source company are individuals or organizations that provide products or services that overlap or directly compete with your core offering. Sometimes, if the overall market opportunity is large, such an offering may be competitive in the part of the market where you are not currently focused, and in that case, this potential competitor can become a partner or an eventual acquisition target.</li></ul><h3>Things to keep in mind as an open source PM</h3><p>Here are some of the things I learned that helped me transition to open source product management from a traditional commercial PM role.</p><ul><li><strong>Marketing</strong>: In the context of open source offerings, how marketing works is very different. Rather than spend a lot of money on branding and top-down sales, it is more typical to rely on users adopting the software directly and sharing their experiences with others through word of mouth. A lot of the marketing activities then become about finding these users and giving them avenues to share their stories — either through virtual and online forums, or in-person meetups and conferences.</li><li><strong>Sales</strong>: Similar to marketing, the sales organization typically works differently in the open-source commercial company. Since your product can be tried at scale and even adopted in production before a sales person ever gets involved, it is possible to to avoid building a massive, top-down sales force in the early stages of the company. You can avoid needing to run long, costly proof-of-concepts and be successful with sales folks who are good at reaching out to existing users of open source and gauging interest in commercial offerings (sometimes referred to as “farming” as opposed to “hunting” in sales lingo).</li><li><strong>Getting product feedback</strong>: It is tempting at first to only get feedback from customers — i.e. those that pay for your commercial offerings — because you know who they are, and they can help you understand why they adopted your commercial offering. But do not forget to talk to your open source users, as well as those that use competitive offerings. These users can help you understand why they are choosing to use your project as opposed to other technology alternatives, as well as discover different types of commercial offerings you may have not introduced yet.</li><li><strong>Innovation</strong>: Building on the previous point, because users can adopt your product for free, the open source offering often becomes a great platform for experimenting with new ideas. Users will choose it for “moonshot projects”, and even if there are rough edges with these new use cases initially, they’ll often stick with it, because the platform is free and they can contribute improvements. As a result, the amount of innovation that happens on top of open source projects, in my experience, is exceptional, and you can often see where the overall industry is headed earlier. In some circumstances, whole new products and viable commercial companies may be built on top of open source outside of your company, and these can become great partners or acquisition targets.</li></ul><h3>Commercial strategies</h3><p>Every commercial open-source company has a strategy for being financially self-sustaining. Commercial goals may differ — from bootstrapping and lifestyle-business as a goal, to venture-backed and aimed at high-growth and eventual IPO.</p><p>If you are a PM for an open source project as part of a company that is commercializing some aspect of this software, it will be important to understand the financial goals of your company and how commercial vs open source offerings fit into these goals. You will have to decide if specific features, new products, or improvements should be built and released as part of open source, built and released under a commercial license, or perhaps not introduced at all.</p><p>There are many ways to build businesses on top of open source offerings, and it is possible to combine them.</p><ul><li><strong>Support and services</strong>, including commercial support, professional services, and paid training and certification. While typically not considered high-growth and enough to sustain a business alone, due to low margins and high cost of hiring technical professionals, almost any business on top of open source will have some amount of these services. However, most modern successful COSS companies target to have support and services to no more than 10% of their business.</li><li><strong>Commercial distribution</strong> of an open source project. Popularized by RedHat in the early days of commercial Linux, it is still not uncommon to have an “enterprise version” of an open source project. This version typically has higher reliability and quality assurance guarantees, and is sometimes combined with commercial features not available in open source.</li><li><strong>Commercial features</strong> on top of open source core distribution released for self-managed usage. These “commercial extensions or add-ons” typically represent “advanced” features that most early adopters and individual users do not need, but are aimed at larger organizations adopting open source in a commercial setting and willing to pay for mission-critical production use of the project. As a result, these features typically include advanced security and disaster recovery capabilities. Elastic and MongoDB both serve as good examples of this model in the early days of their commercial journey.</li><li><strong>Hosted offerings.</strong> It is increasingly common to offer a hosted version of open source software as a cloud or hosted offering, consisting of open source as well as cloud-native tools and services. There are multiple ways to package hosted software — multi-tenant, dedicated, bring-your-own-cloud (BYOC), and even “private cloud” — and successful commercial open-source companies may eventually build out all of the above. Many modern COSS companies today (including ClickHouse, where I am currently), start with sole focus on hosted offerings as the main way to build commercial offerings.</li></ul><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77f19372880" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/strategies-for-open-source-product-management-f77f19372880">Strategies for open source product management</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to maintain pace at a startup without burning out]]></title>
            <link>https://medium.com/@tbragin/how-to-maintain-pace-at-a-startup-without-burning-out-de89cb21d3cc?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/de89cb21d3cc</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 12:14:09 GMT</pubDate>
            <atom:updated>2023-06-21T12:14:09.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdDMgm6XLNQl5d45ycglcA.jpeg" /></figure><p>In my blog <a href="https://clickhouse.com/blog/my-journey-as-a-serial-startup-product-manager?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">“My journey as a serial startup product manager”</a> I shared my story of working at three early stage startups over the years.</p><p>One follow-on question I sometimes get is — <em>how did you survive the fast pace of early stage startups for so long?</em></p><p>Frankly, I don’t really think of working at startups as “surviving” because I enjoy it so much, but I have to admit that not everything came naturally and I learned to pace myself over the years.</p><p>Here are some tips-and-tricks for those newer to startup life:</p><ul><li><strong>Join people and a cause that inspires you.</strong> I mentioned in a previous <a href="https://medium.com/design-bootcamp/product-management-at-startups-2b729026cc64">post</a> that early startup employees tend to be “missionaries”, with a passion for what the company is trying to build together. I think that being one of the missionaries is a key ingredient to making a startup an enjoyable experience. To me, I also look for highly inspiring individuals to look up to and learn from, at every step of my journey.</li><li><strong>Embrace “It’s a marathon, not a sprint” mentality. </strong>Know what you need to be healthy, happy, and present in your reality outside of work. Working hard does not mean you ignore your personal life. While working at startups, I got married, had kids, and had many fun times with my parents and friends. Startups do not have to mean your personal life stops.</li><li><strong>Don’t give up on a “hard day”.</strong> Sometimes working at a startup is really hard, and certain days will make you feel like it is all too much. Close your laptop, take a walk, take a weekend, take a week — simply to recharge. Things will look very different, once you’ve given yourself a chance to breathe and reassess what is important to you.</li><li><strong>Take your career one step at a time.</strong> I was pretty impatient when I got into product management. I wanted to learn everything at once and be an expert others looked up to right away. But there is no shortcut to it. Some things you just have to learn from experience. Look for mentors, but more importantly look for experiences you have not had yet, and just start doing new things without fear. That is the only path to growth.</li></ul><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de89cb21d3cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crafting The Right Product-led Growth (PLG) Strategy For Your Startup]]></title>
            <link>https://blog.startupstash.com/crafting-the-right-product-led-growth-plg-strategy-for-your-startup-419be2e09376?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/419be2e09376</guid>
            <category><![CDATA[sales-led-growth]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cloud-marketplace]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Tue, 06 Jun 2023 12:23:36 GMT</pubDate>
            <atom:updated>2023-07-07T02:12:45.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0fph0HvHiaJfiduZ" /><figcaption>Photo by <a href="https://unsplash.com/@kaleidico?utm_source=medium&amp;utm_medium=referral">Kaleidico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When we set out to build ClickHouse Cloud, one of the core design principles behind the offering was to enable a product-led growth strategy. To us, this meant that developers around the world would be able to start using the product without having previous experience with ClickHouse and other analytical databases. Yet, because ClickHouse is also used by enterprises to power mission-critical applications, we knew we would need account managers and solution architects to help them be successful.</p><p>We heard that it was difficult to build an offering that combines both PLG and sales-led motions. At the same time, we saw examples of companies like Datadog that have successfully done exactly that, so we knew it was possible. In this blog, I share what I learned in the process of bringing ClickHouse Cloud to market about PLG and ways to combine it with enterprise sales-led motion.</p><p>I recently spoke on this topic in the panel discussion at the Tackle.io GTM XP conference. I summarize my insights below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fdo1O6unDrok%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ddo1O6unDrok&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fdo1O6unDrok%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f2655010d54f5791b9f3a25e64d5c192/href">https://medium.com/media/f2655010d54f5791b9f3a25e64d5c192/href</a></iframe><h4><strong>What is Product-Led Growth?</strong></h4><p>Product-led growth (PLG) is a business model where the product itself drives how users initially discover, start using, and remain loyal customers of the solution. By contrast, sales-led motion relies heavily on traditional marketing (ads, inside sales outreach) and direct sales engagement (meetings, formal POCs) to generate user interest and influence conversions. Benefits of PLG include lower customer acquisition costs and higher gross margins, as well as faster growth because it is not directly limited by how fast you can scale your sales force.</p><p>PLG does not happen by accident — the product itself needs to be designed, positioned, and distributed with this model in mind. For instance, if it is difficult for a potential user to understand the value of the product without talking to a salesperson or the product that is difficult to get up and running without consulting services, this product is not a good candidate for a product-led growth strategy.</p><h4><strong>How to design &amp; position your offering to be successful at PLG?</strong></h4><p>There are four stages of the product life cycle you should consider when you design a product for PLG or decide if an existing product is a good fit for it.</p><p><strong><em>Acquisition</em></strong><em>: How do you get customers to discover your product?</em></p><ul><li><strong>Technical content. </strong>Users don’t want to be “sold to” via mass mailing, ads, or direct contact. When they have a challenge, they want to self-educate. At ClickHouse, our users are very technical and they trust other technical expertise to help them in choosing their analytical database. As a result, we focus on deeply technical content like <a href="https://clickhouse.com/blog?category=engineering&amp;utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">blogs</a> and <a href="https://benchmark.clickhouse.com/?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">benchmarks</a>, to help our users self-educate in the areas where they are making choices. We pay attention to SEO, to make sure this content is accessible when users search for common terms.</li><li><strong>Community. </strong>Users also want to learn from the peers they trust. As a result, we invest in supporting our users where they are, speaking to other users in communities they are part of, be that <a href="https://github.com/ClickHouse/ClickHouse/issues">GitHub</a>, <a href="https://twitter.com/ClickHouseDB">Twitter</a>, <a href="https://news.ycombinator.com/news">Hacker News</a>, <a href="https://www.reddit.com/r/Clickhouse/">Reddit</a>, <a href="https://clickhouse.com/slack">Slack</a>, and so on. With the move back to in-person events, we are also organizing <a href="https://www.meetup.com/pro/clickhouse">meetups</a> and customer roundtables globally in key cities and post all of our meetup content on <a href="https://www.youtube.com/c/ClickHouseDB">YouTube</a>. We help users tell their stories through our <a href="https://clickhouse.com/blog?category=customer-stories&amp;utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">blog</a> and amplify their success in the various channels accessible to us.</li><li><strong>CSP marketplaces.</strong> Many of our customers prefer to consolidate their onboarding and billing through their existing cloud service provider (CSP). As a result, we invested early on in partnering closely with major CSPs where we host our solution to have a marketplace integration, have a clear listing that we advertise in multiple places of the customer acquisition funnel, and leverage their events and alliance programs to let their customers know we have a joint solution we both stand behind.</li></ul><p><strong><em>Activation</em></strong><em>: What is the “aha moment” that causes them to like the product?</em></p><ul><li><strong>Onboarding UX</strong>. User experience is king in PLG strategies. The expectation is that even if your product is B2B, your onboarding experience rivals some of the best consumer grade products. At ClickHouse, our mantra was “time to value in 5 minutes”. The user had to be able to sign up, start a service, load data and run blazing fast queries using ClickHouse Cloud in under 5 minutes. This influenced engineering choices we made, such as how and how fast we provisioned services and how much we invested in providing sample datasets, in order to support this requirement.</li><li><strong>“Aha moment”.</strong> Initial success does not mean the user is immediately convinced. They usually need more proof — working with their own data, trying out more scenarios, running a full-blown POC, or comparing to alternatives. To support this motion, the product experience needs to be as self-service as possible, and if there is a need to reach out to support, the process is seamless (e.g. in product chat, in-product support case flow).</li><li><strong>Free trial vs free tier.</strong> One big decision at this stage is how to enable users that are still deciding to have the right level of access to your product to make this decision. Inevitably this means that you have either a time-limited free trial or a capacity or feature-limited free tier. The free tier model is a good choice if there is basic usage for an individual where perpetual free access makes sense, but if they were to invite others and upgrade to team or department usage, they would be motivated to pay. A free trial is a good choice when individuals make a choice on behalf of the organization and need access to the full product suite during a limited period of time to make this decision. With ClickHouse Cloud, we started with a 30-day free trial during which we offer $300 of free credit toward a POC. This model works well for an analytical database because it allows the majority of our prospects to test the solution at a reasonable scale without being capacity and feature-limited.</li></ul><p><strong><em>Conversion</em></strong><em>: What causes the user to become a paying customer?</em></p><ul><li><strong>Persona-segmented packaging</strong>. Just because someone decides that your product solves their problem and they are happy using it, does not yet mean that they are convinced to become a customer. If your price point is too high or your packaging does not make sense for their needs, even the best product may become an unreasonable expense. For a broad platform solution like ClickHouse Cloud, it was important for us to realize that we appeal both to individual developers and small startups building analytical applications as well as large enterprises running data platforms for all of their teams. Our <a href="https://clickhouse.com/pricing?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">packaging</a> reflects that — we offer capacity limited, but very cost effective usage tiers, for the former and increasingly powerful and flexible tiers for the latter.</li><li><strong>Paid tier only features.</strong> Even with a generous free tier or free trial, it is a good idea to reserve some features that appeal to the most high-intent users for paid only. Your free offering should make it clear that these features exist and invite users to add a credit card to “unlock” them. As an example, the ability to run multiple services simultaneously in ClickHouse Cloud is not available under a free trial and reserved for paid users only.</li></ul><p><strong><em>Retention</em></strong><em>: How do you design your product for the longevity of use?</em></p><ul><li><strong>Usage-based pricing</strong>. The pricing model itself needs to be closely aligned with PLG motion. The most important tenet of PLG is adopting a frictionless, usage-based pricing model where you pay only for when and how much you use the product. I dedicated a separate <a href="https://medium.com/@tbragin/optimizing-usage-based-pricing-for-infrastructure-saas-83b6cec92d49">blog to usage-based pricing design for infrastructure SaaS companies</a>, and recommend interested readers to explore it. Choosing the right pricing dimensions to match how your users adopt the product initially and scale their usage is going to be one of the most important business decisions of a PLG strategy.</li><li><strong>Exit feedback.</strong> Some users will inevitably leave your service. It is important, to the best of your ability, to capture reasons for why this happens, so you can improve your service. It is best to send out a survey shortly after the user stops use, and offer the ability to speak live if they are willing to share more.</li><li><strong>Nurture.</strong> Some users leave the service because some functionality is missing for their current use case, but they may be interested to come back, once the service improves. Periodically send out concise product updates to those users that have opted in to stay in touch, so users can decide if they want to give your service another try.</li></ul><h4><strong>How do you successfully combine PLG with sales-led motion?</strong></h4><p>At a certain level of usage and for customers where PLG is not the right fit, your customers will want to reach out to a representative to work more closely together toward mutual success. They may want assistance with a really large migration, which requires an extended trial and tailored advice, or they may be interested in prepaying for some amount of usage in exchange for a discount.</p><p>It is important to make sure sales assistance is not required for initial adoption, and to let customers decide when they would like to engage with a salesperson. This can be done by embedding explicit “Contact Us” callouts on the website and the product or make such introductions through support. You can also alert on certain levels of usage, and send tailored communication to customers that exhibit specific signals.</p><h4><strong>Importance of ongoing usage and conversion analytics</strong></h4><p>Since the goal is for users to adopt and use your product without your help, you have to establish an effective product telemetry collection and analytics practice to understand whether your users are having a good time, which features delight them and help conversions, and which challenges cause them to stop using your service.</p><p>Some useful metrics to consider:</p><ul><li><strong>Conversion funnel by weekly and monthly cohorts</strong>. <em>Are users converting at higher rates as you evolve your platform? </em>We look at the number of users that reached, for instance, trial start, activation (data loading &amp; queries), and billable status.</li><li><strong>Activation is segmented by type of usage. </strong><em>What type of user is successful on your platform, and is this aligned with your hypothesis of the target persona? </em>We look at usage by customer size, geography, and types of features in use.</li><li><strong>Overall consumption by billing dimensions</strong>. <em>Are users as a whole consuming more of your platform over time? </em>We look at total storage and compute under management.</li><li><strong>User churn.</strong> <em>Are users leaving your platform more or less as you invest in the experience? </em>For a product like ours, this includes users that chose to leave the platform or significantly reduced activity leading to less billable usage.</li></ul><p>Whatever your signals, I highly recommend setting up product analytics data collection very early in your PLG journey and maturing your reporting as your offering evolves.</p><p>You can build an analytical platform yourself by collecting events into a database and analyzing them using a BI tool. At ClickHouse, we collect every click on our website, and all key events in our control plane, data plane, and core database and put them into a ClickHouse Cloud service and use an open-source BI tool called <a href="https://superset.apache.org/">Superset</a> on top of it to perform analytics and build dashboards (see more details in our <a href="https://clickhouse.com/blog/building-clickhouse-cloud-from-scratch-in-a-year#ui-and-product-analytics?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">blog</a> on this topic). There are also great turnkey product analytics tools out there, many of which happen to also be built on top of ClickHouse, e.g. <a href="https://posthog.com/">Posthog</a>.</p><h4>Resources</h4><p>Thanks for reading! As I mentioned at the beginning, for more discussion on Product Led Growth in ClickHouse Cloud and NetApp products, you can watch this <a href="https://www.youtube.com/watch?v=do1O6unDrok">panel recording</a> from Tackle.io GTM conference.</p><blockquote><em>For additional tools and resource ➡️ </em><strong><em>Visit </em></strong><a href="http://www.startupstash.com/"><strong><em>StartupStash</em></strong></a><em><br>Zendesk is giving $75,000 in credits and perks for startups! ➡️ </em><a href="https://tinyurl.com/4ta2c8j6"><strong><em>Apply Now!</em></strong></a></blockquote><p>If you are interested to learn more about my thoughts on product management, packaging, pricing, and the latest news about the products I am building, please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdNkqZeCg9j88Cw7djuAzA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=419be2e09376" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/crafting-the-right-product-led-growth-plg-strategy-for-your-startup-419be2e09376">Crafting The Right Product-led Growth (PLG) Strategy For Your Startup</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimizing usage-based pricing for infrastructure SaaS]]></title>
            <link>https://medium.com/@tbragin/optimizing-usage-based-pricing-for-infrastructure-saas-83b6cec92d49?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/83b6cec92d49</guid>
            <category><![CDATA[infrastructure-services]]></category>
            <category><![CDATA[usage-based-pricing]]></category>
            <category><![CDATA[usage-based-billing]]></category>
            <category><![CDATA[pricing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Wed, 17 May 2023 12:07:13 GMT</pubDate>
            <atom:updated>2023-05-17T12:07:13.013Z</atom:updated>
            <content:encoded><![CDATA[<p>When I joined ClickHouse to build out our <a href="https://clickhouse.com/cloud?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">serverless cloud offering</a>, one of the biggest unknowns was how to approach pricing.</p><p>For a full story of how we built the cloud offering, read <a href="https://clickhouse.com/blog/building-clickhouse-cloud-from-scratch-in-a-year?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">Building ClickHouse Cloud From Scratch in a Year</a>. This article focuses specifically on what I learned about usage-based pricing in the process, and tips-and-tricks applying this concept to infrastructure SaaS products.</p><p><strong><em>What is usage-based pricing?</em></strong></p><p>In a SaaS world, a usage-based pricing model means that you pay for the service based on consumption or “usage” by the users of the service. In contrast, a more traditional subscription-based model means that you get charged a flat fee on a monthly or early basis for a package chosen by you, regardless of usage.</p><p>Usage-based pricing can be more user-friendly, especially if it is hard to predict how the service will get used, because you don’t have to select the right subscription package upfront, and your bill is adjusted dynamically as you rely more (or less) on the product or service chosen.</p><p>For enterprises and larger customers, usage-based pricing is often coupled with the concept of “committed spend” for those users that know how much they will use the service and are comfortable pre-committing to a certain level of spend in return for discount.</p><p>Finally, one of the main advantages of usage-based pricing is that customer use of your product (and thus presumably the value they derive from it) is directly related to the revenue you derive. This means your incentives are aligned — you don’t “sell and forget”, but try at every step to ensure that your existing customers keep using your product with success.</p><p><strong><em>How to decide on usage-based pricing dimensions?</em></strong></p><p>Usage-based pricing is not always straightforward to define, because it may be hard to predict on which “dimension”, or indicator of usage, to base the pricing model. Ideally, pricing dimensions should be simple to reason about and possible to estimate based on how users envision themselves consuming the service as well as previous usage patterns.</p><p>For example, when we built out pricing for a cloud database like ClickHouse Cloud, there are several options we considered:</p><ul><li><strong>Many granular dimensions.</strong> If you consider every scenario in which your service may get used, you could arrive at dozens of potential pricing dimensions. Exposing all of them is likely going to be overwhelming to users, but paradoxically it is often the most “fair” pricing model, because it fine-tunes the pricing to every type of workload. You may have a user that is writing and reading at vastly different levels, storing vastly different amounts of data, creating a lot of tables vs not, a lot of partitions vs not, using a lot of columns vs not, using the network heavily vs not, relying on backups a lot vs very little, and so endlessly on. After evaluating the “extremely fair but inscrutable” pricing model, we discarded it as not the most user-friendly in ClickHouse Cloud.</li><li><strong>Opaque “usage units”.</strong> To deal with the explosion of granular dimensions, some SaaS services hide this complexity behind opaque “usage units” and charge by a single dimension calculated in the background by the cloud vendor. This approach may keep the fairness of the above model, but relies on user trusting the SaaS provider to be fair and honest. The opaque model makes it impossible for the user to reason upfront about intended usage vs price upfront; the only way to learn how much you will pay is to start using the service and see how many “units” a particular workload accrues. We briefly considered this approach in ClickHouse Cloud, but ultimately decided that it was a bit too opaque for the types of users we have, who are typically more technical and pride themselves on understanding the details.</li><li><strong>A few simple dimensions. </strong>This pricing model can be derived from the first model by taking away some dimensions from initial pricing, typically those that are either fairly constant amongst all users (e.g. all users want basic backups) or scale well with other dimensions (e.g. network consumption typically scales well with read and write volume). By simplifying the pricing model to a few core dimensions is not easy, but if you can do it, you can have the best of both worlds — a model that can be reasoned about by the users upfront and fair across your user base.</li></ul><p>Here is what we ended up with <a href="https://clickhouse.com/pricing?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">https://clickhouse.com/pricing</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cHjiJNLsRKpDTV5u8BB5QA.png" /></figure><p>As you start on your pricing work, it is important to make sure you have a reliable metering, billing, and pre-paid credits account engine. At ClickHouse we chose not to build our own and instead partnered with <a href="https://www.m3ter.com/customers/how-clickhouse-launched-its-cloud-database-with-m3ter">m3ter</a> on this capability. This allowed us to play around with different pricing models quickly during the private preview and beta period, without having to spend engineering resources building out functionality that we ultimately never shipped in production in GA, without regret. It also helped us get to market faster with our usage-based billing.</p><p><strong><em>How to make sure your pricing is “correct”?</em></strong></p><p>There are several places where you can go wrong with pricing, and it is important to pay attention to them continuously and course-correct as needed. Here are two examples:</p><p><strong>User friction</strong></p><p>Once you’ve come up with the pricing model, you can try to market-test it by showing it to users and asking for their feedback. Even better, you can get users to try an early version of your service for free, show them “mock usage bills”, and ask for their reactions. However, in my experience, this type of early market testing has limited value, because there is always selection bias in that type of exercise, and the real test comes when your service is out there used by many users with different workloads and needs.</p><p>When you go into public beta, it is very important to listen to the many signals that you receive (e.g. in HackerNews, Twitter, support cases, direct feedback) for any signs of friction in users understanding your pricing or misalignment between what you charge, the value users get, and alternatives they consider. Based on the feedback, you may have to make a pricing adjustment (e.g. take away a particularly difficult to reason about dimension and build it into the margin), or introduce a new class of an offering for a sub-classes of users with different needs (e.g. a new usage tier for a subset of the market).</p><p>In ClickHouse Cloud, we learned a lot through working with real users in Beta and made both types of these changes — we removed “read and write units” from pricing to simplify it, and introduced “developer services” for users that are just getting started vs going to production.</p><p><strong>Margins</strong></p><p>One thing you have to watch for with all these models is how your infrastructure costs scale with your pricing model, because if you missed a dimension or predicted wrong how it scales with usage, you may end up with higher costs vs how you priced for usage, and thus lower margins. If that happens, you can still correct it after the fact. For instance, you can add a new dimension to pricing or rate limit / cap usage for that dimension and optionally charge for overages as an add-on.</p><p><strong><em>Importance of ongoing usage and pricing analytics</em></strong></p><p>It is important to recognize that usage-based pricing is never final and you need to continue to evolve it as your product changes and new usage patterns emerge. It is very important to collect all usage dimensions (not just the ones you bill by) as well as all your infrastructure costs into a reliable datastore and analyze it overtime. At ClickHouse, we use our own analytical database technology for this, and can tell at any point in time how usage translates into billings for our users, and how additional usage dimensions and our trend, translating into margins. This enables us to adjust pricing and roll out changes to our service with confidence.</p><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83b6cec92d49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Lead a Global Product Team]]></title>
            <link>https://blog.startupstash.com/how-to-lead-a-global-product-team-f3a4b1f244aa?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3a4b1f244aa</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Wed, 03 May 2023 14:13:16 GMT</pubDate>
            <atom:updated>2023-05-18T04:10:43.813Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to lead a global product team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DjblU6tXrYizFY8hQqF2kw.jpeg" /></figure><p>I recently shared my story of working at three early-stage startups as a product manager in <a href="https://clickhouse.com/blog/my-journey-as-a-serial-startup-product-manager?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">“My journey as a serial startup product manager”</a>, and followed it up with advice on how to <a href="https://medium.com/@tbragin/how-to-move-to-product-management-from-technical-roles-b0d6503f77bd">move into PM from other technical roles</a> and <a href="https://medium.com/@tbragin/how-to-move-to-product-management-from-technical-roles-b0d6503f77bd">being a PM at a startup vs big company</a>.</p><p>In this story I wanted to dive deeper on team collaboration and how to build a global company, starting from an early startup stage.</p><p>First, a few examples from my experiences.</p><p><a href="https://www.extrahop.com/">ExtraHop</a> employees all worked out of a single office in Seattle. It had a hipster, fun startup feel to it, and being part of that culture was one of the best experiences of my life. However, when I moved to the Bay Area and tried to lead product management remotely, it was not practical, despite the efforts the ExtraHop team made. Too many conversations happened offline, and I felt out of the loop and ineffective. I decided to fly to Seattle every week, which helped me stay there a couple more years, but eventually became impractical as a lifestyle.</p><p><a href="https://www.elastic.co/">Elastic</a> and <a href="https://clickhouse.com/?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">ClickHouse</a> are both globally distributed and very multicultural organizations. Elastic was distributed from the very beginning, long before Covid made it popular, because early on it hired original committers to the Elasticsearch project, who were spread all over Europe. I love working for distributed companies, because I can hire great people wherever they live, and I can decide when to stay local and work from home, when to go to a local office, and when to travel to see customers or part of the team. This flexibility matters to me, and I do not think I personally would like <em>having to</em> go to the office every day again (I think it’s okay, if it’s a choice).</p><p>In my view, there are a few necessary ingredients that make fully distributed organizations work.</p><ul><li><strong>Optimize day-to-day for asynchronous work and decision making. </strong>Realize that live meeting time overlap between globally distributed teams is precious and finite. As a result, minimize meeting time, instead trying to make decisions via Slack, email, Github tickets. If a meeting is necessary, consider who is required, send pre-reads ahead of time, and record the meeting.</li><li><strong>Leverage time differences for their strengths, not weaknesses. </strong>When organizing collaboration, consider how you can leverage global distribution to accelerate things, instead of slowing them down. For instance, if you have one team member in EMEA and one in PST, consider a hand-off point at EMEA evening / AMER morning and another one AMER evening / EMEA morning, and be thoughtful about what information your colleague needs to have to be productive as he/she wakes up in the morning.</li><li><strong>Get together for offsites and working sessions (planned and unplanned). </strong>Some problems and decisions are really hard to work through remotely. Recognize when you’ve reached a point where in-person collaboration is necessary and make it happen (some budget should always be set aside for these impromptu in-person meetings). In addition, plan annual or bi-annual all-company get-togethers. Those are harder to plan, but are extremely important.</li><li><strong>Protect your (family) time.</strong> The biggest pitfall I’ve seen between distributed teams is consistently scheduling mandatory, recurring meeting times at a time highly inconvenient for a particular group of individuals. For instance, 8am-11am PST is dinner time in Europe. If you have a family with kids, it may be the worst time to have a recurring meeting, depending on circumstances. For many individuals I have worked with, it was preferable to have an occasional meeting after their kids go to bed, rather than intrude on family time. As a result, I usually suggest that everyone on the team advertises their sleep / family time on their calendars and opens up some “less convenient” times for meetings outside of business hours that they control. It is important to reciprocate — for instance, I am willing to wake up at 5 or 6am PST to have a meeting with my EMEA colleagues, but that also means I stop my work at 4pm PST to go on a jog and recharge.</li></ul><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><blockquote><em>For additional tools and resource ➡️ Visit </em><a href="https://startupstash.com/"><strong><em>StartupStash</em></strong></a><em><br>Zendesk is giving $75,000 in credits and perks for startups! ➡️ </em><a href="https://tinyurl.com/4ta2c8j6"><strong><em>Apply Now</em></strong></a><em>!</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3a4b1f244aa" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/how-to-lead-a-global-product-team-f3a4b1f244aa">How to Lead a Global Product Team</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How being a product manager at a startup is different than in big tech]]></title>
            <link>https://medium.com/design-bootcamp/product-management-at-startups-2b729026cc64?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b729026cc64</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Wed, 19 Apr 2023 16:53:04 GMT</pubDate>
            <atom:updated>2023-04-21T05:13:15.056Z</atom:updated>
            <content:encoded><![CDATA[<p>I often get questions about how I decided to become a product manager, and what I learned over the years being a PM at three startups — ClickHouse, Elastic, and ExtraHop. I shared a chronology of my career in <a href="https://clickhouse.com/blog/my-journey-as-a-serial-startup-product-manager?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">“My journey as a serial startup product manager”</a> blog on clickhouse.com website. In the next few articles, I will share my answers to frequently asked questions I get from other product managers or folks that want to get into product management.</p><p>A question I sometimes get asked is —<em> is product management different at startups vs later stage companies?</em></p><p>I have found that product management at early stage startups is very different from working at a bigger company. I left Elastic when it was a 2,000+ person public company with $500M+ in revenue and it was very different to lead product management at an organization that scale, compared to a 10-person pre-revenue startup :-) Here are a few things to expect from product management at early stage startups.</p><p><strong>Founders (especially technical founders) are product visionaries and de-facto heads of product at early stage startups.</strong> This is natural and should be expected. Who else would have had the idea to form the company, and raised money from investors? Contrary to popular belief, this does not conflict with strong product management leadership. I specifically look for passion and strong product vision in the founders I work with. I view the role of a product management in that equation as someone who is responsible for continuously checking the current vision against market signals, refining it as early customers start using the product, and helping make sure execution on this vision remains strong both on the product side (pricing, packaging, design/UX, etc..) as well as engineering (focused roadmap, realistic goal setting, iterative execution, strong technical differentiation, etc..)</p><p><strong>Product management and product marketing at early stages are tied at the hip.</strong> No matter how strong the original vision and business plan is, in early stage companies it should be expected that you are constantly learning more about the market, your place and opportunity in it, and adjusting execution based on that knowledge. The role of product marketing in that scenario is to talk to early customers and continuously refine understanding of user and buyer personas, their motivations, their willingness to use your product, and alternatives they consider. Based on that knowledge, you not only adjust messaging and run top of the funnel campaigns, but also consider changes in product priorities and direction. I sometimes refer to “product marketing” at early stage startups as “outside product management” and consider the skillsets of good early PMs and PMMs interchangeable.</p><p><strong>At a successful startup, execution will slow down over time.</strong> Everyone knows that startups can (and often have to) move fast in order to capture the market opportunity in front of them. But if you are successful and start acquiring customers at a high rate, it should be expected that your execution will slow down over time. This is not only due to customer support burden and maintenance, but also because as the company grows you are going to have less “missionaries” — passionate starting employees that joined for the idea and the team — and more “mercenaries” — seasoned professionals that join primarily for financial and career opportunities because the company is already successful. As it happens, the makeup and cadence of the team is likely to shift from working longer hours in a tight-knit group to something more measured and decentralized. I view this as a natural evolution of crossing the chasm.</p><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Chx-bWtQl7b-kDEW84XcA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b729026cc64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-management-at-startups-2b729026cc64">How being a product manager at a startup is different than in big tech</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to move to product management from technical roles]]></title>
            <link>https://medium.com/@tbragin/how-to-move-to-product-management-from-technical-roles-b0d6503f77bd?source=rss-83277fe57157------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0d6503f77bd</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Tanya Bragin]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 15:02:55 GMT</pubDate>
            <atom:updated>2023-04-19T18:36:28.118Z</atom:updated>
            <content:encoded><![CDATA[<p>I often get questions about how I decided to become a product manager, and what I learned over the years being a PM at three startups — ClickHouse, Elastic, and ExtraHop. I shared a chronology of my career in a blog titled <a href="https://clickhouse.com/blog/my-journey-as-a-serial-startup-product-manager?utm_medium=social&amp;utm_source=medium&amp;utm_campaign=tbragin">“My journey as a serial startup product manager”</a> on clickhouse.com website. In the next few articles, I will share my answers to frequently asked questions I get from other product managers or folks that want to get into product management.</p><p>One question I get asked is — <em>what do you do if you already work in another role in tech, but suddenly decide that you want to do product management?</em></p><p><strong>If you are in a company that supports transfers between roles,</strong> I’d recommend exploring opportunities there, before exploring roles outside. The reason is — you have already established your reputation, and now it’s a matter of gaining and showing off transferable skills. I have seen and supported successful transfers to product management from sales engineering (or solution architecture), consulting, software development, and design. There are surely other paths, but those are the most common that I have seen. Some of the best PMs I have worked with have come from these backgrounds.</p><p><strong>If you are in the field (consulting, training, solution architecture, etc..) </strong>consider helping define detailed requirements for a new feature already on the roadmap, bringing in specific examples from the customers you are working with. Connect product managers with these customers, but also write down and share your thoughts in a helpful way. In parallel, informally share your interest with a hiring manager you trust on the product side, and ask for coaching, as well as advance notice if they plan to open product management roles on their team.</p><p><strong>If you are on the engineering side (software development, design, etc..) </strong>consider asking for more direct customer exposure by joining PMs or support on customer calls to observe and learn about user and market needs. If you work at an open source company, take initiative to support open source users by answering questions in forums, Slack, Github, etc.. The more you know about customers’ needs, the more ideas you’ll have on how to solve their problems. At that point, you can either make a business case for a new feature or product, or even quickly build a prototype to show the business what is possible.</p><p><strong>If you don’t get a chance for a role change inside the current company</strong>, it’s perfectly valid to seek roles outside by applying for product management roles directly. One area of product management that is often a great fit for field engineers is ecosystem integrations or partner product management, because practical field experience often results in broader perspective compared to “career PMs” at bigger companies who have had to focus on a particular type of product or market. If you have a software development background, you may consider applying for “technical product management” roles that may have a much higher technical bar to meet and are often hard to fill with more traditional candidates that have less recent hands-on experience. Finally, if you are a designer or a user experience professional, you may be a great fit for a product that has complex user interactions as a big part of the scope.</p><p>Thanks for reading! Please follow me here on Medium, <a href="https://twitter.com/tbragin">Twitter</a>, and <a href="https://www.linkedin.com/in/tbragin/">LinkedIn</a> to learn more about my thoughts on product management, packaging, pricing, and latest news about the products I am building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0d6503f77bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>