<?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 Pragati Sinha on Medium]]></title>
        <description><![CDATA[Stories by Pragati Sinha on Medium]]></description>
        <link>https://medium.com/@pragati?source=rss-fab34ba5266------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0UpGb8htzczTHVXbKQ9qtg.jpeg</url>
            <title>Stories by Pragati Sinha on Medium</title>
            <link>https://medium.com/@pragati?source=rss-fab34ba5266------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:21:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pragati/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[Gherkin, But For Your AI Prompts]]></title>
            <link>https://medium.com/analysts-corner/gherkin-but-for-your-ai-prompts-6f6ecc4a69cb?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f6ecc4a69cb</guid>
            <category><![CDATA[gherkin]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Mon, 20 Apr 2026 00:37:31 GMT</pubDate>
            <atom:updated>2026-04-20T00:37:31.833Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why Gherkin thinking beats prompt templates when you want real analysis, not just auto-generated artifacts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gsSZOx_M-HPb1IlF" /><figcaption>Photo by <a href="https://unsplash.com/@suckerpunchgourmet?utm_source=medium&amp;utm_medium=referral">SuckerPunch Gourmet</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Most BA advice about AI is stuck in the wrong gear. You’ll see tutorials on “how to use AI to write a user story” or “how to generate acceptance criteria.” That’s using a jet engine to power a stagecoach.</p><p>We’re so focused on getting the AI to produce the artifacts we’re used to — the stories, the AC, the documentation — that we’re missing what the engine is actually built for: analysis.</p><p>If you’re a BA, you probably already know about <a href="https://automationpanda.com/2017/01/30/bdd-101-writing-good-gherkin/">Gherkin</a>, where you use Given-When-Then to describe how a feature should behave so developers know exactly what to build.</p><p>But Gherkin’s logic isn’t just for your outputs. It’s a great mental model for talking to an AI. Use its principles to structure your prompts, and you stop filling out templates and start doing actual analysis.</p><p>Here are four rules that change how you work with AI as a BA.</p><h4><strong>Rule 1: Declare the state, don’t narrate the steps.</strong></h4><p>The first thing I tell newbies to Gherkin is to stop being imperative. Don’t describe every button click in your Gherkin-style acceptance criteria. Describe the business state.</p><p>When you apply Gherkin logic to a prompt, the mapping looks like this:</p><ul><li><strong>Given = system context (the state the world is in)</strong></li><li><strong>When = trigger (the event you care about)</strong></li><li><strong>Then = constraint-based outcome (what “good” looks like)</strong></li></ul><p>Most people prompt AI the same way bad Gherkin reads: step by step, micromanaging the logic.</p><p><strong>Imperative prompt:</strong></p><blockquote>First, look at this SQL schema. Then map the Customer_ID to the UUID. Then check for duplicates. Then write migration steps.</blockquote><p><strong>Declarative prompt:</strong></p><blockquote>Given a legacy database with ten years of messy data and a new CRM requiring strict UUID uniqueness, identify the logical rules needed to resolve identity conflicts without losing historical records.</blockquote><p>Same problem. Very different outputs. The first gets you a checklist. The second gets you edge cases you didn’t know to ask for, because you gave the AI a problem instead of instructions.</p><h4><strong>Rule 2: Name the actor, the action, and the system.</strong></h4><p>Good Gherkin steps don’t say “the user does something.” They specify who, what, and in what context. Vague subject, vague output.</p><p>“Explain how the error is handled” is a prompt that deserves a vague answer.</p><p>This is better:</p><blockquote>Describe how the <strong>Billing System</strong> (System) <strong>notifies</strong> (Action) the <strong>Delinquent Customer</strong> (Actor) when a <strong>Payment Method fails</strong> (Context).</blockquote><p>You’ve named the system, the action, the actor, and the business context. The AI now has enough to give you something you can actually put in front of a stakeholder. More importantly, it has enough to expose gaps in your thinking before your stakeholder does.</p><h4><strong>Rule 3: Test one behavior across many variables in a single prompt.</strong></h4><p>In Gherkin, you don’t write ten separate scenarios for ten types of users doing the same thing. You write one Scenario Outline with an examples table. Same logic, different data, one place to maintain it.</p><p>Do the same when you’re prompting for analysis across roles, tiers, or conditions:</p><blockquote>Analyze the impact of a Refund action for each of these user tiers:</blockquote><blockquote>Basic: request only, $0 limit</blockquote><blockquote>Manager: instant approval, $500 limit</blockquote><blockquote>Admin: full override, unlimited”</blockquote><p>One prompt. Three analyses. Consistent structure across all three so you can actually compare them.</p><p>The alternative is three separate prompts that come back in different formats with different assumptions baked in, and now you’re reconciling instead of analyzing.</p><h4><strong>Rule 4: One prompt, one goal.</strong></h4><p>In Gherkin, a scenario with six Whens and seven Thens is garbage. It’s testing too many things at once and when it fails, you don’t know why.</p><p>The same is true of prompting. Don’t throw a “mega-prompt” at the AI asking for the user stories, the functional specs, and the test plan all at once. You’re asking the AI to hold too many loosely related goals in its brain all at once. Break it down.</p><blockquote><strong>Prompt 1:</strong> Define the business logic and constraints.</blockquote><blockquote><strong>Prompt 2:</strong> Ask for edge cases against that logic.</blockquote><blockquote><strong>Prompt 3: </strong>Draft the stories from the edge cases.</blockquote><p>Three prompts. Three tight outputs you can actually use. Each one builds on the last, which means errors stay small and fixable instead of compounding through an entire deliverable.</p><p>The underlying principle across all four rules is the same one that makes Gherkin useful in the first place: write clearly enough that a human stakeholder could read it and understand exactly what business problem you’re solving.</p><p>If it’s clear enough for a human, it’s clear enough for the AI.</p><p>The point isn’t to teach you how to write better prompts. It’s to show that the discipline of writing one well forces you to clarify what you’re actually asking — and that’s usually where analysis breaks down first.</p><p>Stop using AI to fill out templates. Use it to surface the risks, edge cases, and gaps you haven’t thought of yet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f6ecc4a69cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/gherkin-but-for-your-ai-prompts-6f6ecc4a69cb">Gherkin, But For Your AI Prompts</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Monkey Who Kept His Heart in the Tree]]></title>
            <link>https://medium.com/illumination/the-monkey-who-kept-his-heart-in-the-tree-04a4c53a9926?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/04a4c53a9926</guid>
            <category><![CDATA[folklore]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 22:38:56 GMT</pubDate>
            <atom:updated>2026-03-09T22:38:56.701Z</atom:updated>
            <content:encoded><![CDATA[<h4>A folktale about crocodiles, AI, and knowing what not to hand over</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6S64rqncqwKeuS_Y" /><figcaption>Photo by <a href="https://unsplash.com/@antoniolopezvelasco?utm_source=medium&amp;utm_medium=referral">Antoino Lopez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When I was a kid, I used to watch this old Hindi cartoon — colorful, slightly dark, and completely normal for ’90s children’s programming.</p><p>The two <a href="https://www.talesofpanchatantra.com/the-monkey-and-the-crocodile">main characters were a monkey and a crocodile</a> who had somehow become friends across their very obvious food chain differences. The monkey lived in a jamun (plum-like fruit) tree by the river. The crocodile lived in the water, grumpy but loyal enough. Everything was fine until a wife got involved (of course!).</p><p>The crocodile’s wife decided she wanted to eat the monkey. She claimed she was sick, that only a monkey’s heart could cure her. The husband resisted (he wasn’t a monster, just an obedient spouse in a moral dilemma) but eventually, happy wife, happy life won.</p><p>So, he went to invite the monkey for dinner.</p><p>The monkey was trusting enough to climb onto a crocodile’s back and smart enough to survive it. When, halfway across the river, the crocodile nervously confessed the real dinner plan, the monkey paused just long enough to sound casual and said, “Oh, why didn’t you tell me sooner? My heart’s back in the tree.”</p><p>The crocodile paddled back. The monkey leapt off, scrambled up the branches, and shouted down: “You fool. Who keeps their heart outside their body?”</p><p>A little cruel. Completely fair.</p><p>I think about that monkey on and off when I’m working with AI.</p><p>Not because AI is plotting against you or me. It isn’t, it’s a tool. But the dynamic feels familiar. You start curious. The thing is fast and capable and willing to carry you. But somewhere in the middle of crossing the river, you look down and realize how much you’ve handed over, and you start wondering where your judgment went.</p><p>The monkey didn’t swear off crocodiles. He just never forgot which part of himself needed to stay on shore.</p><p>That instinct — run the experiment, stay curious, but keep something tethered — is what I had in mind when I built the <a href="https://www.notion.so/marketplace/templates/ai-pilot-canvas">AI Pilot Canvas</a>, a free tool for testing AI use cases before committing to them. Not a framework for being afraid of AI. A framework for being smart about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*se32GdMwtUWFr89SIrhi5Q.png" /><figcaption><a href="https://www.notion.so/marketplace/templates/ai-pilot-canvas">AI Pilot Canvas</a> #StressTestBeforeYouInvest</figcaption></figure><p>The monkey knew what he was willing to risk before he got on the crocodile’s back. That’s still good advice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04a4c53a9926" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/the-monkey-who-kept-his-heart-in-the-tree-04a4c53a9926">The Monkey Who Kept His Heart in the Tree</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Leadership Gap]]></title>
            <link>https://medium.com/analysts-corner/the-leadership-gap-d3f155fccf9f?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3f155fccf9f</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Tue, 17 Feb 2026 11:22:32 GMT</pubDate>
            <atom:updated>2026-08-06T23:04:06.346Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Leadership Gap: How to Build Influence When You “Don’t Lead Anyone Yet”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rATvl8qpeEea-wro" /><figcaption>Photo by <a href="https://unsplash.com/@micheile?utm_source=medium&amp;utm_medium=referral">micheile henderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When you are early in your Business Analysis career, everyone tells you to “show leadership.” But almost no one tells you what that actually looks like when you don’t “lead” anyone yet.</p><p>That gap between the vague instruction to “be a leader” and the daily reality of “just trying to figure Jira out” is where a lot of talented BAs stall.</p><p>The way to bridge this gap is to change your mental model. You aren’t just completing tasks; you’re building <strong>leadership capital</strong>.</p><h3>The Bank Balance in Their Heads</h3><p>Think of <strong>leadership capital</strong> like a bank balance that lives in other people’s heads. It represents how much they trust your judgment, how much they believe you’ll follow through, and how safe they feel telling you the truth.</p><p>Here is the reality of the BA role: <strong>You are constantly making withdrawals.</strong></p><p>Every time you ask a stakeholder for a decision, challenge a specific requirement, or propose a new way of working, you are spending from that balance. If your balance is low, you can have a perfectly good suggestion and still feel like you are pushing a boulder uphill on every project.</p><p>But if you consciously build that balance, you trigger the <strong>leadership paradox</strong>: The more capital you have built, the less of it you need to spend to move things forward. People start taking your ideas seriously sooner, and you stop having to fight for every inch.</p><p>So, how do you grow that balance when you are still figuring out the difference between a “business requirement” and a “user story”? You follow three repeating loops: <strong>Learn, Earn, and Return.</strong></p><h4>Phase 1: Learn (The Foundation)</h4><p>In your first 90 days, your job is not to be the smartest person in the room. Your job is to become the <strong>most curious</strong> person in the room. You build capital by:</p><ul><li>Learning how your company actually makes money, rather than just memorizing which functionalities live in which systems.</li><li>Studying the basics of good analysis (problem framing, process mapping, simple diagrams), until they are second nature.</li><li>Asking the questions others are too shy to ask.</li></ul><h4>Phase 2: Earn (The Outcome)</h4><p>Over time, you shift from “learning how things work” to “helping things work better”. This is where you earn your stripes; not through your job title, but through the relief stakeholders feel when you show up. You earn capital when you:</p><ul><li>Find edge cases before they explode in production.</li><li>Facilitate conversations so two departments actually agree on a single definition.</li><li>Turn a messy problem into multiple clear options with trade-offs.</li></ul><p>Notice that these are <strong>deliverable-agnostic</strong>. It doesn’t matter if the output is a user story or a slide. What matters is that decisions got easier because you were involved.</p><h4>Phase 3: Return (The Community)</h4><p>There is a misconception that you have to wait ten years to give back. You can “return” capital immediately, marking yourself as someone who lifts others up. You do this by:</p><ul><li>Sharing notes or templates that helped you with a new teammate.</li><li>Volunteering to walk an intern through how you prepared for a workshop.</li><li>Posting an honest reflection on what you learned during a sprint.</li></ul><h3>The Vision: From Justification to Trust</h3><p>When you commit to these loops, the dynamic of your job changes.</p><p>Early on, you have to explain yourself constantly. You justify your questions. You triple-check that you are “allowed” to speak up. But as your track record grows, those same stakeholders start turning to you and asking, <strong>“What do you think?”</strong> before you even open your mouth.</p><p>That is the power of high leadership capital.</p><h3>Stop Guessing Your Way Through</h3><p>Building these foundations requires invisible work, and trying to guess your way through it often leads to burnout.</p><p>That is why I created <a href="https://www.notion.so/marketplace/templates/your-first-90-days-as-a-business-analyst"><strong>Your First 90 Days as a Business Analyst</strong></a><strong> </strong>as a free Notion micro-course. Think of it as a small playbook that sits beside your day job. It is designed to nudge you to understand your role, map one real process, and document one thing clearly without the overwhelm.</p><figure><img alt="A Screenshot of Your First 90 Days as a Business Analyst: Notion Micro-Course." src="https://cdn-images-1.medium.com/max/1024/1*qkJJeOvO4dgqZc7uZbmdrQ.png" /><figcaption>Your First 90 Days as a Business Analyst: Notion Micro-Course</figcaption></figure><p>If you are ready to stop guessing and start building the trust you need for the rest of your career, check out the micro-course. Let’s grow our leadership capital as a community, not just as individuals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3f155fccf9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/the-leadership-gap-d3f155fccf9f">The Leadership Gap</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your First 90 Days as a Business Analyst]]></title>
            <link>https://medium.com/@pragati/your-first-90-days-as-a-business-analyst-96ffe7ae5fd8?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/96ffe7ae5fd8</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Wed, 28 Jan 2026 18:56:09 GMT</pubDate>
            <atom:updated>2026-08-06T23:03:42.808Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="House number ninety (90) on a textured gray surface with dirt stains visible. The numbers are made of a metal base, painted black and the metal is oxidized" src="https://cdn-images-1.medium.com/max/1024/0*fw7zcATT4-bw79si" /><figcaption>Photo by <a href="https://unsplash.com/@lallaoke?utm_source=medium&amp;utm_medium=referral">Lallaoke</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’re a new BA and secretly thinking “I should switch to QA, at least I’d know what I’m doing” – I wrote something for you.</p><p>It’s the 90‑day path I wish someone had handed me in my first role: what to do in Week 1 when you don’t even know what counts as a problem, what to say when your manager says “I need the requirements by Friday,” and how to know you’re actually getting better.</p><p>I’ve parked it in a Notion Hub.</p><p><a href="https://www.notion.so/Your-First-90-Days-as-a-Business-Analyst-2f6d225c759f8021af14e92d4e647734?source=copy_link">Your First 90 Days as a Business Analyst | Notion</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96ffe7ae5fd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Change Manager’s Real Job (and why most get it wrong)]]></title>
            <link>https://medium.com/analysts-corner/the-change-managers-real-job-and-why-most-get-it-wrong-f37d088902af?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/f37d088902af</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[business-transformation]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Mon, 29 Sep 2025 00:10:47 GMT</pubDate>
            <atom:updated>2026-08-06T22:37:41.753Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How change managers can use problem validation tools to design better change plans.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5kNpE_AnM4oPo2zF" /><figcaption>Photo by <a href="https://unsplash.com/@heydedesign">Matthias Heyde</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>Most change managers spend their time in the wrong place.</p><p>They’re writing communications for changes that shouldn’t happen. They’re designing training for solutions that don’t work. They’re trying to drive adoption of things that solve the wrong problem.</p><p>Here’s the thing: it’s not their fault.</p><p>By the time most change managers get involved, the decisions have been made. The solution is locked in. Their job becomes:</p><blockquote><strong><em>Make people use this thing we’ve already built.</em></strong></blockquote><p>But the best change managers? They ask different questions. And they use those insights to design better change plans.</p><h3>The change plan problem</h3><p>Your job is to design a change plan that gets people to adopt the solution. But here’s what makes that nearly impossible: most solutions were never properly validated in the first place.</p><p>You’re asked to create communications, training, and engagement strategies for something that might not even solve the right problem. It’s like being asked to sell a product that nobody wants.</p><p>So what can you do? You can’t redesign the solution, but you can understand the real problem it’s supposed to solve. And that understanding changes everything about how you approach the change plan.</p><h3>Build this into your discovery process</h3><p>Before you start writing communications or designing training, spend a week doing discovery: change discovery.</p><p>Use the <a href="https://proofsprint.substack.com/i/161019401/requirements-compass">Requirements Compass</a> in your stakeholder interviews. Instead of just asking:</p><blockquote><em>“What’s changing?”</em></blockquote><p>Ask:</p><blockquote><em>“What problem is this solving?”</em></blockquote><p>Map out whether you’re dealing with validated problems, technical constraints, business preferences, or assumed solutions.</p><figure><img alt="Circular quadrant diagram with concentric circles used to map requirements by type and level of supporting evidence." src="https://cdn-images-1.medium.com/max/1024/1*gu5H7hfHAOmSK3pWtwj2EA.png" /><figcaption>Requirements Compass: Visual tool that sorts inputs into quadrants (Real Problems, Assumed Solutions, Constraints, and Preferences) and layers them by evidence strength to expose risky assumptions.</figcaption></figure><p>This tells you what story you need to tell. If it’s a validated problem, you can lead with the pain it’s solving. If it’s a business preference, you need to focus on benefits and buy-in. If it’s an assumed solution, you need to be extra careful about adoption barriers.</p><p>Next, use the <a href="https://proofsprint.substack.com/i/161019401/behavior-lens">Behavior Lens</a> to observe people in their actual work environment. Don’t just interview them. Watch them work for an hour or two. See how they currently handle the process you’re trying to change.</p><figure><img alt="Circular diagram with four quadrants and three concentric rings, used to classify observed user behaviors by type and impact." src="https://cdn-images-1.medium.com/max/1024/1*HNqcm4Ha4QuczhcZ_RhOOg.png" /><figcaption>Behavior Lens: Quadrant and concentric circle layout used to map user friction by type (e.g., bottlenecks, workarounds) and urgency, revealing what’s actually happening in practice.</figcaption></figure><p>You might discover things like: people email invoices because they trust that method, but they don’t trust the new form because it doesn’t give confirmation. Now your change plan can address trust, not just process compliance.</p><p>Finally, use the <a href="https://proofsprint.substack.com/i/161019401/solution-field-map">Solution Field Map</a> to think through what type of change strategy you actually need. Is this fundamentally a process change? A technology adoption challenge? A behavior shift? Or a communication issue?</p><figure><img alt="3x3 grid comparing solution ideas by type (People, Process, Technology) and ambition level (Safe Bet, Stretch Goal, North Star)." src="https://cdn-images-1.medium.com/max/1024/1*VydA4jlaABG-tE7Zbo4eVQ.png" /><figcaption>Solution Field Map: Structured grid that helps teams explore and compare solution options across ambition and type, before committing to delivery.</figcaption></figure><p>Each type needs a different approach. A process change needs clear workflows and role clarity. A technology adoption needs hands-on practice and troubleshooting support. A behavior change needs reinforcement and social proof. A communication issue needs better messaging and feedback loops.</p><p>As you go, capture everything in the <a href="https://proofsprint.substack.com/i/161019401/evidence-box">Evidence Box</a>. Not just what people tell you, but what you observe, what assumptions you uncover, and what resistance patterns you see.</p><figure><img alt="Three-column canvas with structured sections for capturing validated problems, user behavior insights, and solution test results." src="https://cdn-images-1.medium.com/max/1024/1*P5A5Ts1uURtZwGc2ET3JMA.png" /><figcaption>Evidence Box: Central synthesis tool that tracks what’s been validated, what’s failed, and what still needs investigation (fed by the other Proof Sprint tools).</figcaption></figure><h3>Design your change plan</h3><p>Now when you sit down to design your actual change plan, you’re not guessing.</p><p><strong>Your communications</strong> can address the real concerns instead of generic change messaging. If people don’t trust the new system, your comms focus on reliability and transparency, not just features.</p><p><strong>Your training</strong> can tackle actual friction points instead of just explaining how the tool works. If people struggle with a specific step, you build practice around that step.</p><p><strong>Your engagement strategy</strong> can target the real influencers and address the real barriers. If managers are worried about losing visibility, you show them how they’ll actually gain it.</p><p><strong>Your success metrics</strong> can track behavior change, not just system usage. Instead of measuring “form submissions,” you measure “invoice processing time” or “approval clarity.”</p><h3>Track what’s actually working</h3><p>As your change plan rolls out, keep using the <a href="https://proofsprint.substack.com/i/161019401/evidence-box">Evidence Box</a> to track what’s working and what isn’t. Not just adoption rates, but the underlying behaviors and problems.</p><p>Are people using the new process but finding workarounds for certain steps? That tells you where to adjust your approach.</p><p>Are communications landing well with some teams but not others? That tells you how to segment your messaging.</p><p>This way, when you need to course-correct (and you will), you’re making decisions based on evidence, not instinct.</p><h3>The bottom line</h3><p>Good change management isn’t just about execution. It’s about designing a plan based on reality, not assumptions.</p><p>These tools don’t replace your expertise in communications, training, and engagement. They give you better inputs to work with during your discovery phase, so your change plan actually addresses what’s happening on the ground.</p><p>And when your change plan is grounded in real problems and real behaviors, people don’t just comply, they actually adopt the change.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f37d088902af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/the-change-managers-real-job-and-why-most-get-it-wrong-f37d088902af">The Change Manager’s Real Job (and why most get it wrong)</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Win the Quiet Race: Spot Legacy Pain and Pick the First Fix]]></title>
            <link>https://medium.com/analysts-corner/win-the-quiet-race-spot-legacy-pain-and-pick-the-first-fix-76c5b916b32b?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c5b916b32b</guid>
            <category><![CDATA[discovery]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 11:56:35 GMT</pubDate>
            <atom:updated>2026-08-06T22:37:13.097Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j2O9Ph9JzCBs_Ipb" /><figcaption>Photo by <a href="https://unsplash.com/@deandavid?utm_source=medium&amp;utm_medium=referral">Dean David</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Most teams run two races at the same time. The loud race ships new features, wins demo slots, and fills the release notes. The quiet race keeps yesterday’s system from tripping on its own laces.</p><p>We celebrate the loud race because it is visible. But the quiet race stays after hours and eats overtime without asking. That silence costs more than anyone budgets for.</p><p>I built <a href="https://proofsprint.substack.com/p/scoping-without-the-spiral">Scope Check</a> for the loud races to determine if a fresh idea earns funding.</p><p>The quiet race, however, needed its own lens, so I built the <strong>Recovery Check</strong>.</p><h3>Why Recovery Check matters</h3><p>Scope Check asks:</p><blockquote><em>Do we build.</em></blockquote><p>Recovery Check asks:</p><blockquote><em>What is broken, and what do we fix first.</em></blockquote><p>Same one–page format, but pointed at a very different moment.</p><p>The Recovery Check fits when slow reports, stalled month-end close, or bad data nag the team. It turns quiet pain into facts the room can see. Then it helps the group pick the first stitch instead of guessing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vT8jUsoOplZgqyMF.png" /><figcaption>Recovery Check</figcaption></figure><h3>Ten boxes, one page</h3><p>A single canvas guides the conversation. Each box earns its spot.</p><ul><li><strong>Lost Opportunity</strong> records the hours, sales, or goodwill that drift away every day.</li><li><strong>Domino Effect</strong> shows how one snag in Ops delays Finance, Support, and finally the customer.</li><li><strong>Real Costs</strong> puts numbers on the pain so budget owners pay attention.</li><li><strong>Coping Tactics</strong> lists the scripts and side spreadsheets that keep the lights on.</li><li><strong>Breaking Point</strong> marks when those quick fixes will fail.</li><li><strong>Change Capacity</strong> checks if people and politics can carry the repair now.</li><li><strong>Solution Ideas</strong> suggest fixes sized to the wound.</li><li><strong>New Normal</strong> describes daily work once the leak is sealed. If it sounds like today, aim higher.</li><li><strong>Success Signals</strong> define proof the fix works, like cycle time falling or tickets dropping.</li><li><strong>Reality Check</strong> surfaces hidden links, expiring licences, and key staff who might be away.</li></ul><h3>Running a Recovery Check session</h3><p>Print the canvas, open a Miro board, or sketch the grid on a whiteboard. Invite those who feel the strain and those who sign the budget. Walk left to right in two short passes.</p><p>First pass, write what the group already knows.</p><p>Second pass, fill gaps with quick facts or mark them for follow-up.</p><p>Stop when every box has at least one clear statement.</p><p>Stand back, take stock of what you have, and ask which single fix buys the most relief in the next sprint. Pick the problem, assign a name, and capture the action. Store the canvas where everyone can see it, then review after each repair.</p><h3>What changes after one hour</h3><p>Legacy pain stays invisible until someone writes it down. Recovery Check makes the leak visible, counts it, and links every repair to a simple measure. Teams gain a shared understanding, a ranked list, and proof the work matters.</p><p>That is enough to win the quiet race for another lap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c5b916b32b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/win-the-quiet-race-spot-legacy-pain-and-pick-the-first-fix-76c5b916b32b">Win the Quiet Race: Spot Legacy Pain and Pick the First Fix</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Law & Order Marathons Taught Me About Requirements That Jira Never Did]]></title>
            <link>https://medium.com/analysts-corner/what-law-order-taught-me-about-requirements-that-jira-never-did-92ef8b13c55f?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/92ef8b13c55f</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Mon, 30 Jun 2025 02:20:18 GMT</pubDate>
            <atom:updated>2026-08-06T22:25:15.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ML9bGVkOFxQE28y" /><figcaption>Photo by <a href="https://proofsprint.substack.com/p/true">JOSHUA COLEMAN</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>The Evidence Box, the hub of the <a href="https://proofsprint.com/#proof101">Proof Sprint </a>method didn’t come from agile ways of working. It came from crime procedurals.</p><p>I’ve watched way too much <a href="https://en.wikipedia.org/wiki/Law_%26_Order:_Special_Victims_Unit">Law &amp; Order: SVU</a>. There’s a scene in almost every episode where detectives gather around a giant evidence board. Photos. Strings. News clips. Witness statements. Suspects. Everything visible. Everything connected.</p><p>It wasn’t the drama that got me. It was the system of sharing information.</p><p>No one was texting about crucial updates. No one wondering, “Didn’t you get my email?”</p><p>Every insight lived on the board. One place. One view. One shared truth.</p><p>Meanwhile, at work, I was drowning in stakeholder emails, Slack threads, and meeting notes in five different places. My requirements documents were already outdated by the time they were approved.</p><p>I wondered: What if business analysis worked more like detective work?</p><h3>How I accidentally built this</h3><p>For years, I kept a running “brain dump” document for my projects.</p><p>It wasn’t a methodology. It was survival. A way to keep my head above the water.</p><p>I threw everything into it. Requirements, yes, but also contradictions, offhand comments, things I wasn’t sure were important until they came up again.</p><p>At some point, I realized I was unconsciously sorting things into three piles:</p><ul><li>What we think we know about the problem</li><li>What people actually do</li><li>What we’ve tried and learned</li></ul><p>When I started sharing this method with my peers, they said it helped them think more clearly. Feel more grounded. Be more confident in pushing back.</p><p>That’s when I knew it wasn’t just a personal system.</p><h3>It’s not just a document</h3><p>The Evidence Box isn’t a form or a framework. It’s a shared surface. A Miro board, a Notion page, a Confluence page, or a paper taped to the wall. It doesn’t matter.</p><p>The magic comes from making your discoveries (and linked evidence) visible to everyone at once.</p><p>No more “did you read the doc?”<br>No more version control.</p><p>It’s three columns. Four sections in each.</p><ul><li><strong>Problem Evidence</strong> on the left</li><li><strong>User Behavior</strong> in the middle</li><li><strong>Solution Tests</strong> on the right</li></ul><p>Each section forces you to separate fact from assumption, observation from opinion, results from intention.</p><p>Contradictions stop being confusing. They start becoming valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_lSwLCtuXMcRdavz.png" /><figcaption>The Evidence Box, the hub of the <a href="https://proofsprint.com/#proof101">Proof Sprint</a> method, a lean toolkit for validating assumptions before building solutions.</figcaption></figure><h3>When contradictions create insight</h3><p>Let’s say the Sales leader says: “Sales reps are wasting too much time writing emails. They need AI help.”</p><p>You start filling the Evidence Box.</p><p><strong>Problem Evidence</strong>: Stakeholder says writing is the issue, but your interviews show reps spend more time <em>deciding</em> and <em>prioritizing </em>than writing.</p><p><strong>User Behavior</strong>: You observe reps skipping AI summaries. Ignoring Smart Compose. Forwarding emails to themselves as reminders.</p><p><strong>Solution Tests</strong>: You pilot an AI writing assistant. It flops. Reps say one bad suggestion kills trust. But a prioritization feature? It sticks.</p><p>That’s when the real insight clicks. The root problem isn’t writing speed. It’s triage.</p><p>The reps aren’t struggling to write emails. They’re overwhelmed deciding what matters.</p><p>That clarity only emerges when you lay claims, behavior, and outcomes side by side. The tension between them reveals the truth.</p><h3>Why three sections work</h3><p>Each section checks the others.</p><p><strong>Problem Evidence</strong> shows what people <em>believe</em> the problem is. But it forces the follow-up: “What do we know for sure?”</p><p><strong>User Behavior</strong> often says otherwise. Stakeholders think writing is slow. Observations show reps are actually stuck in decision loops.</p><p><strong>Solution Tests</strong> close the loop. AI writing support gets ignored. But triage tool pilots gain traction.</p><p>The contradiction becomes your compass. It helps you pivot early, before wasted effort becomes sunk cost.</p><h3>Your professional insurance policy</h3><p>Here’s what we often get wrong about senior stakeholders: They don’t actually want status update decks. They just need a single source of truth.</p><p>The Evidence Box becomes that source.</p><p>New stakeholder? Send them the Evidence Box.<br>Executive update? Show them the Evidence Box.<br>Six months later, someone questions a decision? The Box explains the “why.”</p><p>But the real value is in tough moments.</p><p>Let’s say a senior stakeholder has a strong opinion about what to build, but no solid evidence to prove the business need. In traditional requirements work, you have two bad options: Push back (and be labelled “the difficult one”), or build it (and hope it works).</p><p>With the Evidence Box, you can say: “Let’s add that to ‘what we suspect matters, but needs validation.’ We haven’t found supporting data yet, but it’s captured as an important consideration.”</p><p>You acknowledge them. You show your process. You hand them the choice with visibility into the risk.</p><p>Later, if you must build it and it fails? No finger-pointing. Everyone can see what was known, what was assumed, and what was decided anyway.</p><p>This isn’t about being right or wrong. It’s about showing your reasoning.</p><h3>The hypothesis advantage</h3><p>In the Evidence Box, I call business problems “hypotheses” until proven to be true.</p><p>Why hypothesis?</p><p>Problem statements are only statements when proven. Until then, they are just something we think might be true.</p><p>That shift does more than protect your credibility. It creates room for discovery.</p><p>If you’re wrong, it’s not a failure. It’s a win. You investigated and learned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-QK_-4ZaruLA5um7.png" /><figcaption>It’s a hypothesis, not a statement</figcaption></figure><h3>Picture this scenario</h3><p>You’re three weeks into what seemed like a straightforward project. Your stakeholders are pulling you in different directions. Your users are complaining about issues no one mentioned earlier. Your dev team is asking for clarity you don’t have.</p><p>So you pause. You create the Evidence Box. You fill it with what you’ve got.</p><p>Stakeholder claims land in Problem Evidence.<br>User friction goes in User Behavior.<br>Solution ideas and quick tests slot into Solution Tests.</p><p>Within a few hours, patterns start emerging.</p><p>Maybe everyone’s been focused on one loud complaint when the root cause is elsewhere.</p><p>Maybe that half-baked fix from last week revealed the real issue.</p><p>The Box doesn’t give you answers, but it organizes the chaos so you can ask better questions and find clearer answers.</p><h3>From chaos to institutional memory</h3><p>Institutional knowledge doesn’t just get lost between sprints. It evaporates between people.</p><p>That’s why teams repeat mistakes. If the “lessons learned” doc is 10 pages, no one reads it, and even fewer understand it.</p><p>The Evidence Box changes that.</p><p>When you move on from a project, the Box shows what was built, <em>why</em> it was built, and <em>what was learned</em> along the way.</p><p>It turns experience into reusable insight.</p><p>You don’t start every project from zero. You start with a trail of proof.</p><h3>Start before you’re ready</h3><p>You don’t need permission.</p><p>Pick your tool: Miro, Notion, Confluence, Google Docs.</p><p>Create three sections: Problem Evidence. User Behavior. Solution Tests.</p><p>Fill it in as you go. You don’t need perfect evidence. Just a place to capture and document what you’re learning.</p><p>The first time you show it to a stakeholder, they’ll nod.</p><p>The second time, they’ll start showing up with better inputs.</p><p>The third time, they’ll ask: “Can we use that format again?”</p><p><strong>The Evidence Box is the hub of the </strong><a href="https://proofsprint.com/#proof101"><strong>Proof Sprint</strong></a><strong> method: a lean toolkit for validating assumptions before building solutions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*jm2eYFK8RKkH8Wg_b4cBsA.png" /><figcaption>The Evidence Box Snapshot</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92ef8b13c55f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/what-law-order-taught-me-about-requirements-that-jira-never-did-92ef8b13c55f">What Law &amp; Order Marathons Taught Me About Requirements That Jira Never Did</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Ambition Outruns Readiness]]></title>
            <link>https://medium.com/analysts-corner/when-ambition-outruns-readiness-e3f98c8ef633?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3f98c8ef633</guid>
            <category><![CDATA[proof-sprint]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[business-transformation]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Tue, 20 May 2025 06:11:41 GMT</pubDate>
            <atom:updated>2026-08-06T22:24:37.189Z</atom:updated>
            <content:encoded><![CDATA[<h4>A simple way to see what your big solution is really asking of you.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w5BnVoEL4gOTDKPg" /><figcaption>Photo by <a href="https://unsplash.com/@daniele_franchi?utm_source=medium&amp;utm_medium=referral">Daniele Franchi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You’ve got a good idea on the table. One that feels right.</p><p>The problem’s been validated.<br>The behavior is clear.<br>The solution makes sense.</p><p>Everyone nods. “Let’s do it.”</p><p>But then the silence creeps in.</p><blockquote>“Do we even have the team for this?”<br>“Are stakeholders actually bought in?”<br>“This changes… a lot, doesn’t it?”</blockquote><p>Suddenly, the confident decision starts to feel less clear. Not because the idea is wrong. But because <strong>you never realized how far this solution would pivot you away</strong> from how your team actually works.</p><h3>The problem isn’t the change</h3><p>It’s the <strong>stretch</strong>.</p><p>The “stretch” is the hidden load a change (aka any solution) places on the people, processes, and technology expected to deliver it.</p><p>Most ideas don’t fail because they’re flawed. They fail because they <strong>ask for more change than the team (or the organization) can absorb.</strong></p><p>That stretch might look like:</p><ul><li>A new way of working that no one’s heard of before</li><li>A tool that requires retraining and rework</li><li>A behavior shift that challenges how people make decisions</li><li>A stakeholder who says “yes” but acts “maybe”</li><li>A team that’s already full and can’t take on more</li></ul><p>It’s not the idea or solution itself. It’s the ripple it creates. On your team, your department, your organization.</p><p>Unless you name that <em>stretch</em> early, you won’t see the <em>snap</em> until it happens.</p><h3>Remodeling the kitchen</h3><p>Think of proposing a new solution like saying, <em>“Let’s remodel the kitchen.”</em></p><p>You think you’re just replacing cabinets. Maybe a fresh coat of paint.</p><p>But then:</p><ul><li>The kitchen layout needs to change → <strong>workflow disruption</strong></li><li>You realize your circuit box can’t handle the new appliances → <strong>tech/tooling</strong></li><li>Your partner doesn’t want to lose the breakfast nook → <strong>cultural resistance</strong></li><li>You’ll both be working from home during construction → <strong>capacity issue</strong></li></ul><p>Now you’re not just choosing cabinets. You’re redoing plumbing, rewiring the house, and negotiating a lifestyle shift.</p><p>The original idea wasn’t bad. But the <em>stretch</em>? That’s where the real risk lives.</p><h3>What the Pivot Radar is</h3><p>The <strong>Pivot Radar</strong> is a quick tool to visualize the hidden stretch inside any proposed change or solution.</p><p>Why “Pivot”?</p><p>Because most changes aren’t a full 180-degree turn. They’re small but meaningful shifts in direction, ambition, or load. This tool helps you map how far each solution idea pulls you away from your team’s and org’s current reality, so you don’t unknowingly pivot into burnout, resistance, or misalignment.</p><p>Start by mapping your solution idea(s) across six axes (“change dimensions”):</p><h4>1. Workflow Disruption</h4><blockquote><strong><em>How much does this change how people work day to day?</em></strong><em><br></em><strong><em>Think:</em></strong><em> task flow · habits · sequence</em></blockquote><ul><li>Is the task flow shifting?</li><li>Are familiar steps or sequences changing?</li><li>Will this break muscle memory?</li></ul><h4>2. Team Capacity</h4><blockquote><strong><em>Can the current team absorb this work, or does it exceed available bandwidth?</em></strong><em><br></em><strong><em>Think:</em></strong><em> time · skillset · mental load</em></blockquote><ul><li>Do they have the hours <em>and</em> the expertise?</li><li>Will it stretch their ability to make good decisions under pressure?</li><li>Is this piling on when they’re already threadbare?</li></ul><h4>3. Tech/Tooling Impact</h4><blockquote><strong><em>Does this require new tools, systems, or complex integrations?</em></strong><em><br></em><strong><em>Think:</em></strong><em> new systems · rework · support burden</em></blockquote><ul><li>Are we adding or replacing tools?</li><li>Will this ripple into system redesigns or data cleanup?</li><li>Who maintains it after launch?</li></ul><h4>4. Culture/Mindset Shift</h4><blockquote><strong><em>Will this challenge current norms, habits, or unspoken ways of working?</em></strong><em><br></em><strong><em>Think:</em></strong><em> identity · values · social friction</em></blockquote><ul><li>Does it push against how people see their role?</li><li>Does it ask for a mindset shift that could trigger resistance?</li><li>Will this feel like “how we work” or like a foreign thing?</li></ul><h4>5. Stakeholder Appetite</h4><blockquote><strong><em>Are key stakeholders fully supportive, hesitant, or resistant to this idea?</em></strong><em><br></em><strong><em>Think:</em></strong><em> posture · politics · follow-through</em></blockquote><ul><li>Are they championing it or just nodding?</li><li>What happens when this idea meets competing priorities?</li><li>Will they fight for it or ghost it?</li></ul><h4>6. External Dependencies</h4><blockquote><strong><em>Will this rely on vendors, partners, or external timelines that may slow progress?<br>Think:</em></strong><em> third-party risk · timing · access</em></blockquote><ul><li>Do we control the timeline?</li><li>Are we waiting on others to deliver key pieces?</li><li>Is coordination straightforward or high-risk?</li></ul><p>Score each change dimension from <strong>0 (no stretch or minimal disruption)</strong> to <strong>5 (major stretch or maximum disruption)</strong>.</p><p>Then plot the values on a radar chart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8Dgkn4stjxVRaraU.png" /><figcaption>Pivot Radar — a <a href="https://proofsprint.com/">Proof Sprint</a> tool</figcaption></figure><h3>Compare at least three options</h3><p>Don’t just visualize one solution option.</p><p>If you’re using the <a href="https://proofsprint.substack.com/i/161019401/solution-field-map">Solution Field Map</a>, the Pivot Radar can be your next move.</p><p>The Field Map prompts you to explore solution ideas by ambition (Safe Bet, Stretch Goal, North Star) and type (People, Process, Technology).</p><p>The Pivot Radar takes your top solution ideas a step further and prompts you to ask:</p><blockquote><strong><em>Which of these actually fits our team, our culture, our moment?</em></strong></blockquote><p>Even if you’re not using the full Field Map, <strong>brainstorm at least three solution options</strong> with varying levels of ambition:</p><ul><li>One that’s minimal and easy to land (“safe bet”)</li><li>One that’s bold and visionary (“north star”)</li><li>One that sits in the middle (“stretch goal”)</li></ul><p>Each option might solve the same problem, but they ask for <em>very different things</em> in return: different levels of effort, disruption, and coordination.</p><p>The Pivot Radar helps you <strong>push beyond your first or favorite idea</strong>, so you’re not just reaching for the most familiar solution.</p><p>It also gives you a clearer picture of what your top pick actually costs in time, attention, appetite, and risk in stark contrast to other possibilities.</p><p>The Pivot Radar adds perspective, not just prioritization. You are visualizing the full weight of what you’re choosing before you commit.</p><h3>What the shapes reveal</h3><p>The shape of your solution on the radar chart you create tells a story.</p><p>If you think back to the kitchen remodel, each shape reveals what kind of renovation you’re actually committing to, even if it doesn’t look that way on the surface.</p><h4>1. The tight circle (e.g. 0–2 across the board)</h4><p>This is the surface-level refresh. New cabinet handles. A splash of paint. Maybe a drawer organizer or two.</p><p><strong>Interpretation:</strong> A low-stretch move. It fits the current system. We love these. They feel safe. Sometimes too safe!</p><p><strong>Use when:</strong> You need a quick win or want to build confidence.</p><p><strong>Warning:</strong> Don’t confuse ease with impact. Cosmetic changes won’t fix structural or systemic problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4YmMhMVtAa1T3fSn.png" /><figcaption>Pivot Radar — a <a href="https://proofsprint.com/">Proof Sprint</a> tool</figcaption></figure><h4>2. The jagged spike (e.g. 1–1–2–1–5–1)</h4><p>This is when you plan for new cabinets… but suddenly realize the electrical wiring under one wall is decades old and barely code-compliant. Now you’re rewiring the house, whether you meant to or not.</p><p><strong>Interpretation:</strong> One domain is screaming while the rest are silent. This is often a political or cultural mismatch. The idea may be right but it’s landing in hostile territory.</p><p><strong>Use when:</strong> You have the support and stamina to fight one battle.</p><p><strong>Otherwise:</strong> Reshape the solution or delay the move. It’s better to pause than blow out your circuit box mid-renovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hK7NorNiCo07mQ_9.png" /><figcaption>Pivot Radar — a <a href="https://proofsprint.com/">Proof Sprint</a> tool</figcaption></figure><h4>3. The uneven blob (e.g. 3–4–2–2–3–1)</h4><p>This is the full renovation. Layout changes. Wall removal. Plumbing updates. Appliance upgrades. All happening at once.</p><p><strong>Interpretation:</strong> Moderate stretch across most domains. Not unworkable, but not light. It takes planning, energy, and contingency.</p><p><strong>Use when:</strong> You have strong alignment and real momentum, and you’re solving something that truly matters.</p><p><strong>If not:</strong> Consider scaling back ambition or splitting the solution into phases. Fix the flow before you swap appliances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ipmiKRPeb6w5OiM7.png" /><figcaption>Pivot Radar — a <a href="https://proofsprint.com/">Proof Sprint</a> tool</figcaption></figure><h3>How to use it</h3><p>Open a Google Sheet.</p><p>List your six axes as rows (see: “What the Pivot Radar is” section above). Score each 0–5 for your proposed idea(s). Compare two or three options side by side.</p><p>You’ll quickly see:</p><ul><li>Where the stretch hides</li><li>Where your team’s tolerance lives</li><li>Whether the idea can survive or needs reshaping</li></ul><p>Here’s a <a href="https://docs.google.com/spreadsheets/d/1isUB9P5u_0Lvrz_5CFSSxttOg2qEN7btHOCJzsvWLdw/edit?usp=sharing">Google Sheet version you can copy and adapt</a>.</p><h3>When to use it</h3><ul><li>After the <a href="https://proofsprint.substack.com/i/161019401/solution-field-map">Solution Field Map</a>, when short-listed options are on the table</li><li>During roadmap planning, before bets are locked</li><li>In stakeholder meetings, to surface disagreement early</li><li>In <a href="https://proofsprint.substack.com/p/the-problem-isnt-what-happened-last">retros</a>, to reflect on why a recent effort stretched too far</li></ul><h3>What it gives you</h3><p>The Pivot Radar shows you where the <em>stretch</em> (aka load)<em> </em>lives, before it surprises you mid-project, mid-budget, or mid-morale dip.</p><p>It makes the invisible visible.</p><p>You see which ideas are quietly loaded with risk.</p><p>You see where your team might hesitate, slow down, or silently disengage.</p><p>You see how your boldest idea might still be the right one, but only with the right support behind it.</p><p>You’re not saying no to your favorite idea. You’re just going in with eyes open.</p><p>You’re not just asking, “<em>Should we build this?</em>” but “<em>Can we carry the load?</em>”.</p><h3>Want to try it?</h3><p>Here’s a <a href="https://docs.google.com/spreadsheets/d/1isUB9P5u_0Lvrz_5CFSSxttOg2qEN7btHOCJzsvWLdw/edit?usp=sharing">Google Sheet version you can copy and adapt</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3f98c8ef633" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/when-ambition-outruns-readiness-e3f98c8ef633">When Ambition Outruns Readiness</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proof Sprint: The Method Behind the Madness]]></title>
            <link>https://medium.com/analysts-corner/proof-sprint-the-method-behind-the-madness-14afd684f702?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/14afd684f702</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[proof-sprint]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Thu, 08 May 2025 13:27:26 GMT</pubDate>
            <atom:updated>2026-08-06T22:23:54.655Z</atom:updated>
            <content:encoded><![CDATA[<p><em>You shipped the thing. No one used it. Here’s what to do instead.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6LtqaWHgZ_WvVlY4" /><figcaption>Photo by <a href="https://unsplash.com/@leeroyagency?utm_source=medium&amp;utm_medium=referral">WEB AGENCY</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You shipped the thing. No one used it.</p><p>Support tickets pile up. Team morale dips. Execs want answers.</p><p>You followed the process. But you built the wrong thing.</p><p>Most teams build solutions based on what they <em>think</em> people need. It’s why projects fail, features go unused, and delivery teams burn out solving problems nobody actually has.</p><p>For months, I’ve been writing about individual tools. Testing them in the wild. You may have seen my Medium articles. Maybe you’ve even liked or saved them. Thank you.</p><p><a href="https://medium.com/@pragati/list/17a729bae2d3">Proof Sprint</a></p><p>Each post was a small experiment, a way to see if these ideas resonated before I declared what was really brewing.</p><p>I’ve hesitated from explicitly labeling the suite of tools as “Proof Sprint,” a <strong>validation loop for testing assumptions and shaping solutions.</strong></p><p>I’ve mostly referred to it as “the toolkit” and talked about the individual tools: Evidence Box, Requirements Compass, Behavior Lens, and Solution Field Map.</p><p>This is because defining a new “method” for something we’ve been doing for ages felt overly assertive, perhaps even too self-important. But the reality is that something has been simmering behind the tools for the last 6+ months.</p><p>The secret? The tools aren’t the point. The validation loop is.</p><h3>Proof Sprint is not a process, it’s a loop</h3><p>Proof Sprint isn’t a linear process.</p><p>The magic isn’t in any single tool. It’s in how they challenge and work with each other.</p><p>For example, the <strong>Requirements Compass</strong> starts off with a hypothesis. A Problem as Given (PAG): Usually a mixed bag of real problems, assumptions, desires, preferences, and solution ideas.</p><p><a href="https://medium.com/analysts-corner/from-noise-to-north-star-the-real-job-of-requirements-9aa5844aad50">From Noise to North Star: The Real Job of Requirements</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhmPWiFB1WBPpPpjR2SK7g.png" /><figcaption>The Requirements Compass</figcaption></figure><p>The <strong>Behavior Lens</strong> tests that hypothesis against the business processes: What people actually do, not what they say they do.</p><p><a href="https://medium.com/analysts-corner/beyond-process-maps-a-simpler-way-to-spot-whats-breaking-ba1dd2a61cef">Beyond Process Maps: A Simpler Way to Spot What’s Breaking</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c-bwatl_6nfR1tzmI8YiWA.png" /><figcaption>The Behavior Lens</figcaption></figure><p>Together, the Requirements Compass and the Behavior Lens feed the <strong>Evidence Box</strong>, transforming your “Problem as Given” (PAG) into a “Problem as Understood” (PAU) aka validated problem statement.</p><p>You haven’t earned the right to talk solutions until then.</p><p>Once you reach this point, the <strong>Solution Field Map</strong> helps you explore solution options based on what’s actually happening, not what someone in a boardroom decided was happening three months ago.</p><p><a href="https://medium.com/analysts-corner/the-solution-field-map-stress-test-your-options-before-you-build-1b879b15bafc">The Solution Field Map: Stress Test Your Options Before You Build</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7SgGpm172dTrx_gbANmTw.png" /><figcaption>The Solution Field Map</figcaption></figure><p>Interesting solution ideas feed back into the <strong>Evidence Box</strong>. What worked. What failed. What surprised you.</p><p><a href="https://medium.com/analysts-corner/the-evidence-box-stop-building-things-nobody-needs-d235515f7584">The Evidence Box: Stop Building Things Nobody Needs</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qa6-mhY3wW1mpAEO6yfFXA.png" /><figcaption>The Evidence Box</figcaption></figure><p><strong>But here’s the secret sauce: the loop back changes everything.</strong></p><p>When the Evidence Box shows gaps, you cycle back to the Compass with sharper questions.</p><p>When solution tests fail, you revisit your problem statement.</p><p>When patterns emerge, you see things you missed before.</p><p>That’s the power of the loop. It’s not just learning, it’s compounding clarity.</p><h3>A quick example</h3><p>Imagine you’re packing for your partner’s critical business trip. High-stakes client meetings. No time to shop. If you miss something, it’s not just inconvenient. It’s reputational.</p><p>They land, rush into meetings, and their laptop dies. No charger. Your stomach drops. You had one job.</p><p>This is exactly like product work: limited resources, high expectations, and no room for waste.</p><p>The <strong>Requirements Compass</strong> helps you separate the noise (“pack two pairs of dress shoes just in case”) from the signal (“maintain professional presence while staying connected”).</p><p>The <strong>Behavior Lens</strong> shows what actually happens: your partner rushes out of hotel rooms, leaving chargers plugged in the wall — something that oddly only happens on multi-city trips, not single-location stays.</p><p>The <strong>Solution Field Map</strong> explores options: duplicate chargers, morning checklists, multi-device charging hubs.</p><p>The <strong>Evidence Box</strong> captures what worked (dual-charger system), what failed (morning checklist was ignored), and what surprised you (it’s not about forgetfulness, it’s about rushed morning routines).</p><p>Before the next trip, you revisit the Evidence Box, adjust your approach, and loop back. Each cycle deepens clarity.</p><h3>Modular by design</h3><p>You don’t need the full loop to get value. Start where the friction is:</p><p>Use the <strong>Requirements Compass</strong> if you’re drowning in opinions and assumptions, but can’t find evidence.</p><p>Use the <strong>Behavior Lens</strong> if process maps say one thing, but users keep doing something else.</p><p>Use the <strong>Solution Field Map</strong> when everyone has an opinion on what the solution should be, and they’re all pointing in different directions.</p><h4><strong>Not sure where to start?</strong></h4><p>Begin with the <strong>Evidence Box</strong> — it’s the hub. A single view of what’s real, what’s working, and what still needs digging.</p><h3>From method to mindset</h3><p>When teams embrace Proof Sprint, the transformation is visible:</p><p><strong>Business Analysts</strong> stop chasing perfect documentation, and start surfacing the right problems faster.</p><p><strong>Product Teams</strong> move from assumption-driven to evidence-led, without slowing down delivery.</p><p><strong>Delivery Leads</strong> shift from managing work to enabling clarity, before it hits the backlog.</p><h3>The clarity loop recap</h3><ol><li><strong>Requirements Compass</strong> → What might matter</li><li><strong>Behavior Lens</strong> → What actually happens</li><li><strong>Solution Field Map</strong> → What we could do</li><li><strong>Evidence Box</strong> → What we’ve learned</li><li>→ Back to Compass, Lens or Solution Field Map depending on the context, but with sharper thinking</li></ol><p>Every cycle makes your thinking sharper. Assumptions become insights. Guesses become evidence. What felt like noise starts to reveal patterns.</p><h3>Think before you build</h3><p>This isn’t just another framework. It’s a method. A quiet correction to the way delivery teams work.</p><p>Proof Sprint can typically be run in 1–2 weeks per feature or epic. For fast-moving teams or extra-small projects, it can be completed in 2–3 days. For complex projects, it might stretch across multiple weeks, especially when solution validation is needed.</p><p>The point is: the <strong>Proof Sprint method can scale up or down</strong> depending on the context and complexity of your project.</p><p>Start small. Scale as needed. <strong>Each tool adds clarity, but you don’t need them all to begin.</strong></p><p>It’s a method today. A mindset tomorrow. And maybe, if we get it right, a movement.</p><p>Stop building on bad assumptions. Not all requirements are real. Stress test before you invest. Build only what’s real.</p><p>Clarity before delivery. Always.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14afd684f702" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/proof-sprint-the-method-behind-the-madness-14afd684f702">Proof Sprint: The Method Behind the Madness</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scope Without the Spiral]]></title>
            <link>https://medium.com/analysts-corner/scope-without-the-spiral-938c63f40b5f?source=rss-fab34ba5266------2</link>
            <guid isPermaLink="false">https://medium.com/p/938c63f40b5f</guid>
            <category><![CDATA[business-transformation]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Pragati Sinha]]></dc:creator>
            <pubDate>Thu, 08 May 2025 13:24:01 GMT</pubDate>
            <atom:updated>2026-08-06T22:23:11.970Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How to keep your project kickoff from collapsing under its own weight.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3DmkRdcaw0ObuzzW" /><figcaption>Photo by <a href="https://unsplash.com/@flub?utm_source=medium&amp;utm_medium=referral">Maxime Lebrun</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Back in January, I created a scoping canvas. I called it the <strong>Project Discovery Canvas</strong>.</p><p>Not a method. Not a framework. Just a tool. A thinking surface to help teams get clearer before greenlighting big, blurry projects. The kind where everyone’s nodding but no one’s aligned.</p><p>I shared it with a small group of peers and later posted it on LinkedIn. The response?</p><p>Polite. Curious. But mostly:</p><blockquote>“This is cool… I just don’t know what to do with it.”</blockquote><p>Which, to be honest, stung.</p><p>I still believed in the questions. I still do. But I hadn’t given people a way in. No pacing. No structure. No clarity on how to move through it or when to stop.</p><p>Just ten boxes and an invitation to explore.</p><p>That’s not a workshop. That’s a maze.</p><p>So I shelved it.</p><h3>The long shelf life of a tool that’s too much</h3><p>What happened next surprised me.</p><p>While the original scoping canvas gathered dust, I radically simplified one small part of it into what became the <a href="https://proofsprint.substack.com/i/161019401/evidence-box">Evidence Box</a>. That tool took off. It became the backbone of Proof Sprint. Everything else — the <a href="https://proofsprint.substack.com/i/161019401/requirements-compass">Compass</a>, the <a href="https://proofsprint.substack.com/i/161019401/behavior-lens">Lens</a>, the <a href="https://proofsprint.substack.com/i/161019401/solution-field-map">Field Map</a> — followed.</p><p>But the scoping canvas? It stayed in the shadows.</p><p>Until last week.</p><p>I was running a <a href="https://proofsprint.com/#">Proof Lab</a> with someone I trust, a peer whose judgment I genuinely respect. Out of nowhere, she mentioned she’d tried using the canvas.</p><p>And her words stopped me.</p><blockquote>“It’s good,” she said.<br>“But it felt like playing 50-questions with execs.”</blockquote><p>I winced. Because that wasn’t the intention at all.</p><p>And yet… it was exactly how it felt.</p><h3>When you hand someone a map, but no sense of direction</h3><p>I’d done the equivalent of handing someone a beautifully drawn map of every interesting place in the city, but I hadn’t marked where they were standing. Or where they needed to go.</p><p>It was too open. Too ambitious. Too unanchored.</p><p>That’s on me.</p><p>But the bones were still good. The questions still mattered. What it needed wasn’t a rewrite. It needed a better way in.</p><h3>So I brought it back</h3><p><strong>I gave it a new name: Scope Check.</strong></p><p>Same sections. Same prompts. New rhythm.</p><p><strong>Scope Check</strong> isn’t a replacement for Proof Sprint. It’s what comes <em>before</em>. When the project is still hazy and the pressure to deliver is already mounting.</p><p>It’s how you catch misalignment before it calcifies.<br>How you pull focus before you pull budget.</p><p>Here’s how it works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PxLCvntjt4HZ2tdf.png" /><figcaption>Scope Check</figcaption></figure><p><strong>👉 Get Scope Check tool </strong><a href="https://docs.google.com/presentation/d/1u33DkJVCvhUk_wtp1xvf9wDhwjZLjYp4xRIcXmHqnLs/edit?usp=sharing"><strong>here</strong></a><strong> (in Google Slides).</strong></p><h3>The Scope Check</h3><p>You move through the canvas in three focused passes:</p><ol><li><strong>Scan</strong> — build a confidence heatmap</li><li><strong>Zoom</strong> — go deeper where it’s unclear</li><li><strong>Anchor</strong> — identify one next step per gap, and link to the Evidence Box</li></ol><p>You don’t have to fill every box. You just need to find out where you’re standing on shifting sands.</p><h4>1. Scan</h4><p><em>Get the lay of the land.</em></p><p>Walk through each section of the canvas with your stakeholders. No deep dive yet. Just ask:</p><blockquote>“How confident are we about this part of the project?”</blockquote><p>Each person votes:</p><ul><li>✅ Confident — We’ve talked about this. Feels solid.</li><li>⚠️ Mixed — Some clarity, but still fog.</li><li>❌ Concerned — No shared understanding. Big risk.</li></ul><p><strong>How to collect votes:</strong></p><ul><li>In person: dot stickers or sticky notes</li><li>Online: emoji reactions, Miro comments, type in chat</li><li>Timebox it: 2–3 minutes per section</li></ul><p>You’re not looking for answers here.<br>You’re building a <strong>confidence map</strong>.</p><p>Even if someone reacts strongly, pause the urge to dive in. Keep moving. The conversation comes in the next step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*53XipZIbzwIE-LH9.png" /><figcaption>Scope Check — Scan</figcaption></figure><h4>2. Zoom</h4><p><em>Dig into the risky areas.</em></p><p>Look at your heatmap. Choose 2–3 sections with the most ⚠️ or ❌ votes.</p><p>For each, say:</p><blockquote>“This area raised some uncertainty. Let’s unpack what’s behind that.”</blockquote><p>Then use the <strong>prompts in that canvas box</strong>. This is the moment they’re meant for.</p><p>They’re not a script. They’re scaffolding. Use them to unlock thinking, not to interrogate.</p><p>You’ll be surprised how fast the conversation sharpens. The prompts just need the right moment.</p><p><strong>Facilitation tips:</strong></p><ul><li>Ask someone who voted ❌ to share what gave them pause</li><li>Let a team member summarize what’s known so far</li><li>Use a 5–7 minute timer per section to avoid spiraling</li></ul><p>You’re not trying to close the gap in the room.<br>You’re trying to <strong>name the shape of it</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qeA0c13HoGhjusdx.png" /><figcaption>Scope Check — Zoom</figcaption></figure><h4>3. Anchor</h4><p><em>Turn insight into action.</em></p><p>For each section you zoomed into, ask:</p><blockquote>“What’s one thing we can do to reduce this uncertainty?”</blockquote><p>Examples:</p><ul><li>A follow-up conversation: “We should loop in Finance.”</li><li>A validation activity: “Let’s test this assumption with a quick data check.”</li><li>A decision checkpoint: “We’ll wait until the vendor confirms feasibility.”</li></ul><p>You only need one action per area. That’s enough.</p><p>And here’s the important bit:</p><blockquote><em>📦 </em><strong><em>Document those actions in the Evidence Box.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A7EVLD3xB2eu2Ceb.png" /><figcaption>The Evidence Box, part of <a href="https://proofsprint.com/">Proof Sprint</a></figcaption></figure><p>This is how the Scope Check links into the rest of the <a href="https://proofsprint.substack.com/p/what-is-a-proof-sprint">Proof Sprint method</a>. It gives you a landing zone, a way to carry forward what they uncovered without losing it in post-meeting limbo.</p><p>What you capture becomes the seed for what you’ll validate later:</p><ul><li>Unclear problem statements → “What we suspect matters”</li><li>Blocked questions → “Constraints or lessons”</li><li>Team insights → “What made it real”</li></ul><p>You’re not solving everything. You’re starting the right loop.</p><h3>Don’t ignore the canvas prompts</h3><p>Use them at the right time.</p><p>This part matters.</p><p>Each section has <strong>5 question prompts</strong> for a reason. But they <em>don’t</em> belong in the Scan phase. Answering all of them upfront turns a sense-making tool into an interrogation.</p><p>Use them where they belong. In the <strong>Zoom</strong> phase, <em>and only</em> for the sections that surfaced as risky (red ❌ or yellow ⚠️).</p><p>Read them out loud. See which ones get a reaction. Follow the energy.</p><p>They were always meant to open up the conversation, not overwhelm it.</p><h3>This tool isn’t new</h3><p>I almost let this one go.</p><p>The early feedback was lukewarm. The framing didn’t land. And I shelved it — not because it didn’t matter, but because I couldn’t yet see how to make it usable.</p><p>Now I can.</p><p>This isn’t just a canvas anymore. It’s the <strong>Scope Check</strong>.</p><p>It won’t give you instant alignment.<br>It won’t fill in every gap.</p><p>But it will show you what’s known, what’s unclear, and what still needs proving, <strong>before you commit the team to solving the wrong thing, too soon, too fast.</strong></p><p>That’s what I meant to build all along.<br>And now, it’s ready to be used.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=938c63f40b5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/analysts-corner/scope-without-the-spiral-938c63f40b5f">Scope Without the Spiral</a> was originally published in <a href="https://medium.com/analysts-corner">Analyst’s corner</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>