<?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 Elizabeth &quot;Lady Bhie&quot; Ekenimoh on Medium]]></title>
        <description><![CDATA[Stories by Elizabeth &quot;Lady Bhie&quot; Ekenimoh on Medium]]></description>
        <link>https://medium.com/@global-ladybhie?source=rss-3b8d5c97d667------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*W8lEByDzNKmrPx-qHhBjfA.jpeg</url>
            <title>Stories by Elizabeth &amp;quot;Lady Bhie&amp;quot; Ekenimoh on Medium</title>
            <link>https://medium.com/@global-ladybhie?source=rss-3b8d5c97d667------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:40:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@global-ladybhie/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[Conflicting Business Priorities. When Everything Is Important and Nothing Gets Done]]></title>
            <link>https://global-ladybhie.medium.com/conflicting-business-priorities-when-everything-is-important-and-nothing-gets-done-c2ef1b651dae?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2ef1b651dae</guid>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 08:01:03 GMT</pubDate>
            <atom:updated>2026-11-19T08:01:03.104Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When everything is a priority, your business may be moving fast but going nowhere.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbFHaDTnubZeS3W5Oz5a5A.png" /></figure><p>A business starts the week with a plan.</p><ul><li>The marketing team is launching a campaign.</li><li>Sales is working on a new offer.</li><li>Operations is trying to improve delivery.</li><li>The CEO has a new idea.</li><li>The technology team is fixing a system issue.</li><li>Finance is asking why costs are increasing.</li></ul><p>Then Monday’s leadership meeting happens.</p><p>By the time everyone leaves the room, there are five new priorities.</p><ul><li>The marketing campaign is now urgent.</li><li>The new product must launch before the end of the month.</li><li>The website needs a redesign.</li><li>A new system must be implemented.</li><li>Customer complaints need immediate attention.</li></ul><p>And somehow, the team is expected to deliver everything.</p><p>Welcome to the business where everything is important, everyone is busy, and very little actually gets finished.</p><h3>The problem isn’t a lack of effort.</h3><p>Truth is, most times, teams aren’t sitting around doing nothing.</p><p>People are attending meetings, responding to emails, working late, chasing updates, solving problems, and trying to keep up with changing expectations.</p><blockquote>The problem is that activity isn’t the same as progress.</blockquote><p>When priorities constantly change, teams spend more time switching between tasks than completing meaningful work. Projects get started but not finished. Resources are spread thin. Deadlines begin to slip. People become frustrated because they’re working hard but don’t feel like they’re getting anywhere.</p><p>And leadership starts asking:</p><p>“Why aren’t we moving faster?”</p><p>The better question might be:</p><p><strong>“Are we trying to move in too many directions at once?”</strong></p><h3>How conflicting priorities creep into a business</h3><p>It rarely starts with a bad decision.</p><p>A customer makes a request, and the business wants to accommodate them.</p><p>A competitor launches something new, and leadership wants to respond.</p><p>Someone identifies an opportunity, and the business doesn’t want to miss out.</p><p>A problem emerges, and everyone wants it fixed immediately.</p><p>Individually, these decisions may make sense. But collectively, they can create chaos.</p><p>The business ends up with a growing list of initiatives without a clear understanding of which ones matter most, what can wait, or what needs to stop to make room for something new.</p><p>Every department has its own priorities.</p><p>Every manager has their own deadlines.</p><p>Every stakeholder believes their request is important.</p><p>And nobody is looking at the bigger picture.</p><h3>The cost of making everything a priority</h3><p>When everything is urgent, the business pays for it in ways that aren’t always immediately visible.</p><p><strong>1. Resources become stretched.</strong></p><p>People are assigned to multiple initiatives at once. Teams are expected to deliver more without additional capacity. Quality begins to suffer because everyone is rushing.</p><p><strong>2. Decisions become reactive.</strong></p><p>Instead of working towards a defined strategy, the business responds to whoever shouts the loudest, whoever escalates fastest, or whatever problem appeared most recently.</p><p><strong>3. Projects lose momentum.</strong></p><p>Work gets started with excitement but is abandoned when another priority takes over. Teams repeatedly restart, re-plan, and re-adjust.</p><p><strong>4. Employees become frustrated.</strong></p><p>People lose confidence in plans when they know those plans may change tomorrow. Eventually, they stop taking priorities seriously.</p><p><strong>5. Business goals suffer.</strong></p><p>The business may be doing a lot, but the activities aren’t necessarily contributing to its most important goals.</p><p>Busy calendars. Full task boards. Endless meetings.</p><p>But where is the actual value?</p><h3>So, how do you fix it?</h3><p>You don’t solve conflicting priorities by asking everyone to work harder. You solve them by making better decisions about what deserves attention.</p><h3>1. Revisit the business goals.</h3><p>Before prioritising tasks, the business needs clarity on what it is trying to achieve.</p><p>Are we trying to increase revenue? Improve customer retention? Reduce operating costs? Expand into a new market? Improve delivery?</p><p>Every initiative should have a reason for existing.</p><p>If the business cannot explain how an initiative contributes to its goals, it may not deserve to be a priority right now.</p><h3>2. Make priorities visible.</h3><p>Don’t leave priorities inside individual departments, email threads, or someone’s head.</p><p>Create a central view of the initiatives the business is working on.</p><p>For each initiative, understand:</p><ul><li>What are we trying to achieve?</li><li>Why does it matter?</li><li>Who owns it?</li><li>What resources are required?</li><li>What is the expected value?</li><li>What happens if we delay it?</li></ul><p>When leadership can see everything competing for resources, prioritisation becomes a business conversation rather than a guessing game.</p><h3>3. Agree on what “priority” actually means.</h3><p>Not every request is urgent.</p><p>Not every good idea needs to be implemented immediately.</p><p>Not every customer request should override the existing plan.</p><p>The business needs agreed criteria for prioritising work. These could include business value, strategic alignment, urgency, risk, customer impact, cost, effort, and dependencies.</p><p>This makes decisions more objective and reduces the tendency to prioritise based on emotion, pressure, or hierarchy.</p><h3>4. Understand capacity before committing</h3><p>One of the biggest mistakes businesses make is committing to work without understanding whether they have the capacity to deliver it.</p><p>A team can only do so much.</p><p>If the team is already working on five major initiatives, adding another three doesn’t magically increase its capacity. It increases the likelihood that everything will take longer.</p><p>Before committing to new work, understand what the team is already delivering, what resources are available, and what trade-offs need to be made.</p><blockquote>Sometimes the most important decision is deciding what NOT to do.</blockquote><h3>5. Create a process for changing priorities.</h3><p>Business priorities will change. That’s normal.</p><blockquote>The problem isn’t change. The problem is unmanaged change.</blockquote><p>When a new priority comes in, the business should understand its impact on existing work.</p><p>If a new initiative is added, what gets delayed? What gets deprioritised? What resources need to move? Which commitments are affected?</p><p>A new priority should trigger a conversation, not just another task on someone’s list.</p><h3>Where Business Analysis comes in</h3><p>This is one of the areas where Business Analysis can make a real difference.</p><p>A Business Analyst can help leadership move from a collection of competing requests to a clear picture of business needs, opportunities, constraints, and trade-offs.</p><p>Through stakeholder engagement, analysis, prioritisation, and impact assessment, a BA can help the business:</p><ul><li>Understand what is driving each request.</li><li>Identify the underlying business problem.</li><li>Assess the value of competing initiatives.</li><li>Highlight dependencies, risks, and resource constraints.</li><li>Facilitate conversations around trade-offs.</li><li>Align initiatives to business goals.</li><li>Make informed decisions before committing resources.</li></ul><p>A BA doesn’t necessarily decide which priority wins.</p><p>But a BA can help ensure that the decision is based on facts, business value, impact, and strategic direction rather than noise.</p><p>And sometimes, that is exactly what the business needs.</p><h3>A successful business isn’t the one doing the most things.</h3><p>It’s the one doing the right things, at the right time, with the right resources, for the right reasons.</p><p>You don’t need 27 priorities.</p><p>You need clarity.</p><p>Because when everything is important, nothing is truly prioritised.</p><p>And when nothing is prioritised, your business may spend the entire year running around in circles and calling it growth.</p><p><strong>Perhaps it’s time to stop asking your teams to do more and start asking your business to choose better.</strong></p><p><strong><em>FOUNDERS SECRETS</em></strong><em> explores the business strategies that don’t work, why they fail, and the one approach that helps organisations make smarter decisions and build sustainable businesses.</em></p><p><em>Business Analysis isn’t just about documenting requirements. It is about helping businesses understand their problems, make better decisions, and turn strategy into results.</em></p><p><em>— Elizabeth ‘Lady Bhie’ Ekenimoh<br>Business Analyst &amp; Strategy Consultant</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2ef1b651dae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements Analysis: Don’t Just Collect Requirements. Make Sense of Them.]]></title>
            <link>https://global-ladybhie.medium.com/requirements-analysis-dont-just-collect-requirements-make-sense-of-them-92f2551aed6b?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/92f2551aed6b</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[tech-career]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 08:01:02 GMT</pubDate>
            <atom:updated>2026-11-16T08:01:02.282Z</atom:updated>
            <content:encoded><![CDATA[<p>So, you’ve spoken to stakeholders. You’ve reviewed documents. You’ve observed processes. You’ve asked questions and gathered information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oexlea8qrMGKAqlqY0CEBQ.png" /></figure><p>Beautiful. 👏🏽</p><p>Now what?</p><p>Do you copy everything into a requirements document and call it a day?</p><p>Absolutely not.</p><blockquote><strong>Gathering information is one thing. Understanding what that information means is another.</strong></blockquote><p>And that’s where Requirements Analysis comes in.</p><h3>What Is Requirements Analysis?</h3><p>Requirements Analysis is the process of examining, refining, organising and understanding requirements to ensure they are clear, relevant, feasible and aligned with business needs.</p><p>In simple English?</p><p><strong>You take what you’ve discovered and make sense of it.</strong></p><p>You look for gaps. You question assumptions. You identify conflicts. You explore dependencies. You refine vague statements.</p><p>Because stakeholders don’t always give you perfectly formed requirements.</p><p>Sometimes they contradict one another.</p><p>Sometimes they leave out important details.</p><p>Sometimes they tell you what they want without explaining why.</p><p>And sometimes, after further investigation, you realise the requirement you documented earlier needs to change.</p><p>That’s normal.</p><p>Requirements Analysis helps you move from scattered information to requirements that stakeholders and delivery teams can actually work with.</p><h3>Elicitation vs. Requirements Analysis: What’s the Difference?</h3><p>These two activities work closely together, but they aren’t the same.</p><blockquote><strong>Requirements Elicitation</strong> helps you discover and draw out information.</blockquote><blockquote><strong>Requirements Analysis</strong> helps you examine, interpret and refine that information.</blockquote><p>Let’s use our university course-registration project.</p><p>During an interview, a student says:</p><p>“I struggle to register for the courses I want.”</p><p>That’s useful information.</p><p>But it’s not enough.</p><p>During analysis, you begin asking:</p><ul><li>Which courses?</li><li>Why can’t the student register?</li><li>Are the courses already full?</li><li>Are prerequisites involved?</li><li>Is registration happening too late?</li><li>Is the student receiving enough information?</li><li>Does the problem affect other students?</li></ul><p>You may discover that students cannot see course availability before registration opens.</p><p>Or perhaps academic advisers must approve certain courses, but students don’t know which ones require approval.</p><p>Or maybe the courses are genuinely full.</p><p>Different causes. Different requirements. Different solutions.</p><blockquote><strong>Elicitation uncovers information. Analysis helps you understand what that information tells you.</strong></blockquote><p>And yes, you may need to go back and ask more questions.</p><p>BA work isn’t always a straight line. 😂</p><h3>What Exactly Do You Do During Requirements Analysis?</h3><p>Let’s break down some of the activities.</p><h3>A. Clarify Requirements</h3><p>You examine requirements to ensure their meaning is clear.</p><p>Consider this statement: <em>“The registration process must be fast.”</em></p><p>Fast how?</p><p>Five minutes? Ten minutes? Faster than the current process?</p><p>You need to understand what the stakeholder actually expects.</p><p>A more useful requirement might be:</p><blockquote>“Students must be able to complete course registration within five minutes under the agreed test conditions.”</blockquote><p>The five-minute target is illustrative. The actual expectation would need to be investigated and agreed upon.</p><p>The point is to remove ambiguity.</p><h3>B. Identify Missing Information</h3><p>Sometimes a requirement looks perfectly fine until you start asking questions.</p><p>For example: <em>“The system must allow students to register for courses.”</em></p><p>Sounds reasonable.</p><p>But what about:</p><ul><li>Course prerequisites?</li><li>Maximum course capacity?</li><li>Registration deadlines?</li><li>Approval requirements?</li><li>Students who want to drop a course?</li><li>Students who attempt to register for conflicting courses?</li></ul><p>You don’t need to solve every detail immediately.</p><p>But you should recognise what is missing and determine whether further investigation is required.</p><blockquote><strong>A requirement can be clear and still be incomplete.</strong></blockquote><h3>C. Identify Conflicts</h3><p>Different stakeholders may have different expectations.</p><p>Students want flexibility when selecting courses.</p><p>The registrar’s office wants registration rules enforced consistently.</p><p>Lecturers want accurate enrolment numbers.</p><p>Academic advisers may want to approve certain course selections.</p><p>These needs may conflict.</p><p>For example:</p><blockquote>Students may want to register for any available course, while the university requires students to complete prerequisites first.</blockquote><p>Your job isn’t to simply pick a favourite stakeholder.</p><p>You investigate the underlying needs, clarify business rules, assess the implications and facilitate discussions where decisions are needed.</p><blockquote><strong>Conflicting requirements are not a documentation problem alone. They are a business conversation waiting to happen.</strong></blockquote><h3>D. Identify Dependencies</h3><p>Some requirements depend on others.</p><p>For example: <em>A student cannot register for a course until prerequisite checks are completed.</em></p><p>A registration confirmation cannot be generated until the registration has been successfully processed.</p><p>A student cannot see accurate course availability unless course capacity information is maintained.</p><blockquote>Understanding these relationships helps you identify what must happen first and what could be affected by a change.</blockquote><h3>E. Examine Assumptions</h3><p>An assumption is something believed to be true without having been fully confirmed.</p><p>For example: <em>“We assume students have access to the internet during registration.”</em></p><p>That might be reasonable.</p><p>But is it true for every student?</p><p>What happens to students who have limited connectivity?</p><p>Assumptions can influence requirements, decisions and solution design.</p><p>A BA should identify important assumptions and determine which ones need validation.</p><blockquote>Don’t quietly turn assumptions into facts.</blockquote><h3>Refining Requirements: From Vague to Useful</h3><p>One of the most practical things you do during Requirements Analysis is improve requirement statements.</p><p>Let’s look at a few examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*WRGlXhf8e5S2XmLy9jDBhQ.png" /></figure><p>These refined statements are examples, not automatically approved requirements.</p><p>You would still need to validate them with stakeholders and confirm that they address the actual business needs.</p><p>Also, notice something important.</p><p><strong>You don’t refine requirements by making them sound fancy. You refine them by making them clearer and more useful.</strong></p><h3>Are the Requirements Actually Necessary?</h3><p>This is another important part of analysis.</p><p>Just because someone requests a feature doesn’t mean it must be included.</p><p>Ask:</p><ul><li>What business need does it support?</li><li>Who needs it?</li><li>What happens if we don’t implement it?</li><li>Is it required by a policy, regulation or business rule?</li><li>Does it contribute to the intended outcome?</li><li>Is there another way to satisfy the need?</li></ul><p>Imagine a stakeholder requests a dashboard showing twenty different registration statistics.</p><p>Interesting.</p><p>But who will use it? What decisions will it support? Are all twenty statistics necessary?</p><p>Requirements Analysis helps you examine these questions.</p><p>The aim isn’t to reject stakeholder requests.</p><p>It’s to ensure the requirements are justified and relevant.</p><h3>What About Prioritisation?</h3><p>Not every requirement has the same importance.</p><p>Some requirements are essential. Others are useful but can wait.</p><p>Some may be expensive, risky or dependent on other requirements.</p><p>Requirements prioritisation helps stakeholders decide which requirements matter most and what should be delivered first.</p><p>For our university project:</p><ul><li>Enforcing course prerequisites may be essential.</li><li>Displaying registration status may be highly important.</li><li>A personalised registration dashboard might be useful but not critical for the initial release.</li></ul><p>The priorities would depend on business needs, constraints, risks and stakeholder decisions.</p><p>A BA helps stakeholders understand the trade-offs and make informed decisions.</p><p>And please remember:</p><blockquote><strong>Prioritisation is not simply asking everyone to rank their favourite features.</strong></blockquote><p>You need to consider business value, urgency, dependencies, risk, effort and other relevant factors.</p><h3>How Do You Know Your Requirements Are Good Enough?</h3><p>Before requirements move forward, they should be reviewed for quality.</p><p>Depending on the context, you may examine whether they are:</p><ul><li>Clear.</li><li>Complete enough for their intended purpose.</li><li>Consistent with other requirements.</li><li>Relevant to the business need.</li><li>Feasible.</li><li>Testable or assessable.</li><li>Traceable to their source.</li><li>Free from unnecessary ambiguity.</li></ul><p>This doesn’t mean every requirement must be perfect before the project can proceed.</p><blockquote>Requirements may evolve as the team learns more.</blockquote><p>The important thing is to understand their current quality, identify outstanding issues and make sure the appropriate people can make informed decisions.</p><h3>Requirements Analysis Is Not a Solo Performance</h3><p>Here’s something aspiring BAs sometimes forget.</p><blockquote><strong>You are not expected to invent requirements in isolation.</strong></blockquote><p>You analyse information, identify questions, facilitate discussions and work with stakeholders to refine understanding.</p><p>Stakeholders provide business knowledge.</p><p>Subject matter experts explain processes and rules.</p><p>Technical teams help assess feasibility and constraints.</p><p>Testers may help identify what needs to be verifiable.</p><p>The BA brings these perspectives together and helps ensure the requirements tell a coherent story.</p><p>You don’t need to know everything.</p><p>You need to know how to investigate, analyse and collaborate.</p><h3>Let’s Build Your BA Portfolio!</h3><p>Remember our university course-registration project?</p><p>We’ve already worked on:</p><ul><li>The business problem.</li><li>Initial requirements.</li><li>Requirements classification.</li><li>An Elicitation Plan.</li></ul><p>Now we’ve gathered information about the registration process, stakeholder experiences, policies and possible challenges.</p><p>It’s time to analyse what we’ve discovered.</p><h3>Your assignment: Create a Requirements Analysis Document</h3><p>This is where your previous work starts coming together.</p><p><strong>Step 1: Review your existing requirements.</strong></p><p>Open your Requirements Classification document.</p><p>Read through each requirement and ask:</p><ul><li>Is it clear?</li><li>Is it necessary?</li><li>Is it supported by information we’ve gathered?</li><li>Does it connect to the business problem?</li><li>Is anything missing?</li></ul><p><strong>Step 2: Analyse your elicitation findings.</strong></p><p>Return to your Elicitation Plan and findings.</p><p>Identify:</p><ul><li>Stakeholder needs.</li><li>Business rules.</li><li>Process problems.</li><li>Assumptions.</li><li>Conflicting expectations.</li><li>Missing information.</li><li>Dependencies.</li><li>Possible constraints.</li></ul><p>If you haven’t conducted actual interviews or observations, clearly label your scenario assumptions and outstanding questions. Don’t present invented findings as real evidence.</p><p><strong>Step 3: Refine your requirements.</strong></p><p>Update vague or incomplete requirements.</p><p>For example:</p><p>Initial requirement:</p><p>“Students need an easier registration process.”</p><p>Refined requirement:</p><p>“Students must be able to view available courses, their prerequisites and remaining capacity before selecting a course.”</p><p>This is a possible refinement to investigate and validate, not a confirmed requirement.</p><p><strong>Step 4: Document your analysis.</strong></p><p>Your Requirements Analysis Document could include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*JovvoLDlcghQ_xgAuFv_5g.png" /></figure><p>You don’t have to force every section to contain something.</p><p>If no conflict has been identified, say so.</p><p>If something remains unknown, document it.</p><p>That is much better than inventing information to make your document look complete.</p><h3>Step 5: Connect the dots</h3><p>This is where your portfolio becomes interesting.</p><p>Show how:</p><p><strong>Business Problem → Stakeholder Needs → Elicitation Findings → Analysed Requirements</strong></p><p>Explain how your understanding changed as you investigated the problem.</p><p>What did you discover?</p><p>What did you refine?</p><p>What assumptions did you question?</p><p>What still needs to be confirmed?</p><p>That is the evidence of your BA thinking.</p><h3>Final Thoughts</h3><p>Requirements Analysis is where you begin to see the bigger picture.</p><p>You stop treating requirements as isolated statements and start examining how they connect to business needs, stakeholder expectations, processes and potential solutions.</p><p>You question vague wording.</p><p>You investigate gaps.</p><p>You challenge assumptions.</p><p>You uncover conflicts.</p><p>And you refine your understanding.</p><p><strong>You don’t just collect requirements. You make sense of them.</strong></p><h3>Your turn</h3><p>Go back to your university course-registration project.</p><p>Review the requirements you drafted.</p><p>Use your elicitation findings to refine them.</p><p>Identify gaps, assumptions, dependencies and outstanding questions.</p><p>Then document your analysis.</p><p>Don’t worry if you don’t have every answer yet.</p><p>A good BA knows the difference between what is known, what is assumed and what still needs investigation.</p><p>And that distinction alone can save a project from some very expensive surprises. 😂</p><p>One term. One task. One stronger BA portfolio at a time.</p><p>Let’s build!</p><p><em>If you’re building your Business Analysis knowledge from the ground up, follow along as we break down BA terminology, one concept at a time, in language you can actually use, and build a portfolio you can actually show. If you want to work through a specific situation or ned someone to talk to about your concerns, use the link in bio. I’m happy to discuss further.</em></p><p><em>Or find me on social media:</em><br>LinkedIn: <a href="https://www.linkedin.com/in/elizabeth-ekenimoh/">https://www.linkedin.com/in/elizabeth-ekenimoh/</a><br>Tiktok: <a href="https://www.tiktok.com/@ba_with_ladybhie">https://www.tiktok.com/@ba_with_ladybhie</a><br>Instagram: <a href="https://www.instagram.com/global_ladybhie">https://www.instagram.com/global_ladybhie</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f2551aed6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Business Has a Vision Statement. But Does Anyone Know What It Means?]]></title>
            <link>https://global-ladybhie.medium.com/your-business-has-a-vision-statement-but-does-anyone-know-what-it-means-aef19b44c507?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/aef19b44c507</guid>
            <category><![CDATA[business-owner]]></category>
            <category><![CDATA[business-leadership]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 08:01:03 GMT</pubDate>
            <atom:updated>2026-11-12T08:01:03.325Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is The Cost of Building a Business Without a Clear Vision and Mission?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJ1vEcMPzJqgl_eILc7dMQ.png" /></figure><p>A business can have a beautiful logo, a well-designed website, an impressive pitch deck, and a team of talented people, yet still struggle to explain what it is trying to become.</p><p>Ask the founder where they see the business in five years, and you’ll probably get an ambitious answer.</p><p>Ask the employees what the business is working towards, and you might get five different answers.</p><p>Ask the marketing team what message they are communicating to customers, and you may discover that it doesn’t quite match what the product team is building.</p><p>Everybody is working. Everybody has something to do. Everybody is contributing in one way or another.</p><p>But are they building the same business?</p><p>This is a problem many founders overlook.</p><p>They spend time developing products, acquiring customers, raising funds, hiring people, and expanding operations without first establishing a clear direction that connects all these activities.</p><p>And when that direction is missing, the business begins to lose its sense of purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tLWOwoWYYlRhRWy7U4b9ag.png" /></figure><h3>A Vision Statement Is Not Just Something You Put on Your Website</h3><p>Let’s get something straight.</p><p>Your vision and mission are not decorative business statements.</p><p>They should influence how your organization operates.</p><p>Your <strong>vision</strong> describes the future your business wants to create. It gives the organization a destination.</p><p>Your <strong>mission</strong> explains why the business exists, who it serves, and what it does to contribute towards that future.</p><p>Think of your vision as the destination and your mission as the reason and purpose behind the journey.</p><p>Both should influence your business strategy, product decisions, customer experience, hiring, partnerships, and investments.</p><p>If they don’t, you may have written impressive statements, but you haven’t translated them into business direction.</p><h3>Five Problems That Arise When Your Business Lacks a Clear Vision and Mission</h3><h3>1. Your Team Doesn’t Understand What It Is Building Towards</h3><p>Imagine a technology company whose vision is to simplify financial services for small businesses.</p><p>The product team is focused on developing sophisticated features.</p><p>The marketing team is targeting large corporations.</p><p>The sales team is pursuing any customer willing to pay.</p><p>The customer support team is struggling to understand which customers should receive priority.</p><p>Everyone is doing their job.</p><p>But the organization is not necessarily moving towards its stated vision.</p><p>When employees don’t understand the bigger picture, they make decisions based on their individual responsibilities rather than the organization’s intended direction.</p><p>The results are Misaligned efforts, competing priorities, and wasted resources.</p><h3>2. You Keep Making Decisions That Contradict Your Business Direction</h3><p>A business without a clear vision can easily become distracted by attractive opportunities.</p><p>A competitor launches a new product, so you want to launch one too.</p><p>An investor suggests entering another market, so you start exploring it.</p><p>A new technology becomes popular, so you want to integrate it.</p><p>But not every opportunity is right for your business.</p><p>Your vision should provide a reference point for evaluating decisions.</p><p>It helps leadership determine whether an opportunity supports the organization’s long-term direction or simply looks attractive in the moment.</p><p>Without that reference point, strategic decisions become inconsistent.</p><h3>3. Your Customers Cannot Clearly Understand What You Stand For</h3><p>Customers don’t just buy products. They also respond to the value a business consistently delivers.</p><p>If your business keeps changing its message, target audience, and value proposition, customers may struggle to understand what makes you different.</p><p>One month, you’re positioning yourself as an affordable provider.</p><p>The next month, you’re promoting yourself as a premium solution.</p><p>Your messaging changes, but your actual offering hasn’t evolved to support the new promise.</p><p>This creates a disconnect between what customers expect and what the business delivers.</p><p>A clear mission helps the organization maintain consistency in the value it promises and delivers.</p><h3>4. Your Growth Becomes Difficult to Measure</h3><p>How do you know whether your business is moving in the right direction?</p><p>Revenue may be increasing. Your customer base may be growing. Your team may be expanding.</p><p>But growth alone doesn’t tell you whether the organization is becoming the business it intended to build.</p><p>A business needs objectives and performance indicators that connect its daily operations to its long-term direction.</p><p>Otherwise, leadership may celebrate growth without understanding whether that growth is sustainable or strategically relevant.</p><h3>5. You Attract the Wrong People, Partners, and Opportunities</h3><p>Your vision and mission also influence the relationships you build.</p><p>Employees need to understand what kind of organization they are joining.</p><p>Investors need to understand what the business is trying to achieve.</p><p>Partners need to understand where their interests align with yours.</p><p>When your direction is unclear, it becomes harder to attract people who genuinely support the organization’s goals.</p><p>You may end up hiring people whose expectations don’t match the business, entering partnerships that add little value, or pursuing investors whose priorities conflict with your long-term plans.</p><p>That can become an expensive lesson.</p><h3>So, How Do You Fix This?</h3><p>This is not simply a writing exercise.</p><p>You don’t solve an unclear vision by asking someone to come up with a catchy sentence.</p><p>You solve it by understanding the business, its purpose, its customers, and the future it intends to create.</p><p>And this is where Business Analysis becomes particularly useful.</p><h3>How a Business Analyst Can Help</h3><p>A Business Analyst can help leadership move from broad statements to practical business direction. Here are five ways:</p><p><strong>1. Facilitate Vision and Mission Discovery</strong></p><p>Work with founders and key stakeholders to understand why the business exists, the problem it wants to solve, the value it intends to create, and the future it wants to achieve.</p><p>This helps identify gaps between what leadership says the business stands for and what it actually does.</p><p><strong>2. Conduct Stakeholder Analysis</strong></p><p>Different stakeholders may have different expectations of the business.</p><p>A BA helps identify these expectations, understand conflicting interests, and establish a shared understanding of organizational direction.</p><p><strong>3. Assess Strategic Alignment</strong></p><p>Review existing products, services, processes, projects, and initiatives to determine whether they support the organization’s vision and mission.</p><p>This can reveal activities that consume resources without contributing meaningfully to the business’s objectives.</p><p><strong>4. Translate Vision into Business Objectives</strong></p><p>A vision may be ambitious, but the business needs measurable steps to move towards it.</p><p>A BA helps break down that ambition into business objectives, capabilities, initiatives, requirements, and performance measures.</p><p><strong>5. Establish Alignment Across the Organization</strong></p><p>Help departments understand how their responsibilities connect to the bigger picture.</p><p>This may involve defining business capabilities, mapping processes, clarifying responsibilities, and establishing performance indicators.</p><p>The goal is to ensure that the organization isn’t simply working hard but working towards the same outcomes.</p><h3>The One Strategy That Works</h3><p>Your business needs more than a vision statement.</p><p>It needs a vision that informs decisions, a mission that guides action, and a strategy that connects both to execution.</p><p>You should be able to look at a proposed project, a new product, a partnership, or an investment and ask:</p><p><em>Does this support the kind of business we have decided to build?</em></p><p>If the answer is no, you need to question why you’re pursuing it.</p><p>Because not every opportunity deserves your attention.</p><p>Not every customer is your customer.</p><p>And not every form of growth is good growth.</p><p><strong>A business without direction can spend years moving without making meaningful progress.</strong></p><p>Don’t just build a business that does many things.</p><p>Build one that knows why it does them.</p><h3>Let’s Talk, Founders.</h3><p>If I asked your employees, your customers, and your leadership team what your business stands for, would I get the same answer?</p><p>Or does everyone have a different understanding of the organization?</p><p>I’d love to hear your thoughts.</p><p><strong>FOUNDERS SECRETS</strong> explores the business strategies that don’t work, why they fail, and the one approach that helps organizations make smarter decisions and build sustainable businesses.</p><p><em>Business Analysis isn’t just about understanding what a business does. It’s about helping the business understand what it needs to do, why it needs to do it, and how to make it happen.</em></p><p>— Elizabeth ‘Lady Bhie’ Ekenimoh<br>Business Analysis Coach &amp; Mentor</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aef19b44c507" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements Elicitation: Don’t Just Ask Questions.]]></title>
            <link>https://global-ladybhie.medium.com/requirements-elicitation-dont-just-ask-questions-a8743d8c8a98?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8743d8c8a98</guid>
            <category><![CDATA[elicitation]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[tech-skills]]></category>
            <category><![CDATA[tech-career]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 08:01:03 GMT</pubDate>
            <atom:updated>2026-11-09T08:01:03.355Z</atom:updated>
            <content:encoded><![CDATA[<h3>Discover What the Business Needs.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eElnyBOgL_WIcazFdzZdwQ.png" /></figure><p>You’re assigned to a project.</p><p>The stakeholder says:</p><p><em>“We need a new course registration system.”</em></p><p>You smile. You open your notebook. You start asking questions.</p><p>But wait.</p><p>What if the stakeholder doesn’t actually know what they need? And most times they don’t.</p><p>What if students are struggling because of registration policies, approval delays, or poor communication rather than the system itself?</p><p>And what if the person requesting the solution isn’t even the person experiencing the problem?</p><p>That’s where we get <strong>Requirements Elicitation</strong>.</p><p>Because being a Business Analyst isn’t just about asking questions.</p><p>It’s about knowing what to ask, who to ask, how to ask, and what to do with the information you uncover.</p><p>Let’s talk about it.</p><h3>What Is Requirements Elicitation?</h3><blockquote>Requirements elicitation is the process of discovering, gathering and drawing out information about stakeholder needs, expectations, business requirements and solution requirements.</blockquote><p>Notice the phrase <em>drawing out</em>.</p><p>That is important.</p><p>Elicitation isn’t simply asking people what they want and writing down their answers.</p><p>It involves engaging stakeholders, investigating information, exploring problems, uncovering assumptions and helping people articulate needs they may not have clearly expressed before.</p><p>Sometimes, stakeholders know exactly what they need.</p><p>Sometimes, they know what frustrates them but cannot explain why.</p><p>Sometimes, they confidently tell you what solution they want, even though nobody has investigated the actual problem.</p><p>And sometimes, they don’t know what they don’t know.</p><p>Your job is to help make those needs visible.</p><blockquote><strong>Elicitation is discovery, not dictation.</strong></blockquote><h3>Why Can’t We Just Ask Stakeholders What They Want?</h3><p>Excellent question.</p><p>And honestly, if requirements were as simple as asking people what they wanted, Business Analysts would have a much easier life. 😂</p><p>But stakeholders don’t always provide complete, accurate or consistent information.</p><p>Here are a few reasons.</p><h3>1. Stakeholders may describe solutions instead of needs</h3><p><em>“We need an automated approval system.”</em></p><p>Okay. Why?</p><p>Perhaps approvals take too long. Maybe approvers are unavailable. Maybe requests are incomplete. Maybe nobody knows who is responsible for approving what.</p><p>Automation might help or it might automate a broken process.</p><h3>2. Different stakeholders have different perspectives.</h3><p>Students may complain about registration delays.</p><p>The registrar’s office may be concerned about incomplete applications.</p><p>Academic advisers may struggle with course eligibility rules.</p><p>The IT team may be dealing with system limitations.</p><p>One problem. Several perspectives.</p><h3>3. Some information isn’t documented.</h3><p>A process may depend on informal practices, personal knowledge or decisions that were never written down.</p><p>You might discover that the person who knows how a critical process works is the only person who has been doing it for ten years.</p><p>And that person is on leave. Lovely. 😂</p><h3>4. People may forget important details.</h3><p>A stakeholder might describe the normal process but forget exceptions, workarounds, business rules or unusual situations.</p><p>That’s why elicitation requires more than one conversation or technique.</p><p><strong>The information you need may be spread across people, processes, documents, systems and data.</strong></p><h3>The Different Elicitation Techniques Every BA Should Know</h3><p>Now let’s get practical.</p><p>Elicitation techniques are the methods BAs use to discover information.</p><p>There are several. You don’t need to use all of them on every project.</p><p>You need to understand what each technique can help you uncover and when it makes sense to use it.</p><h3>a. Interviews</h3><p>One-on-one or small-group conversations.</p><p>Interviews allow you to explore a stakeholder’s experiences, needs, concerns and expectations in detail.</p><p>They’re particularly useful when you need to understand individual perspectives or investigate something more deeply.</p><p>For our university project, you might interview students who have experienced registration difficulties.</p><p>Questions could include:</p><ul><li>Walk me through how you register for courses.</li><li>Where do you usually experience difficulties?</li><li>What happens when a course is full?</li><li>How do you know whether your registration is complete?</li><li>What do you do when something goes wrong?</li></ul><p>Notice that these questions encourage stakeholders to describe their experiences rather than simply tell you what system they want.</p><h3>b. Workshops</h3><p>Structured sessions involving multiple stakeholders.</p><p>Workshops bring stakeholders together to discuss needs, explore issues, identify differences and develop shared understanding.</p><p>They’re useful when several groups need to contribute to the discussion or when you need to reach agreement on something.</p><p>For example, a registration workshop could involve students, academic advisers and registrar representatives.</p><p>You might use the session to:</p><ul><li>Explore the current registration process.</li><li>Identify common problems.</li><li>Discuss conflicting needs.</li><li>Clarify registration rules.</li><li>Agree on priorities.</li></ul><p>The beauty of workshops is that stakeholders can hear one another’s perspectives.</p><p>Sometimes, what one department considers a minor inconvenience is another department’s daily nightmare.</p><h3>c. Observation</h3><p>Watching people perform their work.</p><p>Observation allows you to see how a process actually works.</p><p>Because what people say they do and what they actually do can be two very different stories.</p><p>For our university project, you could observe students registering for courses or watch administrators process registration requests.</p><p>You might discover:</p><ul><li>Students repeatedly switching between different pages.</li><li>Administrators manually checking course eligibility.</li><li>Staff maintaining separate spreadsheets.</li><li>Students seeking help because instructions are unclear.</li></ul><p>These details may never surface during an interview.</p><p>Observation is especially useful when investigating processes, workarounds and practical challenges.</p><h3>d. Document Analysis</h3><p>Reviewing existing information.</p><p>Sometimes, the answers are already hiding in plain sight.</p><p>Document analysis involves reviewing existing documents and information to understand the business, its processes, rules and current practices.</p><p>For the university project, you might review:</p><ul><li>Course registration policies.</li><li>Student registration guidelines.</li><li>Course eligibility rules.</li><li>Academic calendars.</li><li>Existing process documentation.</li><li>Registration complaint reports.</li></ul><p>This can help you understand how registration is supposed to work and what rules must be considered.</p><p>It also gives you useful questions to ask stakeholders.</p><h3>e. Surveys and Questionnaires</h3><p>Gathering information from many people.</p><p>Surveys are useful when you need feedback from a large number of stakeholders.</p><p>Imagine the university has 10,000 students.</p><p>Interviewing every student would be impractical.</p><p>A survey could help you understand:</p><ul><li>How many students experience registration delays.</li><li>Which stages cause the most difficulty.</li><li>How often registration problems occur.</li><li>How satisfied students are with the current process.</li></ul><p>Surveys can reveal patterns and help identify areas requiring deeper investigation.</p><p>However, they may not explain why those patterns exist.</p><p>That is where interviews, observation and other techniques can complement them.</p><h3>f. Prototyping</h3><p>Using models or mock-ups to explore needs.</p><p>Sometimes stakeholders struggle to explain what they need until they see something.</p><p>A prototype can help them visualise a possible solution and provide feedback.</p><p>For example, you could create a simple mock-up showing:</p><ul><li>Available courses.</li><li>Course prerequisites.</li><li>Registration status.</li><li>Course selection.</li><li>Confirmation of successful registration.</li></ul><p>Stakeholders can then respond to something tangible.</p><p>But here’s the catch:</p><p><strong>A prototype is a conversation starter, not proof that you’ve understood the requirements.</strong></p><p>Don’t present a mock-up too early and accidentally convince stakeholders that the solution has already been decided.</p><h3>How Do You Choose the Right Elicitation Technique?</h3><p>You don’t select techniques because they look impressive on your CV.</p><p>You select them because they help you obtain the information you need.</p><p>Consider these examples.</p><ul><li>Individual student experiences — Interviews</li><li>Differences between departments — Workshops</li><li>How registration actually works — Observation</li><li>Existing registration policies — Document analysis</li><li>How widespread registration problems are — Surveys</li><li>Stakeholder feedback on a proposed interface — Prototyping</li></ul><p>You may also combine techniques.</p><p>For example, you could review registration policies, interview students, observe the process and then conduct a workshop with the registrar’s office.</p><p>Each technique contributes a different perspective.</p><blockquote><strong>Good elicitation isn’t about using more techniques. It’s about choosing techniques that help you discover what matters.</strong></blockquote><h3>Elicitation Is Not the Same as Requirements Analysis. This distinction is worth understanding.</h3><p>During elicitation, you’re primarily discovering and drawing out information.</p><p>During requirements analysis, you’re examining that information to understand its meaning, relationships, implications, feasibility and completeness.</p><p>The activities are closely connected.</p><p>You may discover something during an interview, analyse it, realise you need more information, and return to the stakeholder with additional questions.</p><p>That is perfectly normal.</p><p>Business Analysis isn’t always a neat, straight line.</p><p>Sometimes you move forward.</p><p>Sometimes you go back.</p><p>Sometimes you discover that the question you started with wasn’t even the right question.</p><p>That’s why curiosity is such an important BA skill.</p><h3>What Happens After Elicitation?</h3><p>You don’t finish an interview, collect your notes and declare victory.</p><p>The information gathered needs to be handled properly.</p><p>Depending on the project, you may need to:</p><ul><li>Organise and document the information.</li><li>Identify stakeholder needs and expectations.</li><li>Clarify ambiguous statements.</li><li>Identify assumptions and contradictions.</li><li>Investigate gaps.</li><li>Analyse potential requirements.</li><li>Validate your understanding with stakeholders.</li><li>Update existing requirements and models.</li></ul><p>For example, during an interview, a student might say:</p><p><em>“I always struggle to register for the courses I want.”</em></p><p>That statement is useful, but it isn’t yet a complete requirement.</p><p>You need to investigate further.</p><ul><li>Which courses?</li><li>Why can’t the student register?</li><li>Are the courses full?</li><li>Are prerequisites involved?</li><li>Does the student receive enough information before registration begins?</li></ul><p>The answers may reveal several different issues.</p><p><strong>Don’t turn every sentence a stakeholder says into a requirement.</strong></p><p>First, understand what it means.</p><h3>Common Elicitation Mistakes to Avoid</h3><p>Let’s save you some unnecessary headaches.</p><h3>Mistake 1: Asking leading questions</h3><p><em>“Wouldn’t it be better if the university automated registration?”</em></p><p>You’ve already suggested the answer.</p><p>Try: <em>“What challenges do you experience during registration?”</em></p><p>Let the stakeholder tell you.</p><h3>Mistake 2: Assuming the stakeholder knows everything</h3><p>One person rarely understands the entire business process. Speak to different stakeholders and investigate other sources of information.</p><h3>Mistake 3: Confusing elicitation with documentation</h3><p>Taking excellent notes doesn’t automatically mean you’ve understood the requirements.</p><p>You must interpret, clarify and validate what you learn.</p><h3>Mistake 4: Using only interviews</h3><p>Interviews are useful, but they don’t show you everything. Combine techniques when appropriate.</p><h3>Mistake 5: Forgetting to validate your understanding</h3><p>You might misunderstand a stakeholder, interpret a statement incorrectly or miss an important detail. Confirm what you’ve learned before relying on it.</p><h3>Let’s Build Your BA Portfolio!</h3><p>Remember our university course-registration project?</p><p>We’ve already worked on:</p><ul><li>The business problem.</li><li>Initial requirements.</li><li>Requirement classification.</li></ul><p>Now it’s time to investigate those requirements properly.</p><p>And this is where your next portfolio artifact comes in.</p><h3>Your assignment: Create an Elicitation Plan</h3><p>An Elicitation Plan helps you organise how you intend to gather information for your project.</p><p>It doesn’t need to be a complicated document. It should show that you’ve thought about:</p><ul><li>Who you need to engage.</li><li>What you need to understand.</li><li>How you’ll obtain the information.</li><li>Why you’ve chosen particular techniques.</li><li>What you expect to produce from the activities.</li></ul><h3>Step 1: Identify your stakeholders</h3><p>For our university registration project, consider:</p><ul><li>Students.</li><li>Academic advisers.</li><li>Registrar’s office.</li><li>Lecturers.</li><li>IT support.</li></ul><p>You don’t need to engage everyone in every activity. Decide who is relevant to the information you’re trying to uncover.</p><h3>Step 2: Identify the information you need</h3><p>Think about the gaps in your current understanding.</p><p>For example:</p><ul><li>How does registration currently work?</li><li>What causes registration delays?</li><li>How are course prerequisites checked?</li><li>How are students informed about course availability?</li><li>What happens when a course is full?</li><li>How are registration complaints handled?</li><li>What information do administrators need to process registrations?</li></ul><p>These questions will guide your elicitation activities.</p><h3>Step 3: Choose your techniques</h3><p>Now decide how you’ll obtain the information.</p><p>You might choose:</p><ul><li>Interviews with students to understand their experiences.</li><li>Observation of the registration process.</li><li>Document analysis to review registration policies.</li><li>A workshop with academic advisers and registrar representatives.</li><li>A survey to understand how widespread certain problems are.</li></ul><p>Explain why each technique is appropriate.</p><h3>Step 4: Document your Elicitation Plan</h3><p>Use this simple structure.</p><ul><li>Stakeholder</li><li>Information needed</li><li>Technique</li><li>Why?</li><li>Expected output</li></ul><p>eg:</p><ul><li>Students</li><li>Registration difficulties</li><li>Interviews</li><li>Understand individual experiences</li><li>Student needs and pain points</li></ul><p>These are suggested activities. Adjust your plan based on the information you actually need.</p><h3>Save it to your portfolio</h3><p>Your artifact should include:</p><ul><li>Project context.</li><li>Elicitation objectives.</li><li>Stakeholders to engage.</li><li>Information to uncover.</li><li>Techniques selected.</li><li>Reasons for selecting each technique.</li><li>Expected outputs.</li><li>Assumptions and outstanding questions.</li></ul><p>You can also include a short section explaining how the elicitation findings will inform your existing requirements.</p><p><strong>The goal isn’t to show that you know six elicitation techniques.</strong></p><p>It’s to demonstrate that you can plan how to investigate a business problem.</p><p>And that’s a much stronger portfolio story.</p><h3>Final Thoughts</h3><p>Requirements elicitation is one of those activities that looks simple until you actually do it.</p><p>You ask a question.</p><p>Someone gives you an answer.</p><p>You ask another question.</p><p>Suddenly, you’re discovering a process nobody documented, a business rule nobody mentioned and a problem nobody originally brought to your attention.</p><p>That’s the beauty of elicitation.</p><p>It helps you move beyond what people say they want and understand what they actually need.</p><p>So, remember:</p><p><strong>Don’t just ask questions.</strong></p><p>Listen. Investigate. Observe. Explore.</p><p>And when you think you’ve understood the business?</p><p>Ask one more question. 😂</p><h3>Your turn</h3><p>Go back to your university registration project.</p><ul><li>Create your Elicitation Plan.</li><li>Identify the people you need to engage, the information you need, and the techniques you’ll use to uncover it.</li><li>Don’t just list interviews and workshops.</li><li>Explain why you chose them.</li></ul><blockquote>Your BA portfolio should show more than what you know. <strong>It should show how you think.</strong></blockquote><p>Next, we’ll explore how to turn the information you uncover into something meaningful through <strong>Requirements Analysis</strong>.</p><p>One term. One task. One stronger BA portfolio at a time.</p><p>Let’s build!</p><p><em>If you’re building your Business Analysis knowledge from the ground up, follow along as we break down BA terminology, one concept at a time, in language you can actually use, and build a portfolio you can actually show. If you want to work through a specific situation or ned someone to talk to about your concerns, use the link in bio. I’m happy to discuss further.</em></p><p><em>Or find me on social media:</em><br>LinkedIn: <a href="https://www.linkedin.com/in/elizabeth-ekenimoh/">https://www.linkedin.com/in/elizabeth-ekenimoh/</a><br>Tiktok: <a href="https://www.tiktok.com/@ba_with_ladybhie">https://www.tiktok.com/@ba_with_ladybhie</a><br>Instagram: <a href="https://www.instagram.com/global_ladybhie">https://www.instagram.com/global_ladybhie</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8743d8c8a98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Business Is Busy. But Is It Going Anywhere?]]></title>
            <link>https://global-ladybhie.medium.com/your-business-is-busy-but-is-it-going-anywhere-b941a910e5e0?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/b941a910e5e0</guid>
            <category><![CDATA[startup-founders]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 08:01:04 GMT</pubDate>
            <atom:updated>2026-11-05T08:01:04.125Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is the Hidden Cost of Running a Business Without a Strategic Plan?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ToRryIebk7FQ16iIdOAhDg.png" /></figure><p>Are you a founder who starts Monday morning with fifteen things on the to-do list?</p><p>A potential investor wants an update. <br>The marketing team needs approval for a campaign. <br>A customer has complained about a product feature. <br>Someone has suggested expanding into a new market. <br>The operations team is asking for more resources.<br>The finance team is warning that spending is getting out of hand.</p><p>By Friday, you have attended twelve meetings, approved several initiatives, resolved three emergencies, and made countless decisions.</p><p>Everyone has been busy.</p><p>But when someone asks, <em>“What significant progress did the business make towards its strategic goals this week?”</em></p><p>Silence.</p><p>Not because the business did nothing. Quite the opposite. It did a lot.</p><blockquote><strong>Doing a lot of things is not the same as moving a business forward.</strong></blockquote><p>And this is one of the most expensive mistakes founders and business leaders make.</p><h3>The Business That Never Stops Moving</h3><p>Many businesses don’t struggle because their founders lack ambition.</p><p>They struggle because ambition has no direction.</p><p>There is always another opportunity to pursue. Another market to explore. Another product to launch. Another partnership to consider. Another technology that promises to change everything.</p><p>And because these opportunities sound exciting, they find their way onto the business agenda.</p><p>Before long, the organization has ten priorities, six projects running simultaneously, and three departments working towards entirely different definitions of success.</p><ul><li>The founder is convinced the business is growing.</li><li>The employees are convinced they’re working hard.</li><li>The customers are experiencing inconsistent service.</li><li>And the finance team is wondering why all this activity isn’t translating into better financial performance.</li></ul><p>This is what happens when a business operates without a strategic plan.</p><h3>A strategic plan is not a list of goals you write at the beginning of the year.</h3><p>It is not a motivational document filled with ambitious statements about becoming the leading brand in your industry.</p><p>And it certainly isn’t a presentation that gets discussed at a leadership retreat, approved by management, and forgotten by February.</p><blockquote><strong>A strategic plan is a deliberate decision about where the business is going, how it intends to get there, and what it must do to make that destination achievable.</strong></blockquote><p>It connects ambition to execution.</p><p>It tells leadership what deserves attention, what requires investment, what must change, and what the organization should deliberately avoid.</p><p>Most importantly, it gives the business a basis for making decisions.</p><p>Without it, every opportunity looks equally attractive. Every problem feels urgent. Every new idea competes for resources.</p><p>And the business becomes a collection of activities rather than a coordinated effort towards a meaningful outcome.</p><h3>Five Signs Your Business Is Operating Without a Strategic Plan</h3><h3>1. Everything Is a Priority</h3><p>When everything matters, nothing truly matters.</p><p>The marketing team wants to launch a campaign. The product wants to introduce new features. Sales wants discounts to close more deals. Operations wants new systems.</p><p>All these requests may be reasonable.</p><p>But leadership must determine which initiatives deserve attention first, which can wait, and which should not happen at all.</p><p>Without strategic priorities, departments compete for resources instead of collaborating towards shared outcomes.</p><h3>2. The Business Keeps Chasing Opportunities</h3><p>A partnership opportunity appears. The business pursues it.</p><p>A competitor launches something new. The business wants to replicate it.</p><p>A technology trend emerges. The business wants to adopt it.</p><p>Before long, the organization has spent significant time and money pursuing opportunities that were never part of its original direction.</p><p>Opportunity is good.</p><p>But opportunity without strategic alignment is expensive distraction.</p><h3>3. Teams Are Working Hard but Pulling in Different Directions</h3><p>Ask your sales team what the business is trying to achieve this quarter.</p><p>Then ask marketing.</p><p>Then operations.</p><p>Then product.</p><p>If their answers sound like four different businesses, you have an alignment problem.</p><p>A strategic plan should connect departmental activities to organizational objectives.</p><p>Everyone should understand how their work contributes to the bigger picture.</p><h3>4. Leadership Cannot Clearly Measure Progress</h3><p>Revenue is increasing, but profitability is declining.</p><p>Customer acquisition is improving, but retention is falling.</p><p>The business is launching products, but adoption remains low.</p><p>These are not isolated metrics.</p><p>They are signals that leadership must interpret in the context of its strategic objectives.</p><p>Without clear goals and meaningful performance indicators, management may celebrate activity while overlooking the actual health of the business.</p><h3>5. The Founder Is Still the Strategy</h3><p>Every important decision goes through the founder.</p><p>Every new opportunity requires the founder’s approval.</p><p>Every department waits for the founder to determine what happens next.</p><p>This is not necessarily a commitment problem from the team.</p><p>Sometimes, the organization simply has no shared strategic direction to guide independent decisions.</p><p>The founder becomes the strategy, the approval process, and the bottleneck.</p><p>And that is not a scalable business model.</p><h3>So, What Should a Business Leader Do?</h3><p>A strategic plan cannot be developed by simply asking, <em>“What do we want to achieve?”</em></p><p>Leadership must first understand the business as it currently exists.</p><ul><li>What is working?</li><li>What is failing?</li><li>Where is the business losing money, customers, time, or opportunities?</li><li>What capabilities does the organization have?</li><li>What does the market demand?</li><li>What are customers actually paying for?</li><li>What constraints are preventing growth?</li></ul><p>These questions matter because <strong>you cannot build a sound strategy around an inaccurate understanding of your business.</strong></p><p>And this is precisely where a Business Analyst can create significant value.</p><h3>How Business Analysis Helps Businesses Develop and Execute Strategy</h3><p>A Business Analyst brings structure to strategic conversations.</p><p>Rather than allowing leadership meetings to become endless discussions about ideas, possibilities, and opinions, a BA helps the organization investigate its current state, understand its challenges, and make informed decisions.</p><p>Here is what that can look like.</p><p><strong>1. Business Analysis helps establish the current state.</strong></p><p>Before recommending where a business should go, a BA examines where it currently stands. This may involve reviewing business processes, performance data, customer feedback, organizational capabilities, existing systems, and operational challenges.</p><p>The objective is to identify the gaps between the business’s current reality and its desired future.</p><p><strong>2. Business Analysis helps translate vision into actionable objectives.</strong></p><p>A vision may be to become the preferred provider of a particular service in a specific market.</p><p>But what does that actually mean?</p><ul><li>What customer segments must the business serve?</li><li>What capabilities must it develop?</li><li>What operational changes are required?</li><li>What financial outcomes must it achieve?</li></ul><p>A BA helps break down broad ambitions into specific business needs, requirements, initiatives, and measurable outcomes.</p><p><strong>3. Business Analysis helps prioritize initiatives.</strong></p><p>Not every good idea deserves immediate investment.</p><p>A BA can help evaluate initiatives based on business value, cost, risk, feasibility, dependencies, and strategic alignment.</p><p>This allows leadership to distinguish between activities that create meaningful progress and activities that simply consume resources.</p><p><strong>4. Business Analysis connects strategy to execution.</strong></p><p>A strategic plan becomes useful when people can act on it.</p><p>A BA helps translate strategic objectives into business initiatives, requirements, process changes, stakeholder responsibilities, and performance measures.</p><p>This creates a clearer connection between what leadership wants to achieve and what employees must actually do.</p><p><strong>5. Business Analysis helps evaluate whether the strategy is working.</strong></p><p>Strategy should not be set in stone. Markets change. Customer needs evolve. Competitors respond. Technology advances.</p><p>A BA helps establish feedback mechanisms, analyze performance, identify deviations, and provide evidence that supports strategic adjustments.</p><p>The business can then adapt deliberately rather than constantly reacting to whatever happens next.</p><h3>The One Strategy That Works</h3><p>You do not need another business idea.</p><p>You may not need another product.</p><p>You may not even need another marketing campaign.</p><blockquote>What you need is a clear understanding of where your business is going and a deliberate plan for getting there.</blockquote><p>A business that knows its priorities can allocate resources better.</p><p>A business that understands its capabilities can make smarter growth decisions.</p><p>A business that measures progress can recognize problems before they become expensive.</p><p>And a business that aligns its people around shared objectives can accomplish far more than one where everyone is simply busy.</p><blockquote><strong>The goal is not to do more. It is to do what matters, deliberately, consistently, and with measurable results.</strong></blockquote><p>So, before you approve the next initiative, hire another employee, launch another product, or chase another opportunity, ask yourself:</p><p><em>Does this move us closer to where we have deliberately decided this business should go?</em></p><p>If you cannot answer that question, perhaps the problem isn’t a lack of opportunities.</p><p>Perhaps your business needs a strategy.</p><h3>A Question for Business Leaders</h3><p>If I asked your leadership team to explain your business’s top three strategic priorities for the next 12 months, would everyone give me the same answer?</p><p>And more importantly, would their daily decisions reflect those priorities?</p><p>I’d love to hear your thoughts.</p><p><strong>FOUNDERS SECRETS</strong> explores the business strategies that don’t work, why they fail, and the one approach that helps organizations make smarter decisions and build sustainable businesses.</p><p><em>Business Analysis isn’t just about documenting requirements. It is about helping businesses understand their problems, make better decisions, and turn strategy into results.</em></p><p>— Elizabeth ‘Lady Bhie’ Ekenimoh<br>Business Analyst &amp; Strategy Consultant</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b941a910e5e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Types of Requirements: Not Every Requirement Does the Same Job]]></title>
            <link>https://global-ladybhie.medium.com/types-of-requirements-not-every-requirement-does-the-same-job-ce9a27625df6?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce9a27625df6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[tech-skills]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 10:19:20 GMT</pubDate>
            <atom:updated>2026-11-02T10:19:20.509Z</atom:updated>
            <content:encoded><![CDATA[<h4>So, you’ve identified a business problem and started documenting requirements. Nice! 👏🏽</h4><blockquote>But here’s something you need to understand as an aspiring Business Analyst: <strong>Not every requirement serves the same purpose.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1256MmvmFludwt57AAHJw.png" /></figure><p>Some explain what the business wants to achieve. Others describe what stakeholders need, what a solution must do, or what needs to happen before the business can move to a new way of working.</p><p>If you throw all of these into one document without understanding the differences, things can get messy very quickly.</p><p>And we don’t want that. 😂</p><p>Let’s break it down.</p><h3>First, a quick recap: What is a requirement?</h3><p>A requirement describes a need or condition that must be satisfied to achieve an objective.</p><p>Imagine a university where students struggle to register for courses.</p><p>Registration takes too long. Some students can’t get into their preferred courses. The administration team is dealing with complaints, and nobody seems particularly happy.</p><p>The university wants to improve the registration process.</p><p>Now, before anybody starts shouting, “We need a new portal!”, let’s understand what the university needs and how different requirements help us describe it.</p><p>According to the BABOK Guide, requirements are commonly classified into four categories:</p><ol><li>Business requirements</li><li>Stakeholder requirements</li><li>Solution requirements</li><li>Transition requirements.</li></ol><p>Let’s take them one at a time.</p><h3>1. Business Requirements: What Does the Business Want to Achieve?</h3><p>Business requirements describe the goals, objectives and outcomes an organisation wants to achieve.</p><p>They answer one important question:</p><blockquote><strong>WHY are we doing this?</strong></blockquote><p>Back to our university.</p><p>The university is experiencing delays during course registration and wants students to complete the process more efficiently.</p><p>A business requirement could be:</p><blockquote>Notice what this requirement does.</blockquote><p>It tells us what the university wants to achieve without prescribing a particular solution.</p><p>It doesn’t say the university must build a new website, buy software or hire more administrators.</p><p>Those might be options to investigate later. For now, we know the desired outcome.</p><p>That’s the job of a business requirement.</p><h3><strong>Think of it this way:</strong> If someone asks why the university is undertaking this initiative, the business requirement should help answer that question.</h3><p>Don’t confuse a business objective with a proposed solution.</p><ul><li>“We need a new registration portal” tells you what someone thinks should be done.</li><li>“Reduce the time required to complete course registration” tells you what the business wants to achieve.</li></ul><p>Those are two very different starting points.</p><h3>2. Stakeholder Requirements: What Do the People Involved Need?</h3><p>A business doesn’t operate in isolation. People interact with its processes, systems and services, and they don’t all have the same needs.</p><p>Stakeholder requirements describe what stakeholders need to achieve the business objectives.</p><p>They answer:</p><blockquote><strong>WHAT do the people involved need?</strong></blockquote><p>Let’s look at our university again.</p><p>Who is involved in course registration?</p><p>We have students, academic advisers, the registrar’s office, lecturers and the IT team, among others.</p><p>Their needs may differ.</p><p>For example:</p><ul><li><strong>Students:</strong> Need to see available courses and understand their registration status.</li><li><strong>Academic advisers:</strong> Need to review students’ course selections and advise them where required.</li><li><strong>Registrar’s office:</strong> Needs visibility into registration progress and outstanding issues.</li><li><strong>Lecturers:</strong> Need accurate information about enrolment in their courses.</li></ul><p>These are examples of stakeholder needs that would need to be investigated and confirmed.</p><p>Why does this matter?</p><p>Because if you only speak to the registrar’s office, you might understand the administrative challenges but miss the frustrations students experience during registration.</p><p>And if you only speak to students, you might miss the policies, approval steps and operational constraints that shape the process.</p><p><strong>A BA must understand the business problem and the perspectives of the people affected by it.</strong></p><p>That doesn’t mean every stakeholder gets everything they ask for. Some needs may conflict, and some may fall outside the project’s scope.</p><p>Your job is to help uncover, analyse, prioritise and clarify those needs.</p><h3>3. Solution Requirements: What Must the Solution Do?</h3><p>Now we’re getting into the details.</p><p>Solution requirements describe the capabilities and qualities a solution must have to meet stakeholder and business requirements.</p><p>They answer:</p><blockquote><strong>WHAT must the solution do, or what qualities must it have?</strong></blockquote><p>Solution requirements have two main categories: functional and non-functional requirements.</p><p>Let’s unpack them.</p><h3>A. Functional Requirements</h3><p>Functional requirements describe the<strong> behaviours, features or functions</strong> a solution must provide.</p><p><strong>In simple English, they tell us what the solution must do.</strong></p><p>For our university registration scenario, examples might include:</p><ul><li>The system must allow students to view available courses.</li><li>The system must prevent students from registering for courses when they do not meet the required prerequisites.</li><li>The system must display a student’s registration status</li><li>The system must allow authorised staff to review course enrolment numbers.</li></ul><p>Notice that these statements describe specific behaviours.</p><p>They are more detailed than saying, “Make registration easier.”</p><p>And that’s the point.</p><p>A functional requirement should help the team understand what capability needs to be delivered.</p><h3>B. Non-functional Requirements</h3><p>Non-functional requirements describe <strong>qualities, performance expectations and constraints</strong> that affect how a solution operates.</p><p>They often cover areas such as performance, security, availability, accessibility and usability.</p><p>For example:</p><ul><li>The registration system must display course search results within two seconds under agreed normal operating conditions.</li><li>The system must restrict access to student records based on authorised user roles.</li><li>The registration service must meet an agreed availability target during the registration period.</li></ul><p>These examples would need further discussion and validation with stakeholders before being accepted as project requirements.</p><p>Why?</p><p>Because words such as <em>fast</em>, <em>secure</em> and <em>available</em> can mean different things to different people.</p><p>A BA helps turn those broad expectations into clear, assessable requirements.</p><p>Here’s a simple way to remember the difference:</p><p><strong>Functional = What must it do?</strong></p><p><strong>Non-functional = How well must it perform, or what quality or constraint must it satisfy?</strong></p><p>A system can have all the right features and still be a terrible solution if it is too slow, inaccessible or insecure.</p><p>So please, don’t focus only on features. 😂</p><h3>4. Transition Requirements: What Must Happen to Get Us There?</h3><p>Imagine the university has implemented a new registration solution.</p><p>Everything looks great.</p><p>But there’s one small problem: the existing student records haven’t been migrated, staff haven’t been trained, and nobody has prepared the new process for launch.</p><p>Congratulations. You’ve delivered a solution that the business isn’t ready to use. 😭</p><p>This is where transition requirements come in.</p><p>Transition requirements describe what is needed to move from the current state to the desired future state.</p><p>They answer:</p><blockquote><strong>WHAT must be in place to make the change successfully?</strong></blockquote><p>Examples for our university include:</p><ul><li>Existing student registration records must be migrated before the new system goes live.</li><li>Registration staff must receive training before launch.</li><li>Students must be informed about changes to the registration process.</li><li>The university must confirm that essential operational arrangements are ready before switching to the new process.</li></ul><p>These requirements are often temporary. They support the transition rather than describe the ongoing capabilities of the solution.</p><p>Once the transition is complete, some may no longer be relevant.</p><p>But overlooking them can create serious problems during implementation.</p><p><strong>Remember:</strong> Delivering a solution and successfully moving a business to that solution are not the same thing.</p><h3>Let’s Put All Four Together.</h3><p>Now that we’ve covered the categories, let’s see how they connect.</p><ul><li>Business: Reduce the average time students spend registering for courses. <em>Why are we doing this?</em></li><li>Stakeholder: Students need to see available courses and their registration status. <em>What do stakeholders need?</em></li><li>Functional: The system must display available courses to students.</li><li>Non-functional: Course search results must load within an agreed time. <em>What quality must the solution meet?</em></li><li>Transition: Existing registration records must be migrated before launch. <em>What is needed to move to the new state?</em></li></ul><p>One important distinction: functional and non-functional requirements are both types of solution requirements. They’re included separately in the table to make the difference easier to see.</p><p>Also, these are illustrative examples. In a real project, you would investigate the existing process, gather evidence, consult stakeholders and validate the requirements before treating them as agreed.</p><h3>Common Mistakes to Watch Out For</h3><p>Now that you know the categories, here are a few mistakes to avoid.</p><p><strong>1. Calling everything a business requirement.</strong></p><p>Not every statement belongs at the business level. <strong>“Reduce registration delays”</strong> describes an outcome.<strong> “Display available courses” </strong>describes a solution capability.</p><p><strong>2. Confusing stakeholder requirements with solution requirements.</strong></p><p>A stakeholder might need to know whether their registration is complete. A solution requirement could specify that the system must display the registration status.</p><p>The first describes the need; the second describes a capability that could meet it.</p><p><strong>3. Forgetting non-functional requirements.</strong></p><p>Features alone don’t define a good solution. Performance, security, accessibility and other quality expectations matter too.</p><p><strong>4. Ignoring transition requirements.</strong></p><p>Training, migration, communication and operational readiness can determine whether a solution succeeds in practice.</p><p><strong>5. Classifying requirements without understanding them.</strong></p><p>Don’t just memorise definitions and start assigning labels. Understand what each statement is trying to communicate.</p><p>The goal isn’t to win a requirement-classification competition. 😂</p><p>The goal is to understand the business well enough to define what is needed.</p><h3>Now, Let’s Build Your BA Portfolio!</h3><p>Remember our university course-registration project?</p><p>In the previous article, you were asked to identify the business need and draft an initial set of requirements.</p><p>We’re not abandoning that work to start another shiny new project.</p><p>We’re building on it.</p><h3>Your assignment: Classify and refine your requirements</h3><p>Open the requirements you drafted in the previous exercise.</p><p><strong>Step 1: Review your existing requirements.</strong></p><p>You should have drafted:</p><ul><li>One business requirement.</li><li>Two stakeholder requirements.</li><li>Three functional requirements.</li><li>Two non-functional requirements.</li><li>One transition requirement.</li></ul><p>If you haven’t completed that exercise yet, go back and do it first. You’ll get much more from this task when you have something to work with.</p><p><strong>Step 2: Classify each requirement.</strong></p><p>Create a table with these columns:</p><p><strong>ID — Requirement Category — Why it belongs here</strong></p><p>Your own requirements should reflect the analysis you’ve done for your project.</p><p><strong>Step 3: Check the connections.</strong></p><p>For each requirement, ask:</p><ul><li>What business need does it support?</li><li>Whose need does it address?</li><li>Is it describing an outcome, a stakeholder need, a solution capability, a solution quality or a transition need?</li><li>Is the wording clear enough to understand and assess?</li><li>What information do I still need to confirm?</li></ul><p><strong>Step 4: Improve your requirements.</strong></p><p>If a requirement is vague, revise it.</p><p>If you’ve written a solution requirement without identifying the need behind it, investigate that connection.</p><p>If you’ve overlooked a stakeholder or a transition need, document the gap and the questions you need to explore.</p><p>Don’t invent facts just to make the document look complete. Record assumptions and outstanding questions where necessary.</p><h3>What should go into your portfolio?</h3><p>Save your work as a <strong>Requirements Classification and Analysis</strong> artifact.</p><p>Include:</p><ul><li>Your revised requirements</li><li>Their classifications.</li><li>The reasoning behind each classification.</li><li>Links to the business needs they support.</li><li>Any assumptions or questions that still need investigation.</li></ul><p>This is much more useful than simply listing ten requirements and giving them labels.</p><p>It shows that you understand what the requirements mean and why they matter.</p><p>And that’s exactly what we’re trying to demonstrate through this portfolio.</p><h3>Before You Go…</h3><p>Here’s something I want you to remember.</p><p>You don’t become a good Business Analyst by memorising terminology alone.</p><p>You become better by understanding the terminology, applying it to real situations, asking questions and learning to explain your decisions.</p><p>Today, you learned the four requirement categories and how functional and non-functional requirements fit within solution requirements.</p><p>Now, take the requirements you already drafted and classify them.</p><blockquote><strong>Don’t just read this article and move on. Do the assignment.</strong></blockquote><blockquote>Your portfolio will only grow if you put what you’re learning into practice.</blockquote><p>Next, we’ll look at how BAs discover requirements in the first place — because before you can analyse requirements properly, you need to know how to uncover them.</p><p>One term at a time. One artifact at a time. Let’s build that BA portfolio! 👏🏽</p><p><em>If you’re building your Business Analysis knowledge from the ground up, follow along as we break down BA terminology, one concept at a time, in language you can actually use. If you want to work through a specific situation or ned someone to talk to about your concerns, use the link in bio. I’m happy to discuss further.</em></p><p><em>Or find me on Social media:</em><br>LinkedIn: <a href="https://www.linkedin.com/in/elizabeth-ekenimoh/">https://www.linkedin.com/in/elizabeth-ekenimoh/</a><br>Tiktok: <a href="https://www.tiktok.com/@ba_with_ladybhie">https://www.tiktok.com/@ba_with_ladybhie</a><br>Instagram: <a href="https://www.instagram.com/global_ladybhie">https://www.instagram.com/global_ladybhie</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce9a27625df6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Requirements are More Than Just What the Business Wants]]></title>
            <link>https://global-ladybhie.medium.com/requirements-are-more-than-just-what-the-business-wants-0531611ab773?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/0531611ab773</guid>
            <category><![CDATA[tech-career]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 08:01:02 GMT</pubDate>
            <atom:updated>2026-10-27T08:01:02.544Z</atom:updated>
            <content:encoded><![CDATA[<p>If a stakeholder tells you, “We need a new system,” is that a requirement?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvkx8Pa6c0j0SoeSgkzAbw.png" /></figure><p>Not quite. 👀</p><p>It’s a request. It might be a proposed solution. It might even be the beginning of a very useful conversation.</p><p>But as a Business Analyst, your job is not to take every request at face value, document it, and move on.</p><p>Your job is to understand the need behind it, investigate what the business actually requires, and help define what must be true for that need to be met.</p><p>And that brings us to one of the most fundamental concepts in Business Analysis: <strong>requirements.</strong></p><p>Let me break it down.</p><h3>So, what exactly is a requirement?</h3><p>A requirement is a need or condition that must be met by a solution, a process, a product, or a business capability to achieve an objective.</p><blockquote>In simpler terms, a requirement describes something that is needed or expected for a business need to be satisfied.</blockquote><p>For example, imagine a bank receiving complaints from customers who wait too long for their service requests to be resolved.</p><p>A stakeholder says:</p><p><strong><em>“We need a new customer service platform.”</em></strong></p><p>A less experienced BA might immediately start documenting features for the new platform.</p><p>An experienced BA asks questions to gain more clarity.</p><ul><li>Why do customers wait so long?</li><li>How are service requests currently handled?</li><li>Where do delays occur?</li><li>What do customers and employees need?</li><li>What must change to improve resolution times?</li></ul><p>Perhaps the investigation reveals that requests are manually assigned to teams, there is no consistent tracking process, and employees cannot easily see the status of a request.</p><p>Now we’re getting somewhere.</p><p>The actual requirements might include the ability to track requests, assign them to the appropriate teams, and notify customers when their requests are updated.</p><p>Notice the difference?</p><p>The stakeholder proposed a solution. The BA investigated the need and helped define what the solution must achieve.</p><p><strong>That is the difference between simply recording what someone says and analysing what the business requires.</strong></p><h3>A need, a request and a requirement are not the same thing.</h3><p>These three terms are related, but they serve different purposes.</p><p><strong>A need</strong> describes the problem, opportunity or desired outcome.</p><p><strong><em>Example: Customers need their service requests resolved more quickly.</em></strong></p><p><strong>A request</strong> is what someone asks for, often based on their understanding of the problem.</p><p><strong><em>Example: “We need a new customer service platform.”</em></strong></p><p><strong>A requirement</strong> describes a specific need or condition that must be satisfied.</p><p><strong><em>Example: “The solution must allow service agents to view the status, owner and history of each customer request.”</em></strong></p><p>A request can lead you to a requirement, but it is not automatically a requirement.</p><p>Similarly, a requirement should not automatically be treated as proof that the proposed solution is the right one.</p><p>The BA must investigate, ask questions, and establish whether the requirement is relevant to the business need.</p><p>This is why you should never be afraid to ask a stakeholder, <strong>“Why do we need this?”</strong></p><p>You’re not challenging their authority. You’re trying to understand the business.</p><h3>Not all requirements are the same.</h3><p>Requirements can exist at different levels. Understanding these levels helps you organise your analysis and see how individual needs connect to business objectives.</p><p>The BABOK v3 Guide identifies four commonly recognised requirement classifications.</p><h3>1. Business requirements</h3><p>These describe the goals, objectives or outcomes the organisation wants to achieve.</p><p>They answer the question: <strong>Why are we undertaking this initiative?</strong></p><p>Example: Reduce the average time taken to resolve customer service requests.</p><p>This is about the business outcome, not a particular system feature.</p><h3>2. Stakeholder requirements</h3><p>These describe the needs of a stakeholder or group of stakeholders that must be addressed to achieve the business requirements.</p><p>They answer: <strong>What do the people involved need?</strong></p><p>Examples:</p><ul><li>Customer service agents need to see the current status of each request.</li><li>Customers need to receive updates on their outstanding requests.</li><li>Supervisors need visibility into unresolved requests.</li></ul><p>Different stakeholders may have different needs, and sometimes those needs may conflict. The BA helps uncover, analyse and manage these differences.</p><h3>3. Solution requirements</h3><p>These describe the capabilities and qualities a solution must have to meet the stakeholder and business requirements.</p><p>They are commonly divided into two categories.</p><p><strong>3.1 Functional requirements</strong> describe what a solution must do.</p><p>Examples:</p><ul><li>The system must allow agents to assign requests to service teams.</li><li>The system must generate a unique reference number for each request.</li><li>The system must notify customers when their request status changes.</li></ul><p><strong>3.2 Non-functional requirements</strong> describe the qualities or conditions under which a solution must operate.</p><p>Examples:</p><ul><li>The system must be available 99.9% of the time, subject to the agreed measurement conditions.</li><li>The system must restrict access to customer records based on authorised user roles.</li><li>The system must display a customer’s request history within two seconds under specified normal operating conditions.</li></ul><p>Functional requirements focus on behaviour. Non-functional requirements focus on qualities and constraints such as performance, security, usability and availability.</p><p>The exact classification can depend on context, but the important thing is to capture both what a solution must do and how well it must do it.</p><h3>4. Transition requirements</h3><p>These describe what is needed to move from the current state to the future state.</p><p>They are often temporary because they support the change rather than the ongoing operation of the solution.</p><p>Examples:</p><ul><li>Existing customer records must be migrated into the new platform.</li><li>Service agents must receive training before the platform goes live.</li><li>Historical requests must remain accessible during the transition.</li></ul><p>A solution could meet every functional requirement and still fail during implementation if transition requirements are overlooked.</p><p>Imagine launching a brilliant new system only to discover that nobody transferred the existing customer records. Congratulations, you have a new system and a very unhappy business. 😂</p><p>That is why transition requirements matter.</p><h3>What makes a good requirement?</h3><p>Writing a requirement is not simply a matter of putting “The system must…” in front of a sentence.</p><p>A good requirement should be clear enough to understand, specific enough to assess, and relevant to the need it is intended to satisfy.</p><p>Here are some characteristics to consider.</p><ul><li><strong>Clear:</strong> The meaning should be understandable to the people who need to use or review it.</li><li><strong>Necessary:</strong> It should support an identified need, objective, obligation or constraint.</li><li><strong>Unambiguous:</strong> It should not reasonably mean several different things to different readers.</li><li><strong>Testable:</strong> There should be a way to determine whether it has been satisfied.</li><li><strong>Feasible:</strong> It should be possible to implement within the relevant technical, operational, financial and other constraints.</li><li><strong>Consistent:</strong> It should not conflict with other agreed requirements.</li><li><strong>Traceable:</strong> It should be possible to connect it to its source, the need it supports, and relevant design, implementation or testing activities.</li></ul><p>Consider this requirement:</p><blockquote>“The system should be user-friendly.”</blockquote><p>What does &#39;user-friendly&#39; mean? Who decides? How will we know whether the requirement has been met?</p><p>Now consider:</p><blockquote>“New service agents must be able to locate a customer request using its reference number within 10 seconds under the agreed test conditions.”</blockquote><p>This is more specific and measurable. The ten-second target is illustrative; in a real project, it should be agreed with stakeholders and supported by evidence.</p><p>The lesson is not that every requirement must contain a number. It is that the wording must be appropriate to the requirement and allow the team to determine whether it has been satisfied.</p><h3>Where do requirements come from?</h3><p>Requirements do not magically appear in a requirements document.</p><p>They emerge through Business Analysis activities.</p><p>A BA may discover them through:</p><ul><li><strong>Interviews:</strong> Speaking directly with stakeholders about their needs, experiences and expectations.</li><li><strong>Workshops:</strong> Bringing stakeholders together to explore needs, resolve differences and agree on priorities.</li><li><strong>Observation:</strong> Watching how work is actually performed rather than relying entirely on how people describe it.</li><li><strong>Document analysis:</strong> Reviewing policies, procedures, reports, existing requirements and other relevant information.</li><li><strong>Data analysis:</strong> Investigating trends, patterns, exceptions and performance measures that reveal problems or opportunities.</li><li><strong>Prototyping:</strong> Using mock-ups or models to help stakeholders explore and clarify what they need.</li></ul><p>These are examples of elicitation techniques.</p><p>And here’s an important point: stakeholders do not always know exactly what they need when you first speak to them.</p><p>Sometimes they describe the current process. Sometimes they jump straight to a solution. Sometimes they assume everyone understands a particular rule.</p><p>Your job is to facilitate the discovery process.</p><p>You ask questions, investigate, document what you learn, confirm your understanding, and work with stakeholders to refine the requirements.</p><h3><strong>Requirements are discovered, analysed and agreed upon. They are not simply collected and copied.</strong></h3><h3>What does a BA actually do with requirements?</h3><p>Understanding the definition is one thing. Knowing what to do with requirements in a project is another.</p><p>Depending on the project and delivery approach, a BA may need to:</p><ol><li><strong>Elicit requirements</strong> by gathering information from stakeholders and other sources.</li><li><strong>Analyse requirements</strong> to understand their meaning, relationships, dependencies, feasibility and implications.</li><li><strong>Specify requirements</strong> by documenting them in a suitable format, such as a requirements catalogue, user story or requirements specification.</li><li><strong>Validate requirements</strong> by confirming that they represent the needs of stakeholders and support the business objectives.</li><li><strong>Verify requirements</strong> by checking whether they are sufficiently clear, consistent, complete and of appropriate quality.</li><li><strong>Prioritise requirements</strong> to help determine what matters most and what should be delivered first.</li><li><strong>Manage changes</strong> by assessing proposed changes, maintaining alignment and communicating their impact.</li><li><strong>Trace requirements</strong> to their sources, related requirements, solution components and tests where appropriate.</li></ol><p>These activities are related, but they are not necessarily performed as a rigid sequence. In iterative delivery environments, for example, requirements may be refined and revisited throughout the project.</p><p>The format also varies. A project may use a formal requirements specification, a backlog of user stories, process models, decision tables, or a combination of these.</p><p>The goal is not to produce the thickest document in the room.</p><p>The goal is to make sure the right needs are understood and addressed.</p><h3>A practical example: Putting it all together</h3><p>Let’s return to our bank.</p><p>The bank wants to reduce customer complaints about delayed service requests.</p><p>Here is how the requirements might connect to that objective.</p><p><strong>Requirement level — Example</strong></p><ul><li>Business requirement — educe the average time taken to resolve customer service requests.</li><li>Stakeholder requirement — Service agents need visibility into the status and ownership of each request.</li><li>Functional requirement — The solution must display the current owner and status of each request.</li><li>Non-functional requirement — The request status must load within two seconds under agreed normal operating conditions.</li><li>Transition requirement — Existing open requests must be migrated before the new process goes live.</li></ul><p>These are illustrative examples, not a complete set of requirements for a real banking project.</p><p>Notice how each requirement serves a different purpose.</p><p>The business requirement explains the desired outcome. <br>The stakeholder requirement describes what a group needs. <br>The solution requirements define capabilities and quality expectations.<br>The transition requirement addresses what must happen to move into the new way of working.</p><p>They should not exist in isolation. A BA should be able to explain how they relate to the business need and what evidence would demonstrate that the requirements have been met.</p><p>And remember: <em>a requirement is not automatically valid just because it fits neatly into a category. It still needs to be investigated, analysed and agreed upon.</em></p><h3>Common mistakes aspiring BAs make</h3><p>If you’re learning Business Analysis, watch out for these mistakes.</p><p><strong>Mistake 1: Treating every stakeholder request as a requirement.</strong></p><p>A stakeholder’s request is a starting point for investigation, not a substitute for analysis.</p><p><strong>Mistake 2: Jumping straight to functional requirements.</strong></p><p>Before listing system features, understand the business problem, the desired outcome and the needs of the people involved.</p><p><strong>Mistake 3: Writing vague requirements.</strong></p><p>Words such as <em>fast</em>, <em>easy</em>, <em>flexible</em> and <em>user-friendly</em> may mean different things to different people. Clarify the intended meaning and determine how it can be assessed.</p><p><strong>Mistake 4: Forgetting non-functional requirements.</strong></p><p>A solution may perform the right functions but still be unsuitable because of poor performance, inadequate security, limited accessibility or other quality concerns.</p><p><strong>Mistake 5: Ignoring transition requirements.</strong></p><p>Data migration, training, operational readiness and other change-related needs can be critical to successful implementation.</p><p><strong>Mistake 6: Documenting requirements without understanding their purpose.</strong></p><p>A requirements catalogue filled with statements is not proof of strong analysis. You should be able to explain why the requirements exist, whose needs they address and what they are intended to achieve.</p><h3>Let’s make this practical.</h3><p>Imagine a university where students struggle to register for courses. Registration takes too long, some courses become fully booked before students can complete the process, and the administration team receives numerous complaints.</p><p>Your task is to identify requirements that could help address the problem.</p><p>Start with these steps:</p><p><strong>Step 1: Identify the business need.</strong></p><p>What problem is the university experiencing, and what outcome does it want to achieve?</p><p><strong>Step 2: Identify the stakeholders.</strong></p><p>Consider students, academic advisers, the registrar’s office, lecturers and the IT team. What might each group need?</p><p><strong>Step 3: Draft requirements at different levels.</strong></p><p>Write at least:</p><ul><li>One business requirement.</li><li>Two stakeholder requirements.</li><li>Three functional requirements.</li><li>Two non-functional requirements.</li><li>One transition requirement.</li></ul><p><strong>Step 4: Review your wording.</strong></p><p>Ask yourself:</p><ul><li>Is each requirement clear?</li><li>Is it necessary?</li><li>Can we assess whether it has been met?</li><li>What need does it support?</li><li>What assumptions still need to be investigated?</li></ul><p><strong>Step 5: Explain your reasoning.</strong></p><p>Don’t just develop a document containing your requirements. Explain where they came from, why they matter, and how they connect to the university’s problem.</p><p>That explanation is part of the evidence your portfolio should demonstrate.</p><p>And please, don’t immediately decide the university needs a new registration system. Investigate the existing process first. The problem could involve course capacity rules, approval delays, poor communication, system limitations or a combination of factors.</p><p>Let your analysis lead you to the requirements, not the other way around.</p><h3>Final thoughts</h3><p>Requirements are at the heart of Business Analysis, but understanding requirements goes far beyond knowing how to write a statement or fill in a template.</p><p>You need to understand the business need, recognise different stakeholder perspectives, ask the right questions, analyse what you discover, and define what must be satisfied for the desired outcome to be achieved.</p><p>Most importantly, you need to understand <strong>why each requirement exists.</strong></p><p>Because when someone asks you to explain a requirement, “The stakeholder said so” is not always a sufficient answer.</p><p>You should be able to explain the need behind it, the evidence supporting it, and the outcome it is intended to support.</p><p>That is the difference between documenting requirements and doing Business Analysis.</p><p><strong>Your turn:</strong> Take the business problem in the section above and work on it. Identify the need behind it, then write requirements that could help address it.</p><p>Don’t worry about making them perfect on the first attempt.</p><p>Start by thinking like a BA.</p><p>The templates can come later.</p><p><em>If you’re building your Business Analysis knowledge from the ground up, follow along as we break down BA terminology, one concept at a time, in language you can actually use.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0531611ab773" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stakeholder Management: It’s More Than Knowing Who’s on the Project]]></title>
            <link>https://global-ladybhie.medium.com/stakeholder-management-its-more-than-knowing-who-s-on-the-project-6a64389bb2ec?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a64389bb2ec</guid>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[tech-skills]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business-process]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 07:01:02 GMT</pubDate>
            <atom:updated>2026-10-05T07:01:02.492Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>You can have the perfect requirements and still fail the project if you ignore the wrong people.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNYSwFk_0aCGt2dJFZfxWg.png" /></figure><p>That sounds dramatic, I know</p><p>But anyone who has worked on a project knows that sometimes the biggest project problems aren’t technical.</p><p>They’re people problems.</p><ul><li>Someone wasn’t consulted.</li><li>Someone misunderstood the change.</li><li>Someone expected something completely different.</li><li>Someone important was left out of the conversation.</li></ul><p>And suddenly, the project that looked perfectly fine on paper is facing resistance, delays, rework, and a whole lot of “But I thought…”</p><p>This is where <strong>stakeholder management</strong> comes in.</p><blockquote>Stakeholder Management = Managing the Relationship</blockquote><p>If we strip away the corporate language, stakeholder management is simply:</p><blockquote><strong>Managing the relationship.</strong></blockquote><p>It’s about understanding your people, communicating with them, managing expectations, addressing concerns, and keeping the right people engaged throughout the project.</p><p>Because knowing who your stakeholders are is only the beginning.</p><p>The real work is figuring out:</p><ul><li><strong>Who needs what?</strong></li><li><strong>Who needs to know what?</strong></li><li><strong>Who needs to be involved?</strong></li><li><strong>Who can influence the outcome?</strong></li></ul><p>And perhaps most importantly:</p><p><strong>How do I work with each of them effectively?</strong></p><p>Because the thing is <strong>Your stakeholders are people.</strong></p><p>And people are different.</p><h3>Different People. Different Interests. Different Expectations.</h3><p>Imagine you’re working on a new banking app.</p><ul><li>You have customers who will use the app.</li><li>You have developers who will build it.</li><li>You have business leaders who are funding it.</li><li>You have regulators who care about compliance.</li><li>You have support teams who will deal with customer issues.</li></ul><p>You may also have managers, suppliers, security teams, legal teams, operations teams, and executives involved somewhere along the way.</p><p>Everyone is looking at the same project.</p><p>But they aren’t necessarily looking at it from the same angle.</p><p>The customer may be thinking:</p><blockquote><strong>“Is this easy to use?”</strong></blockquote><p>The business may be thinking:</p><blockquote><strong>“Will this increase revenue?”</strong></blockquote><p>The developer may be thinking:</p><blockquote><strong>“Do I have enough information to build this?”</strong></blockquote><p>The regulator may be thinking:</p><blockquote><strong>“Does this meet the required standards?”</strong></blockquote><p>The support team may be thinking:</p><blockquote><strong>“What happens when customers have problems?”</strong></blockquote><p>Same project.</p><p>Different priorities.</p><p>And that is exactly why stakeholder management matters.</p><h3>Stakeholder Management Isn’t Just Communication</h3><p>One of the easiest mistakes to make is thinking stakeholder management simply means sending updates.</p><p><em>“Hi everyone, here’s the latest project update.”</em></p><p>Email sent.</p><p>Stakeholder management complete.</p><p>Nope. 😂</p><p>Communication is part of stakeholder management.</p><p>But effective stakeholder management goes much further.</p><p>You need to understand <strong>how much communication each stakeholder actually needs.</strong></p><p>Your project sponsor may need high-level progress, risks, decisions, and budget information.</p><p>Your development team may need detailed requirements and quick clarification.</p><p>Your end users may need demonstrations, feedback sessions, and updates about how the change affects them.</p><p>A regulator may need specific evidence and documentation.</p><p>Giving everyone the exact same information in the exact same way isn’t necessarily good communication.</p><p><strong>The right message needs to reach the right person at the right time.</strong></p><p>That is stakeholder management.</p><h3>Manage Expectations Early</h3><p>One of the biggest parts of stakeholder management is <strong>expectation management.</strong></p><p>And this is where BAs can save themselves — and their project team — a lot of pain.</p><p>Let’s say a stakeholder says:</p><blockquote><em>“We just need a small change.”</em></blockquote><p>Sounds harmless.</p><p>Until you discover that the “small change” affects three systems, requires additional testing, changes an existing process, and pushes the delivery date.</p><p>Suddenly, the small change isn’t so small.</p><p>This is why a BA shouldn’t simply say yes to every request.</p><ul><li>You need to understand the impact.</li><li>Ask questions.</li><li>Explore dependencies.</li><li>Clarify priorities.</li><li>Make the consequences visible.</li></ul><p>Sometimes stakeholder management means saying:</p><p><strong>“We can do that, but here’s what it will affect.”</strong></p><p>That conversation may not always be comfortable.</p><p>But it is much better than surprising everyone three weeks later.</p><h3>Not Every Stakeholder Needs the Same Level of Attention</h3><p>Another important part of stakeholder management is understanding <strong>influence and interest.</strong></p><p>Not every stakeholder has the same level of power over the project.</p><ul><li>Some can approve decisions.</li><li>Some can block decisions.</li><li>Some provide critical information.</li><li>Some are directly affected by the change.</li><li>Some have high influence but low day-to-day involvement.</li></ul><p>Others may have low influence but high interest because the change directly affects their work.</p><p>Your approach should reflect those differences.</p><p>You might need to work closely with some stakeholders.</p><ul><li>Keep others informed.</li><li>Consult certain groups regularly.</li><li>Simply monitor others.</li></ul><p>The goal isn’t to give everyone equal attention.</p><p>The goal is to give stakeholders the <strong>right level of attention.</strong></p><h3>What Happens When Stakeholder Management Is Poor?</h3><p>Poor stakeholder management can create problems that look like something else.</p><blockquote>A project is delayed.</blockquote><p>Everyone blames the developers.</p><p>But perhaps the requirements kept changing because key stakeholders weren’t aligned.</p><blockquote>Users reject the solution.</blockquote><p>Everyone blames the product.</p><p>But perhaps the users weren’t involved early enough.</p><blockquote>A senior manager suddenly objects to the project.</blockquote><p>Everyone is shocked.</p><p>But perhaps nobody understood their concerns in the first place.</p><p>The project team keeps going back and forth.</p><p>Everyone says:</p><p><strong>“Why didn’t we know this earlier?”</strong></p><p>Exactly.</p><p>Stakeholder management helps reduce those surprises.</p><p>It doesn’t mean every stakeholder will agree with you.</p><p>It doesn’t mean everyone will love the solution.</p><p>It doesn’t mean conflict disappears.</p><p>It means you are more likely to understand where people stand and deal with those differences intentionally.</p><h3>So, What Does a Good BA Actually Do?</h3><p>A good Business Analyst doesn’t just ask:</p><p><strong>“Who are the stakeholders?”</strong></p><p>They ask:</p><p><strong>“What matters to them?”</strong></p><p><strong>“What influence do they have?”</strong></p><p><strong>“What do they need from this project?”</strong></p><p><strong>“What does the project need from them?”</strong></p><p><strong>“How should I communicate with them?”</strong></p><p><strong>“What concerns might they have?”</strong></p><p><strong>“How involved should they be?”</strong></p><p>And then they act on that information.</p><p>Because stakeholder analysis sitting quietly in a document isn’t stakeholder management.</p><p>The value comes from what you <strong>do</strong> with what you learn.</p><h3>The People Side of Business Analysis</h3><p>Business Analysis is often presented as requirements, processes, models, documentation, and systems.</p><p>And yes, those things matter.</p><p>But underneath all of that?</p><p><strong>People.</strong></p><ul><li>People explain the problem.</li><li>People provide the requirements.</li><li>People make decisions.</li><li>People challenge assumptions.</li><li>People use the solution.</li><li>People approve the change.</li><li>People resist the change.</li></ul><p>And people ultimately determine whether a solution actually works in the real world.</p><p>That’s why stakeholder management is such an important BA skill.</p><p>You can have beautiful requirements.</p><ul><li>A brilliant process model.</li><li>A detailed roadmap.</li><li>A fantastic solution.</li></ul><p>But if the people who matter aren’t aligned, engaged, informed, or heard…</p><p>You may still have a problem.</p><h3>The Simple Way to Remember It</h3><p>If you’re new to Business Analysis, remember it this way:</p><p><strong>Stakeholder = Someone who cares about the outcome.</strong></p><p><strong>Stakeholder identification = Who matters?</strong></p><p><strong>Stakeholder analysis = What matters to them?</strong></p><p><strong>Stakeholder management = How do I work with them?</strong></p><p>Simple.</p><p>No corporate gymnastics required. 😂</p><p>And if you take only one thing from this article, let it be this:</p><blockquote><strong>Don’t just know who your stakeholders are.</strong></blockquote><blockquote><strong>Know how to work with them.</strong></blockquote><p>Because projects don’t happen in documents.</p><p>They happen with people.</p><p>And sometimes, managing those relationships is just as important as managing the requirements.</p><h3>Welcome to the BA Terminology Series. 👋🏽</h3><p>If there’s a BA term you’ve heard that made you think <strong>“What on earth does THAT mean?”</strong></p><p>Drop it in the comments.</p><p>I’ll add the best ones to the series.</p><p>And who knows…</p><p>Maybe the terms will finally stop sounding like something that belongs in a courtroom. 😂</p><blockquote>I’m Elizabeth Ekenimoh. A Business Analyst building scalable solutions for businesses and teaching others to do same.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a64389bb2ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BA Terminology Doesn’t Have to Be Scary. Here is your Cheat Sheet]]></title>
            <link>https://global-ladybhie.medium.com/ba-terminology-doesnt-have-to-be-scary-here-is-your-cheat-sheet-552657afc77f?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/552657afc77f</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business-analyst]]></category>
            <category><![CDATA[business-process-analysis]]></category>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 16:30:08 GMT</pubDate>
            <atom:updated>2026-09-20T16:30:08.644Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Because you shouldn’t need a dictionary to understand your career.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*AlSaUimzY3x07ephI2rOew@2x.jpeg" /></figure><p>If you’re new to <strong>Business Analysis</strong>, there’s a good chance you’ve had this moment:</p><p>You’re watching a BA tutorial.<br>Everything is going well.</p><p>Then someone says:</p><p><strong>“<em>We need to conduct elicitation to identify stakeholder requirements and establish the current-state process before defining the future-state solution.”</em></strong></p><p>And you’re sitting there like:</p><p><strong>“…English, please?”</strong> 😂</p><p>Welcome to Business Analysis.</p><p>The work itself can be practical and exciting.</p><p>The terminologies however, can sometimes be unnecessarily dramatic.</p><p>But the good news is</p><blockquote><strong>Most BA terms are much simpler than they sound.</strong></blockquote><p>And once you understand what they actually mean, the whole BA world starts becoming a lot less intimidating.</p><p>That’s why I’m starting a new series:</p><h3>BA Terminology, Explained Simply</h3><p>No complicated definitions.</p><p>No textbook gymnastics.</p><p>No trying to sound smarter than we need to.</p><p>Just simple explanations, practical examples and the occasional:</p><p><strong>“Ohhh… THAT’S what that means!”</strong></p><p>Let’s start with one of the most important concepts.</p><h3>Requirement = Something That Is Needed</h3><p>The word <strong>requirement</strong> can sound very technical.</p><p>But at its core, it simply answers:</p><blockquote><strong><em>What is needed?</em></strong></blockquote><p>A requirement describes something that is needed by the business, a customer, a user or another stakeholder.</p><p>For example…</p><p>Imagine you’re using an online banking app.</p><p>You forget your password.</p><p>Currently, your only option is to call customer support and wait for someone to help you reset it.</p><p>That’s frustrating for the customer.</p><p>And it’s probably frustrating for the support team too.</p><p>The business identifies a need:</p><blockquote><strong><em>Customers need a way to reset their passwords without contacting Customer Support.</em></strong></blockquote><p>That’s where we start thinking about requirements.</p><p>Maybe the solution could allow customers to reset their password through email or SMS verification.</p><p>But notice something important.</p><p>We didn’t start with:</p><p><strong>“Let’s build a password reset feature.”</strong></p><p>We started with:</p><p><strong>“What does the customer need?”</strong></p><p>That’s an important BA mindset.</p><h3>Don’t Become a Human Notepad 😂</h3><p>One of the easiest traps for a new Business Analyst is thinking that requirements gathering means:</p><p><strong>Stakeholder talks → BA writes everything down.</strong></p><p>Nope.</p><p>That’s not analysis.</p><p>That’s transcription.</p><p>And while documentation is part of the job, the BA’s value comes from what happens <strong>before, during and after</strong> that documentation.</p><p>A stakeholder might say:</p><blockquote><em>“We need a new dashboard.”</em></blockquote><p>A human notepad says:</p><p><strong>“Requirement: New dashboard.”</strong></p><p>A Business Analyst starts asking questions.</p><ul><li><strong>Why do you need it?</strong></li><li><strong>What information are you missing today?</strong></li><li><strong>Who needs this information?</strong></li><li><strong>How are you making decisions currently?</strong></li><li><strong>What problem is the dashboard supposed to solve?</strong></li></ul><p>And suddenly…</p><p>You might discover that the business doesn’t actually need a new dashboard.</p><p>Maybe they need better access to existing data.</p><p>Maybe the data is inaccurate.</p><p>Maybe different teams are using different reports.</p><p>Maybe the real problem is the decision-making process.</p><p><strong>That’s analysis.</strong></p><h3>Request ≠ Requirement</h3><p>This is one of the biggest distinctions I want new BAs to understand.</p><p>Someone can <strong>request</strong> something without fully understanding what they <strong>need</strong>.</p><p>A stakeholder might say:</p><blockquote><em>“We need an app.”</em></blockquote><p>That’s a request.</p><p>But what is the need?</p><p>Maybe customers can’t complete a process easily on the current website.</p><p>Maybe employees are doing everything manually.</p><p>Maybe the company wants to improve customer engagement.</p><p>Maybe there’s a completely different problem.</p><p>If you accept the request immediately, you’ve already jumped toward a solution.</p><p>If you investigate the need first, you’re doing Business Analysis.</p><p>So when someone tells you:</p><p><strong>“We need X.”</strong></p><p>Try asking:</p><blockquote><strong><em>“What problem are we trying to solve?”</em></strong></blockquote><p>That question can take you somewhere very different.</p><h3>Requirement ≠ Solution</h3><p>Another little distinction that will save you a lot of confusion:</p><p><strong>A requirement describes what is needed.</strong></p><p><strong>A solution describes how we might meet that need.</strong></p><p>Let’s go back to our password example.</p><h3>Need:</h3><blockquote>Customers need to reset forgotten passwords without contacting Customer Support.</blockquote><h3>Possible solution:</h3><blockquote>A self-service password reset feature.</blockquote><p>See the difference?</p><p>The requirement focuses on the <strong>need</strong>.</p><p>The solution focuses on <strong>how we address the need</strong>.</p><p>As a BA, you don’t want to become so attached to the first proposed solution that you stop investigating the problem.</p><p>Because sometimes…</p><p><strong>The first solution is not the best solution.</strong></p><p>And sometimes…</p><p><strong>There isn’t even a technology problem to solve.</strong></p><p>Maybe the process is the problem.</p><p>Maybe the policy is the problem.</p><p>Maybe the communication is the problem.</p><p>Maybe nobody has actually agreed on what should happen.</p><p>Again:</p><p><strong>That’s why we analyse.</strong></p><h3>The Three Questions I Want Every New BA to Remember</h3><p>When you come across a requirement, don’t panic.</p><p>Don’t reach for a 400-page textbook.</p><p>Start with three questions:</p><h3>1. What is needed?</h3><p>What does the business, customer or user need?</p><h3>2. Why is it needed?</h3><p>What problem, goal or opportunity is driving the need?</p><h3>3. What outcome are we trying to achieve?</h3><p>What should be different after the change?</p><p>Those three questions won’t solve every BA problem.</p><p>But they’ll get you thinking in the right direction.</p><h3>And This Is What This Series Is About</h3><p>I’m starting this series because I’ve seen how easily BA terminology can make people think:</p><p><strong>“Maybe Business Analysis is too complicated for me.”</strong></p><p>It isn’t.</p><p>The terminology is simply a language.</p><p>And like any language, it becomes easier once someone explains it properly.</p><p>So throughout this series, I’ll take common Business Analysis terms and break them down into:</p><p><strong>Simple meaning.</strong></p><p><strong>Real-world example.</strong></p><p><strong>Practical BA thinking.</strong></p><p>We’ll talk about terms like:</p><ul><li>Requirements</li><li>Stakeholders</li><li>Elicitation</li><li>Business needs</li><li>User stories</li><li>Acceptance criteria</li><li>Business rules</li><li>Current state</li><li>Future state</li><li>Process mapping</li><li>Scope</li><li>Assumptions</li><li>Constraints</li><li>Functional requirements</li><li>Non-functional requirements</li><li>And plenty more.</li></ul><p>No unnecessary jargon.</p><p>No “let’s make this sound complicated because we’re BAs.” 😂</p><p>Just <strong>Business Analysis in plain English.</strong></p><h3>One Last Thing</h3><p>If you’re new to BA, please don’t feel pressured to know everything immediately.</p><p>You don’t need to memorise every term before you can start thinking like a Business Analyst.</p><ul><li>Start with the basics.</li><li>Understand the problem.</li><li>Ask good questions.</li><li>Listen carefully.</li><li>Look for patterns.</li><li>Challenge assumptions.</li><li>Understand the need.</li><li>Then think about the solution.</li></ul><p>Because at the end of the day, Business Analysis isn’t about knowing the fanciest words.</p><p>It’s about being able to look at a business problem and say:</p><p><strong>“Let’s understand what’s really going on here.”</strong></p><p>And that’s where the fun begins.</p><h3>Welcome to the BA Terminology Series. 👋🏽</h3><p>If there’s a BA term you’ve heard that made you think <strong>“What on earth does THAT mean?”</strong></p><p>Drop it in the comments.</p><p>I’ll add the best ones to the series.</p><p>And who knows…</p><p>Maybe <strong>“Elicitation”</strong> will finally stop sounding like something that belongs in a courtroom. 😂</p><blockquote>I’m Elizabeth Ekenimoh. A Business Analyst building scalable solutions for businesses and teaching others to do same.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=552657afc77f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to Grow as a Business Analyst? Stop Building BA Skills.]]></title>
            <link>https://global-ladybhie.medium.com/want-to-grow-as-a-business-analyst-stop-building-ba-skills-0532c8ce79f1?source=rss-3b8d5c97d667------2</link>
            <guid isPermaLink="false">https://medium.com/p/0532c8ce79f1</guid>
            <dc:creator><![CDATA[Elizabeth "Lady Bhie" Ekenimoh]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 07:01:03 GMT</pubDate>
            <atom:updated>2026-09-14T07:01:03.356Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>The fastest way to become a better business analyst may have very little to do with business analysis.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-edWnKBTGYOFF-YDZvyqRA.png" /></figure><p>Let me explain.</p><p>Imagine two business analysts walking into the same project.</p><ul><li>Both know how to gather requirements.</li><li>Both can create process maps.</li><li>Both understand user stories.</li><li>Both can facilitate workshops.</li><li>Both know their way around Jira and Confluence.</li></ul><p>On paper, they look pretty similar.</p><p>Until the project gets messy.</p><ul><li>The customer is unhappy.</li><li>The numbers aren’t adding up.</li><li>The stakeholders disagree.</li><li>The proposed solution is expensive.</li></ul><p>And someone asks:</p><p><strong>“So… what should we actually do?”</strong></p><p>That is where you start seeing the difference.</p><p>One BA looks at the requirements.</p><p>The other looks at the <strong>business.</strong></p><p>And that difference can completely change your career.</p><h3>Business Analysis is bigger than BA</h3><p>One of the biggest mistakes I see aspiring and early-career BAs make is treating Business Analysis like a checklist.</p><ul><li>Learn elicitation.</li><li>Learn requirements.</li><li>Learn process modelling.</li><li>Learn stakeholder analysis.</li><li>Learn Agile.</li><li>Learn some tools.</li></ul><p>Done.</p><p>Except…</p><p><strong>Not done.</strong></p><p>Because Business Analysis isn’t just about knowing how to perform BA activities.</p><blockquote>It’s about understanding <strong>why the business needs you in the first place.</strong></blockquote><p>Businesses don’t wake up on Monday morning and say: <em>“Guys, we need someone to write some requirements today.”</em></p><ul><li>They have problems.</li><li>They have customers.</li><li>They have money at stake.</li><li>They have processes that aren’t working.</li><li>They have goals they are trying to achieve.</li><li>They have technology they need to use wisely.</li><li>And they have people making decisions with imperfect information.</li></ul><p>Your job is to help make sense of all of that.</p><p>So if you want to grow as a Business Analyst, don’t only build BA skills.</p><p><strong>Build business skills.</strong></p><p>Here are five areas I’d pay attention to.</p><h3>1. Understand Money</h3><p>You don’t need to become an accountant.</p><p>But please…</p><blockquote><strong>Know what money has to do with the problem you’re analysing.</strong></blockquote><p>If a company wants to launch a new system, don’t stop at:</p><p><strong><em>“What are the requirements?”</em></strong></p><p>Ask:</p><ul><li><strong><em>Why are we investing in this?</em></strong></li><li>How much will it cost?</li><li>What will it save?</li><li>Will it generate revenue?</li><li>Will it reduce risk?</li><li>Will it improve productivity?</li><li>What happens if we do nothing?</li></ul><p>Imagine you’re analysing a process that takes employees three hours to complete.</p><p>You could simply document the process.</p><p>Or you could ask:</p><p><strong><em>“How much is this inefficiency costing the business?”</em></strong></p><p>Now you’re having a different conversation.</p><p>You aren’t just describing the problem.</p><p>You’re helping the business understand its <strong>financial impact.</strong></p><p>And that is valuable.</p><h3>2. Understand Customers</h3><blockquote><strong>Stop analysing processes as if humans don’t exist.</strong></blockquote><p>A process exists because somebody needs something.</p><p>So understand the person on the other side of it.</p><ul><li>Who is the customer?</li><li>What are they trying to accomplish?</li><li>Where are they getting stuck?</li><li>What frustrates them?</li><li>What makes them abandon the process?</li><li>What makes them choose your competitor?</li></ul><p>You might be asked:</p><blockquote><em>“Can we add another form to the application process?”</em></blockquote><p>A task-focused BA might start documenting the requirements.</p><p>A business-minded BA might ask:</p><blockquote><em>“Why are customers dropping off at this point?”</em></blockquote><p>And suddenly…</p><p>The conversation isn’t about adding another form.</p><p>It’s about fixing a customer experience problem.</p><p><strong>That’s analysis.</strong></p><h3>3. Understand Strategy</h3><p>This one will change the way you look at projects.</p><blockquote>Every initiative should have a reason.</blockquote><p>So when someone says:</p><blockquote><em>“We need to build this.”</em></blockquote><p>Your next question shouldn’t automatically be:</p><blockquote><em>“What are the requirements?”</em></blockquote><p>Try:</p><p><strong>“Why?”</strong></p><ul><li>Why are we doing this?</li><li>What business goal does it support?</li><li>What happens if we don’t do it?</li><li>How does it fit into the wider strategy?</li></ul><p>Because you can deliver a perfectly executed project that was never strategically important.</p><p>Everything works.</p><p>The requirements were met.</p><p>The system went live.</p><p>Everyone celebrated.</p><p>And six months later someone asks:</p><p><strong>“Wait… why did we build this again?”</strong></p><p>Pain. 😂</p><p>A strong BA helps the business connect <strong>activity to outcome.</strong></p><h3>4. Understand Technology</h3><p>No! I’m not telling you to become a developer.</p><p>Your developer friends can breathe. 😂</p><p>But if you’re going to sit between business and technology, you should understand enough technology to have intelligent conversations.</p><p>Learn about:</p><ul><li>Systems</li><li>Data</li><li>APIs</li><li>AI</li><li>Digital products</li><li>Integrations</li><li>Automation</li><li>Security</li><li>Technology limitations</li></ul><p>You don’t need to build the system.</p><p>But you should understand what the system is capable of doing.</p><p>You should be able to ask:</p><p><strong>“Can this system actually support that requirement?”</strong></p><p>And:</p><p><strong>“What happens to the data when this process changes?”</strong></p><p>And:</p><p><strong>“Could we automate this instead?”</strong></p><p>And:</p><p><strong>“Is there already a system that does this?”</strong></p><p>The more technology you understand, the better questions you can ask.</p><p>And great questions are one of a BA’s most powerful tools.</p><h3>5. Understand How Decisions Are Made</h3><p>This is the one people often underestimate.</p><blockquote>Business Analysts work with people.</blockquote><p>Lots of people.</p><p>And those people don’t always agree.</p><ul><li>The person requesting the change may not be the person approving the budget.</li><li>The person using the system may not be the person who owns the process.</li><li>The person with the loudest opinion may not have the most influence.</li></ul><p>So learn to understand:</p><ul><li><strong>Who decides?</strong></li><li><strong>Who influences?</strong></li><li><strong>Who is affected?</strong></li><li><strong>Who has the information?</strong></li><li><strong>Who carries the risk?</strong></li><li><strong>Who needs to say yes?</strong></li></ul><p>Because your analysis can be technically brilliant and still go nowhere if you don’t understand the people around the decision.</p><p>Business Analysis isn’t just about finding information.</p><p>It’s about helping people <strong>make sense of information and make better decisions.</strong></p><h3>And this is where the BA career starts to change</h3><p>At the beginning of your career, you may hear:</p><blockquote><em>“Can you document this?”</em></blockquote><p>Then:</p><blockquote><em>“Can you analyse this?”</em></blockquote><p>Then:</p><blockquote><em>“Can you help us figure this out?”</em></blockquote><p>And eventually:</p><blockquote><strong><em>“What do you think we should do?”</em></strong></blockquote><p>That last question is different.</p><p>It means people trust your judgement.</p><p>They don’t just want your documentation.</p><p>They want your <strong>thinking.</strong></p><p>And that’s the direction I believe more BAs should be moving towards.</p><p>From:</p><p><strong>Requirements → Problems</strong></p><p><strong>Tasks → Outcomes</strong></p><p><strong>Projects → Business</strong></p><p><strong>Documentation → Decisions</strong></p><p><strong>Participation → Influence</strong></p><p>That is where your value starts to compound.</p><h3>So, what should you actually do?</h3><p>Don’t wait for your employer to teach you everything.</p><p>Start looking at your business differently.</p><p>If you work in banking, learn banking.</p><p>If you work in insurance, learn insurance.</p><p>If you work in healthcare, learn healthcare.</p><p>If you work in fintech, learn fintech.</p><p>Understand the business model.</p><p>Read annual reports.</p><p>Look at the company’s strategy.</p><p>Understand its customers.</p><p>Follow industry trends.</p><p>Learn how the company makes money.</p><p>Pay attention to the metrics leaders talk about.</p><p>Talk to people outside your immediate team.</p><p>Ask questions.</p><p>Lots of questions.</p><p>And when you’re working on a project, don’t just ask:</p><p><strong>“What am I supposed to deliver?”</strong></p><p>Ask:</p><p><strong>“What are we trying to achieve?”</strong></p><p>That one question can completely change how you approach your work.</p><h3>Don’t just become a better BA.</h3><p>Become a <strong>more valuable BA.</strong></p><p>Because here’s the thing.</p><p>There are plenty of people who can learn a BA framework.</p><p>There are plenty of people who can write a user story.</p><p>There are plenty of people who can create a process flow.</p><p>There are plenty of people who can document requirements.</p><p>But a person who can walk into a messy business problem and say:</p><p><strong>“I understand what’s happening.”</strong></p><p><strong>“I understand why it’s happening.”</strong></p><p><strong>“I understand the impact.”</strong></p><p><strong>“I understand what our customers need.”</strong></p><p><strong>“I understand our options.”</strong></p><p><strong>“And here’s what I recommend.”</strong></p><p>That’s a different kind of Business Analyst.</p><p>And that’s the BA I want you to become.</p><p>So yes…</p><p><strong>Build your BA skills.</strong></p><p>But while you’re doing that, build your business brain too.</p><p>Understand the money.</p><p>Understand the customer.</p><p>Understand the strategy.</p><p>Understand the technology.</p><p>Understand the people.</p><p>Because the better you understand the business…</p><p><strong>the better you can analyse it.</strong></p><p>And the better you can analyse it…</p><p><strong>the more valuable you become.</strong></p><h3>One question to leave you with:</h3><p>If you had to choose <strong>one business skill</strong> to develop over the next 12 months, what would it be?</p><p>Money?</p><p>Strategy?</p><p>Customer behaviour?</p><p>Technology?</p><p>Decision-making?</p><p><strong>Tell me in the comments.</strong></p><p>Let’s see what BAs are building next.</p><blockquote>If this hits differently than the usual BA content you see — that’s intentional. Follow along for the rest of the series. And if you’re at a career crossroads right now and want to think through what this means specifically for you, my Clarity Session exists for exactly this moment. Link in bio.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0532c8ce79f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>