<?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 Vladimir Leonenko on Medium]]></title>
        <description><![CDATA[Stories by Vladimir Leonenko on Medium]]></description>
        <link>https://medium.com/@leonenko?source=rss-99f71e785867------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yOEb-KdxgeqAAzMZBsFzPQ.jpeg</url>
            <title>Stories by Vladimir Leonenko on Medium</title>
            <link>https://medium.com/@leonenko?source=rss-99f71e785867------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:14:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leonenko/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[The value of explanatory models to product teams]]></title>
            <link>https://leonenko.medium.com/the-value-of-explanatory-models-to-product-teams-5cb48289ce52?source=rss-99f71e785867------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cb48289ce52</guid>
            <category><![CDATA[dominative-narrative]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[explanatory-model]]></category>
            <category><![CDATA[neuroscience]]></category>
            <dc:creator><![CDATA[Vladimir Leonenko]]></dc:creator>
            <pubDate>Tue, 16 Aug 2022 18:58:06 GMT</pubDate>
            <atom:updated>2022-08-16T18:58:06.437Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Not only facts and actions are crucial, but how we explain them to ourselves. </strong>There is more than 100 empirical research that proves — our explanatory models (narratives) impact our adoption capabilities with almost the same power as the biologically determined factors.</p><p>Being aware of that human behaviour, we may expect that influence on product development. We use well-known frameworks and practices, and they not only affect the way we do our daily work. They also affect how we explain the results, external feedback and even graphs in the dashboard. <strong>Explanatory models play a fundamental role in how we as a team reintegrate the new knowledge and experience.</strong></p><p><strong>I consider the impact of those dominative narratives on the long-term product team’s outcome badly underestimated</strong>. Especially in challenging situations, where the product stagnates, the product team has been under pressure for a long or even has to deal with detrimental scenarios (which happens in real life).</p><p><strong>Baseline questions:</strong> What can I say about the explanatory model of my team? Can it adequately describe the situation (is it a realistic model)? Is it empowering the team to act (is it an optimistic model)?</p><p><strong>Share your experience:</strong> Have you ever seen the changes in the team behaviour after the dominant narrative changes? How has it specifically affected the team members? Conversely, how have unaccustomed explanatory models in work influenced you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cb48289ce52" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>