<?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 Shanna Fillmore on Medium]]></title>
        <description><![CDATA[Stories by Shanna Fillmore on Medium]]></description>
        <link>https://medium.com/@shannatheanalyst?source=rss-da42f824af6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vFRJiqOvqi2gqFJniekV8g.png</url>
            <title>Stories by Shanna Fillmore on Medium</title>
            <link>https://medium.com/@shannatheanalyst?source=rss-da42f824af6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:26:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shannatheanalyst/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[How Business Analysts Can Prevent Rework by Verifying Understanding]]></title>
            <link>https://medium.com/@shannatheanalyst/how-business-analysts-can-prevent-rework-by-verifying-understanding-be757be0aa60?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/be757be0aa60</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 18:21:19 GMT</pubDate>
            <atom:updated>2026-07-21T18:21:19.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcvefWM_BF-_oz9vixglxA.png" /></figure><p>The meeting went well.</p><p>Everyone agreed on the requirements. Stakeholders gave their approval. The documentation was completed, and the team moved forward.</p><p>Then, a few weeks later, questions started coming in.</p><p>“That’s not what I thought we meant.”</p><p>“I assumed the process worked differently.”</p><p>“I didn’t realize this would impact my team.”</p><p>Now the project team is spending time clarifying details that everyone thought were already understood.</p><p>This situation is more common than many Business Analysts realize.</p><p>The problem is not always that requirements were missing. The problem is that people walked away with different interpretations of the same information.</p><p>A requirement can be documented perfectly and still create confusion if the people involved do not have a shared understanding.</p><p>This is where one of the most important skills of a Business Analyst comes in: verifying understanding.</p><h4><strong>Why Agreement Does Not Always Mean Understanding</strong></h4><p>One of the biggest challenges Business Analysts face is assuming that agreement means alignment.</p><p>A stakeholder may say, “Yes, that makes sense,” but what they understand may be different from what another team member understands.</p><p>Why?</p><p>Because every person views requirements through their own lens.</p><p>A business user may focus on the process outcome.</p><p>A developer may focus on how the solution will be built.</p><p>A tester may focus on how success will be measured.</p><p>A compliance team may focus on rules and risks.</p><p>Everyone can agree with the conversation while still having different expectations about what happens next.</p><p>For example, consider this requirement:</p><p>“Users need the ability to update customer information.”</p><p>At first glance, it seems clear.</p><p>But different people may interpret it differently:</p><p>The business team may think users should update all customer details.</p><p>The security team may expect only certain fields to be editable.</p><p>The development team may assume a simple update screen is needed.</p><p>The testing team may need clear rules around what changes are allowed.</p><p>The words are the same, but the understanding is not.</p><p>Without clarification, these differences often appear later during development, testing, or implementation when changes become more expensive.</p><h4><strong>The Business Analyst’s Role Is More Than Capturing Requirements</strong></h4><p>Many people think the Business Analyst’s job is to gather information, document requirements, and get approval.</p><p>Those activities are important, but they are only part of the role.</p><p>A strong Business Analyst helps teams create shared understanding.</p><p>This means making sure:</p><p>• Stakeholders understand the reason behind decisions<br>• Teams recognize how requirements impact their work<br>• Assumptions are identified before they become problems<br>• Different groups interpret requirements consistently</p><p>The goal is not simply to have a signed-off document.</p><p>The goal is to help everyone move forward with confidence.</p><h4><strong>Three Ways Business Analysts Can Verify Understanding</strong></h4><p><strong>1. Ask People to Explain Their Understanding</strong></p><p>One of the easiest ways to uncover confusion is to ask people to explain concepts in their own words.</p><p>Instead of asking:</p><p>“Does everyone understand?”</p><p>Try asking:</p><p>“How would this work in your process?”</p><p>or:</p><p>“Can you walk me through what you expect to happen in this scenario?”</p><p>These questions encourage people to think through the requirement instead of simply agreeing.</p><p>You may discover that two teams have completely different expectations.</p><p>That is valuable information.</p><p>Finding the difference during a discussion is much easier than finding it after development has started.</p><p><strong>2. Use Real-World Scenarios</strong></p><p>Requirements can often sound clear when they are discussed at a high level.</p><p>Scenarios help turn abstract ideas into practical examples.</p><p>Instead of:</p><p>“The system should send notifications.”</p><p>Ask:</p><p>“A customer submits a request on Monday morning. Who receives the notification? When is it sent? What happens if the request is incomplete?”</p><p>Scenarios help teams think through:</p><p>• Different user situations<br>• Exceptions<br>• Business rules<br>• Edge cases<br>• Expected outcomes</p><p>They also give developers and testers a clearer picture of what success looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aR6TmzVy0gCZlhy_7HH_8Q.png" /></figure><p><strong>3. Challenge Assumptions Before They Become Issues</strong></p><p>Many project issues are caused by assumptions that were never discussed.</p><p>People often think:</p><p>“Everyone knows how this works.”</p><p>“This process is obvious.”</p><p>“That team already understands this dependency.”</p><p>But assumptions create risk.</p><p>A Business Analyst adds value by asking questions like:</p><p>• What are we assuming here?<br>• Does this apply to every user or only certain users?<br>• Are there exceptions?<br>• Does another team depend on this decision?<br>• What happens if this situation changes?</p><p>These questions may feel simple, but they often uncover the details that prevent future problems.</p><h4><strong>The Impact of Verifying Understanding</strong></h4><p>When Business Analysts make verification part of their process, teams benefit in several ways.</p><p>✅<strong>Less Rework</strong></p><p>Misunderstood requirements are one of the biggest causes of rework. Identifying gaps early saves time and effort later.</p><p>✅<strong>Better Collaboration</strong></p><p>When teams understand the reasoning behind decisions, conversations become more productive. People are more likely to work toward the same outcome instead of protecting their own perspective.</p><p>✅<strong>More Confident Decisions</strong></p><p>Clear understanding helps stakeholders make better decisions because they know the impact, trade-offs, and expectations.</p><p>✅<strong>Stronger Stakeholder Trust</strong></p><p>Stakeholders remember the Business Analysts who take the time to make sure their needs are truly understood.</p><p>That trust becomes one of the biggest ways a BA increases their influence.</p><p><strong>A Simple Question to Add to Your Next Requirements Discussion</strong></p><p>The next time you finish reviewing a requirement, try asking:</p><p>“What could someone misunderstand about this?”</p><p>It is a simple question, but it encourages the team to look beyond the words and consider different perspectives.</p><p>Great Business Analysts do not just make sure requirements are written down.</p><p>They make sure people understand what those requirements mean and how they support the bigger goal.</p><p>That is where a BA moves from being a requirement facilitator to becoming a trusted partner who helps teams make better decisions.</p><h4><strong>Want to Increase Your Impact as a Business Analyst?</strong></h4><p>Becoming a more impactful BA starts with recognizing the value you bring beyond documentation.</p><p>My free <a href="https://shanna-the-ba-ekfa6g.subscribepage.io/"><strong>BA Impact Starter Guide</strong></a> helps Business Analysts identify ways to increase their visibility, demonstrate their contributions, and communicate their impact more effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eVQh0SsRKrDUZV5fZA83dg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be757be0aa60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing Isn’t Just QA’s Job: How Business Analysts Protect Project Outcomes]]></title>
            <link>https://medium.com/@shannatheanalyst/testing-isnt-just-qa-s-job-how-business-analysts-protect-project-outcomes-cba0150f3228?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cba0150f3228</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Sun, 12 Jul 2026 15:30:25 GMT</pubDate>
            <atom:updated>2026-07-12T15:30:25.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Avs-664X6ITfUtWWMyZag.png" /><figcaption>Created using Canva AI</figcaption></figure><p>When people think about testing, they often picture QA analysts running test scripts or developers fixing bugs. While those roles are essential, testing is rarely something that belongs to just one team.</p><p>As Business Analysts, we also play an important role in helping ensure a solution is ready for users. Exactly what that looks like depends on your company, project, and team. There isn’t a universal testing role for BAs, and that’s perfectly normal.</p><p>Some BAs spend most of their time supporting User Acceptance Testing (UAT). Others help create test scenarios, coordinate testing activities, manage defects, or facilitate testing meetings. In some organizations, BAs execute testing themselves.</p><p>In my experience, I supported UAT, but one responsibility I consistently owned was System Integration Testing (SIT). After developers completed their unit testing, I validated how data flowed between multiple systems before the solution was handed over to business users. My goal was to confirm that everything worked together as expected before users ever saw it.</p><p>No matter what your responsibilities look like, one thing remains the same. Testing is one of the biggest opportunities we have to protect the outcome of a project.</p><h3><strong>Testing Starts Long Before the First Test Case</strong></h3><p>One of the biggest misconceptions about testing is that it begins once development is finished.</p><p>In reality, successful testing starts much earlier.</p><p>I’ve learned that some of the smoothest testing cycles were not necessarily the ones with the fewest defects. They were the ones where the team spent time preparing before anyone started testing.</p><p>Without preparation, testing quickly becomes reactive. People scramble to find test data, business users aren’t available, environments aren’t ready, and valuable time is lost solving problems that could have been prevented.</p><p>A little planning upfront can make a huge difference.</p><h3><strong>A BA’s Testing Preparation Checklist</strong></h3><p>Before testing begins, there are several questions I like to work through.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ojlZQjmTVwEQtWW1-MNMg.png" /><figcaption>Created using Canva AI + Canva</figcaption></figure><p><strong>What are we testing?</strong></p><p>Start by understanding exactly what needs to be validated.</p><p>Review the requirements, acceptance criteria, business rules, reports, interfaces, and end-to-end business processes. This helps ensure your testing covers how the business actually works, not just individual system functions.</p><p><strong>Who needs to be involved?</strong></p><p>Testing is rarely a one-person effort.</p><p>Depending on your project, this could include developers, QA analysts, business subject matter experts, product owners, compliance teams, operations, or other stakeholders.</p><p>Knowing who needs to participate early makes scheduling much easier later.</p><p><strong>What scenarios should we test?</strong></p><p>A good testing plan goes beyond the “happy path.”</p><p>Think about exception scenarios, invalid data, edge cases, and complete business workflows. Ask yourself what could realistically happen once the solution is live.</p><p>If a user enters incorrect information, skips a step, or processes an unusual transaction, what should happen?</p><p>Those situations often uncover the most valuable defects.</p><p><strong>Is our test data ready?</strong></p><p>Even the best test scenarios won’t help if you don’t have meaningful data to test with.</p><p>You may need customer records, vendor information, products, tax data, historical transactions, or intentionally invalid data to confirm business rules work correctly.</p><p>I’ve found that poor test data is one of the easiest ways to miss issues that only appear in production.</p><p><strong>Is the environment ready?</strong></p><p>Before testing starts, confirm that everything needed is available.</p><p>This includes the testing environment, deployments, user access, connected interfaces, and any external systems your solution depends on.</p><p>It’s also worth checking for planned system outages or maintenance windows that could interrupt testing.</p><p><strong>Do we have a realistic testing schedule?</strong></p><p>Make sure the right people are available when testing begins.</p><p>Business users still have day jobs, developers may be supporting multiple projects, and vacations happen. Planning ahead helps avoid unnecessary delays once testing is underway.</p><h3><strong>Where Business Analysts Add Value During Testing</strong></h3><p>Once testing begins, the BA’s role often shifts from planning to coordination and problem solving.</p><p>Depending on your organization, your responsibilities may include:</p><ul><li>Executing or leading System Integration Testing (SIT)</li><li>Supporting or coordinating User Acceptance Testing (UAT)</li><li>Reviewing and prioritizing defects</li><li>Investigating issues alongside developers</li><li>Clarifying requirements when questions arise</li><li>Facilitating testing status meetings</li><li>Tracking testing progress and identifying risks</li></ul><p>One part of testing I always enjoyed was investigating defects with developers.</p><p>Not every reported issue is actually a software bug. Sometimes the requirement was misunderstood.</p><p>Sometimes the expected behavior wasn’t clearly documented. Other times the issue revealed a genuine gap that needed to be fixed.</p><p>Those conversations helped bridge the gap between business expectations and technical implementation.</p><h3><strong>Testing Is About More Than Finding Bugs</strong></h3><p>It’s easy to think of testing as a way to catch defects before go-live.</p><p>While that’s certainly important, I believe testing serves a much bigger purpose.</p><p>Testing helps answer questions like:</p><ul><li>Does this solution solve the original business problem?</li><li>Can users complete their work successfully?</li><li>Are business rules working as expected?</li><li>Does data move correctly between systems?</li><li>Will this process support the business once it’s in production?</li></ul><p>Passing test cases is important, but passing test cases doesn’t automatically mean the project is successful.</p><p>Success comes from delivering a solution that creates the value the business expected.</p><h3><strong>Final Thoughts</strong></h3><p>One lesson I’ve carried with me throughout my career is that Business Analysts don’t stop adding value once the requirements are approved.</p><p>Testing is where we have one of our final opportunities to uncover risks, validate assumptions, and build confidence before a solution goes live.</p><p>Whether your role involves leading System Integration Testing, supporting User Acceptance Testing, coordinating defects, or helping the team stay aligned, you’re doing more than testing software.</p><p>You’re protecting the outcome.</p><p>And that’s one of the most valuable things a Business Analyst can do.</p><h3><strong>Make Your Impact Visible</strong></h3><p>One of the core themes in my ebook, <a href="https://shannatheba.gumroad.com/l/make-impact-visible"><em>Make Your Impact Visible</em></a>, is <strong>Protect the Outcome</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaWoGoOeVLQsExiT95LLWw.png" /><figcaption>Created using Canva</figcaption></figure><p>As Business Analysts, our work does not end when requirements are approved. We continue creating value by identifying risks, validating solutions, supporting testing, and helping ensure the business receives the outcome it expected.</p><p>Every requirement clarified, every defect investigated, and every successful test is another opportunity to demonstrate the value you bring.</p><p>That is one way to make your impact visible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cba0150f3228" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Great Business Analysis Is 70% Facilitation and Only 30% Documentation]]></title>
            <link>https://medium.com/@shannatheanalyst/why-great-business-analysis-is-70-facilitation-and-only-30-documentation-12a891f19fc1?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/12a891f19fc1</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[business-analyst]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 13:34:32 GMT</pubDate>
            <atom:updated>2026-06-16T13:34:32.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lkJ2w8BUIYMasZWsOG9PEg.png" /></figure><p>When most people think about business analysis, they think about requirements documents.</p><p>They picture business analysts writing user stories, documenting processes, creating diagrams, or maintaining traceability matrices.</p><p>Those activities are certainly part of the role. But after 15 years working as a Business Analyst, I’ve learned that documentation is rarely the hardest part of the job.</p><p>The real challenge is helping people reach a shared understanding.</p><h3><strong>Documentation Doesn’t Create Alignment</strong></h3><p>A project can have beautifully written requirements and still fail.</p><p>Why?</p><p>Because requirements are often a symptom of a deeper issue: stakeholders have different assumptions, priorities, or definitions of success.</p><p>One group may be focused on compliance.</p><p>Another may be focused on operational efficiency.</p><p>A third may be concerned about technical feasibility.</p><p>Each perspective is valid, but they don’t always align automatically.</p><p>A Business Analyst’s job isn’t simply to capture those viewpoints. It’s to help stakeholders understand each other well enough to make informed decisions.</p><p>That’s where facilitation becomes critical.</p><h3><strong>The Hidden Work of Business Analysis</strong></h3><p>Some of the most valuable work a Business Analyst performs never appears in a deliverable.</p><p>It’s the conversation before the workshop.</p><p>The follow-up discussion after a meeting.</p><p>The question that uncovers an unstated assumption.</p><p>The clarification that prevents a misunderstanding from becoming a production issue months later.</p><p>I’ve found that successful projects often depend less on the quality of the documentation and more on the quality of the discussions that happen before the documentation is written.</p><p>The deliverable is important.</p><p>The alignment behind the deliverable is what makes it successful.</p><h3><strong>The Real Challenge Is Explaining the Value</strong></h3><p>One thing I’ve noticed throughout my career is that many Business Analysts are doing valuable work but struggle to communicate the impact they’re having.</p><p>It’s easy to describe what we did:</p><ul><li>Facilitated a workshop</li><li>Gathered requirements</li><li>Created process flows</li><li>Coordinated testing</li></ul><p>What’s harder is explaining why those activities mattered.</p><p>For example, a workshop isn’t valuable because it happened. It’s valuable because it helped stakeholders reach alignment, uncover risks, or make a decision that moved the project forward.</p><p>The same is true for requirements, process models, and testing activities. The deliverable itself isn’t the outcome. The outcome is the business value created through those activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uhAepe7Cbux9oifVH60nww.png" /></figure><p>In fact, this challenge is one of the reasons I created my free BA Impact Starter Guide. It’s a simple one-page resource designed to help Business Analysts move beyond task-based thinking and start communicating their work in terms of outcomes and impact.</p><p>Because when we can clearly explain the value we create, our contributions become easier for stakeholders, managers, and future employers to recognize.</p><h3><strong>Facilitation Is About More Than Running Meetings</strong></h3><p>When people hear the word facilitation, they often think of scheduling meetings and taking notes.</p><p>Good facilitation is much more than that.</p><p>It involves:</p><ul><li>Asking questions that uncover the real business need</li><li>Helping stakeholders articulate concerns</li><li>Identifying conflicting assumptions</li><li>Keeping discussions focused on outcomes</li><li>Encouraging participation from quieter voices</li><li>Guiding groups toward decisions</li></ul><p>A facilitator doesn’t provide all the answers.</p><p>Instead, they create an environment where the right conversations can happen.</p><h3><strong>The Most Valuable Skill Is Translating</strong></h3><p>Business Analysts often sit between business teams, technology teams, testers, project managers, and leadership.</p><p>Each group has its own language, priorities, and concerns.</p><p>One stakeholder may describe a problem in terms of business impact.</p><p>A developer may focus on system behavior.</p><p>A tester may think about validation and risk.</p><p>A leader may focus on timelines and outcomes.</p><p>The Business Analyst serves as the bridge between those perspectives.</p><p>Success often depends on the ability to translate, clarify, and create a common understanding that everyone can support.</p><h3><strong>Facilitation Creates Better Requirements</strong></h3><p>Strong requirements are produced by conversations.</p><p>When stakeholders feel heard, assumptions are challenged, and business needs are fully explored, the resulting requirements become clearer and more complete.</p><p>The documentation reflects the alignment that was created.</p><p>Without that alignment, even the best-written requirements can lead to confusion and rework.</p><h3><strong>Final Thoughts</strong></h3><p>Business analysis is often viewed as a documentation-heavy profession.</p><p>In reality, documentation is only part of the job.</p><p>The larger responsibility is helping people move from uncertainty to clarity.</p><p>That’s why I believe great business analysis is less about producing documents and more about facilitating understanding.</p><p>The requirements document may be the visible output.</p><p>The conversations, relationships, and decisions behind it are where the real value is created.</p><h3><strong>A Free Resource for Business Analysts</strong></h3><p>One challenge I’ve seen throughout my career is that many Business Analysts are great at doing the work but struggle to communicate the value behind it.</p><p>It’s easy to talk about requirements, process models, workshops, or testing activities. It’s much harder to explain the business impact those activities created.</p><p>That’s why I created the <a href="http://shanna-the-ba-ekfa6g.subscribepage.io/"><strong>BA Impact Starter Guide</strong></a><strong>.</strong> It’s a free one-page resource that helps Business Analysts shift from task-based thinking to outcome-based thinking and communicate their value more effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HBDEz2vkhMnARKqwXLn9Mg.png" /><figcaption>Free BA Impact Starter Guide: Learn how to move from describing tasks to communicating business value.</figcaption></figure><p>What do you think is the most underrated skill in business analysis?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12a891f19fc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Pain Points to KPIs: Why Traceability Is Really Outcome Protection]]></title>
            <link>https://medium.com/@shannatheanalyst/from-pain-points-to-kpis-why-traceability-is-really-outcome-protection-244c071aaa4b?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/244c071aaa4b</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-analyst-role]]></category>
            <category><![CDATA[traceability]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[requirements]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 14:06:58 GMT</pubDate>
            <atom:updated>2026-06-08T14:06:58.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8UvNSWpFfNKHpJEr1AIUg.png" /></figure><p>Most projects don’t fail because people didn’t work hard. They fail because alignment quietly erodes.</p><p>Pain points get forgotten. Solutions drift. New stakeholders join. Timelines shift. KPIs are added late.</p><p>Before anyone realizes it, the work no longer clearly solves the original business problem.</p><p>That’s why I don’t think of traceability as documentation. I think of it as <strong>outcome protection</strong>.</p><h3><strong>Traceability Isn’t a Spreadsheet</strong></h3><p>When people hear “traceability,” they often picture a requirements matrix.</p><p>Important? Yes. But that’s the <strong>mechanical version</strong>.</p><p>The <strong>strategic version</strong> is much more powerful.</p><p>Traceability is the discipline of maintaining a visible connection:</p><p><strong>Pain Points → Current State Gaps → Future State Changes → Objectives → KPIs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7awrPRp30DGUeOkApffagw.png" /></figure><p>When that chain stays intact, alignment holds.</p><p>When it breaks, initiatives drift. And drift is subtle. It doesn’t announce itself; it slowly disconnects effort from impact.</p><h3><strong>Where Alignment Starts to Slip</strong></h3><p>Across initiatives, the same pressure points tend to show up:</p><ul><li>Pain points are identified… but never referenced again</li><li>Solutions evolve independently of original objectives</li><li>KPIs are defined late</li><li>Scope becomes harder to justify</li><li>“Good ideas” enter without clear linkage to the problem</li></ul><p>None of these feel dramatic in the moment. But together, they dilute outcomes.</p><p>Traceability <strong>prevents that dilution</strong>.</p><h3><strong>What Strong Traceability Looks Like</strong></h3><p>For me, traceability shows up in the questions asked:</p><ul><li>What validated pain point does this solve?</li><li>What gap in the current state does it address?</li><li>What objective does it support?</li><li>How will we know if it worked?</li><li>If we remove this, what problem reappears?</li></ul><p>If those answers aren’t clear, it’s usually a sign we’re solving something adjacent, not essential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DGYEe8fyOO1XGP0fiZYcyg.png" /></figure><p>That clarity protects both <strong>time and credibility.</strong></p><h3><strong>KPIs Are Where Alignment Becomes Visible</strong></h3><p>KPIs aren’t just reporting metrics. They’re where <strong>alignment becomes visible.</strong></p><p>If an initiative begins with a clearly defined problem, there should also be a clear way to determine whether that problem improved. That connection shouldn’t be an afterthought.</p><p>Even when KPI ownership sits with leadership or operations, part of the Business Analyst’s role is helping ensure that objectives and outcomes are defined early enough for <strong>meaningful measurement.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PAStjZxwrPS8VK_5bFabYQ.png" /></figure><p>Because if we can’t point to how success will be evaluated, it becomes harder to know whether we truly solved the right problem or simply delivered a solution.</p><p>Traceability strengthens that connection.</p><h3><strong>Where to Start</strong></h3><p>One place to start is with a gap analysis spreadsheet with at least three columns:</p><ul><li>Pain Point</li><li>Current State Gap</li><li>Future State Change</li></ul><p>This alone creates structure.</p><p>It forces clarity around:</p><ul><li>What’s actually wrong</li><li>What isn’t working today</li><li>What specifically needs to change</li></ul><p>From there, objectives and KPIs become much easier to define.</p><p>A well-structured gap analysis becomes the foundation for everything that follows.</p><h3><strong>Traceability Is a Leadership Skill</strong></h3><p>The longer I work as a Business Analyst, the more I realize:</p><p><strong>Traceability isn’t just some administrative task.</strong> <strong>It’s strategic.</strong></p><p>It requires you to:</p><ul><li>Slow down solution jumping</li><li>Push for root cause clarity</li><li>Define success before implementation</li><li>Protect scope boundaries</li><li>Keep cross-functional teams aligned</li></ul><p>In complex or fast-moving environments, alignment doesn’t maintain itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_aDl5VBeNVpFOhV_zk4gug.png" /></figure><p>Someone must <strong>protect it. </strong>That’s part of our job.</p><h3><strong>Final Thoughts</strong></h3><p>Traceability is not about producing more artifacts.</p><p>It is about ensuring that effort translates into value.</p><p>When the chain from pain point to KPI remains intact, outcomes stay protected, even as priorities shift and complexity increases.</p><p>This is where Business Analysis moves beyond documentation support and into strategic impact.</p><h3><strong>Continue Building Your BA Impact</strong></h3><p>Traceability is ultimately about connecting effort to value.</p><p>If you’re interested in strengthening how you communicate the value of your own work, you can download my <a href="http://shanna-the-ba-ekfa6g.subscribepage.io/"><strong>free BA Impact Starter Guide</strong></a>, a simple resource designed to help Business Analysts frame their contributions in terms of business impact rather than activities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=244c071aaa4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Approach Testing for Reporting Projects]]></title>
            <link>https://medium.com/@shannatheanalyst/how-i-approach-testing-for-reporting-projects-84b26f648ac6?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/84b26f648ac6</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Thu, 28 May 2026 13:32:56 GMT</pubDate>
            <atom:updated>2026-05-28T13:32:56.958Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0IPqX2ynfNGWbtDPPhYUWw.png" /></figure><p>Testing is one of the most important and most underestimated parts of reporting work.</p><p>A report can look polished on the surface and still contain logic issues, missing records, incorrect joins, or business rule misunderstandings underneath. And when reports support compliance, operational decisions, or regulatory processes, small errors can quickly become big problems.</p><p>Over the years, I’ve worked on many reporting initiatives across different teams and systems. My testing approach has evolved quite a bit along the way, but one thing has stayed consistent:</p><p>Good reporting testing is not just about executing test cases. It’s about building confidence in the data.</p><p>Here’s the structure and mindset that have worked best for me.</p><h4><strong>Start by Understanding the Report, Not the Test Script</strong></h4><p>Before I even think about testing steps, I focus on understanding the report itself.</p><p>I want to know:</p><ul><li>What business problem the report solves</li><li>What decisions the report supports</li><li>What the report is supposed to show</li><li>Which business rules drive the results</li></ul><p>If I cannot clearly explain the purpose of the report in simple terms, I know I’m not ready to test it properly yet.</p><p>I’ve seen projects where teams jump straight into test execution without fully understanding the underlying logic. That usually leads to surface-level validation instead of meaningful testing.</p><p>For me, understanding comes first. Testing comes second.</p><h4><strong>Understand the Logic Behind the Data</strong></h4><p>Once the purpose of the report is clear, I shift into understanding the technical and data flow side.</p><p>This includes questions like:</p><ul><li>Where is the data sourced from?</li><li>How does the data move between systems?</li><li>Which transformations are happening?</li><li>How are tables connected?</li><li>What filters, joins, or calculations are applied?</li></ul><p>Most reporting defects I’ve encountered were not visual issues.</p><p>They came from:</p><ul><li>Incorrect business logic</li><li>Misunderstood requirements</li><li>Bad joins</li><li>Missing filters</li><li>Unexpected data relationships</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvX2F-sFx1durNX7oeRW1g.png" /></figure><p>This is the stage where a lot of project risk can be reduced early.</p><p>The deeper the understanding of the data, the stronger the testing becomes.</p><h4><strong>Plan Testing Early, Including Regression Testing</strong></h4><p>One mistake I’ve seen on reporting projects is treating testing as a final phase activity.</p><p>In reality, good testing requires planning upfront.</p><p>Before execution begins, I usually identify:</p><ul><li>Which reports need validation</li><li>Which upstream or downstream objects may be impacted</li><li>What requires regression testing</li><li>Which systems or sources will be used for validation</li></ul><p>Regression testing is especially important in reporting environments because even a small logic change can impact multiple reports or teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-GKBXDgutehD7cMCJMHgKw.png" /></figure><p>If another team relies on a report that’s changing, I try to involve them early and include them in UAT discussions. That collaboration helps avoid surprises later and creates shared ownership of the solution.</p><h4><strong>Build Testing Around Real Business Scenarios</strong></h4><p>One of the biggest lessons I’ve learned is this:</p><p>Good reporting testing is scenario-driven, not just script-driven.</p><p>Happy path testing alone is rarely enough.</p><p>I focus on identifying:</p><ul><li>Common business scenarios</li><li>Edge cases</li><li>Exception conditions</li><li>Rare but high-risk situations</li></ul><p>Then I determine:</p><ul><li>What data is needed for each scenario</li><li>Whether the data already exists</li><li>Who is responsible for creating missing data</li><li>When the data will be available</li></ul><p>Strong testing depends heavily on having the right test data at the right time.</p><p>Without realistic scenarios, testing can create a false sense of confidence.</p><h4><strong>Keep Test Scripts Practical</strong></h4><p>Over the years, I’ve experimented with different test documentation approaches.</p><p>The structure that has worked best for me recently is simple:</p><ul><li>One test script per report</li><li>Multiple business scenarios validated within that script</li></ul><p>This creates a clear report-to-scenario relationship that’s easy to track and explain.</p><p>I often maintain a matrix in Excel alongside tools like HP ALM to monitor:</p><ul><li>Scenario coverage</li><li>Testing progress</li><li>Defect trends</li><li>Validation status by report</li></ul><p>The goal is visibility without overcomplicating the process.</p><h4><strong>Make Testing Status Easy to Understand</strong></h4><p>Testing communication matters just as much as testing execution.</p><p>During SIT, I usually send regular status updates that show:</p><ul><li>Progress by report</li><li>Scenario coverage</li><li>Defect counts and categories</li><li>Risks or blockers</li></ul><p>I also pay close attention to how defects are grouped and communicated.</p><p>For example, organizing defects by report can quickly highlight higher-risk areas and help stakeholders prioritize discussions.</p><p>Clear reporting helps teams make faster and better decisions.</p><h4><strong>Involve Business Users Earlier Than You Think</strong></h4><p>One practice that has consistently improved outcomes for me is involving business stakeholders throughout testing, not just at the end.</p><p>As testing progresses, I like to walkthrough:</p><ul><li>Test results</li><li>Open defects</li><li>Scenario coverage</li><li>Observations and assumptions</li></ul><p>These conversations often uncover:</p><ul><li>Missing scenarios</li><li>Subtle logic gaps</li><li>Misaligned expectations</li><li>Real-world process nuances</li></ul><p>Business collaboration during testing almost always strengthens the final solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSAnXQDODAWHP8KvZROOXQ.png" /></figure><p>It also builds trust because stakeholders can see how thoroughly the reporting logic is being validated.</p><h4><strong>Keep Testing Structured and Predictable</strong></h4><p>Testing tends to run more smoothly when operational details are handled proactively.</p><p>A few things I try to organize early:</p><ul><li>Testing calendars</li><li>Meeting cadence</li><li>Required attendees</li><li>Environment refresh schedules</li><li>System availability windows</li><li>SIT readiness checklists</li></ul><p>Simple coordination activities can prevent a surprising amount of testing chaos later.</p><p>The less confusion around logistics, the more focus the team can place on actual validation.</p><h4><strong>Final Thoughts</strong></h4><p>Reporting solutions are often more complex than they appear.</p><p>A single report may need validation across multiple systems, datasets, calculations, business rules, and user scenarios before stakeholders can truly trust the results.</p><p>That’s why I view testing as more than a project task.</p><p>For me, effective reporting testing is:</p><ul><li>Structured rather than rushed</li><li>Collaborative rather than siloed</li><li>Focused on reducing risk rather than simply completing steps</li></ul><p>When testing is done well, it builds confidence in the decisions being made from the data.</p><p>If you’re a Business Analyst looking to better understand your impact beyond just gathering requirements, I also created a free one-page <strong>Business Analyst Impact Starter Guide</strong> to help you think about your work more strategically.</p><p>You can download it here: <a href="https://shanna-the-ba-ekfa6g.subscribepage.io/">shanna-the-ba-ekfa6g.subscribepage.io</a></p><p>What approaches or practices have helped you feel confident that reporting has truly been tested end-to-end?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84b26f648ac6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Grew from a Quiet Reporting BA into a Trusted Voice]]></title>
            <link>https://medium.com/@shannatheanalyst/how-i-grew-from-a-quiet-reporting-ba-into-a-trusted-voice-86a16995fa76?source=rss-da42f824af6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/86a16995fa76</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-analyst-role]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[requirements]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Shanna Fillmore]]></dc:creator>
            <pubDate>Tue, 19 May 2026 16:50:27 GMT</pubDate>
            <atom:updated>2026-06-16T21:25:34.352Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiZX7Fkm5wnAmVAuXZ3t4Q.png" /></figure><p>When I first started working as a reporting Business Analyst, I didn’t think of myself as someone who would simply “take requirements and build reports.”</p><p>Even early on, I questioned everything.</p><p>If numbers didn’t align, I couldn’t ignore it.<br>If a metric seemed unclear, I needed to understand the logic behind it.<br>If something felt off downstream, I kept digging until it made sense.</p><p>At the time, I thought that was just part of being detail-oriented.</p><p>What I didn’t realize yet was that the real evolution in my career wouldn’t come from learning <em>what</em> to question.</p><p>It would come from learning how to bring others into that thinking.</p><h3><strong>Early in My Career, My Questions Stayed Internal</strong></h3><p>In my early reporting roles, most of my analysis happened quietly.</p><p>I would sit with requirements and think:</p><ul><li>Does this metric actually mean what stakeholders think it means?</li><li>Why doesn’t this number tie out?</li><li>What systems or calculations are impacting this output?</li><li>What happens if this definition changes later?</li></ul><p>I often investigated issues on my own, adjusted logic where needed, documented assumptions carefully, and tried to solve problems independently before involving anyone else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-DNr9HxOwUbXRTrKoJ0w3Q.png" /></figure><p>The work itself was solid.</p><p>But my thinking remained mostly invisible.</p><p>And invisible thinking rarely builds visible trust.</p><h3><strong>The Turning Point: Making My Thinking Visible</strong></h3><p>As projects became more complex, the environment changed.</p><p>There were more systems.<br>More dependencies.<br>More stakeholders.<br>More pressure on reporting accuracy.</p><p>And I started noticing something important:</p><p>Even when the output was technically correct, stakeholders still needed confidence in the reasoning behind it.</p><p>That changed the way I approached conversations.</p><p>Instead of silently validating logic behind the scenes, I started externalizing my thought process:</p><ul><li>Walking stakeholders through how metrics were derived</li><li>Talking through downstream impacts before changes were implemented</li><li>Reviewing sample outputs together</li><li>Asking “Does this align with how you interpret the business process?”</li><li>Identifying assumptions earlier instead of waiting for validation later</li></ul><p>That shift changed everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmdFnJa8ybkvu8zYSOCbrg.png" /></figure><p>Stakeholders stopped viewing reports as isolated deliverables.</p><p>They started engaging with the logic behind the numbers.</p><p>And that’s where partnership started to develop.</p><h3><strong>Reporting Roles Expose Gaps Quickly</strong></h3><p>Reporting has a way of exposing unclear thinking.</p><p>If requirements are vague, the report will reveal it.<br>If definitions are inconsistent, the numbers will magnify it.<br>If assumptions go untested, leadership will eventually question the output.</p><p>That’s why reporting Business Analysts often sit at an important intersection between business understanding, data interpretation, and decision-making confidence.</p><p>The role becomes less about “producing a report” and more about creating shared clarity.</p><p>Over time, I realized that trust in reporting environments rarely comes from delivery speed alone.</p><p>It comes from helping people understand what the data actually means, and what it doesn’t.</p><h3><strong>What Trusted Reporting Business Analysts Tend to Do Differently</strong></h3><p>After years of working on reporting and data initiatives, I noticed patterns in the Business Analysts who became trusted partners instead of task executors.</p><p>They consistently:</p><ul><li>Ask “why” before jumping to “what”</li><li>Treat reporting changes as business risks, not just technical updates</li><li>Walk through sample results with stakeholders</li><li>Identify assumptions early, even when uncomfortable</li><li>Think about downstream impacts before implementation</li><li>Protect stakeholders from surprises they may not anticipate</li></ul><p>None of this is about slowing projects down or making work more complicated.</p><p>It’s about ownership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8L5tGnhX1_03E4yhR9zqA.png" /></figure><p>Trusted BAs don’t just complete tasks.</p><p>They help safeguard decision-making.</p><h3><strong>The Conversation Shift That Changed My Career</strong></h3><p>One of the clearest signs that my role had evolved was the way conversations started changing.</p><p>Earlier in my career, interactions often sounded like this:</p><p>“Here’s the report you requested.”</p><p>Later, they sounded more like this:</p><ul><li>“Let’s walk through this together.”</li><li>“Here’s how I’m thinking about the data.”</li><li>“Tell me if this aligns with how the business actually uses these numbers.”</li></ul><p>That difference may seem small.</p><p>But it fundamentally changes how people experience you in the room.</p><p>You stop being viewed as someone who simply delivers outputs.</p><p>You become someone who helps teams think more clearly.</p><p>And in reporting environments, that kind of trust matters.</p><h3><strong>The Mindset I Still Use Today</strong></h3><p>Fifteen years later, I still approach reporting work with the same core mindset:</p><p>If it doesn’t make sense, it’s not ready.<br>If I can’t explain it simply, it’s not clear enough.<br>If the business wouldn’t trust it, it isn’t done.</p><p>That mindset has helped me navigate high-risk reporting initiatives, cross-functional conversations, shifting business definitions, and complex stakeholder environments throughout my career.</p><p>Not because I always had the answers.</p><p>But because I learned that trusted partnership comes from making your thinking visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hcpg5OQvYSBhyHwYFXupGA.png" /></figure><h3><strong>Final Thought</strong></h3><p>You don’t have to stop being a questioner to become a trusted Business Analyst.</p><p>In many ways, questioning is the foundation of the role.</p><p>The difference is learning how to invite others into your reasoning instead of carrying it silently on your own.</p><p>That’s where alignment improves.<br>That’s where confidence grows.<br>And that’s where trust gets built.</p><p>If you’re a Business Analyst trying to better communicate your value and impact, I created a free one-page <a href="https://shanna-the-ba-ekfa6g.subscribepage.io/"><strong>Business Analyst Impact Starter Guide</strong></a> to help you start framing your work more strategically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86a16995fa76" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>