The hardest word in banking isn’t “default.” It’s “no.” And how you say it decides whether the client ever comes back.
There are two kinds of lessons you learn in banking.
The first kind lives in policy manuals, credit frameworks and risk guidelines. You can study those. You can pass exams on them.
The second kind you only learn by sitting across from a real person who is trusting you with their money, their business, and sometimes their whole plan for the future.
I got both in my early years. The second kind changed me more.

The Problem
As I grew out of my first role in operations, I started learning credit.
Credit is where banking stops being about processing and starts being about judgment. You are no longer just carrying out what a customer asks for. You are deciding whether the bank should take a risk on them.
Credit people have a reputation. We’re the ones who ruin a perfectly good conversation by asking, “That’s a lovely idea. How exactly will you repay?” Someone has to ask. That someone was now me.
The frameworks, I could learn. Ratios, cash flow, collateral, risk. Give me enough time and enough coffee and I will understand any framework.
What no framework taught me was the human side.
Because behind every credit file is a real business. A real family. A real plan someone has been thinking about for months, sometimes years. And they are sitting across from you hoping you say yes.
Sometimes the answer is yes. Sometimes it’s “not yet.” Sometimes it’s no. And here is what I learned quickly: a client can survive a “no.” What they don’t forgive is feeling dismissed, confused, or left in the dark.
A client relationship does not survive on one good transaction. It survives on years of being honest, especially when the answer isn’t the one they wanted.
The Pursuit
So I gave myself two jobs.
The first was to do the analysis properly. No shortcuts, no guesswork. If I was going to tell someone yes or no, I wanted to be sure.
The second was to explain it.
I noticed that when a client understood why a decision was made, they trusted the next one. Even a difficult decision. But when they felt rushed or kept in the dark, they started quietly looking at other banks.
So I tried to become the person who:
- Explained things clearly, without hiding behind banking jargon
- Followed up when I said I would, not two days later
- Told the truth early, even when it was uncomfortable
- Asked one more question before assuming I understood
That last one turned out to be the secret weapon.
The request in front of me was not always the real need. Someone might ask for one thing when what they actually needed was something different. If I had just processed the request, I would have solved the wrong problem perfectly. Asking one more question often changed the entire conversation.
Over time, something happened that no policy manual could have taught me. The relationships lasted. Clients came back. They referred people they trusted. When something changed in their business, they called me first.
That is the real currency in banking. Not the money. The trust.
The Payoff
I didn’t realize it then, but I was building the exact skill set I would need years later as a business analyst.
Today, we have fancy names for it. Stakeholder management. Requirements elicitation. Expectation setting. Back then it was simply how I kept my clients.
When I later sat in project rooms with technology teams, executives and operations leads, it felt familiar. Different people, same rules. Explain your reasoning. Follow up. Tell the truth early. And always ask one more question, because the first request is rarely the real requirement.
Numbers get you the decision. Trust gets you the relationship.
What this means for you
When I coach experienced professionals, this is one of the first things I listen for. And it is one of the most common things they leave out.
They have spent years building relationships. They’ve calmed angry stakeholders. They’ve delivered bad news without losing the room. They’ve kept difficult clients loyal.
Then they get into an interview and talk only about tasks and tools. “I used Jira.” “I managed the reports.” “I handled the accounts.”
Hiring managers for mid-to-senior roles already assume you can use the tools. What they really want to know is: can you handle people when it gets hard? Can you earn trust? Can you say no without burning the bridge?
If you have done that, and I’m willing to bet you have, it belongs in your stories. It might be the strongest thing you have.
Try this this week
- Remember your hardest “no.” Think of a time you had to deliver bad news to a client, stakeholder or boss. How did you handle it? What happened to the relationship afterward?
- Find your “one more question” moment. When did asking one extra question reveal the real problem? Write it down. That is a ready-made interview story.
- Audit your stories. Look at the examples you use in interviews. If every one of them is about a task or a tool, replace at least one with a story about trust.
Next week: the project that quietly turned me into a business analyst, years before I ever had the title.
Talk soon,
Jules
P.S. Your Career Readiness Score checks whether your resume shows your impact or just lists your tasks. Free, 3 minutes, no call required.

