<?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 Jérémy Bléhaut on Medium]]></title>
        <description><![CDATA[Stories by Jérémy Bléhaut on Medium]]></description>
        <link>https://medium.com/@jeremy.blehaut?source=rss-75a59b8b9f2a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KsTvFG1wBT1byH85AufKKA.png</url>
            <title>Stories by Jérémy Bléhaut on Medium</title>
            <link>https://medium.com/@jeremy.blehaut?source=rss-75a59b8b9f2a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:15:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeremy.blehaut/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[Main duty of a Product Strategist]]></title>
            <link>https://medium.com/@jeremy.blehaut/main-duty-of-a-product-strategist-127b7a51ac9b?source=rss-75a59b8b9f2a------2</link>
            <guid isPermaLink="false">https://medium.com/p/127b7a51ac9b</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Jérémy Bléhaut]]></dc:creator>
            <pubDate>Thu, 01 Feb 2018 16:51:00 GMT</pubDate>
            <atom:updated>2018-02-01T16:52:54.514Z</atom:updated>
            <content:encoded><![CDATA[<p>Challenge the <strong>Current Status</strong> and <strong>Kill the status quo . . .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*0oNBgPiU-xF1EfSXPQdDQQ.png" /></figure><p>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><p>Compared to an awesome Product Manager, Product Strategist are not dedicated to a feature/product, we work as consultants for the product team.</p><p>The main difference between a Product Strategist and a Product Manager is that we do not own the production roadmap, we are just here to help create it and choose the right path.</p><h3><strong>Differentiation and Key feature</strong></h3><p>The Product Strategist should always strive for differentiation and “Wow” features. A Product Strategist isn’t a Product Manager in the sense that they have no production duties. We aren’t here to actively build the product alongside developers and designers, we’re here to guide the product from conception to completion and iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*CQQ7kLqhXYUg4FPVqxkMQg.gif" /><figcaption>Source: Giphy, Mister Robot, Netflix</figcaption></figure><p>To do so, the Product Strategist has several techniques and approaches to work on differentiation:</p><p><strong><em>Identify market and customer needs:</em></strong></p><ul><li>Basically a benchmark, always in progress, you should map all movements from the competition</li><li>Know all the new improvements made on innovative products or technologies</li><li>The goal is to try to fill a gap and find a real problem to approach</li></ul><p><strong><em>Create business cases and identify key performance metrics:</em></strong></p><ul><li>It can be seen as your feature business plan.</li><li>Defining many things such as how to recruit users, what will you win from this feature, what are your costs …</li><li>You also need KPI’s to mesure if your functionality is successful or not. It’s a target result different from a problem result.</li><li>Example: My problem is: “My users are not coming back”. My KPI “Returning rate per day”</li><li>The goal is to define what’s the target behind a new feature or a new product</li></ul><p><strong><em>Prototype high level features and feasibility studies for new products / features:</em></strong></p><ul><li>In order to understand if the solution is the right one for the problem, you should detail what’s behind your feature.</li><li>Detail the user journey so that all the stakeholders can understand the problem. Especially developers and designers.</li><li>A feasibility study is basically defining prior to any construction or decision if a feature is possible to produce in an acceptable time frame and cost.</li></ul><p><strong><em>Run customer validation testing research:</em></strong></p><ul><li>As soon as you have something that is understandable by everyone, test and validate your ideas with users.</li><li>You never go to production unless you have validation from the users. Or at least some tangible feedback that the solution can interest someone or the problem itself is interesting enough.</li></ul><h3><strong>Cleaning and Killing</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/155/0*KBSTBiQpYQjWHk8H." /><figcaption>Source Giphy: “Cleaning wisely”</figcaption></figure><p>It’s important to understand your work at both ends of the production line.</p><p>One side is the product at its earliest stage which is to enable new ideas into the product loop. The other side is that point just before the big party where you clean up the results. Cleaning here is focusing the overall product focus to new priorities and objectives. A Product Strategist needs to always be focusing the teams and the stakeholders towards the objectives set in early stages.</p><p><strong><em>Monitor results of implementations:</em></strong></p><ul><li>While you are benchmarking what’s happening on the outside of your company, you’ll also need to do the same on the inside.</li><li>Your focus is on providing a map on where you’ve succeeded and where you’ve failed</li></ul><p><strong><em>Adjust vision or kill products / features if they don’t match customer needs:</em></strong></p><ul><li>Your results are bad? Then move on.</li><li>Switch your focus towards other problems.</li><li>Justify why you kill a feature and why you had this feature in the first place.</li></ul><p><strong><em>Partner with product management and development to prioritize and shape features:</em></strong></p><ul><li>You’re part in the production pipeline is to keep the product managers and developers focused on the company and product objectives.</li><li>Prioritize the problems instead of the solutions.</li></ul><p>To sum up your duty is to set the <strong>Vision</strong> and determine where the product should go.<strong> </strong>Find <strong>Problems</strong> to resolve in order to have a real challenge to achieve. Give a <strong>Target</strong> to your problems, these targets are the actionable conditions to divide a problem (linked to metrics or KPI’s).</p><p>Challenge the <strong>Current Status</strong> and <strong>kill the status quo . . .</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*0oNBgPiU-xF1EfSXPQdDQQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=127b7a51ac9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>