top of page

Breaking Into Business Analysis: How to Get In, Even Without a Traditional Path

DAY 1 | How I broke into business analysis without being a developer




I have a Master's in software technology, and I cannot code. I trained as a computer engineer at Covenant University in Nigeria, then moved to Aberdeen for a Master's in software technology, finishing around 2011. On paper, I was headed straight for a developer's desk. And somewhere in the middle of all that study, I had to admit something that felt, at the time, like a quiet kind of failure. I did not have a flair for writing software. I still don't. I could learn the syntax and pass the exams, but the thing real developers have, the genuine pull toward building in code, was simply not in me.

For a while I read that as a verdict. If I could not build the software, I did not belong in tech, and I had just spent years and a great deal of money training for a life I now knew I did not want. That is a lonely thing to realise in a new country with a fresh degree and a growing sense that you have taken a wrong turn you cannot undo. What I could not see then, and want to tell you now, is that I had not taken a wrong turn at all. I had simply confused one job in tech with the whole of it.

The realisation did not arrive all at once. It came in small moments over my time in Aberdeen, watching classmates lose whole happy nights inside a problem in code while I quietly watched the clock, noticing that the parts of the course I came alive in were the ones about how systems were designed, who they were for, and why they mattered, rather than the lines that made them run. I kept waiting for the love of coding to arrive. It never did. What arrived instead, slowly, was the honesty to stop pretending it would.


The default door I refused

When I admitted development was not for me, the advice came back the same from every direction. Go into IT support. Collect the Microsoft certifications. Take the route everyone points the non-coders toward. I understood why people said it. It is safe, it pays, and it keeps you near computers. But something in me refused. I did not want a career I had chosen by default, just because it was the obvious door for someone who could not write software. What I wanted was to stay in the field I genuinely loved and use the way my mind actually works, which was never about producing the code. It was about understanding problems, understanding people, and seeing how the two meet. I did not yet know that the thing I was describing to myself, a role that sat close to technology without being buried in it, a bridge between the people with a problem and the people who build the solution, already had a name and a whole profession behind it.

So I searched. I read, I asked, I looked for any role that would keep me close to the technology I loved without asking me to live inside the code. It was not a fast or tidy process, and for a stretch it felt like plain wandering. But I would rather wander toward something that fit than march confidently through a door I already knew was wrong.


Finding the craft, and a guide

I did not stumble sideways into business analysis, the way the myth says everyone does. I found a school that trained people in it, and I went and learned it on purpose. That one decision, choosing to be taught rather than waiting to be discovered, changed everything that came after. Business analysis turned out to be a craft, and crafts can be learned deliberately, from people who already know them. The door I thought was locked was not locked at all. It just had to be found.

Early on, people who had already walked the road agreed to guide me. I will keep them anonymous, but I owe them more than I can easily put into words. They shortened my mistakes. They told me the things nobody writes down. And in the moments I doubted whether I belonged, they reminded me that I did. So much of a career is not the skill itself but knowing where to point it, and that is the thing a good mentor gives you that no course ever can.

The first time I saw the work up close, something settled in me. Here was a role built entirely around the things I was actually good at: understanding a problem, asking the right questions, making sense of a mess, and helping people who could not quite hear each other finally connect. It did not ask me to be a developer. It asked me to be the bridge, and I already had the makings of one. For the first time since finishing my Master's, the path ahead felt like mine, rather than a consolation prize for the path I could not walk.


Why I am telling you this

For years I saw my engineering and software background as the thing I had abandoned to become an analyst. I see it completely the other way round now. It is the reason I am good at the job. The entire point of a business analyst is to stand between the business and the technology and make each make sense to the other, and that is hard to do if you have never lived on the technical side. The years I thought were a detour were quietly building the exact bridge the role required. Not being able to code was never the handicap I feared. In the end, it was close to irrelevant.

I am telling you this because you may be standing where I once stood. Loving tech but sure you do not fit. Eyeing a default door you do not really want. Wondering whether a degree or a few hard years have gone to waste. They have not. This week is for you. Over the next four days, I will walk through what a business analyst actually does, the experience you already carry without realising it, and the practical path to your first role. Today I only want to leave you with the one thing I most needed to hear back then, and did not: you do not have to be a developer to belong in tech, and you do not have to fall into this profession by accident. You can choose it, and you can be taught it, exactly as I was.

Go out and be successful.

Oluwatosin Ogunkoya | Flotog BA Insights  |  www.flotogbainsights.com


Tomorrow: What a Business Analyst Actually Does. The most misunderstood role in tech, explained plainly, and an honest check on whether it fits you.

 
 
 

Comments


bottom of page