<?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[Product Stories - Medium]]></title>
        <description><![CDATA[Building Amazing Product means getting your entire team — from marketing, design, tech, growth — aligned on delivering the best user experience. Come hear the behind the scene stories about the people who build the products you love to use everyday. - Medium]]></description>
        <link>https://medium.com/productstories?source=rss----23f44cb7cb18---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Product Stories - Medium</title>
            <link>https://medium.com/productstories?source=rss----23f44cb7cb18---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:06:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/productstories" 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 Marketing at an Early Stage Startup]]></title>
            <link>https://medium.com/productstories/product-marketing-at-an-early-stage-startup-fefa263cec50?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/fefa263cec50</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-marketing]]></category>
            <dc:creator><![CDATA[Jonathan Costet]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 14:45:02 GMT</pubDate>
            <atom:updated>2019-04-30T14:45:02.602Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6ygyPpv7Vb-54Tk9I_pgw@2x.png" /></figure><p>In the early stages of a company Product Marketing exists — it just usually isn’t called that. It might be owned by your first marketer. It might even still be owned by one of the founders. And what product marketing comes down to in those early stages is mapping out the story, tuning that story down to your different personas and lifecycle stages, and distributing these messages across the different channels at your disposal.</p><p>As marketer #1, handling all these moving parts can feel overwhelming — because it is. A good rule of thumb is to focus on quality over quantity. You can’t do everything: but everything you do should be done well. Controlling the output and placing a high bar is a great way to both generate maximum impact per action, as well as to focus limited energy and resources on those actions that hold the greatest potential for your business. A logical way to then start breaking down the big blocks that need to be put in place is to proceed in order: starting from the overarching story, and then trickling down to personas, lifecycle stage, and channels.</p><h3>Step 1: Building the story</h3><p>Companies basically exist to make money. But that motive alone doesn’t cut it to construct a story and get people talking about it. In order to do that, companies need to find their “why”. The “why” is what they sell investors when they raise funds. It’s what gets their first employees excited about joining their team. And it’s what the first customers will end up paying for.</p><p>Articulating a full-fledged world-view from an embryonic piece of software isn’t easy. A few questions that can help getting started with uncovering your “why” are: Where do we see the market being in 10 years? How are we helping it get there faster? What obstacles are in the way? Tackling these “big picture” questions should yield some sense of what you stand for as a company, how you envision the future, and the route you’ll trace to get there.</p><h3>Step 2: Positioning the product</h3><p>Positioning touches on everything from what you chose to call the product or service your company provides and how you will showcase the value it creates, to how it will packaged and priced. It’s critical for the continued success of your business, especially as willingness to pay for features has been on a steady decline for the better part of a decade.</p><p>In the early stages, positioning starts with a first articulation of your story to your key personas. Starting with the day-to-day, consider what your persona’s “jobs to be done” look like and how your product fits into performing these tasks. Specifically, delve into the sequence of actions at play and the different tools your personas currently use to complete each one: Which pain points does your product solve and how does it solve them?</p><p>Then move beyond the nitty-gritty. Marketing is also about values, so don’t hesitate to have an opinion and — ideally — one that resonates with your story. How does your persona’s job evolve using your product? What changes does it bring to their life? To their company? In the world? Pick a fight, people will recognize you for it.</p><h3>Step 3: Finding Marketing/Market fit</h3><p>By this point, you show know what you want to say, and who you want to say it to. What remains is sequencing your messages throughout the lifecycle and distributing them across the right channels. A lot of this depends on the nature of your business: low-touch vs high-touch, commercial vs enterprise, solo-use vs cross-functional use. In the early stages, however, a big part of the job is finding the early adopters that exist on your market and cornering that subset of your target.</p><p>Early adopters aren’t present on the usual channels your persona uses. Put yourself on the radar leveraging the communities, content, and interactions that already exist in that space. Early adopter will typically move much quicker from being pain-aware to considering a purchase and will be eminently concerned with your vision. Your messaging needs to reflect that. Hone down your pitch to the bare minimum: a succinct presentation of the pain point, an actionable description of your product, with a dose of inspirational story-telling. Once you’ve tapped the early adopters and are looking to spread your message to your target persona at scale, you’ll need to hire your first product marketer and work the full depth of the messaging, persona development, and distribution you put in place. And ultimately, outgrow your “Product Marketing MVP”.</p><h4>Slides</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FE1iNREq6DXmjgW&amp;url=https%3A%2F%2Fwww.slideshare.net%2FJonathanCostet%2Fproduct-marketing-at-an-early-stage-startup&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fproductstoriesjon-190430144041-thumbnail-4.jpg%3Fcb%3D1556635330&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce5c3a801d7297b86ea73727b0e99b55/href">https://medium.com/media/ce5c3a801d7297b86ea73727b0e99b55/href</a></iframe><h4>Resources</h4><ul><li><a href="https://tomtunguz.com/marketing-roadmap/"><em>The Clearest Articulation of a Marketing Roadmap</em></a>, Tomasz Tunguz</li><li><a href="https://blog.efounders.co/how-to-scale-productmarketing-with-stephanie-bowker-and-roxana-siu-calviac-e4ef418e0238"><em>How to Scale #ProductMarketing, with Stephanie Bowker and Roxana Siu-Calviac</em></a>, Inside eFounders</li><li><a href="https://www.intercom.com/blog/all-walk-and-no-talk-how-to-grow-your-products-voice/"><em>All walk and no talk? How to grow your product’s voice</em></a>, Inside Intercom</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fefa263cec50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/product-marketing-at-an-early-stage-startup-fefa263cec50">Product Marketing at an Early Stage Startup</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Marketing learnings and stories]]></title>
            <link>https://medium.com/productstories/product-marketing-learnings-and-stories-78ce8dcd9b98?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/78ce8dcd9b98</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product-marketing]]></category>
            <dc:creator><![CDATA[Product Stories]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 13:02:35 GMT</pubDate>
            <atom:updated>2019-04-30T14:52:55.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pYLHklNfdcO6F8IaFd7nHQ.jpeg" /></figure><p><em>Here are the key takeaways from our seventh </em><a href="https://www.meetup.com/_ProductStories/"><em>Product Stories meetup</em></a><em> about product marketing management, hosted at Deezer. Jump back to this meetup by watching the recording and going through the main takeaways</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEhinH_aDHBA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEhinH_aDHBA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEhinH_aDHBA%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/9b98e50d0f5bb09ae37bfaae17ffe392/href">https://medium.com/media/9b98e50d0f5bb09ae37bfaae17ffe392/href</a></iframe><p>After an insightful fireside chat about finding the market fit with <a href="https://twitter.com/@g_montard">Guillaume Montard</a>, <a href="https://twitter.com/ArthurROUGIER">Arthur Rougier</a>, and <a href="https://twitter.com/maiametz">Maïa Metz</a>, we were thrilled to touch on a new product management topic: Product Marketing.</p><p>We happily welcomed <a href="https://medium.com/u/532f586940ba">Anne Jouanjean</a> — Head of Product Marketing and Communication (<a href="https://www.deezer.com/en/">Deezer</a>), <a href="https://medium.com/u/d4bb7d8948e0">Jonathan Costet</a> — Head of Marketing (<a href="https://medium.com/u/7081782135b2">eFounders</a>), and <a href="https://medium.com/u/9afdebe24134">Dustin Coates</a> — Voice Search Go-To-Market Lead (<a href="https://medium.com/u/a531947eec97">Algolia</a>).</p><p>They took the stage to share their experiences and thoughts on the role&amp;missions of the Product Marketing Manager from day one, their relationship with other teammates, and many more.</p><p>Here are some of the juiciest takeaways:<br><em>Of course, none of these are cold, hard, facts. Just several viewpoints.</em></p><h4>The role of product marketing</h4><blockquote>Product marketing is the process of bringing a product to market and overseeing its overall success. Product marketers are focused on understanding and marketing to customers. They drive demand and usage of the product, which often includes writing positioning and messaging.<br>Source: <a href="https://www.drift.com/blog/what-is-product-marketing/">https://www.drift.com/blog/what-is-product-marketing</a></blockquote><p>Even if the concept of product marketing may seem totally obvious, our guests emphasize the fact that product marketers wear a lot of different hats and their responsibilities are varied.</p><p>Indeed, they are at the intersection of different roles and almost every team of the company such as Product, Engineering, Sales, Marketing, Customer Success, …</p><blockquote>Communication is so incredibly important because you are touching on so many teams — Dustin</blockquote><p>Anne explained that the product marketing team at Deezer, currently 4 employees, was created to reduce the lack of communication between Engineering, Product and Marketing teams.</p><p>But also to make sure no more feature is launched without a proper promotion plan (<em>The product is key but the storytelling is God!)</em>. An important job considering the 200+ features in Deezer products.</p><p>In addition to external and internal communication, the product marketing team is often in charge of competitive research and collaterals creation. As Dustin said it’s really important that teams are fully aware and trained on the new product.</p><p>He and his team send an email every 2 weeks to nearly the whole company on what’s new, what’s going on with the voice and conversational search products. On a more regular basis (daily), they’re interacting with 10 to 100 people.</p><p>Jonathan completed the job description by explaining how important it is to focus on the story first at an early stage company (more on this topic via the link below 👇)</p><blockquote>You can’t do everything at early stage. But everything you do should be done well — Jonathan</blockquote><p><a href="https://medium.com/productstories/product-marketing-at-an-early-stage-startup-fefa263cec50">Product Marketing at an Early Stage Startup</a></p><h4>Projects and tasks organization in a product marketing team</h4><p>No common pattern. Work can be split by product (Voice vs “traditional” search at Algolia), offers (e.g. Free, Family, Premium, … at Deezer) or not at all at the early stage because of the product simplicity.</p><h4>How to keep consistency across communication</h4><p>They all agreed on the importance of having product marketing collaterals such as feature descriptions (several lengths to adapt to the context) and positioning, glossary, brand guidelines, … to be used by other teams.</p><p>Having someone or a team dedicated to copywriting, not only for the product, is definitely an advantage for keeping a high level of consistency across the company.</p><p>Tools like Confluence, Slite or even Google Docs can be used to centralize this knowledge and easily share it when needed.</p><h4>Building a new feature with customers</h4><p>At an early stage, you’ve kind of a partnership with your few customers or beta testers, creating product marketing content and designing upcoming features with their help.</p><p>They feel like they have a tool that you almost custom-built for them.</p><p>It’s getting more complicated when you’ve 8000+ customers like Algolia.</p><p>Unless you narrowed down your focus to customers with needs specific enough so you can better know when your product development is successful but general enough to be interesting to other customers.</p><p>Here are some of the criteria shared by our guests to pick up these customers to design the next features with:</p><ul><li>relationship (a good one obviously ^^)</li><li>dream customers — the one you’ll love to build your next feature with</li></ul><blockquote>- Make sure you’re not choosing customers you can’t build what they need because you’ll be losing time and never be really sure you reached your goal and succeeded</blockquote><blockquote>- Make sure they’re aligned with your product strategy and have the right mindset (co-building a feature is almost like a pact between you and your customer. Not the traditional seller-to-customer relationship)</blockquote><ul><li>team resources (number of customers, project length, …)</li><li>industry, company size, money raised, office’s locations, …</li></ul><p>Got more questions for our speakers? Don’t hesitate to tweet them:</p><ul><li><a href="https://twitter.com/ajj1808"><strong>Anne</strong></a></li><li><a href="https://twitter.com/dcoates"><strong>Dustin</strong></a></li><li><a href="https://twitter.com/JonathanCostet"><strong>Jonathan</strong></a></li></ul><p>Many thanks to <strong>Deezer</strong> for hosting us and offering food &amp; drink!</p><p><strong>Big thank you to all of those came out too!</strong></p><p>Be sure to <a href="https://twitter.com/_productstories">follow us on Twitter</a>, to <a href="https://www.meetup.com/fr-FR/_ProductStories">join our community</a> or above all to join us on the 22nd at <a href="https://medium.com/u/5751a7af6c3b">Zenly</a> 👇😉</p><p><a href="https://www.meetup.com/fr-FR/_ProductStories/events/260882513/">Product Stories #8: Product Branding</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78ce8dcd9b98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/product-marketing-learnings-and-stories-78ce8dcd9b98">Product Marketing learnings and stories</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The roles and missions of Product Designers from startup to scale]]></title>
            <link>https://medium.com/productstories/the-roles-and-missions-of-product-designers-from-startup-to-scale-3f8424ce3582?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f8424ce3582</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Product Stories]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 09:14:53 GMT</pubDate>
            <atom:updated>2019-01-24T17:36:00.294Z</atom:updated>
            <content:encoded><![CDATA[<h3>Learnings on the Product Designer roles and missions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlDFrHKdSZHNu9RgHeYSZQ.jpeg" /></figure><p><em>Here are the key takeaways from our fourth </em><a href="https://www.meetup.com/_ProductStories/"><em>Product Stories meetup</em></a><em> about the roles and missions of a Product Designer. You can watch the full video or read through the main takeaways, or both!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4L8YgXoSVrU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4L8YgXoSVrU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4L8YgXoSVrU%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/691df8874c9e8469ee739cdd7a32eb70/href">https://medium.com/media/691df8874c9e8469ee739cdd7a32eb70/href</a></iframe><p>After an enlightening chat with <a href="https://medium.com/u/5c72f77b2db9">Dan Cederholm</a>, co-founder at <a href="https://medium.com/u/b2c7a6c2542b">Dribbble</a> (takeaways below), we were thrilled to close 2018 with another meet up about Product Design, hosted at <a href="https://medium.com/u/5751a7af6c3b">Zenly</a>.</p><p>We happily welcomed <a href="https://medium.com/u/c7ab16c83716">Laure Boutmy</a>, Designer (<a href="https://medium.com/u/8dca4bfd0b16">Side</a>), <a href="https://medium.com/u/b0370c6bb39b">Gokce Taskan</a>, Design Director (<a href="https://medium.com/u/a756dfda6073">dailymotion</a>), and <a href="https://medium.com/u/fb80ccfb2108">Benjamin Soukiassian</a>, Product Manager (<a href="https://dreem.com/fr">Dreem</a>).</p><p>They took the stage to share their experiences and thoughts on the role and missions of the Product Designer from day one, her/his relationship with other teammates and the design team’s evolution during company growth.</p><p><a href="https://medium.com/productstories/fireside-chat-with-dan-cederholm-dribbbles-co-founder-ca8fc6816f80">Fireside chat with Dan Cederholm, Dribbble’s co-founder</a></p><p>Here are some of the juiciest takeaways:<br><em>Of course, none of these are cold, hard, facts. Just several viewpoints:</em></p><h4><strong>What’s really behind the title Product Designer?</strong></h4><p>From Communication designer to User Interface, Web, Interaction, Service, Digital Product or even Product Designer, the “title” is ever evolving.</p><p>As <a href="https://medium.com/u/b0370c6bb39b">Gokce</a> says, “Product Designer isn’t necessarily the correct one, it’s the <em>current</em> one. It’s the best title to describe what we’re doing at the moment.”</p><p>Product design is associated with the global product experience and the main role of a Product designer to protect it. Both emotional and functional sides. But who knows, it might change before we know it!</p><h4><strong>When to hire a Product Designer?</strong></h4><p>Hiring at the right time is crucial. The sooner is definitely the better, but scaling with the product is also as important. A great example is <a href="https://medium.com/u/8e37c023687a">Joe Gebbia</a>, Airbnb co-founder, who’s a designer.</p><h4><strong>Is product design externalization a good or bad idea?</strong></h4><p>Do it if you know exactly what problem you want to solve and how. It’ll help you brief the freelancer or the agency and align yourselves on expectations. If not, it can be tricky, and risky, to externalize product design.</p><p>Product design goes through iterations, with several teams (i.e. Product, Marketing, Support…) and it’s almost impossible to do that efficiently with external to your team’s daily interactions. Moreover, feedback cycles tend to be too long with agencies, costing you to lose iteration momentum and reactivity.</p><blockquote><em>“Companies should manage product design internally because it’s the central part of the project you’re dealing with on a daily basis. No freelancers or agencies can be as qualified as your team is.” </em><a href="https://medium.com/u/aa314688eabe"><em>Luc Chaissac</em></a><em>, </em><a href="https://medium.com/u/97a0fadcc2d6"><em>Muxu.Muxu</em></a></blockquote><h4>The first hiring…</h4><p>… needs to be an experienced designer who’s going to guide the (co)founder(s) and the team. She/He needs to have a wide-ranging skill set, be able to get the global product picture and evolve with the team and the product.</p><p>The most important are soft skills. Is their behavior (can they collaborate with different teams?), their attitude (can they criticize their own work?), their approach (e.g. how are they analyzing the problem to be solved), not necessarily the experience nor the skills.</p><h4><strong>Hiring process best practices</strong></h4><p>Define a problem you want the designer to solve and prepare lots of questions to ask when you get their solution. It’s the best way to understand how she/he came up with this solution (e.g. conscious thoughts, process…) and assess the above soft skills.</p><p>You could also choose to ask a designer to explain a piece of her/his portfolio in a very clear way. As Gokce said:</p><blockquote>Being able to do things — like designing product — is great, but being able to explain them is even more valuable.</blockquote><h4>When to grow the designers’ team?</h4><p>The sooner the better (again)! Designers working in a team can bounce ideas off each other and move forward more quickly.</p><p>It’s also key to strike the right balance between designers and developers. The more developers you hire in a team, the more assets you have to produce, the more product designers you need.</p><h4><strong>Design system, yay or nay?</strong></h4><p>As <a href="https://medium.com/u/fb80ccfb2108">Benjamin</a> said, it’s a huge investment upfront but it definitely worth it. In the long run, it helps your team build faster.</p><p><a href="https://medium.com/u/c7ab16c83716">Laure</a> and <a href="https://medium.com/u/b0370c6bb39b">Gokce</a> agreed but insisted that we always underestimate the time it takes to build and maintain it. In their opinion, a design system isn’t a topic small companies address and it’s only possible if there’s a buy-in from the Engineering team (e.g. AirBnB Design System team features the best developers in the company).</p><h4><strong>Product manager, Product designer, and user trio</strong></h4><p>Product managers and designers must work side by side because both inputs help to define and prioritize the right problems.</p><p>They also both need to be close to their users to make the right decisions: whether it’s through user testing and research or data. Their role is really to ensure everyone in the company understands the end-user and makes the right decisions for them, no matter how broad the persona.</p><h4>How to manage the long and short term product vision and decision-making?</h4><p>It’s helpful and important to get your team out of their daily routine and iterations to focus on the next big goals and product challenges.</p><ul><li>At <a href="https://dreem.com/">Dreem</a>, the product team goes on retreats twice a year to lay the foundations of where they are and where they’re headed.</li><li>At <a href="https://www.dailymotion.com/">Dailymotion</a>, they often organize workshops to focus on a big feature or product decision with all relevant stakeholders (designers, developers, etc).</li></ul><h4><strong>Why does design look the same in every company nowadays?</strong></h4><p>Reproducing the core logic of a successfully designed product is useful because they become patterns that users recognize and understand. Gokce put it best:</p><blockquote>“We need copies of products. Not in the sense of copying features but in the sense of copying visuals. You don’t need to always re-invent the wheel, instead, you should focus on creating value within your product, not with the details of the typography”</blockquote><p><a href="https://uxdesign.cc/ever-wonder-why-the-most-popular-apps-are-starting-to-look-the-same-it-might-be-a-good-thing-e54aadd50fd5">Ever wonder why the most popular apps are starting to look the same? It might be a good thing</a></p><h4>What are the relevant KPIs and OKRs to track?</h4><p>Design KPIs should be the same as the company’s KPIs. Everyone is working towards the same goals and the most important is not whether product design is reaching their KPIs but whether they’re aligned with the rest of the company’s objectives.</p><p>Got more questions for our speakers? Don’t hesitate to tweet them:</p><ul><li><a href="https://twitter.com/loupyestu"><strong>Laure</strong></a></li><li><a href="https://twitter.com/gokcetaskan"><strong>Gokce</strong></a></li><li><a href="https://twitter.com/soukiassianb"><strong>Benjamin</strong></a></li></ul><p>Many thanks to <a href="https://twitter.com/zenlyapp"><strong>Zenly</strong></a><strong> </strong>for hosting us a second time in their dope offices and offering food &amp; drink (and goodies)! 🤩🙌 We also wanted to thank our design partners <a href="https://medium.com/u/97a0fadcc2d6"><strong>Muxu.Muxu</strong></a> for their work on our visual identity. 🤗</p><p><strong>Big thank you to all of those came out too!</strong> Be sure to <a href="https://twitter.com/_productstories">follow us on Twitter</a> and <a href="https://www.meetup.com/fr-FR/_ProductStories">join our community</a> to stay in the loop about the next meet-ups 👋.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f8424ce3582" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/the-roles-and-missions-of-product-designers-from-startup-to-scale-3f8424ce3582">The roles and missions of Product Designers from startup to scale</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fireside chat with Dan Cederholm, Dribbble’s co-founder]]></title>
            <link>https://medium.com/productstories/fireside-chat-with-dan-cederholm-dribbbles-co-founder-ca8fc6816f80?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/ca8fc6816f80</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Product Stories]]></dc:creator>
            <pubDate>Wed, 21 Nov 2018 14:14:28 GMT</pubDate>
            <atom:updated>2018-11-21T20:15:32.741Z</atom:updated>
            <content:encoded><![CDATA[<p>For the third <a href="https://meetup.com/_ProductStories/"><strong>Product Stories</strong></a> event, we were proud and humbled to be able to host a last-minute fireside chat at <a href="https://medium.com/u/5751a7af6c3b">Zenly</a> new office in Paris with <a href="https://medium.com/u/5c72f77b2db9"><strong>Dan Cederholm</strong></a>, co-founder at Dribbble.</p><p>Here’s the full recording of the event and some of the most interesting takeaways for those of you who couldn’t make it:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRFNxtZZhfVw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRFNxtZZhfVw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRFNxtZZhfVw%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/1eee5370f1e0650b04580176277e285f/href">https://medium.com/media/1eee5370f1e0650b04580176277e285f/href</a></iframe><h3>A brief history of a long and incredible career</h3><p>As a young man when the web was really just starting, <a href="https://medium.com/u/5c72f77b2db9">Dan</a> was more into music, playing drums before switching to guitar and later banjo. He enrolled in several music programs before dropping out to work at a record label.</p><blockquote>“Pretty quickly I realized I’m not gonna be a rock star and I’m probably not going on tour. I needed to make money.”</blockquote><p>While working at a record label, he managed to work his way up to a desk that had Windows 3.1 and an Internet connexion. That’s when he got bitten by the web and the design. He learned web design from the ground up, mostly from what other designers’ blogs.</p><blockquote>“I fell like I was in the right place at the right time where there was a great tight-knit small community of people that would blog about how they built websites with standards and CSS.”</blockquote><p><a href="https://medium.com/u/5c72f77b2db9">Dan</a> immersed himself in the designers’ community, sharing his own thoughts and learnings. Documenting how he worked helped him to get noticed and opening doors along the way.</p><p>One thing led to another: from blogging, to speaking at conferences to freelancing for top companies (ESPN, MTV, Microsoft, and Google, to name a few). He even told us a funny anecdote about being asked to design the first version of what was going to become Twitter! 😄</p><blockquote>“You don’t have to be an expert to share something on a particular topic even if you’re learning it yourself. I think it’s actually a great time to sort of share your journey of how you’re learning.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLf5vltGqxx6_PJnCdd7Wg.png" /></figure><h3>Dribbble inception, journey, and future 🏀</h3><p><a href="https://medium.com/u/5c72f77b2db9">Dan</a> launched <a href="https://medium.com/u/b2c7a6c2542b">Dribbble</a> with his neighbor and talented Rails developer <a href="https://medium.com/u/ec243a565dab">Rich Thornett</a> on July 9th, 2009. They actually met each other through their kids and started sharing an office a couple of days a week.</p><blockquote>“I wanted to see designers were working on. I wish I could look over the shoulder of people I admired and people I only see at conferences”</blockquote><p>The concept behind Dribbble was really about “what are you working on?” and sharing sneak peeks of design content between designers.</p><p>Dan and Rich invited around a hundred designers they admired by sending them a t-shirt along with a handwritten code to join the beta. Most of them immediately joined, constituting the first members of the Dribbble community.</p><p>Dribbble wasn’t Dan or Rich’s full-time job. With their freelance work, family, friends and respective lives, they set-up an invitation-only system to control Dribbble’s growth. This system also ensured the platform’s quality with little effort on their part.</p><blockquote>“The nice byproduct of that [invitation-only signup] is also that, because of the scarcity of the invites, people thought hard about who to invite. That helped the quality of the site and community.”</blockquote><p>The community thrived quickly taking initiatives of its own. For example, organizing non-official Dribbble meetups, raising the brand’s worldwide awareness. The Dribbble team extends some help to these events by helping with logistics, communication, and merch.</p><p>Just two years ago, the team was made up of eight people. Today, nearly 50 people work remotely for Dribbble, organized into business segments and product squads.</p><p><a href="https://medium.com/productstories/are-squads-the-ideal-product-organization-ef0bfcd272b5">Are squads the ideal product organization?</a></p><h4>Dribbble’s next challenges</h4><ul><li>Allow new media sharing on the platform such as video</li><li>Develop the job platform, improving employer and freelancer connections</li><li>Create more content around the community’s designers (e.g. interviews)</li><li>Perhaps the biggest one: scale the community, without destroying its essence</li></ul><h3>Food for thought on Product Design</h3><p><strong>“The more writing you can do, the better!”<br></strong>Writing, documenting, and sharing your process and work is <a href="https://medium.com/u/5c72f77b2db9">Dan</a>’s top advice to all designers. Don’t assume that your work speaks for itself.</p><p><strong>“The more knowledge you have, the better!”<br></strong>Today, it’s advantageous to know how to code but in the future, Dan feels that it can totally change with more abstraction of code within the tech industry.</p><blockquote>“It should be easier to create the things that we have to make on the web.”</blockquote><p><strong>“I wouldn’t know the first thing about a good VR interface”<br></strong>New technologies (AR, VR, voice control technologies, etc.) are bringing new skillsets and jobs in Product Design. There will be some overlap but we’ll likely see a radical transformation in designers’ skills and missions. According to Dan, a new design world will emerge from these innovations.</p><p><strong>“Not everything has to solve a problem”<br></strong>Sometimes it’s just fun to make things. It can help you learn, help you grow, without solving any particular problem and that’s ok!</p><p>If you’ve got more questions for <a href="https://medium.com/u/5c72f77b2db9">Dan</a>, don’t hesitate to tweet him <strong>@</strong><a href="https://twitter.com/simplebits"><strong>Simplebits</strong></a> &amp; follow his projects (like <a href="https://twitter.com/advencherco">Advencherco</a>) on <a href="http://simplebits.com/"><strong>his blog Simplebits</strong></a>.</p><p>Many thanks to <a href="https://twitter.com/dotCSS"><strong>dotCSS</strong></a> for putting us in touch with Dan 🙏 and a huge one to <a href="https://twitter.com/zenlyapp"><strong>Zenly</strong></a> too for hosting us in their incredible offices and offering food &amp; drink (and goodies)! You guys rock 🤩🙌</p><p>We also wanted to thank our design partners <a href="https://medium.com/u/97a0fadcc2d6"><strong>Muxu.Muxu</strong></a> for their work on our visual identity and the <a href="https://twitter.com/wearemuxu/status/1060607799393161221">meetup’s live tweeting</a>.</p><p><strong>Big thank you to everyone who came out too!</strong> Be sure to <a href="https://twitter.com/_productstories">follow us on Twitter</a> and <a href="https://www.meetup.com/fr-FR/_ProductStories">join our community</a> to stay in the loop about the next meet-ups 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca8fc6816f80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/fireside-chat-with-dan-cederholm-dribbbles-co-founder-ca8fc6816f80">Fireside chat with Dan Cederholm, Dribbble’s co-founder</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Growth learnings and stories]]></title>
            <link>https://medium.com/productstories/product-growth-learnings-and-stories-408031b8d5b8?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/408031b8d5b8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Product Stories]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 15:22:01 GMT</pubDate>
            <atom:updated>2018-11-06T09:58:49.647Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product Growth: some learnings and stories</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLWXqmC4M3SEWuKqLZ-iiA.jpeg" /></figure><p>The second <a href="https://meetup.com/_ProductStories/">Product Stories</a> event was all about Product Growth: from building a Growth team to analyzing experiments. We were lucky to have <a href="https://twitter.com/Maxberthelot">Maxime Berthelot</a> up on stage with <a href="https://twitter.com/ChristophePas">Christophe Pasquier</a> to discuss his experience leading the Product Growth team at <a href="https://buffer.com/">Buffer</a>.</p><p>Here’s the full recording of the event and some of the most interesting takeaways for those of you who couldn’t make it:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsvY2zQQQeP4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsvY2zQQQeP4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsvY2zQQQeP4%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/2b65bff3c2f673056291c666d17740f4/href">https://medium.com/media/2b65bff3c2f673056291c666d17740f4/href</a></iframe><h3>#1 — Growth is all about experiments, and 9 out of 10 times, they’ll fail</h3><p>Maxime warns about Product Growth: “You have to be ready to set yourself up for lots of failures for some big successes.” You can’t predict what’s going to make the needle move, so you need to be constantly experimenting.</p><p>A good example of this was when Maxime’s team changed an in-app CTA button from “Upgrade to Awesome” to “Upgrade for more features”. Their hypothesis was that more straightforward copy would lead to more conversions. It was a small impact but it bumped business conversions up 3%. Basically, you never know when the smallest things will have the most impact, and vice versa. The only solution is to keep experimenting!</p><h3>#2 — Follow one specific metric</h3><p>You’ll often hear Maxime say “Growth = process”. And a huge part of that process is to choose one, unique, metric to impact. Then, you brainstorm on all the different ways you can move that metric. Then, you score to prioritize. Then, you experiment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*s86xATkCrRlWvOsyHaQUNw.png" /><figcaption>Buffer’s Product Growth team’s experiment scoring framework.</figcaption></figure><h3>#3 — Get everyone in the company to pitch growth ideas</h3><p>At Buffer, growth is actually a company-wide effort: everyone can pitch growth ideas to the Product Growth team via a Trello board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/0*pqaeiCBaqBiDjbPY.png" /><figcaption>The Trello board to pitch growth experiments at Buffer.</figcaption></figure><h3>#4 — Intuition first, data second</h3><p>“Intuition drives everything in growth.” The experiments you come up with and the way you score them is driven by the Product Growth team’s intuition. Then, you use the data to validate it, or not.</p><p>It’s a virtuous cycle: the more experiments you run, the better you’ll get at scoring them and analyzing their success. As Maxime said: “Running many experiments will build your team’s gut feeling.”</p><h3>#5 — The quality of what you deliver matters</h3><p>Product Growth ≠ Growth Hacking. When he started at Buffer, Maxime was in the mindset that experimenting means shipping fast, even if that means shipping a less than perfect feature.</p><p>He quickly learned that the quality of what you’re testing has a direct impact on its results. His team had developed a tracker bar at the on boarding to increase user activation. The UX and UI were poor and the tracker bar showed no result. Buffer’s CEO gently reminded him that product quality was one of Buffer’s main success drivers, encouraging him to revamp the tracker bar. Turns out the more beautiful, more interactive version of the bar made all the difference, resulting in 20% increase in activation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*jAPmLGLVFi02tNeJKqa93Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*wzGUHW5NXehse5b0BGWrEw.png" /><figcaption>A before-after view of the tracker bar. On the left, the first tracker bar: not interactive and barely designed. On the right, totally revamped: interactive and well-designed!</figcaption></figure><h3>#6 — Tooling musts</h3><ul><li><a href="https://looker.com/">Looker</a> for monitoring analytics: they build dashboard in Looker for each experiment</li><li><a href="http://hotjar.com/">Hotjar</a> &amp; <a href="http://fullstory.com/">Fullstory</a> to analyze the way users interact with experiments</li></ul><h3>Learn more about Product Growth:</h3><ul><li><a href="https://brianbalfour.com/">Brian Balfour</a></li><li><a href="https://www.reforge.com/brief/building-a-growth-team-according-to-y-combinator#xGfSdciDHdAOBdNq9jPAHg">Building a growth team, according to Y Combinator</a></li><li><a href="https://medium.com/airbnb-engineering/experiments-at-airbnb-e2db3abf39e7">How Airbnb runs experiments</a></li><li><a href="https://medium.com/How%20Not%20To%20Run%20an%20A/B%20Test%20%E2%80%93%20Evan%20Miller">How Not To Run an A/B Test — Evan Miller</a></li><li><a href="https://www.slideshare.net/WrangleConf/ab-testing-at-pinterest-building-a-culture-of-experimentation">Pinterest VP growth presentations with dos and don’ts</a></li></ul><p>Big thank you to everyone who came out! Be sure to <a href="https://twitter.com/_productstories">follow us on Twitter</a> and <a href="https://www.meetup.com/fr-FR/_ProductStories">join our community</a> to stay in the loop about the next meet ups 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408031b8d5b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/product-growth-learnings-and-stories-408031b8d5b8">Product Growth learnings and stories</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are squads the ideal product organization?]]></title>
            <link>https://medium.com/productstories/are-squads-the-ideal-product-organization-ef0bfcd272b5?source=rss----23f44cb7cb18---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef0bfcd272b5</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Product Stories]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 13:21:42 GMT</pubDate>
            <atom:updated>2018-10-22T09:27:13.345Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7dpPNytnOuyFSPZdqnImbg.jpeg" /></figure><p><em>Here are the key takeaways from our first </em><a href="https://www.meetup.com/_ProductStories/"><em>Product Stories meet up</em></a><em> about working in Product Squads from the Drivy, Blablacar and Mention teams. You can watch the full video or look read through the main takeaways, or both!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fqek6jpY8Vsk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dqek6jpY8Vsk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fqek6jpY8Vsk%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/1a1065edca60ef26af0d7d428cc94b81/href">https://medium.com/media/1a1065edca60ef26af0d7d428cc94b81/href</a></iframe><p>We’re excited to have hosted the very first <a href="https://www.meetup.com/_ProductStories">Product Stories meet up</a> at the <a href="https://medium.com/@dashlane">Dashlane offices</a>. <a href="https://twitter.com/nmondollot">Nicolas (Co-founder and CPO of Drivy)</a>, <a href="https://twitter.com/BRetourne">Benjamin (Lead PM at Blablacar)</a> and <a href="https://twitter.com/cyrilcodron">Cyril (Head of Product at Mention)</a> took the stage to share their experiences working in squads.</p><p>If you’re unfamiliar with what a Product squad is, we can only recommend <a href="https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/">Spotify’s handbook</a> to get started.</p><p>Here are some of the juiciest takeaways:<br><em>Of course, none of these are cold, hard, facts. Just several viewpoints:</em></p><h3>#1 — Why work in squads?</h3><ul><li>The growth of your engineering team and hiring more Product Managers can lead to organization difficulties and, ironically, less productivity. For Blablacar and Drivy, squads were the solution to their scaling product team.</li><li>For Mention, the Kanban methodology isolated PMs, Designers and Engineers. They’re starting to work in squads to get these teams to work as one team, not three different ones.</li></ul><h3>#2 — What’s a squad anyway?</h3><h4>Who’s in a squad?</h4><ul><li>The most general interpretation is that a squad is a self-sufficient and autonomous group of engineers, designers and PMs within a company.</li><li>But for Drivy it’s not so limited: there’s always a data analyst and even sometimes someone from Marketing or other Business Development departments depending on the needs.</li></ul><h4>What do squads work on?</h4><ul><li>For both Blablacar and Drivy, squads are mission-based and reviewed quarterly.</li><li>Big point of reference: <a href="https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/">Spotify’s handbook</a> is a reference for lots of startups that start to venture in the squad organization.</li></ul><h3>#3 — The important traits of a squad</h3><h4>The two keywords that pop up when it comes to traits squad should have:</h4><ul><li>Autonomy: the squad should be self-sufficient and have all the resources it needs</li><li>Ownership: the squad defines its goals and owns the responsibility to deliver and follow-up on those</li></ul><h3>#4 — Benefits of working in squads</h3><ul><li>For Drivy and Blablacar working in squads offer higher velocity of delivery in product and all in good quality</li><li>Responsibilizing everyone — not just PMs — around product vision and end users. Specifically, engineers aren’t just asked to execute, but to bring ideas to the table.</li><li>Drivy’s anecdote: the engineers came up with the solution to improve the payment feature in the app, leading to a much better user experience. They directly impacted the product’s direction.</li><li>Blablacar’s anecdote: when the website was being revamped, a team of engineers came up with a slideshow of ideas for the Marketing team, according to what they believed was important to put forward for the end-users.</li></ul><h3>#5 — Delivering in squads: keeping everyone aligned</h3><ul><li>There are many ways to structure the overall logistics of working in squads, the most crucial being reporting back to the rest of the company.</li><li>At Drivy, they hold demo days every Friday, where all squads gather and show off their respective progress.</li><li>At Blablacar, they send out a bi-weekly email to the entire company about product updates and upcoming features.</li><li>At Mention, they have a dedicated Slack channel to announce new features every two weeks to the rest of the company</li></ul><h3>#6 — The exceptions to the rule</h3><ul><li>Like any framework, the squad framework doesn’t adapt to every singe situation that arises in companies.</li><li>Nicolas put it best: “The squad framework works for 80% of our work and it’s light enough to be adaptable to the 20% of non-squad-adapted exceptions.”</li></ul><h4>Dealing with unexpected quick fixes and improvements:</h4><ul><li>Drivy has two Slack channels: #askasquad for people outside of squads to throw in requests and #crossasquad for requests that need to be dealt with but no squad is willing to take responsibility for.</li><li>Blablacar is extremely radical about fixes and improvements: is it directly related to our goals? Unless the answer is yes, they skip them.</li></ul><p>Big thank you to everyone who came out! Be sure to <a href="https://twitter.com/_productstories">follow us on Twitter</a> and <a href="https://www.meetup.com/fr-FR/_ProductStories">join our community</a> to stay in the loop about the next meet ups 👋</p><p>Curious to know more? Reach out to <a href="https://twitter.com/nmondollot">Nicolas</a>, <a href="https://twitter.com/BRetourne">Benjamin</a> et <a href="https://twitter.com/cyrilcodron">Cyril</a> who’ll be for sure happy to pursue the discussion online!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef0bfcd272b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/productstories/are-squads-the-ideal-product-organization-ef0bfcd272b5">Are squads the ideal product organization?</a> was originally published in <a href="https://medium.com/productstories">Product Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>