Human-Centred Analysis: Navigating Needs, Alignment, and Real Impact
Key Takeaways
Business analysis thrives on human connection and shared understanding. By focusing on curiosity, empathy, and alignment, you can reduce risk and create clarity:- Start with curiosity, not documents—notice gaps, tensions, and frustrations
- Listen for unspoken concerns; align stakeholders before acting
- Elicit insights through observation, empathy, and trust
- Treat requirements as validated commitments, not just statements
- Pause when goals, scope, or priorities are unclear
- Lead with understanding to reduce risk and build shared clarity
Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.
Business Analysis Starts With a Question
We often talk about business analysis as if it starts with documentation. In practice, though, it begins much earlier.
It starts with a feeling, a tension, a gap between what we expect and what we experience. Sometimes it’s a failing process. Sometimes it’s a frustrated user. Often, it’s a quiet “this doesn’t make sense” whispered in a meeting no one remembers.
This is where the business analysis professional’s journey begins. Not with the perfect template, but with curiosity.
Establishing Scope and Purpose
One of the first things we should listen for in meetings is what’s left unsaid. Silence when someone asks, “Why are we doing this?” Often, silence can mean uncertainty, confusion, or even fear. As business analysis professionals, our role begins here by proceeding with care and curiosity.
That silence can be uncomfortable, and in many organizations, discomfort is quickly met with an urgency to act. But acting without alignment can lead to incorrect results and might risk broken trust or unmet expectations. That’s why human-centred business analysis starts by listening deeply, not just to what’s being said but what’s being avoided.
As business analysis professionals, we can use the following questions to help stakeholders surface what might be unclear or unspoken:
- What business pain are we trying to relieve, and how would the stakeholders describe it?
- How will we define success for those impacted by the change?
- Who owns this change and who lives with the consequences?
If the answers aren’t clear, it’s a signal that people aren’t in agreement about how or if to start. Getting the stakeholders aligned isn’t a technical process; it’s a human one.
Elicitation Is About Discovery
Elicitation is layered. It happens in workshops and meetings, but also in private chats, informal conversations, and observations. It’s about observing, probing, and reading between the lines. Business analysis professionals should connect all these sources of insight to build a clearer, more empathetic understanding of stakeholder needs.
True elicitation is about discovering what people may not yet have words for. The truth is, people don’t always articulate their needs clearly. Business analysts must go beyond collecting statements to observe, probe, and listen with more than just their ears.
Empathy becomes a key tool, not just for understanding what someone says, but how they say it, what they avoid, and what they assume we already know.
People speak in stories, frustrations, or sometimes just silence, and business analysis professionals should help surface what they’re really saying. Many describe solutions before they've fully articulated the underlying problem. That’s why analysts must create an environment of safety, where stakeholders feel free to express uncertainty, change their minds, or say “I don’t know.”
Human-centred elicitation is built on trust. It’s not just about what we ask, but how. Curiosity must be paired with respect, and structure must leave room for intuition. In practice, this means watching what people do and say. It means noticing the workaround they didn’t mention or the manual task they perform that never makes it onto a process map.
Business analysis professionals should not expect stakeholders to even know what they need, let alone to articulate it perfectly from the start. They should ask questions that seek to understand how people feel for a deeper assessment:
- Have we included everyone affected by the outcome?
- Whose decisions are critical for success?
- Who might not speak directly, but signals indirectly? (A question for yourself as you’re observing your stakeholders)
One thing that business analysis professionals should remember: what’s unspoken is just as important as what’s said. Beyond merely capturing requirements, your role is to notice what others overlook, what isn’t said, and what the silence means. To listen without judgment and to ask with care.
This is where the real insight begins—and where trust is built.
Requirements Are Commitments
Good requirements reflect relationships. They tie business pain to a proposed solution, in language that both technical and non-technical stakeholders can understand. More than just statements, they’re promises made to the stakeholders. Each one represents a shared understanding, a decision made, and a level of trust between people.
Once the raw input is gathered, it shouldn’t be rushed into documentation. Requirements need to be validated through dialogue and reflection. Business analysis professionals should ask questions that show they really understand what’s most important:
- Are these requirements testable in a way that reflects how stakeholders will measure success?
- Have we prioritized these requirements in a way that respects the constraints and concerns of those impacted?
- Can the stakeholders involved in this project see that their input links back to goals, pain points, and expectations that have been documented?
If the answer is “no” or “not yet,” then the deeper business analysis isn’t ready. That’s not always easy. It often requires reworking vague, emotionally charged, or politically sensitive inputs and translating them into something clearer. Human-centred analysis means navigating these dynamics with empathy and care, ensuring that what’s documented truly reflects what matters.
Before finalizing requirements, it’s worth asking: Do these requirements reflect what stakeholders truly need or what they were willing to settle for? If there’s doubt, it’s worth going back for more information.
When done well, requirements are no longer simply documentation. Instead, they become the backbone of delivery success and the foundation of stakeholder confidence.
Know When to Hit Pause
There are moments in every project where continuing without resolving something is tempting. This is the part I wish someone had emphasized to me earlier: pausing is not failure. Sometimes, analysis must stop—not for lack of effort, but because alignment is broken.
Human-centred business analysis means recognizing when momentum is masking misalignment. It means having the courage to say, “We’re not ready yet,” and creating space to regroup, realign, and reengage the right people. Pausing protects the integrity of the work and the relationships behind it.
Here are a few signs that it might be time to hit the brakes.
| Checkpoint | Red Flag | Rationale |
| Blurry goals | No one can articulate the business objective | The clear problem isn’t being solved |
| Missing voices | Key units aren’t consulted or represented | This will be needed during UAT or rollout |
| Undefined scope | Stakeholders keep contradicting boundaries | There’s a risk of scope creep or missed deadlines |
| Conflicting priorities | Competing KPIs (e.g., speed vs. compliance) | No one will be satisfied |
| Unmeasurable success | No KPI, no acceptance criteria | A solution can’t be recommended if success can’t be defined |
Knowing when to pause is a sign of leadership, not hesitation. It’s a commitment to doing the right work, with the right people, for the right reasons.
Leading With Analysis
At its core, business analysis is about people. It’s about reducing risk through clarity. It’s about facilitating tough conversations before they become crises and surfacing needs that go unspoken.
Human-centred analysis begins in the space between assumption and awareness. It grows through curiosity, empathy, and the courage to pause when alignment is missing. The real value of business analysis lies not in the artifacts we produce, but in the shared understanding we help create.
When we listen deeply, ask better questions, and treat requirements as commitments, we move beyond process and build connection.
Dive deeper with IIBA’s KnowledgeHub. Access actionable “how-to” content, globally recognized standards like the BABOK Guide, and practical tools to put human-centred business analysis into practice. Start your FREE 7-day trial today.
About the Author

Lina Druskienė is an experienced business analyst with over 20 years of global transformation experience. A member of IIBA, she is also a BCS-certified business analyst, a professional member of BCS (MBCS), and holds a professional-level certification from the Agile Business Consortium. Lina combines strategic thinking with deep stakeholder insight, driving cultural change across global teams. Lina introduced the first certified business analysis training in Lithuania and continues to teach in universities and tech academies, mentor globally, and write about analytical thinking and leadership.
