<?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 Ram Sevak on Medium]]></title>
        <description><![CDATA[Stories by Ram Sevak on Medium]]></description>
        <link>https://medium.com/@productmgmt?source=rss-df3af3499b59------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1dnRwBex5oEpyZyv2_scsQ.jpeg</url>
            <title>Stories by Ram Sevak on Medium</title>
            <link>https://medium.com/@productmgmt?source=rss-df3af3499b59------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:31:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productmgmt/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[More with less: Implementing data-driven decision-making at Tamara]]></title>
            <link>https://medium.com/tamara-tech-product/more-with-less-implementing-data-driven-decision-making-at-tamara-e08391f5b22c?source=rss-df3af3499b59------2</link>
            <guid isPermaLink="false">https://medium.com/p/e08391f5b22c</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agility]]></category>
            <dc:creator><![CDATA[Ram Sevak]]></dc:creator>
            <pubDate>Tue, 24 Oct 2023 15:52:13 GMT</pubDate>
            <atom:updated>2023-10-25T10:59:29.776Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Data-driven decision making at Tamara" src="https://cdn-images-1.medium.com/max/1024/1*VCvBditxobjShTJrW36KNw.png" /></figure><p>Tamara’s product culture has been built on a few core pillars namely:</p><ul><li>Customer focus (solving a real customer pain)</li><li>Perseverance i.e. relentless pursuit of making things work (“finding a way” is one of our core values)</li><li>Data orientation</li></ul><p>In this article, I will focus on how we work with data and what makes implementing data-inspired decision-making uniquely challenging for innovative start-ups like ours. This article is NOT exactly about how you use data in the software development life cycle, but more about how you supplement the lack of data and STILL remain true to the tenets of being data-driven in a fast-paced innovative setup!</p><p>Product managers at Tamara use data extensively during all stages of the product life cycle. What makes utilizing data for an innovative and disruptive product like ours interesting is that there is quite often not significant enough data to derive insights from and there is sometimes zero data to start with.</p><p>So how do we break this apparent deadlock?</p><h3>Resourcefulness and scrappiness: Working with what you have!</h3><p>This is the fundamental guiding principle we apply at Tamara. While one can derive additional insights and probably clearer actionable inputs from more data, sometimes you just don’t have it or, I would wager, you don’t need it!</p><p>So it’s better to look at what other data points would approximate insights you are looking for and then work towards gathering those data points. In general, please remember if you don’t have access to all the data points and you likely need to move forward, it’s a good sign! Otherwise, your product is probably too late to be released to the market.</p><p>Here are 6 specific pieces of advice to operate effectively when you don’t have all the data you need:</p><p><strong>1.Getting comfortable in operating with insufficient data.</strong> The first starting point is acknowledging that if you are innovating or solving a problem without much precedence, data availability will be a constraint.</p><p><strong>2.Start with industry-specific data points.</strong> Let’s say you are building a content product wherein you want to gauge what kind of content your customers like. For such scenarios, looking at Google Trends, Facebook’s Audience Manager, Google Keyword Planner, and site analytics from Google Webmaster are excellent sources to approximate customer demand. However, be aware to filter out data for your target audience based on geography, demographics, and other behavioral nuances.</p><p><strong>3.Pivot to competitor / industry benchmarking</strong>. Products at Tamara are built to exceed customer expectations–which in most cases are defined by what they have experienced in other contexts and markets. Therefore, product managers at Tamara focus on understanding how the industry benchmarks around specific customer solutions look like and then work to create a WOW experience for our customers!</p><p><strong>4.Look at the secondary data sources internally.</strong> Have an objective assessment of what data points will correlate to your use case and try to find the closest proxy towards that objective. When we were launching the Buyer Protection Program at Tamara, the team looked at data around customer tickets to prioritize roadmap items directionally. Since previously the program didn’t exist in Tamara, it was not possible to use quantitative data for prioritization.</p><p>Internal site search is another excellent source to understand what customers have been looking for. As an example, you can use this data point to estimate how customers view you and the competition. You would be surprised how often people would search for your competition on your own platforms!</p><p>If you are classifying customer intent and interest based on query and volume analysis, be mindful of the following biases:<br>a. Some customers may struggle to articulate their exact needs.</p><p>b. For innovative products, a low volume doesn’t necessarily indicate a lack of demand!</p><p><strong>5.Evaluate alternate types of data.</strong> Sometimes when you don’t have access to quantitative data, it is perfectly okay to gather qualitative data and understand the customer perspective around problem space. Now the question arises, how many customers do you need to talk to? The exact answer of course depends on your customer profile and the problem but I have seen customer insights tend to converge around 15–20 in-depth customer interviews. If you have the prototypes ready, 6–8 customer interviews should also be okay.</p><p><strong>6.Operating with a long-term mindset by investing in gathering data is key.</strong> One should be willing to invest in generating primary data insights from the customers. If that requires investing in specific products, tools, or technology, it should be okay. There are many plug-and-play tools one can integrate to understand customer journeys, create heat maps for critical pages, understand the most unhappy customer scenarios by analyzing the last event behavior before drop-off events, and even explicitly ask customers about their experience.</p><p>For some of the tools, be extra vigilant that you are absolutely compliant with Play/Google Store’s Privacy Policies and of course with country-specific regulations you operate under. When in doubt, please disclose to your users <em>how</em> you are going to use specific data and any extra permissions you may need from them! In such scenarios it’s a good practice to disclose proactively how you would NOT use that feature itself</p><p>Let us know what other methods, tools, and tactics you have found useful, we’d be glad to hear back from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e08391f5b22c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamara-tech-product/more-with-less-implementing-data-driven-decision-making-at-tamara-e08391f5b22c">More with less: Implementing data-driven decision-making at Tamara</a> was originally published in <a href="https://medium.com/tamara-tech-product">Tamara Tech &amp; Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review (3): Gamification — Using Game Elements in Serious Contexts…]]></title>
            <link>https://medium.com/@productmgmt/book-review-3-gamification-using-game-elements-in-serious-contexts-d65f716af431?source=rss-df3af3499b59------2</link>
            <guid isPermaLink="false">https://medium.com/p/d65f716af431</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[requirements-engineering]]></category>
            <category><![CDATA[gamification]]></category>
            <dc:creator><![CDATA[Ram Sevak]]></dc:creator>
            <pubDate>Wed, 04 Apr 2018 19:48:46 GMT</pubDate>
            <atom:updated>2018-04-04T19:48:46.748Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been reading up on how to gamify core product experiences and the current state of art. Came across this book <strong><em>Gamification — Using Game Elements in Serious Contexts, </em></strong>it’s published by Springer whose technical books I tend to like apart from the venerable O’Reilly’s. This book is structured like a compendium of research articles, prose has the same “academic” overtones and each chapter can be read independent of one another. Some familiarity with standard terms in gamification parlance would definitely help in quickly skim through the short but dense book consisting of 11 chapters</p><p><strong>Chapter 1</strong></p><p>Some points and key definitions are belabored again and again throughout the book, mostly since each chapter is contributed by different researchers. For example, <strong>definition of gamification i.e. using game mechanics in a non-gaming / non-serious / business context — so called funware</strong>. Also defined at many places are external and intrinsic motivations and how gamification can help generate the latter</p><p>Equally important is how <strong>affordances for gameful experience may enhance user experience AND outcome. </strong>The book also differentiates between a play and game — the latter being rule based and goal oriented form of playing</p><p>This 2x2 explains the use of play and games and their integration into products (cited from the book)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/0*To_YL6u2O_uKxOD1." /><figcaption>Courtesy: “<strong><em>Gamification — Using Game Elements in Serious Contexts</em></strong>”</figcaption></figure><p>This chapter then introduces well-cited MDA framework i.e. mechanics, dynamics and aesthetics of gamification design. Then various types of game mechanics are enumerated namely points, leaderboards, levels and achievement systems or meta tasks. Game dynamics is defined as the run-time behavior of game mechanics acting on player’s inputs and each other’s outputs while aesthetics describe the desirable emotional responses in a player. <strong>In the gamification context, aesthetics should represent goal of the gamified system. </strong>The chapter then lists the player types as killers (acting on other players), achievers (acting on the world), socializers (interacting with other players) and explorers (interacting with the world)</p><p>The chapter ends with describing different types of achievements per <strong>achievement goal theory</strong>. Instructors are used to guide users throughout the process, quests are unlocked when users accomplish significant tasks, content discovery achievements encourage users to explore the applications, grinder achievements are unlocked when a task is repeated given number of times, Herculean tasks are like bar raisers — relatively difficult and hard to perform tasks. Trophies are designed to mutually exclude other users from winning them and are therefore rare. Loyalty achievements reward the most loyal users</p><p>The chapter sounds familiar — more so when many of the current product engagement hooks built by the likes of Flipkart, Amazon, Swiggy, live quizzing products (MMOs) are using these achievements types as part of core gamification design. Sample these: random often silly sounding games in ecommerce apps’ home screens, product hunts, game design of referral programs, loyalty programs which can only be unlocked at the end of the month, extra lives for watching game till the end….</p><p><strong>Chapter 2</strong></p><p>This chapter can be termed as core of the book with important inferences as to how user behavior can be influenced by gamification. Motivation (desire to perform an action) is an important factor since it drives human behavior and is used to start an activity. <strong>Extrinsic motivation (doing things solely for their outcome) doesn’t create sustainable gamification effect.</strong> Use of cultural influences is considered in shaping people’s preferences. Four cultural categories in communication are time (2 mins delay is not the same everywhere!), space (personal or shared), context (explicit or direct) and information flow (e.g. message speed). <strong>Culture and design can be combined to create serious games e.g. cultural appropriation can be employed to support game’s mechanics, storylines and interface by designers.<em> </em></strong><em>Amazon’s Great India shopping festival and the use of elephants in logo!</em></p><p>From this perspective, semiotics, symbolic interactionism and metaphors are important extensions.</p><p>The authors then proceed to explain <strong>Fogg Behavior Model </strong>which shows that human<strong> </strong>behavior is an outcome of three elements: motivation, ability and trigger <em>happening concurrently</em><strong><em>. </em>Now famous Nudge Theory covers the last two elements: ability and trigger wherein designer simplifies the environment and the context that lead to a certain action<em> </em></strong>while tiny habits method breaks down the desired method into easy-to-adopt small habits</p><p><strong>Chapter 3</strong></p><p>This chapter touches on gamification analytics — tools that help to monitor the success of gamification projects, to understand user behavior and to adopt gamification designs</p><p>One can sequence activities in gamification analytics as business modelling and requirements, design workflow, implementation, monitoring and adaptation. No surprises there for a product manager!</p><p>Some of the key metrics while analyzing gamification:</p><p><strong>Gamification feedback rate:</strong> while gamification feedback is any state change in the game which the user perceives as success. <strong>Feedback rate describes total amount of feedback per time user spent in the gamified application.</strong> Too low feedback rate could imply — scope of gamification is too narrow vis-a-vis problem space or game is too hard!</p><p><strong>Point distributions </strong>over users can help detect flaws in the balance of point amounts for gamified actions</p><p><strong>Achievable gamification elements</strong>: helps to see overall progression of users in the game. Also useful for making adaptation in gamification design — too easy or too hard game!</p><p>User distribution on gamification element state: this should be self explanatory</p><p><strong>Temporal statistics </strong>— how long users need for the completion of particular gamification elements</p><p>User characteristics related cohorts</p><p>The chapter ends with evaluating certain tools for gamification analytics e.g. Upsight, HoneyTracks, GAMEhud, GameAnalytics etc. <strong>Criteria or product capabilities used for ranking the tools are: ability to monitor app KPIs, gamification elements stats, gamification design adaptation, user group of interest and simulation</strong></p><p><strong>Chapter 4</strong></p><p>This chapter discusses use of gamification in customer-oriented strategies specifically Open Customer Innovation (OCI). OCI to me seems fancy term for denoting prosumers. More generally, it can be defined as the process for integrating customer feedback into companies’ processes <em>collaboratively</em></p><p>OCI can have different stages basis how much value companies extract from their customers. For example, OCI can just be an idea spotting tool or a tool to identify customer’s interests and preferences like surveys. It can also be used as co-creation concept or coproduction (provide new products <em>on a regular basis</em>). <strong>Design thinking is in fact one variant of OCI wherein customers are integrated in design and innovation process. </strong>Certain risks of an OCI approach could be: non-awareness on part of customers vis-a-vis their responsibilities concerning the final product, retaining customer motivation to cocreate on a regular basis, lack of creativity on part of customers <strong>in the long run</strong></p><p>Gamification can help in leading to mental states like self-efficacy and flow<strong>. Playing can support divergent thinking while learning / unlearning can be initiated by exposing players to new situations</strong>. Customers can also be provided background stories to make customer familiar and acquainted with the company as well as its values and vision thereby mitigating some of the key risks of an OCI approach driven product creation</p><p><strong>Chapter 5</strong></p><p>This chapter focuses on obstacles and challenges in the use of gamification for virtual idea communities (VICs). <strong>VICs are the communities in which distributed groups of individual customers focus on voluntarily sharing and elaborating innovation ideas. </strong>As an aside, open source software has developed along these lines from the beginning. Linux Kernel Mailing List (<a href="https://lkml.org/">https://lkml.org/</a>) is legendary we all know! Firms benefit from VICs since 1. These are less complex than face-to-face workshops, focused group studies or panels 2. Customer base can be broader in VICs</p><p>However having knowledge about customer motivation to participate in VICs is important for firms. Customer may be motivated by 1. Having fun developing ideas 2. Altruism 3. Product innovation and enhancement 4. Capability-signalling motive or self-marketing motive 5. Recognition motive 6. Learning motive 7. Need motive e.g. lobbying or influencing the firm and its products 8. Contacts-to-peers motive</p><p>Some of the game design elements which can be used in VICs are game points (as starting point to drive competitive behavior), social points (for fostering a sense of social belonging and as competitive anchor), redeemable points (autonomy for individual development and differentiation), levels (to increase competitive character of the community and to enable inter-user comparison), leaderboards and high scores (highly competitive game design elements to drive behavior), <strong>virtual identities (to overcome hierarchy levels and silo thinking) </strong>and collecting (to demonstrate social status)</p><p>Some of the challenges behind gamifying VICs are misuse by developers and decision makers, manipulative users and <strong>overjustification effect demonstrated by players in which external incentives harm intrinsic motivation</strong></p><p><strong>Chapter 6</strong></p><p><strong>This chapter focuses on designing social media based on open innovation tool to harness potential of play by applying game mechanics to innovation management. There can be broadly two ways 1. Enriching open innovation tool with game mechanics i.e. gamification 2. Adjusting a multiplayer online game for the purpose of ideation (online ideation game)</strong></p><p>There are two challenges organisations face regarding design of social media based on open innovation tool 1. Motivating individuals to participate in a state of high involvement and flow 2. Inspiring individuals to generate creative output. For this purpose, online ideation games OIGs can be of high gamefulness i.e. high extent to which design of the system appears to be a game</p><p><strong>How to structure game mechanics in the context of innovation management?</strong></p><p>One way is so called <strong>genex framework</strong> . <strong>According to this framework, efficient creativity supporting software tool must encourage four generic behavior: accumulating (learning from previous work), relating (consulting with peers and mentors), creating (exploring and creating possible solutions) and disseminating (spreading elaborated solutions)</strong></p><p><strong>Game points</strong> can serve as trigger for all four behavior while <strong>social points </strong>can trigger “relating”. <strong>Redeemable points</strong> can serve as trigger for creating and relating. Two of the largest idea management systems in the world Hype and Spigit use virtual stores</p><p><strong>Levels</strong> can trigger accumulating and / or creating. When levels are implemented as sections, it indicates possibility of browsing through information and hence accumulation. While when stages are implemented as stages for example by providing ever-increasing challenges they relate to creating. <strong>Leaderboards </strong>can trigger accumulating and relating while <strong>collecting </strong>can be assigned the behavior of accumulating</p><p>On the other hand, OIGs follow the idea of game with a purpose. They have two design elements: mission specificity and duration (not necessarily though)</p><p>In online communities, minimizing the risk of fraud is very important. Few thumb rules to increase fraud-resistance of a gamified system or OIG are</p><ol><li><strong>The larger effort and more time to cheat the system, the lower the probability of fraud.</strong> For example, users can receive game points based on their trustworthiness levels. Trustworthiness can be calculated by rating the rater or by using meta data about user behavior. Similarly social points are only allocated if certain persons rated the idea positively. Downside is it can lessen site’s credibility and usability</li><li>The more transparent the rules are, easier it is for cheaters to find strategies for cheating. That why Google and Amazon’s rankings are a secret!</li><li><strong>The more the true identity of a user is known, the lower the probability of fraud. </strong>Completely anonymous virtual identities may trigger fake identities and spam. However if privacy concerns are to be addressed effectively, real identity characteristics of every community member can be made visible to only administrators. Thankfully, recent <a href="https://www.hindustantimes.com/india-news/instead-of-aadhaar-now-submit-virtual-id-to-protect-your-privacy/story-eIsFwFnCG9oImArFQJiELJ.html">changes in Aadhar</a> point to adopting similar approach when only virtual Aadhar details are to be shared for authentication!</li></ol><p><strong>Chapter 7</strong></p><p>This chapter focuses on gamification in the context of social collaboration. The central argument of authors has been that gamification elements have mostly ignored augmenting intrinsic motivation. Game elements that include monetary oriented goals can be seen as extrinsic stimuli whereas achievements to learn or improve in a certain activity lead to intrinsic motivation. In specific elements like points, badges and dashboards could diminish intrinsic motivation of users since these elements only support extrinsic motivation. <strong>This effect of secondary extrinsic motivation lowering the primary intrinsic motivation is known as overjustification effect</strong></p><p>Authors then review certain market tools in this space e.g. Chatter, IBM connections, SharePoint and JIVE. Assertion is that market for gamification in social collaboration software is dominated by third party plug-ins. Microsoft SharePoint remains an exception</p><p><strong>Chapter 8</strong></p><p>This chapter is pretty interesting, more so product managers. Think about <strong>gamification as a market research method for purchase decision process! </strong>This space has been traditionally dominated by classical qualitative market research methods e.g. focus groups, interviews and diary studies. Few “problems” with these methods are: methods may be outdated providing only hypothetical and unrealistic results. Probands (best consumers) are rarely able to describe their purchase decision retrospectively since it’s mainly an emotional process. Besides sample bias may be dominant and problematic. Additionally studies themselves run the risk of influencing the decision process!</p><p>The universe of games and related research fields can be visualized in this 2x2 (adapted from the book). Horizontal axis denotes the difference between designing a full game and merely employing some game elements in another context</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/0*kI5fzFn45WGdwMam." /><figcaption>Courtesy: “<strong><em>Gamification — Using Game Elements in Serious Contexts</em></strong>”</figcaption></figure><p>Serious games are also games but with another purpose than mere entertainment for example, teaching the player something</p><p><strong>Why games in market research studies?</strong></p><p>Advantage could be that games allow players to immerse themselves deeply into the topic. As result, player gets in a so called flow and give more valid answers. Players are also more attentive and authentic. There could be higher willingness to participate as well</p><p>Authors then describe a hypothetical serious game (a board game) which mimics purchase decision making process by making the users park the car in middle of the board after having reached a <em>predefined number of information fields. One advantage of having smartphone application of this game is insights can be transmitted to researchers in real time. </em>By changing a few design elements, authors claim that it could be adopted to other products or simulate different processes altogether</p><p><strong>Chapter 9</strong></p><p><strong>This chapter should interest all product managers — use of gamification in requirement engineering (RE) and stakeholder management! Essentially gamification in RE establishes feedback loops that reward the “useful” participants. </strong>On the other hand, related trend of crowdsourcing can be employed to maximize the number of participating stakeholders — crowd-centric requirement engineering CCRE. To be unambiguous though, the chapter falls short in suggesting some practicable action points for typical software products</p><p>Two pillars that authors have proposed to increasing stakeholder engagement and participation are: gamification as means to improve motivation and finally quality 2. Crowdsourcing to achieve higher and broader involvement by means of an open call</p><p>The resulting CCRE method has seven phases</p><ol><li>Feasibility analysis (determine applicability of CCRE for the specific situation) including scope of the method. CCRE would be unsuitable for a product with very few clients and products for which PM has clear vision and low openness to crowd. Conversely CCRE would be more suited for products with numerous customers, low vision and high openness</li><li>Context analysis: analyses the context of requirement elicitation by identifying candidate stakeholders to involve in crowdsourcing as well as existing channels used to provide feedback</li><li>Crowdsourcing preparation: before actually involving the crowd, it has to be formed, its characteristics assessed and members prepared for success. CCRE method should provide enough incentives through gamification elements e.g. roles, points, leaderboards, group formation, exploration and endorsement</li><li>Crowd involvement: this is the phase where gamification and crowdsourcing occurs</li><li>Requirement identification: one has to distinguish between minority and mainstream requirements as well the requirement priority based on business value, implementation cost and business risk</li><li>Focus group execution: organized selectively for requirements with higher business priority and shareholder value</li></ol><p><strong>Challenges of applying crowdsourcing for RE</strong></p><p>Diversity may render decision making processes harder to achieve (inconsistent requirements for example). <strong>Collaboration among stakeholders may also lead to dominance of certain opinions and clustering among the crowd providing the requirements</strong></p><p><strong>Challenges of applying crowdsourcing for RE</strong></p><p><strong>Gamification of RE processes has technical and organisational costs. </strong>Stakeholders may be given an option to opt out of gamification which has its own complexities. <strong>Gamification may also negatively influence trustworthiness of elicited requirements as certain users may participate just for the sake of it. </strong>Some stakeholders may also lack intrinsic motivation to participate</p><p><strong>Chapter 10</strong></p><p><strong>This chapter takes example of gamified e-books to discover distinctive rhetorical resources used to enhance reading experience and achieve convergence with original literary world. Convergence i.e. </strong>the capacity to enhance rather than distract from the narrative is considered a key element for assessing an interactive e-book. Three dimensions to examine convergence between gamified e-books and literary world are: enacting the material world, navigating the medium of text (this can be measured by ratio of reading to other actions, implemented as animated or interactive calligraphy or adding digital materiality to draw attention to text or by concatenating text as taps and choices on user screen), empathy / perception / emotion and choice</p><p>Empathy can be developed through perception for example through animation and interactivity, through choice, through emotions</p><p>In specific, multimedia feature of e-books has a small positive effect on young children’s literacy development.</p><p><strong>Chapter 11</strong></p><p>This chapter analyzes gamification of teaching in higher education and I found it a little underwhelming. Authors have developed a game called GamEducation in a master’s level course over two years. <strong>While gamification improved major fields of university teaching e.g. motivation, fun, participation and learning efficiency — work load for both students and teaching staff increased. </strong>This has roots in both increasing competitiveness among students as well as increased number of challenges</p><p>Typical learning management systems (LMS) are criticized because of their restrictions, refusal of use, complexity and reconstruction of established procedures. However even with integrating game mechanics, projects may not always result in increased learning efficiency. The chapter ends with qualitative evaluation of GamEducation game as described by students themselves</p><p>This is a unique book, little theoretical in its approach — nevertheless to their credit authors concede this limitation at few places in the book. However if you can correlate your workplace learning with amazing situations various contributing authors place their readers in, this book could teach a thing or two.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d65f716af431" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review (2): The Chief Data Officer’s Playbook…]]></title>
            <link>https://medium.com/@productmgmt/book-review-2-the-chief-data-officers-playbook-bdd4e2b3c3?source=rss-df3af3499b59------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdd4e2b3c3</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ram Sevak]]></dc:creator>
            <pubDate>Sun, 18 Mar 2018 18:27:07 GMT</pubDate>
            <atom:updated>2018-03-18T18:27:07.775Z</atom:updated>
            <content:encoded><![CDATA[<p>I chanced upon this book <strong><em>The Chief Data Officer’s Playbook</em></strong> while browsing for the latest practices in the realm of product management specific to data science. It helps that the book got released only in Jan 2018 and how emergence of GDPR in coming May 2018 impacts the role</p><p>In summary, the book defines the emerging role of CDO in C-suite and the success formula for first-time, second time CDOs. There is clear understanding of contextual, undefined and blurring role of a CDO vis-v-a-vis CIO and its dependence on org and data maturity levels</p><p><strong>Why does an Organisation need a CDO?</strong></p><p>In short to help drive business strategy in new age which necessitate data usage! Data quality matters more than a data swamp. Improving data governance across the organisation may require a cultural change. CDO role must allow itself to work across functions. CDOs are to be measured against data management, org efficiency, business outcomes, org agility, profitability and revenue. Please note order is important here!</p><p><strong>Secret Ingredients of a CDO</strong></p><p>CDO must have narrative power within an org i.e. the ability to pitch at the right level. CDO needs to master the relationship building. Passion is another must-have quality of a CDO</p><p><strong>Self-awareness as a CDO</strong></p><p>It helps to know one’s talent, strength, weakness, core values, personality and track record. Secret ingredients of a CDO are: relationship building, communication, credibility, passion for data, specialism (expertise), strategist and tactician and being lucky. I however find this list to be applicable for any leadership role in our times!</p><p>To successfully work with people who rely more on their intuition / gut-feel to take decisions, evidence-based decision making approach may work better. This is like adding science to the art of decisions!</p><p><strong>Difference between CDO and CIO</strong></p><p>Bucket analogy for explaining the difference between CIO and CDO: CIO is responsible for bucket and making sure it’s in safe place. CDO is responsible for fluid in the basket and what happens to it!</p><p>The author then provides a handy trick to identify duplicate reporting or data. Just switch off the suspect reports for a while and see who in the org complains. If nobody does, it’s probably not needed. I can vouch that this approach works!</p><p><strong>The First 100 Days</strong></p><p>Focus has to be on understanding what the business does, how it does it, how it’s treating its data and its understanding about the value of data. Also make sure to understand organisation’s heartbeat, what patterns are there to meetings, what meetings you should be part of and thereafter remaining plugged in those meetings. Be ready to have a team, case of change, vision and makings of a strategy. Also identify and deliver on few quick wins soon!</p><p>The book then delves into differentiating immediate data strategy (IDS) and target data strategy (TDS). A SWAT team can focus on IDS and more transformational team on TDS. Calling some of the new projects as initiatives helps!</p><p><strong>Avoiding the Hype Cycle and Managing Relationships</strong></p><p>This aspects is very important, not just for CDO but for any leadership new hire — how to avoid getting trapped into unrealistic expectations? Some of the tips are: excellent communication, incremental value-add as time passes, early delivery of a piece of advanced analytics and managing leadership teams ahead of time by managing / minimizing shocks</p><p>To manage relationships with other C-level executives, make sure you set up meetings when you say you will and do what you say you will do. Trust is an important element. Also other stakeholders need to be made understood that data ownership is a shared ownership while accountability cannot be shared. Being accountable means being responsible and being answerable for your actions</p><p><strong>Data, Disruption and Innovation</strong></p><p>Mainly four aspects can be looked into when evaluating innovation potential of data: disruption in the data itself, positive effect on the balance sheet, developing new revenue streams and future M&amp;As</p><p>First-generation and second-generation CDOs need to balance between risk aversion and value addition. FCDOs may also rely more on POCs and IDS to keep stakeholders glued in (remember hype cycle!) and manage risks. SCDOs may also have an opportunity to be truly innovative since good FCDO would have hopefully done his / her job of laying basics well!</p><p><strong>Data, Information Ethics and GDPR</strong></p><p>Need to consider unintended consequences irrespective of how ethical our intentions are. We also need to consider data aggregation effect when sharing bulk data in public even if it’s not classic PII. Data governance and incoming GDPR also needs to consider availability, usability, integrity and security of data systems</p><p><strong>How to value your data?</strong></p><p>It’s very important to understand data valuation especially when a CDO wants to tackle data hoarding mentality across the organisation. Different factors which determine data value could be: 1. Are you the only company that has it? 2. How accurate / complete is it? 3. Is it updated? 4. Is is relevant? 5. Can you use it for more than its current usage? 6. Opportunity cost</p><p><strong>How to drive change?</strong></p><p>Some tips to overcome resistance are: make people understand why they are being asked to do something differently, share the change load with other leaders, paint optimistic picture of the future, communicate vision using org advocates and be careful of what you measure. What you measure drives behavior!</p><p>In short, I found this book to be good as an introductory reading for the uninitiated data leadership professionals. Even for those of us who have been in product data / leadership trenches for some time, some of the suggestions could be really useful irrespective of our functions or data maturity</p><p>The book is available from <a href="https://www.amazon.in/Chief-Data-Officers-Playbook/dp/1783302585">Amazon</a>. I could not find it on Flipkart though :(</p><p>PS: Glossary defines 5Vs of Big Data: Volume, Variety, Velocity, Veracity and Value</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdd4e2b3c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review (1/n): Product Leadership — How Top Product Managers Launch Awesome Products…]]></title>
            <link>https://medium.com/@productmgmt/book-review-1-n-product-leadership-how-top-product-managers-launch-awesome-products-a8c1e4ed0f48?source=rss-df3af3499b59------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8c1e4ed0f48</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[consumer-products]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[Ram Sevak]]></dc:creator>
            <pubDate>Sat, 24 Feb 2018 12:32:41 GMT</pubDate>
            <atom:updated>2018-02-24T12:32:41.935Z</atom:updated>
            <content:encoded><![CDATA[<p>The book <strong><em>Product Leadership — How Top Product Managers Launch Awesome Products and Build Successful Teams</em></strong><em> </em>focuses on specific aspects concerning product leaders across different organisation stages</p><p>Basic premise of the book is about reinforcing that domain-specific skills aside, product leadership is more about leading people and less about pushing pixels, writing code or administering project schedules. And that it’s not about individual success, it’s about getting the best out of others</p><p><strong>Key Traits of Great Product Teams</strong></p><p>Efficient communication and decision making are key to great teams</p><p>The theme of having right people present to make daily, weekly or longer term decisions is ubiquitous in successful product teams</p><p><strong>What’s Product Management?</strong></p><p>The book starts with familiar UX, Tech and Business Venn diagram and its intersection to be the defining place of PM as far as these specialities are concerned. It then proceeds to describe genesis behind marketing and product schisms in many tech organisations where both departments feel they “own” the customer. The chapter ends with authors’ views on the future of product leadership revolving around driving customer experience in organisations</p><p><strong>Product Leader’s Role</strong></p><p>Product leadership position can be a source of truth and one of the purest forms of unbiased knowledge transfer for an organisation. Developing processes that remind teams of the customer and their needs is a big part of leader’s role. Operating at a cross-functional level is the whole point of having people who lead departments</p><p>How the team is recruited, developed and guided is probably one of the most important elements of product leader’s role. Product leaders also have first-hand insight into customer experience. In C-suite, specific to a product leader’s role is challenging task of synthesizing and figuring out other leader’s expertise and molding it to make the most effective strategy. Besides while leverage is essential elements of all leadership positions, what’s unique about product leadership is the leader’s sharp focus on strategy and to ensure that product strategy <strong><em>is </em></strong>essentially the company strategy</p><p><strong>Product Leadership challenges</strong></p><ol><li>Prioritisation: especially when it’s seen polarising by other stakeholders. Having a testable prototype through design sprint or directed discovery or having data behind design decisions could be helpful to reduce dissonance among stakeholders / executives</li><li>Prioritisation can be modeled as co-creation exercise to neutralize politics in the organisation</li><li>Managing upwards: knowing who is road blocker and who is decision maker</li><li>Aligning and focusing the organisation: being passionate helps</li></ol><p><strong>Setting Product Principles</strong></p><p>Getting buy-in from stakeholders for the first 5–6 things which need to be achieved in the year is the first step. Any feature should align with the product vision</p><p>Influence product manager’s decisions in the right direction since most often people do what they want to do and not exactly what you tell them to do. Make it valuable for both individuals and the organisation</p><p>Product discovery process should consumer larger time of a product leader. Also focus on why and how of the work</p><p>Successful product leaders are great team workers, seek challenge, remain attached to details, possess great communication skills especially written and demonstrate selling skills</p><p><strong>Start-Ups and Product Leadership</strong></p><p>Lack of clarity is the biggest challenge. Focus on the vision and not the chaos. And always solve the number one problem. Don’t skip to know your customer</p><p>In early stage products</p><ul><li>Leaders can get to play the customer in order to bootstrap the system, then get in beta users and then daily users as proxy for customers</li><li>With so many tension, respect and empathy are part of creating a space where the team can be productive and supportive</li></ul><p><strong>Emerging Organisations and Product Leadership</strong></p><p>Biggest challenge is to manage growth of the team. Have your first public win in the first 90 days as a new hire. Maintaining user focus is important. Vision is aspiration, while strategy is execution, maintain the distinction. In hiring, key is to separate the task the person did with team’s output</p><p><strong>Enterprise Organisations and Product Leadership</strong></p><p>An appetite for change needs to be nurtured especially when established products are concerned. Ensure that at least one product sets the company apart and focus on the most interesting customer segment. Undocumented checkpoints should be watched out for while executing product roadmap. And executives must avoid using sanitized data for taking decisions</p><p><strong>Parting Advice</strong></p><p>Ask often: is it valuable (to customer and business, feasible (to deliver) and delightful (to use)?</p><p>And always be learning!</p><p>Overall I found this to be a great book for understanding practical nuances of product leadership roles across organisation life-cycle. Since product management is essentially a leadership role, the book should be useful for all product people along the totem pole!</p><p>The book can be ordered from <a href="https://www.amazon.in/Product-Leadership-Managers-Products-Successful/dp/9352135660">Amazon</a>. Cannot link to Flipkart since site search was non-functional for a weird reason!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8c1e4ed0f48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About the Blog]]></title>
            <link>https://medium.com/@productmgmt/about-the-blog-f3923fa0474b?source=rss-df3af3499b59------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3923fa0474b</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ram Sevak]]></dc:creator>
            <pubDate>Sun, 18 Feb 2018 14:51:49 GMT</pubDate>
            <atom:updated>2018-02-18T14:51:49.687Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello all!</p><p>I am Ram — a product manager by profession and based out of India. While my <a href="https://www.linkedin.com/in/ram107/">LinkedIn profile</a> provides more details on kind of products and businesses I have worked with; this blog intends to summarize my learning in product. At a minimum, I intend to publish summaries of books — that might be of interest to product managers and leaders alike. Since I possess little expertise to summarize stuff as a book reviewer, these summaries would be published in cheat-sheet style — more like how we scribble notes in our diaries. I hope to retain summaries unambiguous and explanatory enough in isolation though!</p><p>A caveat — though most books / topics can be thought of concerning product management, I will however be mostly covering books related to “hard skills” in product management e.g. analytics, data science, design, growth, psychology and negotiation. Primary reason: IMO these areas are covered relatively lesser than most of the other disciplines e.g. business strategy, biographies, leadership. Or so I hope!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3923fa0474b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>