<?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 Product Fundas on Medium]]></title>
        <description><![CDATA[Stories by Product Fundas on Medium]]></description>
        <link>https://medium.com/@productfundas?source=rss-caa140c621a4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SzGXqvfYGgKY-Mnx7KHf9Q.jpeg</url>
            <title>Stories by Product Fundas on Medium</title>
            <link>https://medium.com/@productfundas?source=rss-caa140c621a4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:51:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@productfundas/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[Product Management Vs.]]></title>
            <link>https://medium.com/design-bootcamp/product-management-vs-27acf4f6a4ba?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/27acf4f6a4ba</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[differences-between]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Mon, 22 Aug 2022 08:41:57 GMT</pubDate>
            <atom:updated>2022-08-23T05:43:00.119Z</atom:updated>
            <content:encoded><![CDATA[<h4>Vs. Project Management, Vs. Business Analysis, Vs. Product Owner, Vs. Scrum Master</h4><p>What are the differences between the <em>role</em> of a Product Manager and a Business Analyst, a Product Owner, a Project Manager and a Scrum Master?</p><p>I used to have this question myself. I’m sure many of us have the same question. And, honestly, there are a lot of answers out there. Good ones.</p><p>My 2 cents, visually, as follows…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pMXJgwdpz33XJdKw" /></figure><h4>Product Manager Vs. Project Manager</h4><p>In my opinion, Product Manager and Project Manager are two equally important but totally *non-overlapping* roles.</p><p>A Project Manager needs to mainly bring Project Thinking to bear. But she must also utilise her Product Thinking ability from time to time.</p><p>One the contrary, a Product Manager must primarily deploy their Product Thinking super power, but also employ Project Thinking in a timely manner.</p><p><a href="https://twitter.com/shreyas">Shreyas Doshi</a> has quite eloquently explained the concept of Product Thinking and Project Thinking <a href="https://twitter.com/shreyas/status/1471650411341750273">here</a>. If you’ve not studied it, you must. It is awesome with examples and everything.</p><p>Inspired by Shreya’s thoughts, here’s my representation of the distinctions between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*RHVCdbTBwK0lTA_s" /></figure><p><strong>Key Takeaway</strong>:</p><p>There’s no one-better-than-the-other between Project and Product Thinking. There’s nothing like one must be a product thinker more than a project thinker. It’s like saying gravity is better than time. No. Both are needed, and both are relevant.</p><p>In fact, as a Product Manager, we must know when to deploy product thinking and when to wear project thinking hat. The same is true even for a Project Manager.</p><h4>Product Manager Vs. Scrum Master</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pMXJgwdpz33XJdKw" /></figure><p>Intuitively we all get that there is an overlap between Project Management and Scrum Master roles, and that there is quite a bit of uniqueness to the Scrum Master role.</p><ul><li>Scrum Master is a role defined in the Agile Scrum methodology as a custodian of the Scrum process whereas a Project Manager is an role ubiquitous across industries.</li><li>Scrum Master is a servant leader role, not so much a Project Manager (although an individual playing the PM role may choose to play it as a servant leader)</li><li>Scrum Master does not ‘manage’ her team. Every team member in the Agile Scrum team is expected to be mature, self-driven and self-managed. On the other hand, a Project Manager is the manager of her team — assign tasks, monitor progress, seek status reports, track a project plan, everything.</li></ul><p>There is no overlap between a Product Manager and Scrum Master roles.</p><blockquote><strong>Mind you: </strong>we’re talking about <strong>roles</strong> here, <strong>not titles or designations</strong>. We might find instances where, for example, Krish, a designated Product Manager, is playing an additional role of a Scrum Master also. I know, weird…but anything is possible for Krish. But that doesn’t mean that the Product Manager and Scrum Master roles overlap.</blockquote><h4>Product Manager Vs. Product Owner</h4><p>Here’s where there is a lot of confusion. Let’s try to resolve them.</p><p>But first let’s get one thing sorted out: Product Owner is a role described in the Agile Scrum methodology (like Scrum Master). Outside the Agile Scrum, there is no role called Product Owner.</p><p>Having gotten that out of the way, below is the 6 phase Product Management Lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*BKPNw8i0-SXtCiqy" /></figure><p>A Product Manager coordinates across all six phases. However, the Product Manager can delegate to a Product Owner her responsibilities in Design, Develop and Deliver phases.</p><p>Let’s take an example: Consider Amazon Music.</p><p>It is easy to imagine that there could be several, several Scrum teams working on various parts of this one product. Let’s assume that there is one Product Manager for the entire Amazon Music.</p><p><em>I know, I know…in reality there are several Product Managers too. But for the sake of this discussion, assume one Product Manager.</em></p><p>Every Scrum team must have one Product Owner, as mandated by, well…Scrum methodology. The Product Manager focuses on Discover, Define, and Debrief phases, and relinquishes to the individual Product Owners the responsibilities of Design, Deliver and Develop phases.</p><p>The Product Manager, of course, gets involved quite intensely in the Deliver phase, because that’s where a lot of GTM is choreographed.</p><p>But the bottomline is that the Product Owner role is completely subsumed under the Product Manager role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pMXJgwdpz33XJdKw" /></figure><h4>Product Manager Vs. Business Analyst</h4><p>The Business Analyst title is ubiquitous in the IT consulting industry and is largely involved while custom developing bespoke applications for businesses.</p><p>The BA title is also widely adopted within the IT departments of corporations, where the BAs serve to discover and define the needs of <em>internal users </em>and stakeholders</p><p>But a Business Analyst’s role, like a Product Manager’s, is fundamentally about problem solving. Both roles go through similar lifecycle phases — Discover, Define, Design, Develop, Deliver and Debrief</p><p>The differences lie in details:</p><ul><li>The Product Manager discovers users’ needs via user research by collaborating with <em>representative </em>users because their larger user base is potentially a large market. The Business Analyst discovers user needs by collaborating with <em>named</em> users because their user base is restricted within the company.</li><li>The Product Manager gets involved in deciding the GTM strategy. The Business Analyst provides inputs to develop a OCM strategy.</li><li>The Product Manager gets to weigh in on aspects like pricing, messaging, etc. A Business Analyst almost never gets to do that.</li><li>A Product Manager role almost never surfaces in Management Consulting companies. A Business Analyst (under the title of Consultant) is definitely a part of such consulting companies</li></ul><p>That’s it, folks. Thanks for reading.</p><p>Do let me know what you think in comments below.</p><p>Also, please share this piece to your network if you liked what your read.</p><p>You might also like the following articles:</p><ul><li><a href="https://bootcamp.uxdesign.cc/a-case-in-product-discovery-f1532271c9fa">A Case in Product Discovery</a></li><li><a href="https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732">The 5 types of Questions</a></li><li><a href="https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2">The 4Ps that every Product Manager and Business Analyst must know</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27acf4f6a4ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-management-vs-27acf4f6a4ba">Product Management Vs.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Success α Effort²]]></title>
            <link>https://productfundas.medium.com/an-incident-from-mahabharata-epic-795bacdd512b?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/795bacdd512b</guid>
            <category><![CDATA[secrets]]></category>
            <category><![CDATA[formula]]></category>
            <category><![CDATA[epic]]></category>
            <category><![CDATA[success]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Wed, 01 Jun 2022 05:09:54 GMT</pubDate>
            <atom:updated>2022-09-09T03:52:39.833Z</atom:updated>
            <content:encoded><![CDATA[<h4>Success is directly proportional to the square of the effort invested</h4><p>From my Manipal diaries: I heard this beautiful story from Mahabharata narrated by the then main pontiff of the Udupi Krishna temple.</p><p>— -</p><p>Yudhistira desires to perform Ashwamedha Yagna.</p><p>He assembles his brothers and invites Sri Krishna for a meeting.</p><p>He proposes his desire in the meeting.</p><p>All the brothers agree unanimously.</p><p>Krishna being Krishna says, “Sure, sure…great idea. Just one point to ponder though. For the Yagna to succeed, either Jarasandha must voluntarily pay you obeisance, like all other Kings will OR you must defeat Jarasandha.”</p><p>Yudhistira says, “Of course. But you know we all knew that. What are you trying to say?”</p><p>Krisha responds, “Well, nothing earth-shattering. Jarasandha is no ordinary human. He is powerful. Even my mighty army ran away from him 17 times.”</p><p>Yudhistira goes pale, “Oh darn! Then forget it. If you couldn’t defeat him, then why even bother.”</p><p>Krishna says, “Oh hold on a second. That’s not why I said, what I said. I only surfaced the critical success factor in your endeavor. I didn’t say defeating Jarasandha is impossible.”</p><p>Yudhistir responds, “But Krishna, how is it possible for us to succeed where you failed 17 times.”</p><p>Bheemasena intervenes, “Bro, there are only three ingredients needed to succeed in any endeavor — commensurate effort, adequate competence, and God’s blessings. We have the competence, you believe that, right? And Krishna is right here, so we got God’s blessings also. All that is remaining is effort…so why don’t we?”</p><p>The rest is, well, history. Krishna takes Arjuna and Bheema along and gets Bheema to literally split Jarasandha into two.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRcf3Gp3f0WC-2p0s6-wXQ.jpeg" /></figure><p>When you dissect what Bheema said, it translates to an equation for success:</p><h4>Success ∝ Effort * Competence * God’s Will</h4><p>Assume God is always willing, God’s Will = 1</p><p>and</p><p>that we’re adequately competent, Competence = 1</p><p>Success is directly proportional to our Effort</p><p>If we’re not competent at present, not a problem. Invest effort to acquire competence. here</p><p><strong>Success α Effort²</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=795bacdd512b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Case in Product Discovery]]></title>
            <link>https://medium.com/design-bootcamp/a-case-in-product-discovery-f1532271c9fa?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1532271c9fa</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[analysis]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 07:08:59 GMT</pubDate>
            <atom:updated>2022-03-25T00:24:53.997Z</atom:updated>
            <content:encoded><![CDATA[<h4>A real world (fictional) example for Product Discovery</h4><h3>The Case</h3><p>Jay is a Senior Product Manager at Amazon responsible for Amazon Music</p><p>That is a Friday. Jay is at his desk. Alone. Engrossed.</p><p>Jay’s calendar notification pops up. It reminds him that it is time to sequester himself to some solo, heads-down thinking on ideas to make Amazon Music better.</p><p>Jay eagerly looks forward to this alone time every week. He is already on the task. He closes the notification. He sets his iPhone and Mac to ‘Do Not Disturb’, and soon enough, he is back into deep rumination.</p><p>Jay’s plan is to deep-dive into consumer feedback, which he does religiously every month. He has a simple process: review the output generated by an AI engine that performs some heavy-duty analytics on raw ratings and feedback data.</p><p>Jay furrows his eyebrows zooming in on one feedback. It says:</p><blockquote><strong>Amazon Music needs to offer social networking ability for people to connect with and interact around an album, a song, an artist, a podcast, a topic or anything related to music or podcast.</strong></blockquote><p>Jay quickly opens the reports for the last three months. He observes that this is a consistent feedback from many users.</p><p>What should Jay do now? As the Product Manager, how should Jay proceed?</p><h3>React vs. Respond</h3><p>In my opinion, there are only two ways forward — react or respond. There’s a difference.</p><ul><li>Reaction is typically quick, without much contemplation, and mostly driven by one’s beliefs and biases. On the spectrum of all possible options available to deal with the situation, reaction typically are the extremes.</li><li>Response is typically calm, well-thought-through, and driven by facts and data</li></ul><p>If Jay were to <strong>react</strong>, the two extreme positions could be:</p><ol><li>Jay agrees, <em>“It is a great idea to build social features into Amazon Music! Why didn’t I think of it earlier?”</em> Jay proceeds to imagine some features, maybe gets inspired by other social platforms. He then documents the PRD and sends it up the flagpole for approval.</li><li>Jay dumps the idea saying, “Amazon does not own a social platform. Amazon Music is certainly not a social platform. It is a music streaming service. There are workarounds on the platform that allows the user to network socially. It is absurd to turn Amazon Music into another social network.”</li></ol><p>If Jay were to <strong>respond</strong>, then there is really just one way forward —begin with problem discovery.</p><blockquote>By the way, I’m not passing any judgment on react vs. respond. In some cases, reacting may well be the best way forward. In other cases, responding could be the best foot forward.</blockquote><p>In this case, I believe it is clear as daylight that Jay would be much better off if he chooses to respond by kicking-off a new problem discovery thread, because reacting would end up being just knee-jerk.</p><h3>Product Discovery — a quick recap</h3><p>Problem Discovery involves the following steps, at a high level:</p><figure><img alt="Identify problem &amp; User segments -&gt; Discover root causes &amp; motivations -&gt; Estimate user segment size -&gt; Calibrate problem freq. &amp; severity -&gt; Validate vision alignment -&gt; Determine relevant metrics -&gt; Brainstorm solution ideas -&gt; Validate ideas" src="https://cdn-images-1.medium.com/max/960/1*A7r1GHSnrVjpa8NeG4oCjQ.png" /></figure><p>All of the above, before the solution is built. No scratch that. It is <em>before we even prepare to build anything.</em></p><h3>Product Discovery — the Amazon Music Case</h3><h4><strong>Step 1: Problem — User Segment/s — Motivation — Engagement</strong></h4><p><strong>Problem:</strong></p><p>The word <em>problem</em> is usually used to refer to <em>symptoms, </em>like the lack of <em>something</em> in the product, say an ability, a feature, usability and so on.</p><p>In Amazon Music’s case, the problem clearly is the lack of social features. The abilities such as <em>like/dislike</em> a song, <em>share</em> a link via email, Facebook or Twitter, or copy-paste the link on any other platform, hardly count as social features.</p><p><strong>User Segment</strong>:</p><p>The idea here is to construct the persona of the users who are sorely missing the social features.</p><p>It is not straightforward to pinpoint the specific user segment/s. There are several ways to collect data to construct a user persona and box the user segment/s. For example,</p><ol><li>Users who use the <strong>like/dislike feature</strong>, with a hypothesis that these users most likely want the social features.</li><li>Users who use the <strong>share</strong> <strong>feature</strong>, with a hypothesis that those who share are even more likely to want the social features.</li><li>Users who provided <strong>feedback</strong> (provided it is a statistically significant number)</li><li><strong>In-app survey (or external survey) — </strong>If none of the above methods work, construct a survey based on the above data and target it to a larger set of users.</li></ol><p><strong>Motivation</strong>:</p><p>Now that we have the user segment/s nailed down, we begin with the <em>why</em> questions. The <strong>purpose</strong> is to discover the root causes of the problem, as any solution needs to address the root causes or the users’ motivations:</p><ul><li>Why do these users need social features within the app?</li><li>What satisfaction might they derive from in-app social features that is not gained by simply copying a link and sharing it on other platforms?</li></ul><p>Oftentimes, users mask their motivations. They disguise their imagination of the solution as their needs.</p><blockquote>Almost nobody says, “Hey, here are my motivations. How can you help meet them?” Users simply say, “I need social features.” As a Product Manager, it is expected of us to investigate why (underlying motivations), and then solve for them.</blockquote><p><strong>Breadth-Frequency-Severity</strong>:</p><p>Finally, a Product Manager must consider the numbers: how <em>many</em> users are expected to use it? How often will they use it?How sorely are they missing it today?</p><p>Step 1 ends with a decision on whether it is worth investing in building these features.</p><h4><strong>Step 2: Vision Alignment &amp; Metrics</strong></h4><p><strong>Vision Alignment:</strong></p><p>The next step is to validate if solving for the root causes, or users’ motivations align with the company’s and product’s vision.</p><p>Amazon’s vision is to <strong>“be the most customer-centric company on earth”</strong></p><p>Amazon Music’s vision is “<strong>to be the best value music service for Amazon customers, not a me‐too on‐demand streaming service”</strong></p><p><em>Would adding social features continue to keep Amazon and Amazon Music aligned to their respective vision?</em> Some follow up questions would be:</p><ul><li>Does <em>customer-centric </em>mean that Amazon builds every feature that the customers request?</li><li>Would social features count as the <em>best value music service for customers</em>?</li><li>Would not adding social features make Amazon Music a <em>‘me-too’</em> service (because no one else does)? If yes, should they build the social features?</li></ul><p><strong>Metrics</strong>:</p><p>Every Product Manager tracks metrics: NSM, Revenue, Usage, Usability, NPS, and so on.</p><p>Metrics are one of the key considerations for decision-making. The simple question would be: which Amazon Music’s metrics would the social features help move, and to what degree? Are these the primary metrics, like NSM?</p><p>For example, suppose the NSM for Amazon Music is Cumulative Streaming Hours. Would social features help increase CSH? It could if the social features are built in such a way that they become accessible while streaming is in progress. Otherwise, they may not.</p><h4>Step 3: Ideas for Solution</h4><p>The Product Manager has two decision-making points, one after Step 1, and the second after Step 2.</p><p>If the decision is a ‘go’ at both these points, that is when the ‘how might we’ questions begin:</p><ul><li>How might we get users to interact with each other?</li><li>How might we get users to post their thoughts about a song, an album, an artist, a playlist, etc., and share a link to it while they are at it?</li><li>How might we get users to like someone’s post or add their comments to it?</li></ul><p>Questions like these help generate ideas for solutions. Some basic UX design will help test out these ideas. Maybe we iterate a while with different solution ideas.</p><p>Mind you, there is zero implementation effort invested. We’re still within the boundaries of Product Discovery.</p><p>Product Discovery helps the Product Manager to develop a strong business case for an idea for product improvement and run it up the flag pole for approvals.</p><h3>Conclusion</h3><p>To conclude, it takes some intense research, analysis, and decision-making before choosing to make any significant improvement to a product.</p><p>The challenge is to engage in such an intense analysis while simultaneously preventing analysis paralysis.</p><p>That’s the post, my friends. Thanks for reading till the end.</p><p>If you have some views about this piece, please feel free to add your comments.</p><p>If you liked this piece, go ahead and share it with your network. And of course, tap the clap icon below and show me your appreciation. Follow <a href="https://medium.com/u/caa140c621a4">Product Fundas</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1532271c9fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-case-in-product-discovery-f1532271c9fa">A Case in Product Discovery</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monopoly & 3 steps to prioritisation]]></title>
            <link>https://medium.com/design-bootcamp/monopoly-3-steps-to-prioritisation-696ea826c64?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/696ea826c64</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[gamification]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[techniques]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Fri, 11 Mar 2022 08:34:06 GMT</pubDate>
            <atom:updated>2022-03-16T03:01:12.785Z</atom:updated>
            <content:encoded><![CDATA[<h4>Gamify prioritisation. Put an end to all your frustration.</h4><p>A while ago, I’d written a story on a Product Manager’s frustrations with prioritisation. If you have not read that story, here it is 👇🏻</p><p><a href="https://bootcamp.uxdesign.cc/everything-is-a-priority-that-is-why-nothing-is-ac7c14df1ede">“Everything is a priority. That is why NOTHING is!”</a></p><p>In this story, I wish to narrate a technique that is most likely to work for you, the Product Manager, especially if you’re collaborating with business stakeholders, whose default position is <em>‘everything is important’</em>.</p><h4>Step 1: Explain in good faith the <em>why</em> of prioritisation</h4><p>The first step is to try to explain to the stakeholders the underlying reasons for prioritisation. Try to reason with them to elicit their collaboration for the prioritisation exercise.</p><p>One way to do this is as follows, and I’m quoting from my earlier story:</p><p><em>“If everything is a priority, really, nothing is.</em></p><p><em>Not all requirements contribute equally to business impact, do they? Some requirements deliver more business impact than others, right?</em></p><p><em>Likewise, not all requirements present themselves as equally risky. Some requirements present more risk to the business than others because they might need more org. changes to adopt. Or implementation wise, they are more risky than other requirements.</em></p><p><em>So, Ms. Stakeholder, the purpose of prioritization is to surface up those requirements that are relatively more important than others for reasons outlined above. The real reason for prioritization is to determine how to maximise delivery of business value.</em></p><p><em>And only you, all of you stakeholders, can prioritize requirements. As a BA / PM, I can only facilitate the process. I am accountable for prioritization. But you all are responsible.”</em></p><h4>Step 2: Minimise bias</h4><p>Prioritisation is assigning relative importance to requirements, and such assignment is based on stakeholders’ gut feel. Prioritisation is fundamentally a subjective exercise. It is riddled with bias. You cannot escape from it.</p><p>There couple of ways to infuse objectivity into a predominantly subjective exercise:</p><p>One, involve more number and more diverse stakeholders, hoping that each individual’s bias negates others’ biases to bring the overall bias close to zero.</p><p>Two, prioritise using weighted parameters. What are these? These are parameters like business benefit, risk, penalty, implementation difficulty, cost of implementation and so on. Each parameter has an assigned weight. Stakeholders prioritise the requirements against each parameter, and at the end, you do a weighted average scoring to arrive at the final priority.</p><h4>Step 3: Use money</h4><p>Yep, you read it right…use <strong>money</strong>. Let me explain.</p><p>You see, money does something to our brains. Where money is involved, you tend to be naturally careful or guarded. Which board game do you think is among the most successful ever, till date?</p><p>Yep, it is Monopoly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1dq98dOk0FBYaoKvOq6b3Q.jpeg" /><figcaption>Monopoly money</figcaption></figure><p>Imagine the time when you played Monopoly. You rolled your dice and moved your piece. You arrived at a square called New York City, and you decided to ‘buy’ a property there. Honestly, recall the feeling you experienced when you completed this imaginary purchase. You were elated, weren’t you? Ecstatic even. The rational part of your brain went, “Oh relax! this is just a game”. But the child in you was screaming with joy, wasn’t she?</p><p>That is because money does something to our brains. How about we use this to our advantage for prioritisation?</p><p>No, come on! We’re not going to cheat anyone, especially not your stakeholders. We’re not even going to use real money. We will use fake Monopoly money.</p><p>Here’s how…</p><ol><li>Give all the stakeholders, say $1000 each (₹, €, ¥, £, or any other currency) of fake Monopoly money.</li><li>Explain to them that the idea is for them to ‘purchase’ those requirements that they think are the most important among all.</li><li>They must spend all $1000.</li><li>To arrive at the ‘value’ of a requirement, encourage them to consider the aforementioned factors like business benefit, risk, penalty, implementation difficulty, cost of implementation and so on.</li><li>The more strongly they want a requirement, the more they pay for it. Consequently, they will have that much less to purchase other requirement. So they have to maintain a balance.</li><li>Finally, the most important rule: time-box this activity to a reasonable amount of time.</li></ol><p>That’s it. That’s the technique.</p><p>If you objectively look at this technique, it is nothing more than a 1000 point rating scale.</p><p>The value of this technique stems from the following — You are <strong>gamifying</strong> the prioritisation exercise. You have transformed the mundane prioritisation exercise to some sort of demand-supply economics driven ‘bidding war’.</p><p>Oh…fun! 👏🏻👏🏻😃</p><h4>When to use this technique?</h4><p>Use this as the last resort. If MoSCoW, RICE or ICE works for you, then please, by all means, use it.</p><p>If nothing else works, use this money technique, instead of tearing your hair.</p><p>Let me know what you think, folks!</p><p>Thanks very much for reading. Please hit the ‘clap’ icon at the bottom to show some love, if you liked this story. Share it with your network on social media to help more people read this story.</p><p>Have a great weekend!</p><p>— — —</p><p>Some more posts for your weekend reading</p><ol><li>Effective meetings series:</li></ol><ul><li><a href="https://bootcamp.uxdesign.cc/my-first-aha-learning-of-my-career-2feb9e22547f">My first ‘aha’ learning of my career</a></li><li><a href="https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732">The 5 types of Questions</a></li><li><a href="https://bootcamp.uxdesign.cc/run-your-meeting-lest-it-will-run-away-6cd2af93c2f6">Run your meeting, lest it will run away</a></li></ul><p>2. Gaining domain knowledge series:</p><ul><li><a href="https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2">The 4Ps that every Product Manager and Business Analyst must know</a></li><li><a href="https://bootcamp.uxdesign.cc/p-for-parts-one-of-the-4ps-f55b267dd5ec">P for Parts — one of the 4Ps</a></li><li><a href="https://bootcamp.uxdesign.cc/p-for-parts-one-of-the-4ps-e196204cedb5">P for Parts — One of the 4Ps</a></li><li><a href="https://bootcamp.uxdesign.cc/p-for-parts-one-of-the-4ps-3-of-3-98b87513599a">P for Parts — One of the 4Ps…3 of 3</a></li></ul><p>3. Stakeholder Management series:</p><ul><li><a href="https://bootcamp.uxdesign.cc/how-i-dealt-with-stakeholder-conflict-and-got-stung-badly-in-the-process-fa9ec526d73a">How I dealt with stakeholder conflict…and got stung badly in the process 😬</a></li><li><a href="https://bootcamp.uxdesign.cc/how-i-dealt-with-stakeholder-conflict-got-stung-badly-and-learned-something-valuable-in-the-dca21460d292">How I dealt with stakeholder conflict, got stung badly, and learned something valuable in the…</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=696ea826c64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/monopoly-3-steps-to-prioritisation-696ea826c64">Monopoly &amp; 3 steps to prioritisation</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Like a lotus leaf]]></title>
            <link>https://medium.com/design-bootcamp/like-a-lotus-leaf-2aa3e63a24e8?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aa3e63a24e8</guid>
            <category><![CDATA[attitude]]></category>
            <category><![CDATA[attachment]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Tue, 01 Mar 2022 16:52:59 GMT</pubDate>
            <atom:updated>2022-03-03T01:31:54.641Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Product Manager’s relationship with her product</h4><p>A lotus leaf has a very unique relationship with water. It is <em>ultrahydrophobic</em>.</p><p>On one hand, to survive, a lotus leaf must remain on the water. If you take it out of the water, it withers away quite quickly.</p><p>But on the other hand, the leaf does not get attached to water. It does not get wet. It is waterproof. Water quickly flows away off of the leaf and what remains quickly assumes the shape of spherical droplets rolling freely like a ball on a smooth surface.</p><figure><img alt="Lotus leaf has a unique non-stick quality. Water doesn’t adhere to it. It doesn’t absorb water. But, it must stay in the water to live." src="https://cdn-images-1.medium.com/max/728/1*_STL18HEJV_FEJv4R37cJg.jpeg" /></figure><h4>Are you obsessed with your product?</h4><p>If you have been a Product Manager of your product for long enough, you might know the answer to this question.</p><p>For those who don’t know, regardless of how long you’re the manager of your product, here is a quick instrument to determine if you are obsessed with your product:</p><ol><li>Do you find yourself responding to user feedback saying, “That is how I’ve defined the product. It is supposed to work exactly like this. Maybe this user is not whom we’re targeting.”?</li><li>Do you find yourself getting annoyed, irritated, angry, enraged, furious at anyone who critiques your product?</li><li>In response to feedback like, “your product doesn’t do this”, do you point to workarounds and say, “but it most certainly does”?</li><li>Do you think of a feature and say to yourself, “our users most definitely need this feature”?</li><li>Do you catch yourself prioritising features based on your gut feel rather than backed by data?</li><li>When a new release fails to move the success metric needles, do you find yourself explaining it away saying, “We’re early to this game. The market needs to catch up.”?</li><li>Do you find yourself generating personal dislike towards those who disagree with your ideas?</li></ol><p>If your answer is <em>yes</em> to many of the questions above, maybe you are too attached to your product.</p><p>Such obsession might not be productive for you.</p><p>Attachment with your product clouds your judgment and decision making. Attachment with your product compels you to act defensively all the time, leading to unnecessary stress and anxiety. Attachment with your product impedes its growth, which is counterproductive.</p><h4>Obsess with the users and their problems</h4><p>Instead of obsessing with your product, maybe it is a relatively better idea to obsess over your users’ problems, their pain points, and how you might solve those problems.</p><p>When you are not attached to your product, you can objectively assess its shortcomings, accept criticisms calmly, receive constructive feedback, accept failure in stride and go back to the first principles with renewed resolve to problem-solve for your users.</p><p>Be like a lotus. Relate your product like how a lotus treats water. Thrive in your product, but don’t get wet with it.</p><p>What do you say? Please share your thoughts in the comments.</p><p>Thanks much for reading. If you like this piece, please hit the clap option below.👏🏻 Show some love. :)</p><p>Also, please share it with your network. 🤝</p><p>— — — — — — — — — — — — — —</p><p>Some of my other popular pieces are 👇🏻</p><ul><li><a href="https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2">The 4Ps that every Product Manager and Business Analyst must know</a></li><li><a href="https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732">The 5 types of Questions</a></li><li><a href="https://bootcamp.uxdesign.cc/how-i-dealt-with-stakeholder-conflict-and-got-stung-badly-in-the-process-fa9ec526d73a">How I dealt with stakeholder conflict…and got stung badly in the process 😬</a></li><li><a href="https://bootcamp.uxdesign.cc/how-i-dealt-with-stakeholder-conflict-got-stung-badly-and-learned-something-valuable-in-the-dca21460d292">How I dealt with stakeholder conflict, got stung badly, and learned something valuable in the…</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aa3e63a24e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/like-a-lotus-leaf-2aa3e63a24e8">Like a lotus leaf</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Run your meeting, lest it will run away]]></title>
            <link>https://medium.com/design-bootcamp/run-your-meeting-lest-it-will-run-away-6cd2af93c2f6?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cd2af93c2f6</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[meeting-preparation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Mon, 28 Feb 2022 06:59:03 GMT</pubDate>
            <atom:updated>2022-03-01T06:34:29.407Z</atom:updated>
            <content:encoded><![CDATA[<h4>The design of a productive meeting</h4><p>Raise your hands if you agree with any or all of the following 🙋🏼‍♂️:</p><ul><li>Your work day is so chockablock with meetings, that you facepalm with frustration</li><li>You think that most meetings are a waste of time</li><li>You feel that meetings are obstacles in your way of getting real work done</li></ul><p>If your hands are raised, then you have company.</p><figure><img alt="Google search results when you search for “meetings are time wasters”" src="https://cdn-images-1.medium.com/max/839/1*JIaiAsWsRYVZfht4_k5atw.png" /></figure><p>I know, I know!✌🏻 I am a victim of my confirmation bias. Google gives you results based on your search string. I get that.</p><p>But <em>meeting</em> is one topic where no matter which way you spin the search string, Google shows that HBR, Forbes, Gartner, McKinsey and even my neighbor Mrs. Doubtfire seem to have advice on how to make meetings productive, useful, better. 🤷🏻‍♂️</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxqfaukOwr5c%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxqfaukOwr5c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxqfaukOwr5c%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/5f1f799b35ac760fb7b68d1a39ea35bf/href">https://medium.com/media/5f1f799b35ac760fb7b68d1a39ea35bf/href</a></iframe><p>There is something horribly wrong about how we run meetings today.</p><p>So I studied hundreds of blog posts, articles, books on running productive meetings. Below are some of the best practices that I managed to distill, synthesise, coagulate, wring from my research.</p><h4>Phases of a meeting</h4><p>There are four distinct phases to any meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*PsjT3NZUYAU5rwsojErTQQ.png" /><figcaption>Meeting Phases</figcaption></figure><p>The higher the intentionality and purposefulness we bring to each phase, the higher the productivity of the meeting.</p><p>The most important phase of a meeting is the prepare phase. Research says that the primary root cause for the failure of a meeting is lack of preparation, especially on the part of the meeting organiser.</p><p>Let’s do a deep dive into prepping for a meeting.</p><h4>Prepare for a meeting</h4><p>In my previous post, I shared how I learned that preparation is the key to the success of any meeting 👇🏻</p><p><a href="https://bootcamp.uxdesign.cc/my-first-aha-learning-of-my-career-2feb9e22547f">My first ‘aha’ learning of my career</a></p><p>There is a massive misconception that preparation means just setting an agenda for the meeting. While that is an important part of prepping, it is not all and it is not the first.</p><p>So, what exactly does preparation mean? What does prepping entail? Here is a quick framework.</p><figure><img alt="Meeting preparation framework: Why (purpose), What (desired outcomes and agenda), Who (the participants), How (the meeting technique such as interview, workshop and so on plus questions to ask), When (the schedule, and logistics)" src="https://cdn-images-1.medium.com/max/868/1*DCCGg3nzKQ4YbrpLj7iHHg.png" /><figcaption>Meeting Preparation Framework</figcaption></figure><h4>1. WHY: The purpose of the meeting</h4><p>The first step in prepping for a meeting is to clarify for yourself the overarching purpose of the meeting.</p><p>This step sounds so obvious that you might be tempted to gloss over or even skip. Please don’t.</p><p>In the meeting invite that you will send out later to the participants, the purpose of the meeting will occupy the subject line.</p><p>If you receive meeting invites with subject line saying “Discussion”, it is best to decline that meeting because it is a definite indicator that the meeting will be a time-waster.</p><p>This means that it is quite important to be pithy and intentional in your articulation of the purpose of the meeting.</p><h4>2. WHAT: The agenda and the desired outcomes</h4><p>The purpose of the meeting drives its agenda and its desired outcomes.</p><p>For instance, say the purpose of a meeting is to brainstorm possible approaches to solve a specific problem.</p><p>The agenda for this meeting might look like:</p><ul><li>Introductions — 5 min</li><li>Recap the symptom and its root causes — 5min</li><li>Establish the ground rules for brainstorming exercise — 5 min</li><li>Ideation — 20 min</li><li>Evaluation —20 min</li><li>Selection — 20 min</li><li>Wrapping up — 10 min</li><li>Call out action items and its owners — 5 min</li></ul><p>The desired outcomes could be:</p><ul><li>At least 3 actionable solution approaches identified</li><li>Approval for running POCs for the solution approaches secured</li><li>SPOCs for these POCs assigned</li></ul><h4>3. WHO: Participants</h4><p>You might find it easy to default to inviting a crowd of people to your meeting. But that is inviting failure. With too many participants, you are forced to focus on everyone, thus accomplishing nothing.</p><p>Likewise, with ever one of the right participants not being in the meeting, you run the risk of not accomplishing anything.</p><p>The right and necessary participants normally fall under the following categories:</p><ul><li><strong>Decision makers</strong>, based on the purpose of the meeting</li><li><strong>Domain subject matter experts</strong>: those who have knowledge of the subject under discussion in the meeting</li><li><strong>Stakeholders</strong>: people who have a stake in the issue being discussed in the meeting</li><li><strong>Implementation folks</strong>: those who will implement the decisions made</li></ul><p>As a meeting organiser, you must be diligent in selecting ONLY those participants who are right and necessary to the success of the meeting, and ruthless in eliminating those who are not.</p><h4>4. HOW: The technique</h4><p>Depending upon the purpose and the number of participants, a meeting takes on a different color. For instance,</p><ul><li>A meeting to elicit information (say, the root causes of a symptom, or how they operate a business process, and so on) from up to three participants may be termed as an <strong>interview</strong></li><li>A meeting to elicit the same information, but from more number of participants, roughly between 8 and 20, then it is called a <strong>workshop</strong></li><li>A meeting with a bunch of carefully selected people to understand how they think, feel and behave in a give context (say a new product, or a presidential candidate) is also a workshop, but <strong>more specifically called a focus group</strong></li><li>A meeting to generate ideas for say, solutions to a problem, is a workshop, more specifically known as <strong>brainstorming</strong> or <strong>brain-writing</strong> workshop</li></ul><p>Each technique has its own specific structure and rules and deserves separate blog to document them all. For instance, a brainstorming session has three distinct non-overlapping phases: Ideation, Evaluation and Selection. Participants are not allowed to judge ideas during the ideation phase.</p><p>Finally, if the meeting is for eliciting information, then an important part of preparation is to think of relevant questions to pose to the participtants. I have a separate blog on the types of questions and a nice <a href="https://www.hbr.org/">HBR</a> question framework that Product Managers can take advantage of 👇🏻</p><p><a href="https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732">The 5 types of Questions</a></p><h4>5. WHEN: The roles, schedule and logistics</h4><p>The final dimension of the meeting preparation framework is thinking about the role, schedule and logistics.</p><p><strong>Roles</strong>:</p><p>A meeting requires you to organise for people to take on certain roles to make the meeting successful. They are as follows:</p><ol><li><strong>Facilitator</strong>: typically this role is played by the meeting organiser. A facilitator ensures that the meeting is guided according to its structure and rules, and that every participant contributes. This role demands leadership abilities and requires the person to play a prominent but neutral role throughout the meeting.</li><li><strong>Scribe</strong>: is a person responsible to capture accurate and comprehensive notes. These days, it is perfectly fine to seek all participants’ consent and audio / video record the meeting. There are AI tools available to auto-transcribe a meeting down to who-said-what-and-when.</li><li><strong>Timekeeper</strong>: is a person who tracks time and keeps a hold on how much time is spent on each agenda item</li></ol><p>Depending upon the scale and complexity of the meeting, one individual can play all the above roles.</p><p><strong>Logistics</strong>:</p><p>A meeting requires certain logistics to simply enable it or to enhance the quality and effectiveness.</p><p>Logistics includes the meeting room, stationery, flip charts, white boards, sticky notes, projector, audio amplification systems, food, beverages, and so on.</p><p><strong>Schedule</strong>:</p><p>Last, but not the least, the schedule. Due thought must be provided to the duration of the meeting.</p><p>Consider having physical meetings only if it needs 30 min or more. Anything less, you must consider other forms of collaboration, say a simple phone / zoom conference.</p><p>Plan for breaks every 90 min. That is the extent of a human’s attention span.</p><p>If you need more than 90 min, then plan for refreshments.</p><h4>Do you even need a meeting</h4><p>Finally, it is important to give this one aspect a thought — do you even need a meeting? People are frustrated with too many meetings in their calendars already. So, it is a good idea to give them a break.</p><p>Think if you can accomplish your objective with an email, a phone call, IM, Slack, and another alternate collaboration format.</p><p>In the next blog, I will try to cover some best practices to follow while conducting a meeting.</p><p>Thanks much for reading! If you found value in this article, give me a cheer by clapping :) Also, please share it in your network so more people can discover this material.</p><p>Chao! Have a great week ahead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cd2af93c2f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/run-your-meeting-lest-it-will-run-away-6cd2af93c2f6">Run your meeting, lest it will run away</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5 types of Questions]]></title>
            <link>https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d03e9a24732</guid>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[asking-questions]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Thu, 24 Feb 2022 02:35:26 GMT</pubDate>
            <atom:updated>2022-02-25T11:25:01.391Z</atom:updated>
            <content:encoded><![CDATA[<h4>The kick-ass framework for every Product Manager</h4><p>In my previous post, I had shared my story of how my manager taught me the greatest ‘a-ha’ lesson of my professional life. 👇🏻</p><p><a href="https://bootcamp.uxdesign.cc/my-first-aha-learning-of-my-career-2feb9e22547f">My first ‘aha’ learning of my career</a></p><p>TL;DR — The stakeholders are mostly clueless about their own needs, and they are totally allowed to be so. As a Product Manager, it is completely my responsibility to <em>extract</em> user needs by asking probing questions, by inspiring them to think and discover their needs. That is why it is called <strong><em>elicitation</em></strong>.</p><p>It appears, therefore, that <strong>asking questions is an art-form</strong> that we must master to have any hope to succeed in a Product Manager role.</p><p>I’m eager to share with you <strong>five types of questions</strong> and a <strong>framework</strong> for deciding which type of question must be used in what kind of situations.</p><p>So, without further ado, let’s dive in.</p><blockquote><strong>This framework is adapted from the 2015 Harvard Business Review </strong><a href="https://hbr.org/2015/03/relearning-the-art-of-asking-questions"><strong>article</strong></a><strong> authored by </strong><a href="https://hbr.org/search?term=tom%20pohlmann"><strong>Tom Pohlmann</strong></a><strong> and </strong><a href="https://hbr.org/search?term=neethi%20mary%20thomas"><strong>Neethi Mary Thomas</strong></a></blockquote><h4>Five types of questions</h4><p>There are the following five types of questions, actually six.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*uZxFnHwpPn_e51SBp3QbfQ.png" /></figure><p>Everyone knows what open and close ended questions are. Open/Close question-type is the foundation on which the other five types rest.</p><p><strong>Clarifying Questions</strong></p><p>Clarifying questions help <strong>elicit more detail or dig deeper into a specific topic</strong>. For example:</p><ul><li><em>Could you explain the business rule with an example?</em></li><li><em>You said that the customer must call again to raise a release. What is this release, please?</em></li><li><em>You said you run this process every week. Which specific day or days in the week?</em></li><li><em>What do you mean “page should load quickly”? Is it less than 1 sec?</em></li></ul><p><strong>Funneling Questions</strong></p><p>Funneling questions start with broad, open questions and build on the responses by asking narrower, more specific questions. For example:</p><p><em>Q: What is the problem that you are facing at your restaurant?</em></p><p><em>A: I think my customers are dissatisfied</em></p><p><em>Q: Why do you think your customers are dissatisfied?</em></p><p><em>A: Because of the long wait time before they are allotted a table to occupy</em></p><p><em>Q: What makes the wait time so long that they have to be dissatisfied?</em></p><p><em>A: The table turnover is pretty slow. It takes a long time for the customers already at the table to vacate the same.</em></p><p><em>Q: What contributes to the slow table turnover?</em></p><p><em>A: The waiters take a long time to generate the check</em></p><p><em>Q: Why does it take a long time to generate the check?</em></p><p><em>A: Because waiters have to generate the check manually</em></p><p><strong>Elevating Questions</strong></p><p>Elevating questions help stakeholders zoom out when you find them immersed in details, and fail to see the larger context. It helps you raise broader issues. For example:</p><ul><li><em>Are we even addressing the right problem?</em></li><li><em>Let’s take a step back. What is the real issue?</em></li><li><em>What are the larger trends that are at play here?</em></li><li><em>What is the business benefit of having this feature?</em></li><li><em>Why do you think having this drop down field on the search screen will help?</em></li></ul><p><strong>Adjoining Questions</strong></p><p>Adjoining questions help you understand the related aspects of a problem that are ignored during the elicitation session. Adjoining questions are exploratory in nature, and helps us gain a broader understanding of the subject matter. For example:</p><ul><li><em>Are there any other areas where the same issue is applicable?</em></li><li><em>Where else can we use the same solution?</em></li><li><em>Is there anyone else who is impacted by this requirement?</em></li><li><em>If you could change three things in the existing process to make it more efficient, what would they be?</em></li></ul><p><strong>Leading / Rhetorical Questions</strong></p><p>Leading questions help you lead the stakeholders to your line of thought. For example:</p><ul><li><em>A google-like search capability is really what you need here, isn’t it? — </em>leading the stakeholder to believe that this what they need.</li><li><em>Do you think that user interface of this system is providing you with the exceptional user experience that you were expecting? — </em>leading the stakeholder to answer yes or no depending upon the tone you used to ask this question</li></ul><p>Rhetorical questions are those that don’t really expect any response.</p><ul><li><em>Why would anyone not like this feature in the system?</em></li><li><em>How could no one think of this issue?</em></li></ul><p>Leading and rhetorical questions need to be used carefully and sparingly. They do not offer you much in eliciting the needs of the stakeholders. It helps in pushing your opinion on the stakeholders.</p><h4>The Framework</h4><p>Leaving aside the leading/rhetorical questions, let’s slot the remaining four types of questions in a framework. The following 2x2 grid indicates what type of questions should primarily be used in what kind of interaction with stakeholders</p><p>The <strong>scope</strong> of a specific interaction with the stakeholders could be strategic or detailed.</p><p>The <strong>focus</strong> of the interaction could either be to discover or to validate what we already know.</p><p>The framework is simple and is pretty self-explanatory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*IYctDgRYxdAypm0Vyo7pHg.png" /></figure><p>I have extensively used this framework to prepare for every stakeholder interaction.</p><p>The related advantage of this framework is that it forces us to nail down the scope and focus of our interaction. It forces us to ask — what is the purpose of this interaction? — a point when not asked, invariably leads to a failed meeting.</p><p>Thanks for reading. Hope you too will find this framework useful.</p><p>If you liked this piece, do share it in your professional network. Thanks much!</p><p>Chao! Have a great rest of the week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d03e9a24732" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-5-types-of-questions-5d03e9a24732">The 5 types of Questions</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first ‘aha’ learning of my career]]></title>
            <link>https://medium.com/design-bootcamp/my-first-aha-learning-of-my-career-2feb9e22547f?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2feb9e22547f</guid>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[meeting-preparation]]></category>
            <category><![CDATA[asking-questions]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Wed, 23 Feb 2022 05:09:10 GMT</pubDate>
            <atom:updated>2022-02-24T02:53:51.537Z</atom:updated>
            <content:encoded><![CDATA[<h4>“How can stakeholders be so clueless!”</h4><p>“Have you prepped for the meeting tomorrow?”, my manager asked me referring to the upcoming elicitation session the following day.</p><p>The year is 2004. I’m a couple of years into my career, and my first time onsite at the customer location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*jjSzKmiQTjay0bp5UHsirg.png" /></figure><p>This conversation with my manager gave me my first ‘aha’ learning of my career. So here goes…</p><p>“Yes.”, I replied proudly, “I’ve sent out the meeting invite. I am prepared with a voice recorder to record the session. I will also take furious notes.” I tried in vain to appear nonchalant. I was just too impressed with myself. 😌</p><p>“Great. Lemme hear the questions you’re going to ask the stakeholders.”, quizzed my manager.</p><p>“Questions! What questions?”, 😕 I asked nervously. “All I plan to ask is what their needs are.”</p><p>My manager smiled, as though he had predicted this, “ 🙂 I thought so. It doesn’t work that way.”</p><p>He then let me in on the open secret about customers.</p><p>He said, “Stakeholders generally don’t know what they want or need. The sponsor and some senior stakeholders may have some idea. They may know at a high-level, but not wide or deep enough. Definitely not all stakeholders.”</p><p>He continued, “Your job is to ask them probing questions that will get them to think. Remember, in their eyes, you are the expert. They expect you to know what they need.”</p><p>“But…but,”, I protested, “it is <em>their</em> organisation, right? 🤔 They’re facing the problem. How can they not know what they want? 🙄”</p><p>“Let’s see.”, my manager said as he cogitated something, and continued, “Imagine you have a plot of land, and decide to construct a house there…your dream house.”</p><p>“Okay.”</p><p>“You enlist an architect to help you design your dream house, right?”</p><p>“Sure.”</p><p>“What do you expect the architect to do for you? I don’t mean what output you need them to produce…not the blueprint, plan. That they will for sure. But, really, what do you expect them to do?”, my manager probed.</p><p>“Well, I look forward for the architect to understand my taste and needs, and develop a plan for my house that reflects me and my family.”, I said.</p><p>“Great. But what if the architect just sits there with a paper and pen, and asks you, <em>‘go on…tell me what you need.’</em> Would you be able to articulate all that you would need in your house? It is <em>your</em> dream house, remember. Given your logic, you ought to know everything you need, right?”, my manager posed a thinker of a question to me.</p><p>“Well, no. Not really. I don’t know much of what is possible. The architect is the expert. So I expect them to help me out.”, I retorted.</p><blockquote><strong>“Exactly. That is exactly how our stakeholders think of us. Experts. And they expect us to help them out.</strong></blockquote><blockquote><strong>It is your responsibility to open them up, inspire them to think and give you the answers you’re looking for.</strong></blockquote><blockquote><strong>And for doing that, you got to prepare well, prepare in advance.”, said my manager, resting his case.</strong></blockquote><p>That was among the first ‘a-ha’ moments for me in my professional life.</p><p>It dawned on me that it would be terribly stupid and inconsiderate of me to quip, “I can’t believe the stakeholders are so clueless. How can they not know anything about what they want?”</p><p>That day, I realised that it is I, who must be in control of my elicitation sessions. I have to direct my conversations in a way that is productive for the assignment that I’ve set out to execute.</p><p>Thanks for reading folks! Follow <a href="https://medium.com/u/caa140c621a4">Product Fundas</a> for more stories. If you like what you read, do share it on Twitter or LinkedIn or wherever your network resides.</p><p>Also, do check out the following stories.👇🏻</p><ul><li><a href="https://bootcamp.uxdesign.cc/you-are-a-glorified-stenographer-5eea2b892a69">“You are a glorified stenographer”</a></li><li><a href="https://bootcamp.uxdesign.cc/it-should-be-black-in-color-24e3756d0157">“It should be black in color”</a></li><li><a href="https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2">The 4Ps that every Product Manager and Business Analyst must know</a></li></ul><p>So long! Have a great rest of the week!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2feb9e22547f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/my-first-aha-learning-of-my-career-2feb9e22547f">My first ‘aha’ learning of my career</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[P for Parts — One of the 4Ps…3 of 3]]></title>
            <link>https://medium.com/design-bootcamp/p-for-parts-one-of-the-4ps-3-of-3-98b87513599a?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/98b87513599a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[conceptual-model]]></category>
            <category><![CDATA[visual-thinking]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Mon, 14 Feb 2022 16:19:05 GMT</pubDate>
            <atom:updated>2022-02-15T06:34:18.323Z</atom:updated>
            <content:encoded><![CDATA[<h3>P for Parts — One of the 4Ps…3 of 3</h3><h4>Chapter Three: Step up the critical thinking</h4><p>Hey Welcome back!</p><p>This is the final chapter of the series on Conceptual Data Modelling, a technique that wrings out the last ounce of critical thinking in you, and delivers to you insights about a business domain that you wouldn’t otherwise have acquired.</p><p>This is the final chapter in the series. If you have not had a chance to review the first two chapters, here they are. Please review them in that order, lest the series will not make sense to you.</p><ul><li><a href="https://bootcamp.uxdesign.cc/p-for-parts-one-of-the-4ps-f55b267dd5ec">P for Parts — one of the 4Ps</a></li><li><a href="https://bootcamp.uxdesign.cc/p-for-parts-one-of-the-4ps-e196204cedb5">P for Parts — One of the 4Ps</a></li></ul><h4>What is the Merchandising Firm’s core value proposition?</h4><p>At the end of Chapter Two, we ended with a set of questions to ponder over:</p><ul><li>What is this release?</li><li>Why should a customer place an order first, and later raise a release for delivery? Isn’t that bad CX?</li><li>Does ‘bulk’ Order have any relevance here?</li></ul><p>The answer to these questions lies with another underlying question: What is the Merchandising Firm’s business? What is their core value proposition?</p><p>A Merchandising Firm is obviously not a retailer: you cannot explain the concept of a ‘release’ in a retailer context. A Merchandising Firm is also not a producer/manufacturer: it just doesn’t make sense to explain the existence of a supplier their domain.</p><h4>Could the Merchandising Firm be a B2B player?</h4><p>That is the only space that makes sense given everything we know so far.</p><p>Let’s explore this B2B idea a bit more.</p><blockquote><strong>As you read the following paragraphs, please notice how this conceptual data modelling technique forces you through a path of critical thinking leaving you with valuable domain expertise when you emerge at the other end.</strong></blockquote><p>If the Merchandising Firm is indeed a B2B player, then who are its Customers and Suppliers that we know for sure are a part of the firm’s domain.</p><h4>The Merchandising Firm’s Customers</h4><p>What Customers find it acceptable to place one or more Orders first, and then separately raise Releases against those Orders? And why? Surely they are not retail consumers (we’re exploring B2B, remember!).</p><p>Let’s assume for a minute that these Customers are retail businesses, as in stores where consumers come to shop. It is understandable that retailers don’t want to order too much (inventory carrying costs), nor too less (stock-out costs).</p><p>Ergo, retailers would want to place bulk orders (based on rough estimates). Why? Because, they don’t need to accept delivery of the bulk order. They only need to accept delivery of, and pay for, the ‘Releases’, which they will raise when they need more stock. This provides awesome flexibility for them.</p><h4>The Merchandising Firm’s Suppliers</h4><p>On the other side, the Suppliers are manufacturers. They don’t want to manufacture too much (inventory costs), nor too less (opportunity costs)</p><p>The Firm aggregates all the orders by Product and places a large quantity order with the Suppliers. The Supplies may invoice the Firm on these orders. This is obviously beneficial for the Suppliers.</p><p>In return, the Firm asks the Suppliers to provide favorable pricing and have them ship the releases to specific locations.</p><p>The problem that the Firm solves is truly critical at both ends — inventory management. The Firm takes on the inventory risks from either side and make their margins on the price spread on huge volumes</p><blockquote><strong>Please reflect on how much domain knowledge we’ve acquired simply by thinking critically, especially on release and order, guided by the rigor of domain modeling. I realise that I’m emphasising this point one too many times. But that is how important I believe it is.</strong></blockquote><h4>Back to the Conceptual Data Model</h4><p>Here is your notes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*_bI9PHy75I4NId8SOVP26A.png" /></figure><p>Here’s the model we’ve developed so far:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DRyyp8Bgmy7oXdHJBO2E5Q.jpeg" /></figure><h4>Step 10:</h4><p>We still need to associate Release to something.</p><p>Is it Order? It appears so, because your notes says that clearly: <em>“…release can be against several orders”.</em></p><p>But if we think deeper, the Customer will ask for release of <strong>Products.</strong></p><p>Should be therefore associate Release and Product? Not really. Because, only Products that are a part of one of the Customer’s earlier Orders, can be Released.</p><p>So which entity provides us with information of both Order and Product? The Order Line.</p><p><strong>So Release must be associated with Order Line</strong></p><p>How about multiplicity? A Release can be for one of more Products. A given Product can be released in one or more Releases. So it is many to many association.</p><p>Let’s break it. Why? Because there is an important business attribute called Release Quantity, which can neither be part of Release nor Order Line entities.</p><p>The joining entity is <strong>Release Line</strong>, which will house Release Order Quantity attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hGLRCCus0PgQYUNm4a-oAA.jpeg" /></figure><h4>Step 11</h4><p>The last loose end to tie is this statement from your notes: <em>“The releases are always supplied by a single supplier”</em></p><p>Now that we know what the business meaning of Release is, we understand that a Customer raises one Release for a bunch of Products with its individual Release Quantity.</p><p>A good CX will dictate that the Customer gets one Release Number. It does not make sense to create multiple Release Numbers, right? In fact, this is a good question to go back to the stakeholders with. Maybe they don’t realise it, and they might appreciate your insight.</p><p>But then here is a point to ponder: why would the stakeholder make it a point to emphasise that releases are always supplied by a single supplier? If we think critically, this means that all the products in the release, which are supplied by a given supplier must be bundled together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ox2KcYKirG85ym9eq8tpqg.jpeg" /></figure><p>That’s it. This is our final Conceptual Data Model.</p><p>Which, by the way, is less important. What is more valuable is the domain expertise we’ve gained as a result of the critical thinking enforced by the grammar of the model.</p><p>Thanks for reading folks!</p><p>If you enjoyed reading this three part series, do let me know. I will create more such series for a bunch of other techniques that are quite valuable for a Product Manager.</p><p>So long guys. Chao…have a great rest of the week. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98b87513599a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/p-for-parts-one-of-the-4ps-3-of-3-98b87513599a">P for Parts — One of the 4Ps…3 of 3</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[P for Parts — One of the 4Ps]]></title>
            <link>https://medium.com/design-bootcamp/p-for-parts-one-of-the-4ps-e196204cedb5?source=rss-caa140c621a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e196204cedb5</guid>
            <category><![CDATA[critical-thinking]]></category>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[domain-expertise]]></category>
            <category><![CDATA[business-knowledge]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Product Fundas]]></dc:creator>
            <pubDate>Sat, 12 Feb 2022 02:56:50 GMT</pubDate>
            <atom:updated>2022-02-14T13:38:22.887Z</atom:updated>
            <content:encoded><![CDATA[<h3>P for Parts — One of the 4Ps…2 of 3</h3><h4>Chapter Two — Rigour in Thinking</h4><h4>The Background Story</h4><p>In Chapter One we looked at a (common) scenario where you, a Product Manager, are assigned to attack a problem space in which you do not have deep enough domain expertise.</p><p>If you have not reviewed Chapter One yet, please do so now before you proceed with Chapter Two:</p><p><a href="https://productfundas.medium.com/p-for-parts-one-of-the-4ps-f55b267dd5ec">P for Parts — one of the 4Ps</a></p><h4>Get a cuppa java</h4><p>and pens and a stack of plain paper.</p><p>In this chapter, I will walk you through a technique that you can apply to analyze exactly such vague, abstract scenarios, and <strong>emerge with a deep sense of domain understanding</strong> on the other side.</p><p><strong>This is an important analysis technique for all Product Managers. </strong><br>It is called <strong>Entity-Relationship Diagram (ERD)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*YuNg4jO8uuKNVj-ER3S1YA.jpeg" /><figcaption>The most famous meme in history — 🙌🏻 to Mr. Mohd. Sarim Akhtar</figcaption></figure><blockquote>I know, right? An ERD? Come on! ERD is a tech artifact, isn’t it? The tech folk like DB Architects use this. Why should a PM be interested in this?</blockquote><p>Trust me, this technique is more business than tech. More product definition than implementation. More useful to a Product Manager than it is to a techie.</p><p>Ready? Great, let’s dive in.</p><p>Oh, and do get that cuppa java. Also, a pen and a stack of A4 paper</p><h4>Conceptual Data Model</h4><p>This analysis technique is known as Business Domain Modelling or Conceptual Data Modelling.</p><p>In this technique, we analyse one of the 4Ps of cracking a business domain — Parts (or Data).</p><blockquote><strong>The Conceptual Data Modelling technique has its own grammar or syntax. This grammar imposes on us some rigorous critical thinking. This critical thinking helps us discover the domain and ultimately crack it open.</strong></blockquote><blockquote><strong>You’ll see. 🙂</strong></blockquote><h4>Step 1</h4><p>In Chapter One, we introduced the merchadising firm scenario, where you took some serious notes.</p><p>We first identify all the NOUNS in your notes, as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*_bI9PHy75I4NId8SOVP26A.png" /></figure><h4>Step 2:</h4><p>Let’s bring all the nouns into a visual model one by one.</p><p>First in, the Merchandizing Firm. Draw a large enough rectangle on that A4 page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHtV_1eSSksd7YB_seFNWw.jpeg" /></figure><p>This rectangle represents the Merchandizing Firm. The rectangle is the busines domain that we’re modelling. It represents the business domain that we hope to understand better.</p><p>Actually, scratch that, we’re not modeling the entire business domain. Not all the aspects of the domain will be modelled. We will <strong>only model the P for Parts or ‘data’ aspect of the domain</strong>, and even in there, we’ll focus on just those data that we know are significant to the business domain.</p><p>Remember — don’t boil the ocean.</p><p>If you don’t get this reference about the ocean, please refer to this post:</p><p><a href="https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2">https://bootcamp.uxdesign.cc/the-4ps-that-every-product-manager-and-business-analyst-must-know-932fd7ac6af2</a></p><h4>Step 3:</h4><p>Let’s move on to the first line in your notes. Let’s get customers and suppliers into the model.</p><p>Customers and suppliers are outside but interacting with the business. Let’s model them as such.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wsxphl6ut9mJGSRxZmbZlg.jpeg" /></figure><p>The notations that we will use here are from <strong>UML — Unified Modelling Language.</strong></p><p>This notation for Customer and Supplier is called *<strong>BUSINESS ACTOR</strong>* — those outside the domain, and interact with the domain.</p><blockquote><strong>The grammar, syntax, or rules of Domain Modeling are important. That is what creates the rigor in our thinking. And that thinking helps us discover the domain.</strong></blockquote><h4>Step 4:</h4><p>Then your notes say that <em>“</em><strong><em>customers</em></strong><em> place bulk *</em><strong><em>orders</em></strong><em>* with the firm’s *</em><strong><em>order entry clerk</em></strong><em>* for *</em><strong><em>products</em></strong><em>*”</em></p><p>The Order Entry Clerk is within the domain — a <strong>BUSINESS WORKER</strong> — interacting with the Customers. Business Workers are those inside the domain and interact with the Business Actors.</p><p>Order and Product are called <strong>BUSINESS ENTITIES</strong> — a logical grouping of related atomic data.</p><p>Order is a logical group of atomic data like Order Number, Order Date, and so on. Product is a grouping of atomic data like Product Number, Product Name, Description, Image, and so on.</p><p>These atomic data are called <strong>BUSINESS ATTRIBUTES</strong>. Business Entities are composed of Business Attributes.</p><blockquote><strong>Any given Business Attribute must reside in one and only one Business Entity. Of course, every rule has an exception and we’ll get to this in a minute.</strong></blockquote><h4>Step 5:</h4><p>Customer places Order.</p><p>There is an <strong>ASSOCIATION</strong> between Customer and Order. The green line between Customer and Order is the association, as is the green line between Order Clerk and Order. The words ‘<em>places</em>’ and <em>‘creates’</em> are the <strong>RELATIONSHIPS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5wavRw9y0jp8PK3DYxuK0w.jpeg" /></figure><blockquote><strong>Quick detour: Should we associate Customer and Order Clerk? Why? Why Not? If yes, what is the relationship? Think about it.</strong></blockquote><h4>Step 6:</h4><p>Here’s a couple of Qs: <br>- How many Orders can a given Customer place?<br>- How many Customers can place a given Order?</p><p>The answers are obviously:<br>- Many<br>- One and only One</p><p>Right?</p><p>This is called <strong>MULTIPLICITY</strong> or <strong>CARDINALITY</strong>. Let’s represent them in the model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p_r7IJlIs0v5EGnHfNr1NA.jpeg" /></figure><p>Here’s a related Qs:</p><ul><li>What is the minimum Order that a Customer must place to be recognized as a Customer?</li><li>Does the firm recognize a Customer even if they haven’t yet placed a single order? If yes, then it is 0..n</li><li>Or does the firm create a Customer ONLY when they place their first Order? In this case, it is 1..n</li></ul><p>Who can answer these Qs? The business stakeholders, of course.</p><p>But as a PdM, we now know another important aspect of the business that our product must support. For now, let’s assume it is 1..n and progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uXkrj4FVOJaqY8USvwWMSQ.jpeg" /></figure><blockquote><strong>These are really important aspects of how the business operates. And different firms operate differently.</strong></blockquote><blockquote><strong>What you must notice here is this: the rigor of thinking imposed by the syntax of domain modeling forced us to ask these questions that we might otherwise have easily missed, glossed over or skipped.</strong></blockquote><h4>Step 7:</h4><p>Let’s now look at Order and Product.</p><p>Obviously, there is an association between them. Order is <strong><em>for</em></strong> Products.<br>What about multiplicity? How many Products in a given Order? Minimum one, right? You can’t have an order with no products, can you?. And maximum? Any number, isn’t it?</p><p>So <em>one</em> Order is for <em>one or many</em> Products</p><p>Further, each Product in the Order will have individual Order Quantity.</p><p>For e.g., consider the table below. The Order O101 from Mary is for 8K pens, 15K sharpeners, 7.5K notebooks, and 3.8K erasers. This order has <em>four</em> Products, and each Product with different order quantities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Bm2IA2z28aFetMV2paSFQ.jpeg" /></figure><p>Now let’s look from the Product side. How many Orders could each Product be a part of ? For the table above, the Product Pen is ordered in O101, O103 and O105. And as time progresses, each Product will be a part of many orders.</p><p>Ergo, the <em>multiplicity</em> between Order and Product is Many to Many.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUrnda1LmYzh87hxfj8x6Q.jpeg" /></figure><h4>Step 8:</h4><p>Now here’s a pickle: Order Quantity is one piece of data. It is an important piece of atomic data, or an attribute.</p><p>Which entity would <strong>Order Quantity</strong> be an attribute of? Order or Product?</p><p>If you say Order, then Order Quantity of which Product? Because there is room for only ONE quantity in the attribute.</p><p>If you say Product, then Order Quantity for which Order?</p><p>So the answer is, Order Quantity can be an attribute of neither Order nor Product.</p><p>The only way to resolve this is by adding a third entity that connects Order and Product, and Order Quantity will be an attribute of this third connecting entity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IW7t7nHiqsfeKC2HatgLSA.jpeg" /></figure><blockquote><strong>This is called <em>Normalization</em> in DB lingo. But that is not why we’re doing this.</strong></blockquote><blockquote><strong>We added this third connecting or joining entity because an important Business Attribute — Order Quantity — needed a rightful home.</strong></blockquote><blockquote><strong>And if you look deep, right now, something about the business domain has clicked into place inside your brain somewhere.</strong></blockquote><p><strong><em>Step 9:</em></strong><br>Let’s connect Supplier and Product. Your notes say: “The products are supplied by many suppliers.”</p><p>Can there be a more vague statement than this? Let’s try to decipher it. Add multiplicity to the modle to validate if it checks out.</p><p>Is it Many to Many? i.e., a given supplier can supply 1 or more products. And, a given product can be supplied by 1 or more suppliers.</p><p>OR</p><p>Is it One to Many? i.e., a given supplier can supply 1 or many products. And, a given product can be supplied by one and only one supplier.</p><p>The answer is: we don’t know. See the non-clarity in the statement now?</p><blockquote><strong>I wish to draw your attention again to the fact that this non-clarity surfaced because of the rigor in thinking imposed by the syntax of domain modeling.</strong></blockquote><blockquote><strong>Each such clarification adds to domain clarity and consequently to the quality of product definition.</strong></blockquote><p>Let’s move ahead…</p><h4>Step 10:</h4><p>“Customers raise releases with shipping clerk”</p><p>Some Qs to ponder over:</p><ul><li>What is this release?</li><li>Why should a customer place an order first, and later raise a release for delivery? Isn’t that bad CX?</li><li>Does ‘bulk’ Order have any relevance here?</li></ul><p>Give it a think? Maybe you want to comment your thoughts first.</p><p>This is the end of Chapter Two.</p><p>In Chapter Three, let’s make progress to this domain modelling exercise, and take it through completion.</p><p>Thanks for reading! I appreciate your time. Do share this post far and wide. Thanks much!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e196204cedb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/p-for-parts-one-of-the-4ps-e196204cedb5">P for Parts — One of the 4Ps</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>