Everyone in the meeting agreed. Nobody in the meeting agreed. That’s when I found my calling.
Some career moves are planned. You apply, you interview, you get the title.
Others sneak up on you. You get handed a project much bigger than your job description, and somewhere in the middle of it, you realize you’ve found the work you were made for.
For me, that project was a national payment integration.

The Problem
Let me explain what that means without putting you to sleep.
A national payment integration connects a bank’s systems to payment infrastructure that serves an entire country. When it works, money moves smoothly between people, businesses and banks, and nobody thinks twice about it. When it doesn’t, millions of people notice very quickly.
This was not one team’s project. It touched technology, operations, compliance, finance and external partners, all at once. Every one of those groups had a stake in it. Every one of them had opinions. And every one of them spoke a completely different language.
Technology talked about systems, interfaces and integrations.
Operations talked about processes, exceptions and what happens when things go wrong at the end of the day.
Compliance talked about rules, controls and risk.
Finance talked about cost and reconciliation.
Everyone was smart. Everyone was right about their own piece. But nobody was holding the whole picture.
If you’ve worked on a big project, you know the kind of meeting I’m talking about. Everyone nods. Everyone says, “Yes, that makes sense.” Everyone leaves feeling aligned. Then two weeks later you discover that each person walked out with a completely different idea of what was agreed.
Everyone agreed. Nobody agreed.
When people don’t share a language, requirements get lost in translation. Assumptions go unchecked. And problems show up late, right when they’re most expensive and most embarrassing to fix.
The Pursuit
Here is where my unglamorous background suddenly became my superpower.
Those years in operations and credit meant I understood how the business actually ran. So I could sit with the technology team and explain what the business really needed, in terms they could build. Then I could walk back to operations and explain what the system would do, what it wouldn’t do, and what that meant for their daily work.
I became a translator.
I mapped the processes, step by step, so everyone could see the same picture instead of five different pictures in five different heads.
I wrote requirements in plain language. Not jargon. Not fifty-page documents nobody reads. Clear statements that a developer, an operations lead and a compliance officer could all read and agree on.
And I became a professional asker of “basic” questions.
“When you say the transaction is complete, complete for who?”
“What happens if this fails halfway?”
“Who owns this step after go-live?”
Those questions can feel almost too simple to ask in a room full of experts. Nobody wants to be the one who looks like they’re behind. But I learned that the simple questions are usually where the biggest risks hide. The question everyone is too proud to ask is often the one that saves the project.
I followed up until everyone agreed, really agreed, on what “done” meant.
And somewhere in the middle of all of it, it hit me. I was not just working on this project. I was the bridge holding it together.
The Payoff
That was the moment I understood what I wanted to do with my career.
I was a business analyst before I ever held the title. The work energized me in a way routine banking never had. I loved the puzzle of it: taking messy, conflicting needs from different people and turning them into something clear enough to build.
Years later, when I moved to Canada and formally became a business analyst, I didn’t feel like I was starting from scratch. I felt like I was finally getting a name for the work I had been doing all along.
If everyone in the room speaks a different language, the person who can translate becomes the person everyone needs.
What this means for you
This is the story I share with experienced professionals who tell me, “But I’ve never officially been a BA.”
Or a project manager. Or a leader. Fill in the title you’re chasing.
Here’s what I tell them: titles lag behind skills. Very often you have already done the work. You just did it under a different name.
Look closely at your past projects. Have you ever:
- Been the person connecting the business side to the technical side?
- Written down what was actually needed when everyone was talking in circles?
- Asked the question nobody else wanted to ask?
- Gotten a room full of people to genuinely agree on what “done” meant?
If yes, you have done business analysis. You have done project leadership. You have done the work.
Your job now is not to go back and get the experience. Your job is to name it and tell it well. That’s the difference between “I don’t have the experience” and “Let me tell you about the time I held a national project together.”
Try this this week
- Find your translation moment. Think of one project where people weren’t understanding each other. What did you do to bridge the gap? Write it down in five sentences.
- List your “basic” questions. What questions have you asked in meetings that changed the direction of the work? Those are proof of analytical thinking. Put them in your interview stories.
- Retitle your experience. Look at one past role and ask: if I described the actual work, not the official title, what would I call it? Use that language on your LinkedIn.
Next week is the last story in this series, and it’s the most honest one. Ten years into banking, I discovered a gap I had been hiding. Here’s what I did about it.
Talk soon,
Jules
P.S. If you’ve been doing the work without the title, your Career Readiness Score will show whether your resume makes that clear. It’s free and takes 3 minutes.

