<?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 Yogyata Mehtani on Medium]]></title>
        <description><![CDATA[Stories by Yogyata Mehtani on Medium]]></description>
        <link>https://medium.com/@yogyata?source=rss-1f62ebd2b0d1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DN1s7FIaLgnHEaSUcTj8oA.jpeg</url>
            <title>Stories by Yogyata Mehtani on Medium</title>
            <link>https://medium.com/@yogyata?source=rss-1f62ebd2b0d1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:41:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yogyata/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[“Wiring the Winning Organization” — A book about making everything right in your organization]]></title>
            <link>https://medium.com/@yogyata/wiring-the-winning-organization-a-book-about-making-everything-right-in-your-organization-46b2d3f83bb0?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/46b2d3f83bb0</guid>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[gene-kim]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Tue, 21 Nov 2023 12:05:09 GMT</pubDate>
            <atom:updated>2023-11-21T12:23:22.548Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Wiring the Winning Organization” — A book about making everything right in your organization</h3><p>Book review of “Wiring the Winning Organization” by Gene Kim &amp; Steven J Spear</p><p><em>Grateful to IT Revolution for sharing me the copy and I am super excited to review it. The book shared a lot of instances which I could easily relate at my workplace and how close they lie in just being called as “corporate politics” but I am glad the authors have worked on creating this masterpiece that now makes these situations a bit positive to look at and resolve comfortably.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*xIuIocf42bNZ0c1EHcPOEw.png" /></figure><p><em>My personal view before you read the blog further:</em></p><p>The book is a fresh perspective on the problems we face in our workplaces. The impact of the problems varies depending on what kind of role you play. There can be times that you face no complex situation at all, or may be you have to deal with complex situations daily. This variance can impact your mentality for work and how you feel about your work as well as the organization.</p><p>This book has posed some great questions:</p><ol><li>Are we learning from our problems? or are we forced to solve the situations in an unforgiving environment of performance?</li><li>Are we making our problems easier to solve because they are simple, low risk and controllable or are we dealing with them as high risk, high stakes, fast moving with many factors where it is difficult to learn and iterate?</li><li>Are we calling out problems loudly and consistently so that they can be swarmed, contained, solved and prevent future occurrences?</li></ol><h3><strong>Concepts from the book</strong></h3><h3>1.Understanding the purpose &amp; structure of an Organisation</h3><p>The book starts by explaining why Organisations are built &amp; their purpose of doing something bigger. Organization brings together so many people for common goal, where we all get this opportunity once in our career to conquer bigger challenges together. People go to organizations and they feel demotivated when there is lack of clarity of purpose in daily routine and eventually we start to feel our dignity is being erroded away.</p><p>The book has given alot of comparisons of cultures and examples from Toyota, Apple, Amazon, US joint seperation operations command, Western Pennslvania Hospital to mention that some organizations are better at accomplishing great challenges.</p><p>Collaboration is well choreographed in these kind of organizations and performance becomes graceful. The organization here is imagined in 3 layers.</p><p><em>Layer 1: Technical objects being worked on.</em></p><p><em>Layer 2: Tools and instrumentation</em></p><p><em>Layer 3: Social Circuitry.</em></p><p>When layer 3 is wired well problems are easier, safer and faster to solve. The authors have continued to focus on these 3 layers in the whole book to explain problems at different layers and their impact on other layers.</p><h3><strong>2. The 3 Mechanisms (Hero of the book)</strong></h3><p>The authors have shared 3 mechanisms that can work together to solve any complex situation within the organization: <strong>“Slowification — Simplification — Amplification”</strong></p><p><em>Slowification : Pull problem solving out of the fast paced realm of performance.</em></p><p><em>Simplification: Reshape problems to smaller problems.</em></p><p><em>Amplification: Make problems obvious.</em></p><h3>3. Distribute your expertise to get more results from the teams.</h3><p>In any functionally oriented organization, people are structured in various teams according to their specialities where leaders assume that things will naturally self organize towards a common purpose. But things will be much better if we divide teams with seperate goals where each team has multifunctional people.</p><p>No matter what is the structure teams usually become chaotic in “danger zone” situations. Danger zone are explained in this book as situations where you cannot bring insights into practice effectively, conditions are complex, fastchanging and unforgiving, its hard to manage and stakes are really high.</p><p>Comes in the hero : “<strong><em>Simplification</em></strong>”</p><p>Simplification helps the teams to move out of the danger zone. Authors have talked about 3 ways to implement Simplification (Quoting directly from the book):</p><ol><li><em>Modularization : Partition large system into smaller ones, where each system is coherent.</em></li><li><em>Incrementalization: Add novelty bit by bit.</em></li><li><em>Linearization: Partition problem solving withing sequential workflows.</em></li></ol><p>Simplification moves people to the winning zone by:</p><ol><li><em>Easier experiements</em></li><li><em>Easier learning from experiences and experiments</em></li><li><em>More experiments</em></li><li><em>Distributed learning</em></li></ol><h3>4. When things are slow, start self reflecting</h3><p>Slowification (the next step to simplification) has 2 parts:</p><ol><li><em>Slow yourself down to self reflect.</em></li><li><em>Slow down the environment to move work into planning or practice phases.</em></li></ol><p>The authors have also described the situations which makes us do <strong>“fast thinking</strong>” leading to poor results and how it is related to cognitive biases as well.</p><p><strong><em>Comes in the 3Ps of slowification : Planning — Practice — Performance</em></strong></p><p>Find slow moving conditions that allows you time to build skill and performance.</p><h3>5. Capturing &amp; using knowledge</h3><p>The authors have amazingly put a few lessons around capturing knowledge and how to use that knowledge.</p><ol><li>Feedback free, non-learning dynamic: There is expectation that subordinates will execute the plans as explained and at the time of evaluation, how well the plan was executed will be evaluated and not about the reason-ability of the plan itself.</li><li>On the other side the authors have also talked about incorporating feedback into planning, practice &amp; performance.</li></ol><h3>6. Linear or serialized execution</h3><p>The book describes that linearization (a mechanism for simplification) has 4 elements:</p><ol><li><em>Sequentialization</em>: Single pathway of connected activities.</li><li><em>Standardization: </em>Pre-specified definition of exepectation around output, steps to be performed to generate the output, nature of handoffs, methods etc.</li><li><em>Stabilization:</em> Settling down a situation or a problem with the help of triggers that are built into outputs, pathways, connections and activities so that when something wrong or surprising happens, the resources are directed onto the problem.</li><li><em>Self synchronization </em>: Production systems can automatically self pace without scheduling systems.</li></ol><h3>7. Isomorphism</h3><p>The book also connects the behaviors from an organization to the concept of “Isomorphism” : Quality of related items having similar structures.</p><ol><li>The social circuitry of the organization must support the technical work. If this is wired properly, everyone gets what they need quickly and easily.</li><li>Throughout the organization people need to support the work of eachother, whether it is information, approvals, requirements, time, attention or expertise.</li></ol><h3>8. Call out your problems loudly and consistently</h3><p>Calling out your problems in the organization helps to trigger the help which is needed to control and contain the situation.</p><p>Here comes in “Amplification”</p><p>For control systems to be effective, the generation, transmission, reception and reaction to signals must keep pace with the changes happening within the system. Even a control system can fail because of delays and imprecision. Signals need to be sent with adequate frequency, speed, detail and accuracy for the reaction to be helpful.</p><p><strong>6 Steps of amplification:</strong></p><p><em>1.Sender generates signals. <br>2. Sender transmits the signals.<br>3. Receiver receives the signals.<br>4. Corrective reaction is started.<br>5. Corrective reaction is completed.<br>6. Sender confirms that reported problems has been solved, otherwise they send another signal.</em></p><p>— — — — — -</p><p><em>End note</em></p><p>The book has poured humble suggestions with diagrams to help you visually understand the grids and where the authors are trying to move you. There are examples where authors have shown themselves being a part of the instances and how they solve it like storytelling. The book doesn’t feels heavy on head but like an activity book where each chapter ends with questions and next steps for you to try out immediately the next day in your workplace.</p><p>Its a must read!!</p><p>Have thoughts to share ? Drop your comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46b2d3f83bb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All about agility in Audits from “Beyond Agile Auditing”]]></title>
            <link>https://medium.com/@yogyata/all-about-agility-in-audits-from-beyond-agile-auditing-889fecbc204d?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/889fecbc204d</guid>
            <category><![CDATA[audit]]></category>
            <category><![CDATA[agile-auditing]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Sat, 08 Jul 2023 11:55:46 GMT</pubDate>
            <atom:updated>2023-07-08T12:02:52.643Z</atom:updated>
            <content:encoded><![CDATA[<p>Book review of “Beyond Agile Auditing” by Clarissa Lucas</p><p><em>Grateful to IT Revolution for sharing me the free copy and I am super excited to review it. The book is about Agile Auditing &amp; touches several aspects of Auditing that we experience at our workplace. The book goes deeper into the experiences created by Auditors and helps you build perspective around Auditing &amp; its importance in today’s world.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*UN14HzfG9dAcvD9wOFL_kg.png" /></figure><p>I am a Product manager (&amp; not an auditor) but have been a part of the audits that have been conducted at my workplace. Based on my experiences I was able to relate with the book and also empathize with the author and the message they have tried to convey. This book is an eye opener for anyone who wants to understand Auditing and also want to contribute to the process of auditing. With the concept of Agile Auditing, Clarissa has went deeper to bring versatility by comparing traditional auditing process, risk management, change management &amp; faster movement in the process of Audits and prepare practically. This book is an attempt to encourage people across the organization to be productive &amp; feel heard and know that their inputs are strongly considered as a part of the audits. I personally liked the way Clarissa has expressed her thoughts by adding several use cases and her past case studies in the book.</p><h3><strong>Why Internal audits are done?</strong></h3><p>Clarissa started the book by explaining what are internal audits. Internal audits are important to help an organization succeed in what they do where the auditors help the organization with an impartial perspective and find out if the policies are being followed, controls are effective and org is operating as the management intends. Auditors provide the insights about the risks that might lead to disasters, how to improve controls, processes &amp; risk management that eventually helps to reduce costs &amp; increase profits</p><h3><strong>Painful experiences of an organization going through an audit</strong></h3><p>After explaining the process of audits, the book further relates to the pain points of an organization which is going through an audit. While the organization goes through an audit, it faces problems like need to reeducate auditors, lack of inconsistency in the audit, high volume of requests and questions from the auditors but the org always gets to see the results only when the first audit draft is prepared by the auditors which actually is a long period of waiting time for the org.</p><p>Clarissa has also tried to help you compare the both sides of the coin by highlighting the problems faced by clients and auditors.</p><p><strong>Problems a client faces while audit:</strong></p><ol><li>Unplanned audit work</li><li>Auditors don’t understand the business</li><li>Auditors reports don’t tell us anything we dont already know</li></ol><p><strong>Problems an auditor faces while audit:</strong></p><ol><li>Context Switching</li><li>Managing dependencies on certain people</li><li>Ongoing observation negotiations after agreement</li></ol><h3><strong>Imagining the better Audit experience</strong></h3><p>Clarissa has put a lot of emphasis on the classical way of Auditing and compared it with an enhanced and agile way of Auditing. While it’s not only about changing the way audits are done but also about how auditors can change their perspectives on things as the technical world advances.</p><p>Auditors helping their clients with shared outcome and common goal which unravels risks (from today &amp; predict for future). What we are imagining can be a reality if we are able to create value driven, integrated &amp; adaptable approach to the internal audit.</p><p><strong>Value driven</strong>: The scope of work is driven by what adds the most value to the organization.</p><ul><li>Value driven insights over extensive doc</li><li>Deliver value frequently</li><li>Break down audit scope into manageable pieces</li><li>Increase visibility</li><li>Constantly optimize for global goals rather than individual goals</li></ul><p><strong>Integrated:</strong> The audit should align with the client’s daily work &amp; integrates continous improvement into the audit process.</p><ul><li>Intentional collaboration</li><li>Single team and collective goal</li><li>Create feedback loops</li></ul><p><strong>Adaptable:</strong> Focus on improving the audit team’s ability to respond to change and add flexibility into the audit process.</p><ul><li>People over processes</li><li>Respond to change</li><li>Pursue simplicity</li><li>Leverage self organizing team</li><li>Limit work in progress</li></ul><p>Clarissa points out Agile Auditing as a project management framework that provides a consistent approach to auditing delivered as sprints instead of delivery only at the end of the process.</p><p>This book also talked briefly about the Auditing Standards:</p><ul><li>Performance Standard 2240: Engagement work Program</li><li>Performance Standard 2100: Nature of Work</li><li>Performance Standard 2330: Documenting Information</li></ul><p>— — — — — -</p><p><em>End note</em></p><p>While we all talk about Agile as a core part of delivery of products, then auditing can also become an Agile process if we can fundamentally understand the perspective behind performing Audits. Audits being treated as overhead can be a great advantage once we try to implement them as an integrated &amp; value driven process. Parts of this book will twist your minds while keeping all the experiences relatable. The book has a lot of ideas and thoughts for us to catch &amp; thoroughly understand each and every step of the audit. While the book has so much for us, it is fairly easy to read and understand for anyone who is new to Auditing.</p><p>Have thoughts to share ? Drop your comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=889fecbc204d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 Questions from “Agile Conversations”- Part-2]]></title>
            <link>https://medium.com/@yogyata/20-questions-from-agile-conversations-part-2-1c8d99a54ec5?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c8d99a54ec5</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Thu, 14 May 2020 16:06:13 GMT</pubDate>
            <atom:updated>2020-05-14T16:06:13.354Z</atom:updated>
            <content:encoded><![CDATA[<p>Book review of “Agile Conversations” by Douglas Squirrel &amp; Jeffrey Fredrick</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*6cFfUOrllwCHedDEyza_Hg.jpeg" /></figure><p>This blog is in continuation to <a href="https://medium.com/@yogyata/20-questions-from-agile-conversations-76a2c0d699d4">part-1</a></p><h3>20 questions I asked myself while reading “Agile Conversations”</h3><h4>9. Are we afraid of the fear itself?</h4><p>Any organization may suffer from the fear of error, failure, building the wrong product, disappointing managers, exposing poor leadership, of any number of other disasters. Uncover your own fear, locate &amp; understand the fear of others, &amp; lead a fear conversation to mitigate fear on all sides. Fear of complexity, disengagement, skill gaps, missing key steps, deadlines &amp; bugs.</p><h4>10. Did we prep before the “why” conversations?</h4><p>We are exposed to the “why” questions all the time during sprint delivery. So in such scenarios we have to make sure of the following:</p><ul><li>Redefining the team lead’s role &amp; coaching him in collaborative leadership.</li><li>Making quality fears discussable &amp; reshaping the release process to address them.</li><li>Removing an ineffective senior leader whose actions had undermined trust.</li></ul><h4>11. Why designing of the “why” jointly for the organization is difficult?</h4><p>This is harder because it means negotiating &amp; compromising, one step back &amp; 2 step forward- a seeming waste of time.</p><p>It’s also harder because it means the death of the ego for all sides; we can no longer believe that we are the only source of truth &amp; direction in our working lives.</p><p>It’s especially difficult for executives or founders who sincerely believe the they are the only ones who know, or should know, the right direction for the organization.</p><h4>12. Why teams are unable to have productive conflicts instead of interminable debates?</h4><p>Position &amp; interests are always conflicting within a group of people. The success of the team depends on how they concentrate on productive conflicts rather than having never ending debates over things just to justify the hierarchy or designations.</p><h4>13. Why having compliance is just not enough?</h4><p>This is a compliance vs commitment conversation:</p><ul><li>Compliance is ‘showing up’; commitment is engaging with your whole self.</li><li>Compliance is filling the space; commitment is participating.</li><li>Compliance can be enough for routine day to day tasks, compliance is not enough to generate change, to improve, to excel. I f these are your aims, you need commitment.</li></ul><h4>14. Why definition of done is so hard to understand for team?</h4><p>When you’re asking for a commitment to a process or cultural change, it’s even more important to align on the meaning of your language by using specific examples. “Done” are not well defined inside our brain only through examples we can align about their meaning.</p><h4>15. How to define a successful commitment?</h4><ul><li>Agree on the meaning of the commitment</li><li>Agree on the next outcome to commit to.</li><li>Reaffirm the commitment.</li></ul><h4>16. Is it reasonable or even sensible to expect accountability from your team?</h4><p>We can get better results more cheaply by using the drive for success inherent in each individual. Instead of trying to micro- manage them just because we don’t trust them:</p><ul><li>Give motivated individuals the environment &amp; the support they need.</li><li>Trust them to get the job done.</li><li>Empower the team.</li><li>Trust that everyone is doing their best for their business.</li></ul><h4>17. How we are understanding the gap in plans &amp; outcomes?</h4><ul><li>Knowledge gap- what we would like to know &amp; what we actually know.</li><li>Alignment gap- what we want people to do &amp; what they actually do.</li><li>Efforts gap- what we expect our actions to achieve &amp; what they actually achieve.</li></ul><h4>18. Why conversations are so important in agile?</h4><p>The only way you make the work transfer from one point to the other is conversation or communication. To really think about making your effort agile, you will also have to focus on your conversations during agile.</p><h4>19. We really talk in the agile ceremonies?</h4><p>Most of us just focus on keeping the ceremonies time boxed and focus less on what is actually being done within the ceremonies. The purpose of having ceremonies in agile was to increase collaboration within team members but now focusing more on making it “effective”, we somehow forgot the real purpose of the ceremonies.</p><h4>20. So what does the authors meant with “Agile conversations”?</h4><p>The author gave a great thought about what we are conversing about, and how it should be conversed. They also focused on treating conversations as the hook to keep all the team members as close as possible. They also talked about how to project anything within your conversation so that it transfers to the listeners with the same effect.</p><p>— The END —</p><p>This book has tons of pointers and I am sure this is not the exhaustive list that I have shared 😊. If you have also read this book and got something to share, feel free to drop your comments.</p><p>You can share this book to your team while you work, you can quote its examples and discuss about it.</p><p><em>Wish you the best!</em></p><blockquote>Like what you read? I deserve a clap then !</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c8d99a54ec5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 Questions from “Agile Conversations”]]></title>
            <link>https://medium.com/@yogyata/20-questions-from-agile-conversations-76a2c0d699d4?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/76a2c0d699d4</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Tue, 12 May 2020 16:08:39 GMT</pubDate>
            <atom:updated>2020-05-14T16:07:27.612Z</atom:updated>
            <content:encoded><![CDATA[<h3>20 Questions from “Agile Conversations”- Part-1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*6cFfUOrllwCHedDEyza_Hg.jpeg" /></figure><p>Book review of “Agile Conversations” by Douglas Squirrel &amp; Jeffrey Fredrick</p><p><em>Thanks a ton to IT Revolution for sharing me the free copy of the copy and I was super excited to review it. But when I started to read this book, I found it so relevant that I feel lucky to be reviewing it</em> 😌</p><p>We all have been hearing about the “Agile methodology”, dos and don’ts. I spent past 3 years reading loads of blogs &amp; books just to bring more clarity about how I practice Agile and how I can keep the experience better for my team.</p><p>I understood Agile is not just a methodology but more of a mindset shift where you start thinking from a perspective of making everything work in an agile manner. You make your team think of problems and not directly jump over solutions instead find the most agile way to solve a problem.</p><p>I believe you might also have some wonderful stories to tell about “why you learned agile”, “how you got to know about agile” and so on. Most of us just wanted to implement agile because we wanted to get our work done, while saving our resources as well. We started to measure the effort being put, made work granular, estimated everything, even time boxed our meetings but we forgot to think about the most crucial player in this overall journey. 😐</p><p>We forgot to rethink about our communication. It can be verbal, written or recordings but we forgot to estimate it. We forgot to measure the efficiency of our communication. Communication plays the lead role behind every piece of work, success of a task depends on how the work is conveyed. But we forgot to measure it!</p><p>The “Agile Conversations” by Douglas Squirrel &amp; Jeffrey Fredrick talks about how to do your conversations or communication in an agile manner. Each page that I turned within this book made me think about what I did wrong in my past years and what could I have done instead. 😌</p><h3>20 questions I asked myself while reading “Agile Conversations”</h3><h4>1. Why don’t we talk more often?</h4><p>The primary focus for all of us is to get the work done and so we tried to reduce the time of “Talking” and spent more on executing. But this lead to increase in the time of execution because of missing clarity within members of a team.</p><h4>2. Are we just “feature factories”?</h4><p>Delivering more and more features based on the defined scope is just making us feature factories and we moved away from solving a problem and finding solution. We also limited ourselves to the fact that the problems can be solved only by adding features.</p><h4>3. Can documentation reduce the “Scope of failure”?</h4><p>In the light of agile, we started defining our documents in a manner which is granular and the person implementing the requirement can just follow it without thinking outside of it. Reread the last sentence to find the problem. 😅 The scope of failure can be effected by documentation but not always reduce the impact.</p><h4>4. Should Collaboration be put on hold by the processes?</h4><p>We tend to “go by process” in the uncertain times, so that we can also make someone accountable for the upcoming failures but we don’t choose to sit together and collaborate more often from the very beginning. We stay away from the other people on the team in the name of “process” and create loopholes by ourselves.</p><h4>5. Why we keep so much work in progress at an instant?</h4><p>We tend to start alot of tasks together, thinking we can complete them parallely but that just means starting alot of work together which just reduces the chances of atleast one of them to get completed.</p><h4>6. Why conversations are still controlled in corporates?</h4><p>Controlling conversations in order to save time of team doesn’t do any good for them. It just damages the collaboration, relationships &amp; team productivity.</p><h4>7. Why things change within a team when the situations are potentially threatening or embarrassing?</h4><p>When almost everyone claims to adopt the approaches &amp; behaviors of productive reasoning, it is unreasonable for the team to change its behavior in threatening situations. But it still happens, always!</p><h4>8. Is our communication having the required clarity?</h4><p>The book explained an amazing model to gauge if your communication has the required clarity.</p><h4>The four ‘R’s formula:</h4><ul><li>Record: Storing your communication so that it can be revisted. If it is verbal, you can record it. If written then the documentation itself can be revisted.</li><li>Reflect: Pay attention to the tool &amp; technique you are trying to use at that time.</li><li>Revise: Revise your communication to try &amp; produce a better result.</li><li>Role play: Find a friend &amp; try saying your dialogue aloud.</li></ul><p>Continue Reading in <a href="https://medium.com/@yogyata/20-questions-from-agile-conversations-part-2-1c8d99a54ec5">part-2</a></p><p><em>Liked what you read? I deserve a clap then.</em>😁</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76a2c0d699d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is inspiring customers to change habits/ adopt something?]]></title>
            <link>https://medium.com/@yogyata/what-is-inspiring-customers-to-change-habits-adopt-something-b699fc9060fb?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b699fc9060fb</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[goleanwithyogyata]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 15:40:03 GMT</pubDate>
            <atom:updated>2020-01-13T15:40:03.888Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hBNFQv4S9xzEif9IbTKoA.png" /></figure><p>Did you try bungee jumping just because it looks cool?</p><p>Did you ever thought to live a life like “man vs wild”?</p><p>Were you ever inspired by any blogger for that unusual look?</p><p>Did you just signed up on netflix? Just because you don’t want to miss out?</p><p>Do you file your vote during elections because its a responsibility?</p><p>Many such questions are there, or instances where you are actually influenced by any advertisement, your friends, responsibilities, loyalties or may be just out of boredom. But you definitely feel to try something new or unusual.</p><p>That is what is an impeccable trait of humans which I believe will always escape the notoriety of AI and ML.</p><h3><strong>The back story</strong></h3><p>I am working on building a next level product for cloud management, where the vision is to “simplify” cloud management for companies. Well, you can check our progress over <a href="https://powerboard.tech/"><strong>here</strong></a>, and signup if you like :)</p><p>This product deals with a lot of “mindset” related queries and assumptions. While I worked on this product, I realized the behavior is more dependent on how the users actually feel about “Cloud management” or may be it is just unusual to talk about.</p><p>Based on a few thoughts, I ran an experiment on Twitter to understand, what makes people change habits or adopt something.</p><h3>The Experiment</h3><p>I ran a poll on twitter with a few generic options:</p><ul><li><strong>Relatability </strong>: What users or people find as “relatable”. Anything that seems as a fit at the moment or the stage of their life, due to any problem, limitations they are facing, or just the best option available at the moment.</li><li><strong>Social Acceptance:</strong> When users or people feel left out while everybody else is doing it or using it, or may be if there is pressure from their friends &amp; family, or if it is something related to contributions towards society or government.</li><li><strong>Monotony:</strong> People or users are just bored of the current situation and want to get over it, they are doing something on repeat for a long time and want to look for options, they just want to try something new in their lives.</li></ul><p>As you can see, all the options still have a lot of questions that require clarity or can be debatable, but the current experiment is to find the best of these 3 that we should consider drilling down further.</p><p>The second consideration that I have is, that none of the options can impact the well being of the human or is related to any factor that effects the human life e.g. quiting smoke or alcohol; which means we are trying to find the best choice while the audience is fully in free will.</p><p>The third consideration is that we are not talking or mentioning about any brand or entity to make people vote in influence, they are till open to vote with their choice.</p><h3>The Results</h3><p>The poll was held for a week and received 93 votes globally.</p><p>Almost all the options are selected by people, which seems like a close enough consideration by people but the most voted is “Social acceptance”.</p><p>So, people are okay to still have repeated things in life, find relatable options but they will bring changes to their routine, or adopt something mostly if their is a factor of social acceptance for them.</p><h3>Yogyata 👩🏻‍💻 on Twitter</h3><p>What inspires people to change habbits ? #productresearch #userexperience</p><p>Have something on your mind? Did you ran a similar experiment? Feel free to comment!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b699fc9060fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20+ lessons learned from “The Unicorn Project” by Gene Kim- Part-3]]></title>
            <link>https://medium.com/@yogyata/20-lessons-learned-from-the-unicorn-project-by-gene-kim-part-3-a4f695164ba?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4f695164ba</guid>
            <category><![CDATA[goleanwithyogyata]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Sun, 24 Nov 2019 10:02:06 GMT</pubDate>
            <atom:updated>2019-11-24T10:02:06.413Z</atom:updated>
            <content:encoded><![CDATA[<p>Storyline of a novel about developers, digital disruption and thriving in the era of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CnUDv86ZP4_1tivz.png" /></figure><p>This blog is in continuation to <a href="https://medium.com/@yogyata/20-lessons-learned-from-the-unicorn-project-by-gene-kim-part-2-55cf36e99fe8"><strong>Part-2</strong></a> of my learning from <strong>“ The Unicorn Project”</strong></p><h3>20+ pointers I wrote down in my diary and are taken from this book</h3><p><strong>18. TWWADI: The Way We have Always Done It</strong></p><p>Each plan or process adds to the coordination cost for everything we do and drives our cost of delay. And because the distance from where decisions are made and where work is performed keeps growing, the quality of our outcomes diminish.</p><p><strong>19. Rethinking leadership</strong></p><p>For the leaders, it is no longer about directing and controlling, but guiding, enabling and removing obstacles. Leaders getting more involved with the team and collaborating closely is the need of the hour for effective results.</p><p><strong>20. Not delivering what’s needed</strong></p><p>When the teams work away from the customer focus, they often “assume” things will work in a certain way when released to the customers. Which leads to releasing things which might not even be what customers need right now or too complex for them to use. We are not delivering what’s needed and when we find something wrong, there’s not enough time to fix it.</p><p><strong>21. Dev teams becoming prisoners of what business teams need</strong></p><p>Development teams are expected to be guards of what they develop. They should know how to optimize it, make it stable and effective with time and to avoid technical debt. But, gradually as the product progresses, they get overburdened by the business teams and try to keep up with the pace of changing requirements from the business and marketing teams. That’s where they stop being the guards, in fact they start to love being prisoners so much, that they just think the bars are keeping them safe.</p><p><strong>22. Incorporating feedback early to the process.</strong></p><p>The book shares a situation where Maxine understands the gravity of the product. For something this important, she finds that the company wasted 2 years. In the ideal, they should have just assigned a team that included developers to explore the idea &amp; build a solution together. Instead of one product manager working on this the entire time, they could have 5 people working on it. And they could have been learning the whole time.</p><p><strong>23. Sharing goals with the team</strong></p><p>When everyone knows what the goals are, teams will organize to best achieve these goals. We often limit the information passed on to the team, in order to prevent confusion and wastage of time. But sharing the essence of goals will give everyone a taste of “what achievement looks like” for a product team, which will help them understand the goals and become self-sufficient to manage a lot of things without superior interference.</p><p>— — The End — —</p><p>This book has tons of pointers and I am sure this is not the exhaustive list that I have shared 😊. If you have also read this book and got something to share, feel free to drop your comments.</p><p><strong>The Unicorn Project</strong> is something that you can always share while you work, you can quote its examples and discuss about it. Might be possible that you are not in such a situation as The Unicorn project right now, but can be in future.</p><p><em>Wish you the best!</em></p><p>Also read about <a href="https://medium.com/lovescloud/lessons-learned-from-the-phoenix-project-part-1-70075116de"><strong>The Phoenix Project by Gene Kim</strong></a></p><blockquote>Like what you read? Oh! I deserve a clap then.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4f695164ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20+ lessons learned from “The Unicorn Project” by Gene Kim- Part-2]]></title>
            <link>https://medium.com/@yogyata/20-lessons-learned-from-the-unicorn-project-by-gene-kim-part-2-55cf36e99fe8?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/55cf36e99fe8</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[goleanwithyogyata]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Sun, 24 Nov 2019 08:24:35 GMT</pubDate>
            <atom:updated>2019-11-24T10:07:03.961Z</atom:updated>
            <content:encoded><![CDATA[<p>Storyline of a novel about developers, digital disruption and thriving in the era of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gmgdRix97E8giLOy.png" /></figure><p>This blog is in continuation to <a href="https://medium.com/@yogyata/22-lessons-learned-from-the-unicorn-project-by-gene-kim-part-1-6f47fa2fc036"><strong>Part-1</strong></a> of my learning from <strong>“ The Unicorn Project”</strong></p><h3>20+ pointers I wrote down in my diary and are taken from this book</h3><p><strong>8. Centralized integration helps developers to remain consistent.</strong></p><p>One of the really nice things about running your program frequently is that you get to see it running, which is fun &amp; that’s what programming is all about.</p><p><strong>9. Each developer on team should be able to be productive.</strong></p><p>When you work in a team, as a part of project management, it is your primary responsibility to ensure that any contributor can be productive. Each member of the project has access to the information that they require to work independently or may be with less dependency and also they are able to execute their codes independently.</p><p><strong>10. Scattered information &amp; hierarchy kills time.</strong></p><p>In the book, there is a situation where Maxine is trying to get access to all the information she needs to run the code by herself. You will find her going up 2 levels, over 2 levels and down 2 levels just to talk with a fellow engineer as for each and every thing she has to raise a ticket. She doesn’t want to depend on people and keep waiting for the ticket to resolve or just wait to find that the ticket got closed for no reason.</p><p><strong>11. Big projects, personal incentives &amp; no cross checks?</strong></p><p>The book also focuses on the teams or sub-groups which only care about growing the union &amp; the project budget but not about what’s right for the business.</p><p><strong>12. First Ideal: Simplicity &amp; Locality</strong></p><p>Simplicity is important because it enables locality. Locality in code is what keeps systems loosely coupled, enabling teams to deliver features faster.</p><p><strong>13. Complexity debt vs new features</strong></p><p>You can choose to build new features or pay down complexity debt. When a fool spends all their time on features, the inevitable outcome is that even easy tasks become difficult and take longer to execute. And no matter how hard you try or how many people you have, it eventually collapses under its own weight forcing you to start over from scratch.</p><p><strong>14. Second Ideal: Focus, flow &amp; joy</strong></p><p>A good product describes how it was built. Great ideas are generated by people who are focused towards what they do or build and infact enjoy building it. If a team enjoys building something then it turns out to be a stable and wonderful product as compared to teams where people are working in silos and are less involved mentally.</p><p><strong>15. Third Ideal: Improvement of daily work</strong></p><p>Every human’s goal should be to “improvise” in whatever they do, gradually as they spend more days doing it. For every repetitive work, we should work on improving the quality and try to innovate it so that we are also not feeling it monotonous to perform every day.</p><p><strong>16. Fourth Ideal: Psychological safety</strong></p><p>Whenever we work in groups or teams, we should ensure psychological safety, which means we make it safe for people to talk about problems. Because solving problems requires prevention, which requires honesty and honesty requires the absence of fear. Psychological safety will always help to improve the quality of work everybody is doing and their contribution to the project. Not only this, it will also bring empathy within your team where each member can understand the problems everybody else is going through.</p><p><strong>17. Fifth Ideal: Customer focus</strong></p><p>Development teams are always kept away from customer focus, as they are only given the details or requirements which are needed to understand a feature but not the information about the impact. While its important to keep team focused only on the scope for which they are responsible, a summary of customer impact should also be added to their requirements so that they can relate what impact this feature will produce once it is released.</p><p>Customer focus: where we ruthlessly question whether something actually matters to our customers, if they are willing to pay us for it or is it only of value to our functional silos.</p><p>Continue reading<a href="https://medium.com/@yogyata/20-lessons-learned-from-the-unicorn-project-by-gene-kim-part-3-a4f695164ba"> <strong>Part-3</strong></a></p><blockquote><em>Like what you read? Oh! I deserve a clap then.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55cf36e99fe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[22 lessons learned from “The Unicorn Project” by Gene Kim- Part-1]]></title>
            <link>https://medium.com/@yogyata/22-lessons-learned-from-the-unicorn-project-by-gene-kim-part-1-6f47fa2fc036?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f47fa2fc036</guid>
            <category><![CDATA[the-phoenix-project]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Sat, 23 Nov 2019 11:34:38 GMT</pubDate>
            <atom:updated>2019-11-24T08:26:46.075Z</atom:updated>
            <content:encoded><![CDATA[<h3>20+ lessons learned from “The Unicorn Project” by Gene Kim- Part-1</h3><p>Storyline of a novel about developers, digital disruption and thriving in the era of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rFDawFxCkgP2qXLI.png" /></figure><p>Last year (2018) I spent some time reading <strong>“The Phoenix Project” by Gene Kim</strong>, the book which will make you think about the things that come across your way if you run a tight ship in your organization, devops and typical project teams.</p><p>You can read about my thoughts for the book <a href="https://medium.com/lovescloud/lessons-learned-from-the-phoenix-project-part-1-70075116de"><strong>here</strong></a></p><p>This year I got a chance to read <strong>“The Unicorn Project” by Gene Kim</strong> before the official launch and I went nuts!! 😁</p><p>Really thankful to <strong>IT Revolution</strong> for sharing me a free copy 🤗</p><h3>Yogyata 👩🏻‍💻 on Twitter</h3><p>Last year I wrote a review about &quot;The phoenix project&quot; by @RealGeneKim sharing the lessons learned from the book. This year I got a chance to review &quot;The Unicorn Project&quot; before the release. 😊 Soooo excited ! Sharing the blog soon !! #bookreviews #devops</p><h3>Storyline</h3><p>The Unicorn Project is a whole new plot, it is about “Maxine Chambers” (the developer lead losing her mind as she is forced to stay away from doing “anything”) who will run the ship this time, big surprises along the way, exposure to not only technicalities but also the customer facing problems too, a lot of layoffs &amp; a crazy bartender who knows stuff better then you do!</p><p>It is pretty amazing how Maxine was able to link the dots along the way, she motivated her team, changed the way the team was working, made the deployments to move faster, solved problems in the offline stores, created better experiences for the store teams and innovated products for running the grand marketing plans.</p><p>It will keep you gripped on every page, the stress, fire fighting, broken things, buggy code, firing of people, sarcasm, empathy is coming along your way.</p><p>Both the books “The Phoenix Project” &amp; “The Unicorn Project” are running the plots in parallel, there will be characters in this book that you will recognize from the Phoenix Project but it is not mandatory that you need to read The Phoenix Project before you read The Unicorn Project as both have separate story lines and are not interconnected at all.</p><h3>20+ Lessons learned from “The Unicorn Project”</h3><ol><li><strong>The cycle of corporate grieving</strong></li></ol><p>Maxine Chambers will help you understand her movement from the one stage of grieving to the other with no specific order at all. She mentions about the Kuber Ross model of grieving. This is what we go through everyday of our work and we might just relate it to our “bad mood” but actually it is about your mental thoughts transformation in a cycle.</p><p><strong>2. Mistakes and entropy are fact of life</strong></p><p>With more and more firing of the employees, the book will consistently make you feel how punishing the failure and shooting the messenger can only cause people to hide their mistakes and eventually all desire to innovate is completely extinguished.</p><p><strong>3. Missing documentation &amp; scattered information</strong></p><p>Maxine joins a project where she is struggling real hard to collect all the information about the configurations, whatever information she has in hand is either outdated or not working and she just spent days sitting ideal as she is unable to setup a test environment for herself.</p><p><strong>4. Developers must not work in the isolation.</strong></p><p>The book focuses on a scene where a 100 of developers are typing on their laptops without constant feedback from a centralized build, integration and test system, and hence they have no idea what will happen when all their work is merged with everyone else.</p><p><strong>5. Sometimes your checklist just doesn’t work.</strong></p><p>Maxine makes a checklist for herself to collect the information she needs to complete the setup on her end, its crazy how her checklist changes from “<em>get account for integration test environments</em>” to “<em>find someone who can give me access to Dev or test environments</em>”. A person who is super productive and doesn’t like to waste any minute of their daily working hours will definitely find this as a frustrating experience.</p><p><strong>6. Less or no importance to dev environments will definitely lead to blunders.</strong></p><p>The team focuses on features as they can see them into action on web, app or in the API but no one seems to realize how important the build process is. Developers cannot be productive without a great build, integration and test process.</p><p><strong>7. Shhhh no one knows the effect, no one knows the cause.</strong></p><p>As there is no centralized build, the link between the cause and the effect will disappear with no trace and that’s never a way to run a project.</p><p>Continue reading in <a href="https://medium.com/@yogyata/20-lessons-learned-from-the-unicorn-project-by-gene-kim-part-2-55cf36e99fe8"><strong>Part-2</strong></a></p><blockquote>Like what you read? Oh! I deserve a clap then.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f47fa2fc036" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Products are built on stories not insecurities]]></title>
            <link>https://blog.prototypr.io/products-are-built-on-stories-not-insecurities-b56e8ed6bdce?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b56e8ed6bdce</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[goleanwithyogyata]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 18:31:24 GMT</pubDate>
            <atom:updated>2019-10-08T08:56:16.748Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rb65gIm3Q3uz6XEZC9h-ZQ.png" /></figure><blockquote>Why you should never build a product, “inspired” from what’s already existing in the market.</blockquote><p>Today is the era of products, product talks, building competition and what not. Not only products have evolved but users have also become smarter. It is the time for something new and better, there is no end to innovation.</p><p>There are products which are literally mind blowing while there are some which are just built on having the target market share and be another competitor.</p><p>Just for an instance, how many e-commerce or project management tools do we literally need?</p><h3>Why build products?</h3><p>Products are purely built on demand, to help people solve a problem in their lives, to give some happy experiences to users, reduce manual work, making lives easier and similar thoughts.</p><h3>Where we went wrong?</h3><p>When a product idea gets successful, people try to build more products on the same idea with a bit of variation (nearly negligible) and release it into the market. This is just not solving a customer’s problem, it is just breaking the market, and customer’s usually go to the cheaper ones, which just dilutes the purpose of building a product and it all boils down to just competing for prices.</p><h3>Why we should not build a competitor?</h3><ul><li>It will not take you long to realize that you are not able to scale a copied version of some other’s product idea.</li><li>You are killing “actual customer journeys”, because a user never gets matured on one single platform, they will definitely switch to a competitor.</li><li>Depth of a product is not built, a lot of resources are just spent to perform better than a competitor.</li><li>Everything ends with “more ads”</li><li>It takes years for a real product to rise up from the competition and gain customer’s trust.</li><li>It takes a lot of time to build loyal customers.</li><li>You can never stick to just one plan, because competitors are waiting to copy that too.</li></ul><h3>What should we do, instead of building competitors?</h3><p>A market is actually a composition of users of different type and are never associated to one single persona. Instead of building products for the same market, we can rather build products for a smaller market or niche market.</p><p>We are not in the era, where we lack choices, we rather have “loads” of them. Instead, we need products that are actually a “market-fit”. Products that absolutely fit a user’s purpose. Where user can actually utilize the full potential of the application, is never bored of it, not want to exchange with an alternate and instead wants to share suggestions to improve it. We should focus on creating experiences which help our users to evolve, become a better version, only switch to other applications when they no more lie in that particular market, they should actually grow with your product.</p><h3>Food for thought</h3><p>We must not build products just focused on revenue, we must rather focus on creating a monopoly or tapping the new markets.</p><p><em>Liked my blog? Oh I deserve a clap then :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b56e8ed6bdce" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/products-are-built-on-stories-not-insecurities-b56e8ed6bdce">Products are built on stories not insecurities</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study- 3:  Scope stretch never develops a product]]></title>
            <link>https://medium.com/@yogyata/mvp-goleanwityogyata-c21630d8afba?source=rss-1f62ebd2b0d1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c21630d8afba</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[mvp]]></category>
            <category><![CDATA[goleanwithyogyata]]></category>
            <category><![CDATA[productmanagment]]></category>
            <dc:creator><![CDATA[Yogyata Mehtani]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 16:44:40 GMT</pubDate>
            <atom:updated>2019-04-03T16:44:40.216Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study- 3: Scope stretch never develops a product</h3><p>It is not too hard to stick to your MVP for a while, but it is difficult for teams to understand if they don’t know the consequences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*GRPTHfiekRGSYU6Gb6LMig.png" /></figure><p>Hey guys,</p><p>It is my 1st blog of 2019, had a lot of things going on. Mental shifts in product management and development, new product teams joined and yes it is as exciting as it looks tiring.</p><p>All this while I am working with early stage startups and we have been struggling a lot around MVP, how we can innovate and give the best experience while sticking to minimal features for just proving the concept and yet being a complete application. And, I am writing this blog because I noticed a common mentality between these product teams that I am working with.</p><p><strong>What is scope stretch?</strong></p><p>Scope, “As we all know”, means the goal that was initially decided with a timeline, that after x months the team will deliver y features which will be fit for a release. And “stretch” means, increasing timelines of delivery due to additions to the scope which somehow thought to be connected with the features of the scope but are actually independent.</p><h3>5 ways to identify if you are having scope stretch</h3><ul><li><strong>New additions in feature list:</strong> Growing feature list always increases timeline but if it decreases your timeline then it is considerable.</li><li><strong>Considering “enhancements” as a part of MVP</strong>: Enhancements, as the word suggests are actually applied or developed on a feature base but they are not supposed to be developed at the time of MVP.</li><li><strong>Long discussions even after scope approvals</strong>: When team continues to argue or add more thoughts to the initially decided scope even after mutual agreement then also your MVP scope is changing.</li><li><strong>No or less clarity of what is to be developed:</strong> MVP is like an experiment which is to be developed in order to give customers, “something usable”. But if your team is unclear of the flow of “minimal” features then either your team is not on the same page or you are considering a complex which is not really a “minimum viable”.</li><li><strong>No clear timelines for scope completion: </strong>It happens alot of times when we estimate something initially but able to complete that feature with a huge gap of days. The chances of “incorrect estimation” is less in this case, as this was a MVP, so yes! you picked up something on the way and added to your scope leading to this gap of estimation.</li></ul><h3>5 reasons why you should prevent “Scope-stretch” for your MVP</h3><ul><li><strong>If your MVP is having complex features, then it is not a MVP </strong>: MVP itself stands for “minimum viable product”. If you are moving out with complex features which are hard to understand for any user then the opportunity that you could have established with your MVP will be lost and it is definitely not a MVP.</li><li><strong>Unnecessary resource cost:</strong> The human resource cost, asset cost, time, marketing cost etc will be higher and is unnecessary because you could have released a MVP without the additional mess. And as you have included the unrequired features, the test matrix will also grow.</li><li><strong>Marketing of the product will become difficult</strong>: MVP is made so that you can enter the market with a hypothesis and then test the opportunity in that market if the product is actually treasured by prospects or not. If your MVP is complex, you will have a hard time in establishing a position in the market and the customers will also not be able to adopt it easily.</li><li><strong>Cost of loss will be high:</strong> In addition to my previous point, if your hypothesis is incorrect and your idea fails then the cost of loss will be too high because you invested too much initially.</li><li><strong>You are too late to enter the market</strong>: If you got that idea of your next “big startup idea” then 90% chances are that there are existing competitors or probably someone is already half way through. If you spent too much time in developing something that just validates your idea, then probably you will realize you were already missing in action and the world has moved on.</li></ul><p><strong>Conclusion:</strong> Don’t stress too much in implementing your MVP. Atleast in the product world, first impression is never the last impression. Infact, there is no last impression for a growing product. So just beat it! But remember, it is not just about over-developing a MVP but also about under-developing a MVP. Always make sure that your MVP is complete in the sense of what a customer has to do with your product to actually call it a MVP.</p><blockquote>Liked this case study? don’t forget to share a thought or leave a clap. This will help me spread this to more people.</blockquote><p>In case you are a #startup #founder, who is depending on such vendors, here is a blog that will help you make better decisions if your vendor is not considering it “ in scope”</p><p><a href="https://medium.com/@yogyata/test-your-idea-not-the-application-the-first-thing-to-do-before-you-build-your-startup-107c99b9d8d1">Test your idea not the application</a></p><p>I talked more about the similar concepts in my last event, checkout <a href="https://youtu.be/s_zbNvM6oW0">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c21630d8afba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>