<?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 Dineshi Marasinghe on Medium]]></title>
        <description><![CDATA[Stories by Dineshi Marasinghe on Medium]]></description>
        <link>https://medium.com/@dineshi.marasinghe?source=rss-606d2efd517b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Dineshi Marasinghe on Medium</title>
            <link>https://medium.com/@dineshi.marasinghe?source=rss-606d2efd517b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:23:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dineshi.marasinghe/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[The Hidden Struggles of Requirements Gathering in Real-World Projects]]></title>
            <link>https://medium.com/axonect-blog/the-hidden-struggles-of-requirements-gathering-in-real-world-projects-622f7a30c1fa?source=rss-606d2efd517b------2</link>
            <guid isPermaLink="false">https://medium.com/p/622f7a30c1fa</guid>
            <category><![CDATA[requirements-gathering]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Dineshi Marasinghe]]></dc:creator>
            <pubDate>Thu, 06 Aug 2026 09:29:33 GMT</pubDate>
            <atom:updated>2026-08-06T09:29:33.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RBQKh0jnaWGuVt-vFtRrqw.jpeg" /></figure><p>Requirements gathering is one of the major factors of any successful project. It is a structured process that can be carried out step-by-step, whether that’s asking the right questions from the right person or gathering the answers and moving forward with required design and development. As business analysts, we need to understand clarity, accuracy, and completeness of requirements that directly affect the trajectory of projects. However, the reality for business analysts is far from linear, and there are hidden struggles that critically impact project outcomes.</p><p>In this article, I intend to share some of the less-discussed challenges faced by business analysts during requirements of elicitation and documentation in real-world projects. Recognising these challenges not only prepares BAs to handle them more effectively but also enhances stakeholder communication and delivers better outcomes.</p><p><strong>Why Requirements Gathering Matters</strong></p><p>Before sharing the challenges, it is essential to discuss why effective requirement gathering holds such a pivotal role. Requirements define the boundaries of a project and provide the foundation for:</p><ul><li>Designing and building accurate solutions</li><li>Aligning stakeholders and managing their expectations</li><li>Avoiding project delays and costly reworks</li><li>Ensuring compliance, usability and sustainability</li></ul><p>Inaccurate requirements lead to rework, delayed timelines, and sometimes project failures. Gathering clear, accurate, comprehensive, and complete requirements is a key skill for a business analyst. But hidden challenges behind this requirement gathering process are where skilled business analysts are tested.</p><p><strong>Hidden Struggles in Requirements Gathering</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*KDnUqmhe-yOC8eTGZYnKPA.png" /></figure><p><strong>1. The “Lost in Translation” Effect</strong></p><p>Stakeholders may express their needs clearly, but different industry jargon, different cultures or organisational language can create different meanings within Business Analysts. For example, while one stakeholder may consider a process as a “workflow,” another may describe it as a “process chain.” This may lead to stakeholders misunderstanding key requirements, resulting in misalignment between businesses and technical teams.</p><p><strong>2. Relevant vs. Irrelevant details</strong></p><p>In requirement gathering, stakeholders share extensive details and believe everything they share is relevant. However, not all details are actual requirements. Most of the details may include their opinions, assumptions, or organisational preferences that do not have a direct impact on the outcome. However, skilled Business Analysts should have the knowledge to filter out these irrelevant details. Failing to separate relevant and irrelevant information can lead to bulky documentation, making it difficult to prioritise actual business requirements.</p><p><strong>3. Over-Reliance on “Power Users”</strong></p><p>Projects often rely heavily on a few subject matter experts because of their experience and deep knowledge in specific areas. However, where a team rely on the few subject matter experts constantly, they may unknowingly skew the project’s requirements toward their own perspectives and preferences. This may neglect the views of less-vocal stakeholders, resulting in requirements becoming somewhat biased. Constant reliance on a few members may also lead to gaps in user experience, reduce the outcome of the project, and be difficult to address broader business needs.</p><p><strong>4. Silent Assumptions</strong></p><p>Sometimes stakeholders assume that certain elements are not required to be mentioned because they are “obvious”. Therefore, they omit mentioning those requirements during the requirement gathering. These hidden assumptions, like integration with existing systems or compliance with regulations, often surface late and cause major disruptions in the projects. Furthermore, they can lead to delays, costly reworking, and increased project complexity. Additionally, these missing requirements can create tension between business and technical teams.</p><p><strong>5. Evolving Organisational Politics</strong></p><p>Organisational politics can significantly impact the requirement management. Behind every requirement there are ownership battles and priorities. When leadership changes or shifting priorities during a project, previously agreed requirements can become invalidated. These evolving agendas create conflicts between teams and slow project progress.</p><p><strong>6. Invisible Technical Constraints</strong></p><p>Outdated systems and infrastructure, or vendor limitations are often invisible during initial discussions. When these constraints are neglected at the beginning of projects, analysts may discover some requirements are impossible to implement as originally planned. This may lead to stakeholder frustration and cause significant delays in the project due to redesigning the work scope within existing technical limitations.</p><p><strong>7. Time Compression Pressure</strong></p><p>Sometimes business stakeholders want solutions within a limited time, while analysts recognise that thorough requirement gathering requires sufficient time. This may result in compressed timelines, leading to missing critical requirements or overlooking important details. This can increase overall project risk as decisions are to be made with incomplete details. Additionally, this can lead to lower quality requirements and failure to meet stakeholder expectations.</p><p><strong>Techniques to Overcome These Challenges</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*DwIqgO5inzCd9ZsGXtmfyw.png" /></figure><p><strong>1. Ensure Shared Understanding</strong></p><p>Different meanings arise in some teams due to unclear terminology, jargon, or differences in stakeholder backgrounds. Using glossaries and domain-specific dictionaries language can be standardised across the project. In addition to this, visual models, such as process flow diagrams, wireframes, and charts can be used to clarify concepts. This ensures that stakeholders and analysts share a common understanding.</p><p><strong>2. Prioritise Requirements</strong></p><p>Prioritisation is essential when gathering requirements. MoSCoW (Must, Should, Could, Won’t) and impact vs. effort analysis are a few approaches used to identify the value of requirements. Prioritising requirements helps to reduce scope creep and ensures that teams focus on what truly drives the organisation’s objectives.</p><p><strong>3. Broaden Stakeholder Input</strong></p><p>Highly relying on subject matter experts can make requirements bias towards a specific area. Engaging a broader range of stakeholders through surveys, shadowing or observation ensures that the needs of less-vocal users are captured. This approach ensures that they address all the needs of users while aligning with business objectives.</p><p><strong>4. Validate Assumptions</strong></p><p>Stakeholders sometimes neglect some requirements by assuming those requirements are “obvious”. Maintaining assumption logs and validating these assumptions during elicitation sessions helps to reveal hidden requirements. This practice reduces delays and reworks, and helps teams to breakdown complex project.</p><p><strong>5. Manage Changing Priorities</strong></p><p>Shifting leadership and organisational politics can invalidate requirements. Maintain clear stakeholder maps, establish regular review and update cycles to adapt organisational changes. Making use of change control boards can manage conflicts and adapt requirements without losing alignment with organisational goals.</p><p><strong>6. Identify Technical Constraints Early</strong></p><p>Outdated infrastructures, legacy systems and vendor limitations may not be obvious at the start of a project. Architects and technical leads attending workshops help to expose these constraints early in the process. Understanding technical constraints in advance ensures that requirements are feasible and reduces costly rework later.</p><p><strong>7. Managing Time Compression Pressure</strong></p><p>Analysts can balance speed with the project completeness by providing “good enough” requirements early and consistently refining them. Iterative discovery allows for continuous validation and adjustment as the project progresses, improving accuracy and alignment with stakeholder needs.</p><p><strong>Requirement Gathering is More Than Documentation</strong></p><p>Requirements gathering is not just about documentation — it’s about working through uncertainty, political management, revealing hidden needs and translating complex ideas into real world solutions. By identifying these challenges, business analysts can move beyond checklists and templates to truly enable project success.</p><p>The hidden challenges may never disappear, but with awareness, structured techniques and better strategies, business analysts can turn challenges into opportunities for clarity, alignment, and delivery of value.</p><p><em>The views and opinions expressed in this article are those of the author and do not necessarily reflect the official policy or position of Axonect</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=622f7a30c1fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/axonect-blog/the-hidden-struggles-of-requirements-gathering-in-real-world-projects-622f7a30c1fa">The Hidden Struggles of Requirements Gathering in Real-World Projects</a> was originally published in <a href="https://medium.com/axonect-blog">Axonect Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>