The Volere Snow Card
13 March 2026
Rapport Is a Skill
7 April 2026⏱️ 12 min reading time (includes watching videos)
Rapport Is Not Small Talk: What Business Analysts Get Wrong About Building Trust
Rapport is one of those business analysis skills everyone agrees is important, yet it is often described so vaguely that it becomes useless. We hear that good analysts should “build trust,” “connect with stakeholders,” or “develop strong relationships.” All true. But what does that actually look like in the moment?
In practice, rapport is not small talk, friendliness, or a naturally easy conversation. It is the point at which the other person starts to feel that you are paying attention to them rather than waiting for your turn to speak. It is a working connection built through curiosity, respect, and the ability to respond to what matters to the stakeholder, not just to your own agenda.
That connection matters because stakeholder engagement rarely fails on process alone. It fails when people hold back, stay guarded, test your credibility, or decide very early that you are not worth opening up to. When rapport is present, stakeholders share more, surface risks earlier, and become easier to work with. When it is absent, even a well-structured conversation can go nowhere.
The challenge is that rapport is fragile. It can be strengthened in seconds, but it can also be lost in seconds, often through habits that feel professionally sensible at the time: jumping too quickly into the agenda, trying to prove competence, or responding to a personal disclosure with a polished project pitch.
So, what does building rapport look like?
Imagine the following situation: You have 10 minutes with a sceptical stakeholder before a steering committee meeting. No agenda. No formal workshop. Just a corridor conversation.
What you do in those 10 minutes will shape everything that follows: whether this stakeholder shares information openly, flags hidden risks early, or simply sends you a calendar invite and moves on.
Most business analysts know that rapport matters. Fewer know how to build it under pressure, and even fewer recognize the exact moment when they lose it.
This post walks through three versions of the same conversation. Same BA. Same stakeholder. Same 10 minutes. Three very different outcomes.
The Setup
Anna is a business analyst newly assigned to a digital transformation project at a logistics company. Her first meeting is with Marcus, the IT Director, who has a reputation for being dismissive of “people from head office.” He is technically brilliant but territorial, and he has seen too many consultants come and go.
Anna notices Marcus’s whiteboard covered in network architecture diagrams. She recognizes the approach from a previous role. She has a choice: launch straight into the project agenda, make small talk about the weather, or acknowledge what she sees on the board and ask a genuine question.
Watch all three scenarios below. Pay attention not just to what Anna says, but to when Marcus opens up and when he shuts down.
Scenario 1: Rapport Established
The conversation starts the same way in all three scenarios. Marcus opens with a slightly guarded line: “You must be the new BA they’ve sent over. Anna, right?” He follows up with a pointed comment about the last BA who talked at him for 45 minutes. Then he shares something that matters to him: he has been up since 6 AM compressing three years of technical debt onto one page for the committee.
This is the moment that defines the conversation.
In Scenario 1, Anna responds to what Marcus actually said. She acknowledges the effort without flattery “Three years on one page! That must have been a painful edit” and then asks a genuine question: “What’s the biggest thing you had to leave out?”
That question does two things. It signals that she respects his expertise. And it hands him control of the conversation, which is exactly what a territorial stakeholder needs.
Marcus begins to engage. He asks about her background. Anna answers with calibrated honesty: she has worked alongside infrastructure teams but would not claim his depth on the technical side. She learns fast. She asks a lot of questions. Fair warning.
No performance. No overselling. Just an honest positioning of herself as a respectful collaborator.
When Marcus asks for her honest read on the project, Anna resists the urge to perform competence. She tells him she does not have one yet, and that she would be making it up if she said otherwise. What she does know is that the projects that go wrong are usually the ones where the BA stopped listening too early.
Marcus’s response: “That’s a better answer than I expected.”
A strong rapport has been established.
What Made It Work
Anna did three things consistently throughout this conversation. She followed Marcus’s lead instead of steering toward her own agenda. She showed genuine curiosity about his work rather than trying to demonstrate her own expertise. And she was honest about the limits of her knowledge without being self-deprecating about it.
Rapport is not about being likable or showing off your skills. It is about making the other person feel heard.
Scenario 2: Rapport Not Established
The opening is identical. Marcus makes the same comment about technical debt. But this time, Anna jumps straight into her agenda: “That’s exactly what I’m here to help with, making sure we surface all the technical constraints early. I’ve got a requirements workshop planned for next week.”
From Marcus’s perspective, she has just confirmed his suspicion. Another head office BA who is not really listening.
His response is polite but closed: “Great. Send me a calendar invite.”
Anna does not notice. She pushes further, asking Marcus for a quick summary of his main concerns before the meeting. This is a reasonable BA instinct but the timing is entirely wrong. She is asking him to do work for her before she has given him any reason to invest in the relationship.
Marcus shuts it down: “That’s what the meeting’s for.”
He leaves this conversation with broadly the same view he started with. The opportunity was there. He signalled it when he mentioned his architecture work, when he shared his frustration about technical debt being ignored. Each time, the instinct to pitch, redirect, or extract information got in the way.
What Went Wrong
Anna treated the conversation as a task: introduce yourself, align expectations, gather information. But rapport does not follow an agenda. It follows the other person’s lead.
The core mistake was responding to Marcus’s personal disclosure with a professional sales pitch. When someone shares a frustration, they are not asking you to solve it, they are testing whether you are the kind of person who actually listens.
Rapport must come before information extraction. Always.
Scenario 3: Rapport Partially Established (Recovered)
This is the most instructive scenario of the three, because it shows what happens when rapport starts to break down and what it takes to repair it.
The opening plays out the same way. Marcus shares his frustration about the technical debt summary. But this time Anna makes a different misstep: she redirects the conversation back to herself. “I know how it is. I’ve been dealing with a lot of documentation myself this week. Anyway, I just wanted to introduce myself.”
Marcus shared something meaningful. Anna moved on. From his side, that exchange just closed a door.
Marcus begins to pull back: “Well, I’ll see you in the meeting.”
But Anna catches the shift. She has one moment left before the meeting starts, and she uses it carefully:
“Before we go in, I just want to say: I know you’ve probably seen a lot of BAs cycle through here. I’m not going to tell you I’m different. But I am genuinely interested in understanding how your team works before I start drawing any conclusions.”
This works because it is disarmingly honest. She named his skepticism without being defensive about it. She made a behavioral commitment rather than a promotional one. The earlier misstep is not fully repaired, but the door reopens.
When Marcus asks for her honest read, she gives the same answer as in Scenario 1 and it lands. Not as strongly, because trust has been dented. But enough.
Marcus: “That’s a better answer than I expected.”
A partial rapport has been established. Fragile, but real.
The RAPID Model for Rapport Recovery
What Anna did instinctively in Scenario 3 maps onto a structured approach for repairing rapport when it wobbles. Even strong professional relationships can hit a rough patch: a rushed response, a tone mismatch, a moment of defensiveness. The question is whether you notice it and respond deliberately.
Rapport repair is not about saying the perfect words. It is about signaling three things: I see you. I respect you. I am willing to adjust.
What Rapport Actually Looks Like in Practice
Rapport in business analysis is not charm and it is not small talk. It is a working relationship where stakeholders feel safe enough to share information openly, including the information they would rather keep to themselves.
Building that kind of trust involves showing genuine interest in stakeholders and their problems, establishing common ground, being reliable and consistent, adapting your communication style to the person in front of you, and staying neutral between stakeholder groups.
In practice, this means things like acknowledging stakeholder frustrations without taking sides, remembering personal details, explaining why you ask certain questions, admitting when you do not know something, staying calm during disagreements, and making your follow-through visible so people can see that their input actually mattered.
The net effect is significant: stakeholders volunteer more complete information, surface hidden issues earlier, and actively support the process instead of resisting or withholding.
Three Conversations, One Lesson
The difference between Scenario 1 and Scenario 3 is not skill level. Anna is the same person with the same experience. The difference is attention. In Scenario 1, she paid attention to Marcus. In Scenario 2, she paid attention to her own agenda.
Scenario 3 is the most realistic because in real projects, you will not always get it right on the first try. What matters is whether you notice and whether you are willing to adjust.
The next time you walk into a meeting with a difficult stakeholder, ask yourself one question before you say anything:
"Am I about to follow their lead, or my own agenda?"
That single moment of awareness is where rapport begins.
This post is part of the BA Coach stakeholder engagement series, based on the EXIN/BCS Business Analysis certification curriculum. The animated scenarios used in this post are available in the BA Coach e-learning programme. Would you like to receive similiar posts, enroll to our blog:
