<?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 Swapnil Baheti on Medium]]></title>
        <description><![CDATA[Stories by Swapnil Baheti on Medium]]></description>
        <link>https://medium.com/@sbaheti56?source=rss-b81c6af40276------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hvPMvFukw5XopqlQhS96Jg@2x.jpeg</url>
            <title>Stories by Swapnil Baheti on Medium</title>
            <link>https://medium.com/@sbaheti56?source=rss-b81c6af40276------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:52:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sbaheti56/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[Summary — Harward Business School — How to get started with Entrepreneurship]]></title>
            <link>https://medium.com/@sbaheti56/summary-harward-business-school-how-to-get-started-with-entrepreneurship-16f7ab12988b?source=rss-b81c6af40276------2</link>
            <guid isPermaLink="false">https://medium.com/p/16f7ab12988b</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[harvard-business-school]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Swapnil Baheti]]></dc:creator>
            <pubDate>Sat, 11 Mar 2023 15:07:16 GMT</pubDate>
            <atom:updated>2023-03-11T15:07:16.543Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary — Harward Business School — How to get started with Entrepreneurship</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldh7cOmaIwHZiwoCc_k5JA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16f7ab12988b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Summary — How to get started with Entrepreneurship]]></title>
            <link>https://medium.com/@sbaheti56/summary-how-to-get-started-with-entrepreneurship-2d1cf1293c16?source=rss-b81c6af40276------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d1cf1293c16</guid>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[harvard-business-school]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <dc:creator><![CDATA[Swapnil Baheti]]></dc:creator>
            <pubDate>Thu, 23 Feb 2023 11:15:49 GMT</pubDate>
            <atom:updated>2023-02-23T11:15:49.453Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldh7cOmaIwHZiwoCc_k5JA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d1cf1293c16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Continuous Discovery Habits” Book Summary for Product Teams]]></title>
            <link>https://medium.com/@sbaheti56/continuous-discovery-habits-book-summary-for-product-teams-7f1e9c82841d?source=rss-b81c6af40276------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f1e9c82841d</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Swapnil Baheti]]></dc:creator>
            <pubDate>Sun, 08 May 2022 11:17:55 GMT</pubDate>
            <atom:updated>2022-05-08T11:20:23.559Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Rn5X-nHJUMBOydcxherzKA.jpeg" /></figure><ol><li>Obviously, there’s a clear distinction between two major activities — discovery &amp; delivery. Discovery — is never one-time activity. If you are doing it for one-time then you are part of a project (Not Product)— requirement given at the annual budget meeting and the product manager&#39;s job is to translate req to the engineering team.</li><li>Agile is perfect to ensure continuous discovery — companies are now so aware of agile processes, knowledge, and training but their emphasis on using agile for delivery and not for discovery — ultimately it targetted to deliver (more) output — whereas discovery is a continuous process to ensure a user is generating value.</li><li>keeping customer focus at the centre of the epicentre is the most important thing for your business.</li><li>Discovery starts with problem defn to solve — then considering opportunity space, scope, existing players and market — taking ahead specific opportunity based on some analysis — brainstorming ideas around opportunity — some solution — prototype — test and LOOP — n number of loops around each promising idea. The same can be done with n number of opportunities. An ultimate list of all probable solutions from all opportunities combined can lead us to product definition somewhere.</li><li>The word — outcome — psychologically — puts responsibility, ownership, and autonomy for team members (instead of output)</li><li>During user research/interviews — Instead of asking “what criteria do you use when purchasing a pair of jeans” — we could ask<br> “Tell me about the last time you purchased a pair of jeans” — this will help uncover what criteria our participant used while purchasing one<br> your customer’s actual behaviour — their reality not the story they tell themselves</li><li>If the participant requests a specific feature or solution, ask about why they need it and capture the opportunity — you could ask “if you had that feature, what would that do for you?”</li><li>Common Anti-patterns to avoid here are<br> o Getting bogged down in endless debates on minute details<br> o Using words instead of visuals — the more you draw the more you will realize that drawing is a superpower<br> o Moving forward as if your map is true — a draft could go through multiple refinements before we take the next step in the process<br> o Forgetting to refine and evolve the map as you learn more — continuously synthesize what you collectively know and have a shared understanding of customer context</li><li>When we interview users and hear about their wishes, pain points needs..each story gives many opportunities. Good idea to create an opportunity backlog as a product backlog. Many times when we look at multiple opportunities (Smaller or bigger) we can see the relation between them — we can either group them together or create an opportunity tree — as parent-sibling relationships</li><li>Common Anti-patterns to avoid here are<br> o Opportunities framed from your company’s perspective — and not from the customer’s perspective<br> o Vertical opportunities — when you get narrow-focused, where we have a parent with only one child, who in turn has only one child — creating a vertical stack. Good to explore the parent to get a broader picture in future interviews<br> o Opportunities have multiple parent opportunities — top-level opportunities represent distinct moments in time and hence should not have two parents<br> o Opportunities are not specific — opportunities that represent themes, design guidelines, or sentiment aren’t specific enough. In such cases, focus on specificity to make a good opportunity<br> o Opportunities are solutions in disguise — important to distinguish between a solution and an opportunity. E.g., “I wish I could fast forward through commercials” could mean that he “does not like commercials” and so we might ask how might we address I don’t like commercials?<br> o Capturing feelings as opportunities — customer expressing emotion in an interview could mean there is an opportunity behind the emotions. Try to understand the cause of these feelings — and that could get to the bottom of what the customer actually needs</li><li>Typically, most of our conversations happen in the solution space with product teams talking about shipping the next release, building roadmaps, backlogs etc. Melissa Perri calls this the “build trap”. It is important to keep in mind that product strategy does not happen in the solution space — it happens in the Opportunity space</li><li>Researchers measure creativity using three primary criteria — fluency<br> (number of ideas we generate), flexibility (how diverse our ideas are) and originality (how novel an idea is)</li><li>We need to push beyond our first mediocre and obvious ideas and delve into the realm of more diverse original ideas</li><li>Four rules for brainstorming<br> o Focus on quantity — generate as many ideas as you can<br> o Defer judgement and separate idea generation from idea evaluation<br> o Welcome unusual ideas<br> o Combine and improve ideas</li><li>Common Anti-patterns to avoid here are <br>o Limiting ideation to one session — do not expect to have ideas brainstormed and<br>o generated by scheduling a 1-hour meeting</li><li>Assumptions test, the various types of assumptions are<br> o Desirability assumptions — does anyone want it? Will we be able to provide value for it?<br> o Viability assumptions — should we build it? Would it be viable for the business to get ROI<br> o Feasibility assumptions — can we build it? What is feasible for the business?<br> o Usability assumptions — is it usable? Can customers find what they need?<br> o Ethical assumptions — is there any potential harm in building this idea</li><li>Some ways to pre-test<br> — story map<br> — Pre-Mortem — which happens at the beginning of the project and is designed to map out what could go wrong in the future.<br> “Imagine it is six months in the future, your product has launched and is a complete failure. What went wrong” — generate reasons why your product might fail — and you are exposing assumptions that your idea that depends on it may not be true. “My worst nightmare” — from Innovation games could be an example of Pre Mortem</li><li>Common Anti-patterns to avoid are<br> o Not generating enough assumptions — good to have at least 20–30 assumptions for an idea<br> o Phrasing assumptions that you need them to be false — in other words phrasing them negatively — Customers won&#39;t remember their passwords<br> o Not being specific enough — generic assumptions will not help<br> o Bias toward one category at the cost of other categories</li><li>When we present our conclusions, we tend to focus on the outputs — the roadmap, release plan or the backlog. It is good to share the journey the team took to arrive at those conclusions<br> • The journey includes showing the opportunity solution tree, the desired outcome, the prioritization of items, the target opportunity, story maps, assumption tests and sharing the solutions generated.<br> • When we show our work we are inviting our stakeholders to co-create with us. We share our work and invite them to assess our thinking and add their own</li><li>Common anti-patterns<br> o Telling instead of showing<br> o Overwhelming stakeholders with unnecessary details<br> o Arguing with stakeholders about why their ideas won&#39;t work<br> o Trying to win the ideological battle instead of focusing the decision on the hand</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f1e9c82841d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“HOOKED” Book Summary For Product Managers & Product Teams]]></title>
            <link>https://medium.com/@sbaheti56/hooked-book-summary-for-product-managers-product-teams-9b9f1ee3771?source=rss-b81c6af40276------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b9f1ee3771</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-marketing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Swapnil Baheti]]></dc:creator>
            <pubDate>Sun, 16 Jan 2022 09:58:31 GMT</pubDate>
            <atom:updated>2022-01-16T10:06:42.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOftWxB-lkzj6ldOZqkZ0w.png" /></figure><p><strong>First thing first</strong> <br>Question to ask yourself/your team, before understanding the process to hook your users. <br>1. What habits does your business model require?<br>2. What problems are users turning to your product to solve?<br>3. How do users currently solve that problem and why does it need a solution?<br>4. How frequently do you expect users to engage with your product once they are habituated?<br>5. What user behaviour do you want to make into a habit?</p><p><strong>First Step to Hooked: Trigger </strong><br>1. Identify the user.<br>2. Identify users daily habits, beside or just before your intended habit <br>3. Place triggers that will help users to take action. Put at least 3 of them. (Ideation part — finding simple, easy, conventional, crazy stuff)<br>4. Check if you have identified internal trigger <br>5. Check if the timing of internal trigger and external trigger are so close to each other <br>6. Check if it’s happening as “every time user does this (trigger) he would do this (intended habit)”</p><p><strong>Second Step to Hooked: Action</strong> <br>1. There must be a combination of motivation, ability and trigger (MAT) happening at the same time <br>2. Motivation — fear or hope, acceptance or rejection (by society), pain or pleasure (all these can be applied and checked or say contribute either to increase or decrease user usage)<br>3. Ability — only refer to the action of making it as easy as possible). <br>Observe impediments on the user’s journey in your product<br>- if time <br>- If money <br>- If physical effort <br>- If the brain cycle <br>- If social deviance <br>- If non-routine<br>4. Trigger — We already talked</p><p><strong>Third Step to Hooked: Rewards </strong><br>1. Rewards must fit the narrative of why the product is used and align with the user&#39;s internal triggers and motivation. <br>E.g. You cannot necessarily attract users to the QnA site with monetary rewards. If the motivation was money in the first place, then the user definitely can find other ways to earn better money utilising that time. <br>Even points, badges and leaderboards can prove effective only if they scratch users’ itch. <br>No amount of gamification would help if there’s a mismatch between the customer’s problem and the product’s assumed solution. <br>2. Direction to design a reward system <br>A) rewards of the tribe — gratification from others <br>B) rewards of the hunt — material goods, money or information <br>C) rewards of the self — mastery, completion, competency or consistency</p><p><strong>Fourth Step to Hooked: Investment </strong><br>1. Look what is there in your product which users are having as their investment. If not, can you think of some ways to make it happen, maybe some shorter ways to make users such investments? Be careful, a user should be a little engaged, motivated and had trigger placed…and get invested slowly.</p><p><strong>Hooked Four Steps: Summary of Summary</strong> <br>1. What does your user want? What is the pain that your product is relieving? (Internal trigger) <br>2. What brings the user to your service (external trigger) <br>3. What is the simplest action a user takes (or can we make it simpler) in anticipation of rewards?<br>4. Are users fulfilled by rewards, still left wanting more? (Variable rewards) <br>5. What “bit it work” do users invest in the product? Does it load the next trigger and carry any value to improve the product with use and time.</p><p><strong>Understanding Manipulation Matrix</strong> <br>- Deciding between facilitator, peddler, entertainer and dealer based on two questions if the maker does use the product and it materially improves users life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*sWpzGE6-rXSxHzTo1_1Usw.jpeg" /></figure><p>- Overall, it’s just a way to understand if you are proud of your way to influence people</p><p><strong>Understanding Habit Testing</strong><br>The process to find product devotees and understand from them about product elements which are habit forming, why and which product elements changing user behaviour <br>Three steps <br>1. Identify — how people using the product <br>2. Codify — new hypothesis. Actual path(Habit path) followed by user and <br>3. Modify — accordingly changes to be done in the product, if any</p><p>Lastly, <br>- Brainstorm new (at least five) interfaces that can introduce opportunities or threats to your business</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b9f1ee3771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“INSPIRED” Book Summary For Product Managers & Product Teams]]></title>
            <link>https://medium.com/@sbaheti56/inspired-book-summary-for-product-managers-product-teams-b4eb63487661?source=rss-b81c6af40276------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4eb63487661</guid>
            <category><![CDATA[product-team]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[inspired]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-culture]]></category>
            <dc:creator><![CDATA[Swapnil Baheti]]></dc:creator>
            <pubDate>Tue, 23 Nov 2021 09:34:56 GMT</pubDate>
            <atom:updated>2021-11-23T09:44:41.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*t5E2d18bmW6qjw7q4B8Ubw.jpeg" /><figcaption>Inspired Book Summary</figcaption></figure><p><strong>Product Culture</strong></p><ol><li>The celebration should be around achieving business objectives and not release</li><li>Obsession should be over referenced customer rather than on competitors</li><li>Freedom to try new ideas, ways at every level instead of approval to run even a test</li><li>Tips for culture change <br> — One-week design spring to work on the major problem <br> — Pilot team for new things/processes <br> — Showing results — talking about results every time — when followed old process or system and if results are not favorable then proposing new ways</li><li>It’s a high team we target or report the number of features we developed. Can we start talking in a way about, number of problems we solved? Maybe small, medium, large</li><li>While building product — reference customer is a very nice method — having 6 different reference customers of the same type — to validate product</li><li>For any product, if one user refers another user — nothing like it</li></ol><p><strong>Product Team Mindset</strong></p><ol><li>Things for designers to keep in mind <br> — how will customers learn about the product?<br> — How to onboard first-time users?<br> — How gradually onboard for newer functionality?<br> — How will users interact at different times of the day?<br> — What Other things compete for the user’s attention?<br> — difference between the 1-month-old customer and 1 year old?<br> — Motivating users to a higher level of commitment to the product?<br> — Creating moments of gratification?<br> — how will users share experiences with others?<br> — How will customers receive offline experience?<br> — What is the perceived responsiveness of the product?</li><li>Ideas from other team seniors and leaders should be welcomed</li><li>Should not consider that we can anticipate the user’s response. Always test with real users</li><li>The company has earned its reputation and brand value. It’s the product team&#39;s responsibility to keep it going and capitalize on it.</li><li>Engineers/designers or say, team members — very important that they get a chance for user visits. Users ultimate pain should be felt, understood together, at the same time or say at the Same level</li></ol><p><strong>Product Manager Mindset</strong></p><ol><li>A good product manager — have technology sophistication, business savvy, credibility with key executives, deep customer knowledge, passion for the product, respect for the product team, and one of the organization’s best talents, if not the best.</li><li>Things to keep in mind as a leader <br> — keep everyone empowered and autonomous, although they just work on a small part of the whole<br> — Keeping holistic view product in everyone’s mind all the time <br> — Encourage accountability, although CEO has all the powers <br> — Calmly resolving and understanding dependencies</li><li>Genuine care for the customer and problem-solving approach one side while the utmost amount of interactions, respect, empathy and help to empower your teammates — especially engineers and designers — these two would always help in any situation, any product, any company. Now of course another question arises that why your team would help or respect you <br> — be knowledgeable about your work <br> — Do complete work. Do extra than what was needed <br> — Be skillful <br> — Have depth product, knowledge, and customer knowledge <br> — Transparent and true — you know what you know and you don’t know what you don’t know</li><li>The company has earned its reputation and brand value. It’s the product team&#39;s responsibility to keep it going and capitalize on it.</li><li>Important for a product manager to understand the difference between user tests, product demo, and walkthroughs. Often appear as similar activity as everything involves showing a prototype but the purpose is different in each of them. In user tests, you want honest feedback about the product, you are there for quick learning and discovery mode. In a demo, you must showcase your feature and make an impression about your product and the value you are providing. A walkthrough is for your stakeholders with utmost honesty and transparency so they can spot faults or loopholes or arising challenges/issues. Often people do a demo/walkthrough to everyone.</li></ol><p><strong>Product Fundamentals</strong></p><ol><li>Before we start working or thinking about any product, the first question we can ask is about in which stage the product is now. Inception/growth/matured/rehab. Action items, processes, approaches will change accordingly as it helps define the desired state to go clearly.</li><li>Risk management is just not for document, and it’s required, Maybe in mind or discussion, but clearly require at every stage. Asking the same questions at every stage? Do people need it? Will people be able to use it well? Can the engineering team really implement it the way it’s envisioned? And Maybe a backup plan for everything. Also, if not a backup plan, then understanding the risk of things to lose upon.</li><li>Product — which problem to solve? With what feature? How to build (engineering)? How to present (UX)? How can we even earn to achieve sustainability (Business)?</li><li>Holistic product definition — worrying about also merchandise on the e-commerce website, worrying about content on OTT. Basically, also about offline things or things that maybe not be part of the software directly. Example — In an educational product. Keeping content/question concern on very low priority and focusing more on the extra modules and features, is surely not the holistic product definition.</li><li>Fundamentally product manager is responsible for things that will be developed and today engineers/designers want to see some evidence/data to understand the worthiness of the feature which you are asking</li><li>Product discovery stage (one can apply this at every level like from business to feature) <br> — is it useful? — product/idea/user pain/problem/req<br> — Is it usable? — UX <br> — is it feasible to build? — Engineer <br> — Can it (ever) be monetized? Business<br> And this should not be the product manager (or anyone’s) opinion but should have evidence/research behind each point</li><li>Very important…fall in love with the problem and not the solution.</li><li>Just because someone can use your product, doesn’t necessarily mean they will choose to use your product. There’s a big difference and you need to work on that difference. In the end, it’s a big journey from finding value to starting using/subscribing/purchasing it and stopping using their old solutions for the same needs.</li></ol><p><strong>Product Team Working Methodology</strong></p><ol><li>Product, design, engineering should sit/work side by side and not through the exchange of documents and meeting requests</li><li>Engineers should be involved right from research instead of seeing prototype during sprint plan, that too for estimation</li><li>The product team should be skilled to judge top priority for customers instead conduct long-lasting meetings to discuss</li><li>Key to manage stakeholders — understand their concern, think for solutions over their concerns, continuous transparent communication and meeting with them separately — even while showing new plans, prototype — meet separately to each one of them and address/discuss concerns separately. Unnecessarily one department should not confuse or divert to other department people</li><li>Ideas should come from observing customers, analyzing customer data, constantly seeking to apply new technology and not from sales, marketing &amp; stakeholders</li><li>Of course, the product, engineering, and design team should work side by side else wise it&#39;s a waterfall, but the question is how? 😊 Discovery and delivery should be continuous processes. Managers, designers, and engineers should work closely, daily. Engineers can also help in discovery, who create major scope for innovation while managers and designers can also contribute to delivery. During discovery, we should be able to filter between good ideas and bad ideas and finally should have validated product backlog as the output.</li><li>In the modern age, tech-business-design all there can change or initiate the way for anything for other two so highly recommended to work them together, consistently, if possible, they should sit together</li><li>Demand testing can be useful sometimes. Instead of developing a new feature or landing page — just announce it or place a small button or page in the existing product/website and see how many people clicking on it, how many doing inquiries, what really there are expecting.</li><li>Significant things to do with data analysis <br> — user-behavior analysis (click path, engagement) <br> — Business (active user, conversation rate, lifetime value, retention)<br> — Financial (ASP, billings, time to close) <br> — Performance (load time, uptime) <br> — Operational costs (storage, hosting) <br> — Go to market cost (acquisition cost, sales cost, programs) <br> — Sentiment (NPS, customer satisfaction, surveys)</li><li>However, this quantitative (data) analysis tells you what really is happening, but you again must do qualitative analysis to find out why behind these what’s.</li><li>Steps to new product or major feature — check if useful, then usable, feasible to build, sellable, and discussed with all stakeholders to understand their POV right from engineers, business developers, partners, marketing, sales, designers, and finance people. Putting their concerns, conflicts to CEO</li><li>A demo is not a training or user guide. It’s about what value and why you are providing that — which will ultimately value them to solve their problems or get empowered in any other way. It’s an important thing to learn.</li><li>User Story map in form of the product backlog is good but its extensive version would be more beneficial — 2D — story map — on horizontal rows — epic story — flow wise and below that details of related epic — first normal user stories — and below that details — task, etc.</li><li>Customer letter or press release — one of the ways to discover what needs to be developed</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4eb63487661" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>