How to Become a Business Analyst in Nigeria (No Tech Background Needed)
You don't need a computer science degree to become an IT business analyst. You need to understand problems, write them down so clearly that nobody has to guess, and prove you can do it. This is the path I'd follow if I were starting in Nigeria today.
01What an IT business analyst actually does
A business analyst sits between the people who have a problem and the people who build the fix. On one side are operations teams, finance officers, customers and regulators. On the other are developers, testers and vendors. The BA's job is to understand what the business really needs, turn it into requirements a team can build from, and make sure what gets delivered actually solves the problem.
In practice that means running workshops, mapping processes, writing requirements documents and user stories, answering developers' questions, planning user acceptance testing and chasing sign-off. I've done that work across banking operations, capital markets, treasury and public-sector finance. The tools change from project to project; the core job doesn't.
If you want the day-to-day picture, read what a business analyst does in a typical week.
02You probably have more BA skills than you think
Most strong business analysts didn't start as business analysts. Some of the most common starting points:
- Researchers and analysts. You already frame good questions and read data. Elicitation and requirements work use the same muscles.
- Banking and finance staff. You know the processes BAs get hired to fix: account opening, reconciliations, loan approvals, payments. That domain knowledge is hard to teach.
- Operations and customer service. You see where systems break every day. That is the raw material of good requirements.
- Graduates and early-career professionals. You start without bad habits, and a structured portfolio can make up for limited experience.
The gap for most career changers isn't talent. It's knowing the vocabulary, the documents and the methods that employers look for, and having proof that you can use them.
03The six skills to learn first
| Skill | What it means | How to practise |
|---|---|---|
| Elicitation | Getting the real requirements out of people through interviews, workshops and observation | Interview a friend about a frustrating process at their work and write up what they need |
| Process modelling | Mapping how work happens today (as-is) and how it should work (to-be), usually in BPMN | Map a process you know well, such as a bank account opening, in a free BPMN tool |
| Requirements documents | Writing a BRD or FRS that a team can build and test from | Write a short BRD for the process you mapped. Use our BRD guide |
| User stories | Breaking requirements into small, testable pieces for agile teams | Turn your BRD into five user stories with acceptance criteria |
| Testing and UAT | Planning how users confirm the system works, and managing defects to sign-off | Write test cases from your acceptance criteria |
| Data basics | Reading data well enough to question it: simple SQL joins and filters, and how APIs pass data between systems | Learn SELECT, WHERE and JOIN on a free practice database |
Underneath all six is stakeholder management: getting people who disagree to a documented agreement. I teach that with the 4C Framework: Clarity, Conflict, Consensus, Commitment.
04The tools Nigerian employers expect
Job adverts at banks, fintechs and telcos tend to ask for the same small set of tools. You don't need to master them all before applying, but you should have used each one on real work:
- Jira for backlogs, user stories and sprint work
- Confluence or SharePoint for requirements documents and decision logs
- A BPMN tool such as draw.io, Visio or Bizagi for process maps
- Excel for requirements traceability, analysis and UAT tracking
- Figma or a similar tool for simple wireframes
- SQL and Postman for checking data and reading APIs
If you want to practise the core artefacts in one place, the free BA Workbench takes you from a stakeholder map to a process score, a RACI and a draft BRD.
05Build a portfolio, not just a certificate
A certificate says you studied. A portfolio shows you can do the work, and that is what gets you through interviews. Pick one realistic case, such as a fintech onboarding flow or a loan approval process, and take it from brief to test plan:
- A stakeholder map
- A business requirements document
- As-is and to-be process maps
- A backlog of user stories with acceptance criteria
- A UAT plan and a requirements traceability matrix
Put them in a clean folder you can share, and be ready to walk an interviewer through the decisions you made. One well-reasoned project beats five thin ones.
06Do you need a certification?
Not to get your first role, but it can help you get past screening, especially at larger banks and multinationals. For beginners, the IIBA's ECBA is the natural entry point. Once you have experience, CCBA and then CBAP follow. I hold the PSM I from Scrum.org and I'm working towards the CBAP.
I compare the options, costs and requirements in ECBA vs CCBA vs CBAP.
07Your CV, LinkedIn and interviews
- Rewrite your current experience in BA language. "Handled customer complaints" becomes "identified recurring failure points in the complaints process and documented fixes with the operations team".
- Lead with outcomes. Hours saved, errors reduced, approvals sped up. Numbers get read.
- Link your portfolio in your CV and your LinkedIn Featured section.
- Prepare for scenario questions. Most BA interviews ask how you'd handle a stakeholder who disagrees, or a requirement that keeps changing. Have a real or portfolio example ready for each.
08The faster route: learn it with a cohort
You can piece all of this together on your own. The hard part isn't finding information; it's knowing what to focus on, getting honest feedback on your work, and staying consistent alongside a full-time job.
That's why I built the BA Bridge Cohort: a live programme for career changers that takes you from first principles to interview-ready, built around one real project you can show employers.
- Taught live by a practising BA. Two sessions a week, a weekday evening class and a Saturday workshop, and every session is recorded.
- A portfolio, not just notes. Each week adds a deliverable to one capstone project: a stakeholder map, a BRD, process maps, a user story backlog, a UAT plan and a traceability matrix.
- Feedback on everything you submit. Written feedback on every weekly assignment, plus a small peer pod that reviews your work.
- Ready for the job search. A CV and LinkedIn rewrite, an interview question bank, mock interviews with feedback, and a clear route to the ECBA.
- Built around your job. Fully online, so you can join from anywhere.
The next cohort starts in November 2026. It's ₦80,000 for the full 12 weeks for the first five students to enrol, then ₦100,000. See the programme and enrol.
09Common questions
Can I become a business analyst without an IT degree?
Yes. Many business analysts come from finance, research, operations or customer service. Employers care more about whether you can elicit requirements, document them clearly and manage stakeholders, which you can prove with a portfolio.
How long does it take to become a business analyst?
With focused study, around three months is enough to learn the core skills and build a portfolio project. Landing the first role can take longer, depending on your background and how actively you apply and network.
Do business analysts need to code?
No. You need to understand how systems work well enough to talk to developers, and basic SQL and API reading help a lot, but writing production code is not part of the role.
Which certification should a beginner get?
The IIBA's ECBA is designed for people with little or no business analysis experience. It is useful, but a strong portfolio matters more for your first role.