When a request is not the requirement

Jasmin Nurkovic Categories: Business Insights Date 19-Nov-2026 4 minutes to read

Every business analyst eventually encounters the same situation. A stakeholder arrives with a request that is specific, confident, and fully formed.

Vizuali Za Novi Tekst When A Request Is Not The Requirement NEWS (1)

Table of contents

    Every business analyst eventually encounters the same situation. A stakeholder arrives with a request that is specific, confident, and fully formed.

    They don’t want a new report. They want this exact report, with these columns, filtered this way.

    They don’t want better visibility into orders. They want a dashboard, on the homepage, refreshing every five minutes.

    And somewhere in the first conversation, a quiet doubt appears as you become aware that their ideas probably won't solve what they are trying to solve.

    The common advice at this point is to look past the request and find the real need. Books like From Analyst to Leader make a similar case: the profession’s value lies in shaping what gets built rather than documenting what was asked for.

    While this advice is sound, it is also often applied badly. Taken too far, it turns into a habit of assuming stakeholders don’t understand their own problems, which is both wrong and a reliable way to lose their trust.

    The more useful starting assumption is that a request is rarely noise. It is the visible end of a chain of reasoning that happened before you arrived.

    People bring solutions because solutions are easier to describe

    Most stakeholders do not experience their work as a set of problems waiting to be articulated. On the contrary, they experience it as a series of frustrations, workarounds, and things that take longer than they should. When someone finally asks what they need, describing a solution is far easier than describing the underlying problem.

    When a client says they need a dashboard, that’s an easy sentence to say. What actually sits behind it takes longer to put into words. “Three times a week I have to ask someone in another department whether an order shipped, because I can’t tell from the system. By the time they answer, the customer has usually called twice.” It takes effort to piece that story together, and nobody walks around with it neatly formulated. That’s why the conversation starts with the dashboard.

    There is a second effect that matters just as much. By the time a request reaches a delivery team, it has often passed through several people, and each has refined it slightly. The original problem gets summarised, then summarised again, and what arrives is a solution with the reasoning stripped out. And, it’s not because anyone was careless, but because context gets lost as information moves through an organisation.

    Vizuali Za Novi Tekst When A Request Is Not The Requirement DETAILS 01

    Recovering the reasoning without interrogating anyone

    The instinct is to ask why, and the five whys technique is built around that instinct. Used too literally, it can feel like an interrogation. People who feel interrogated tend to become defensive and start justifying rather than explaining.

    What works better, in my experience, is asking about events rather than intentions.

    “Walk me through the last time this was a problem.” A specific incident is easier to recall than a general requirement, and it contains details nobody would have thought to include in a request: who was involved, what they tried, and what it cost.

    “What are you doing today instead?” Most unmet needs have a workaround. The workaround tells you what the real constraint is and how expensive it currently is to live with.

    “What happens if we don’t build this?” This question does more work than almost any other. The answers differ enormously: “we carry on as we are”, “we miss a regulatory deadline”, or “the team I promised this to stops trusting me”. Each answer points somewhere different.

    “Who else is affected by this?” Requests tend to arrive from one person’s perspective, and the same problem often looks quite different two desks away.

    None of these questions challenges the request, as they just ask about the environment around it. That distinction matters because the conversation stays collaborative, and you learn things the stakeholder would not have thought to mention.

    Vizuali Za Novi Tekst When A Request Is Not The Requirement DETAILS 02

    The part that gets left out of most advice

    Discovery has a cost, and it is not always worth paying.

    An analyst who treats every request as a symptom becomes exhausting to work with. Stakeholders learn that asking for something small triggers a workshop, and they begin routing around the process entirely. That is a worse outcome than occasionally building something suboptimal.

    There is also the uncomfortable possibility that the stakeholder is right and you are wrong. They have usually lived with the problem for far longer than you have. Sometimes the obvious solution is obvious because it is correct.

    A reasonable test is to ask what would have to be true for the request to be the right answer. If those conditions are plausible and the cost of being wrong is low, build it. Small, reversible, inexpensive changes rarely need extensive discovery. Save the effort for decisions that are expensive to undo.

    And sometimes the constraint is not technical at all. The request may be tied to a commitment someone has already made, a budget that has to be used this quarter, or a system being decommissioned on a fixed date. These constraints are real even when they are invisible. Understanding which are fixed and where there is room to manoeuvre is part of finding a workable answer.

    Vizuali Za Novi Tekst When A Request Is Not The Requirement DETAILS 03

    What this looks like in practice

    The goal is not to replace the stakeholder’s request with your own. It is to get the reasoning back into the room so that everyone can see the same picture.

    In most cases, this produces one of three outcomes. The request turns out to be right, and you proceed with a clearer understanding of why. The request addresses a symptom, and the conversation moves to something that addresses the cause. Or the request turns out to be one of several reasonable options, and the stakeholder makes a better-informed choice.

    All three are good outcomes. Only one of them necessarily involves changing the original request.

    From understanding the request to shaping delivery

    At Vega IT, this is part of how we work with clients: understanding what prompted a request, which constraints we need to work within, and where the cost of getting it wrong is highest. That understanding shapes what gets built. It is usually quicker to establish it at the start than to recover it halfway through delivery.

    The aim is to ask enough questions to make sure what gets built is what was actually needed, and to recognise when the request in front of you is already that thing.

    Jasmin Nurkovic OUR TEAM
    Jasmin Nurkovic Technical Product Owner & Business Analyst

    Gym regular, devoted reader, terrace-in-the-sun enthusiast, and always up for a good meal. Meet Jasmin, our Technical Product Owner & Business Analyst, who came to product work from software engineering and is convinced most delivery problems started as a conversation nobody wrote down properly

    Real People. Real Pros.

    Send us your contact details and a brief outline of what you might need, and we’ll be in touch within 12 hours.