The earlier archive Written for a different audience — operations teams, business stakeholders, new joiners. It is kept unchanged, with its original date, because a dated body of work says something a rewritten one cannot.

From Developer to Business Analyst: The Bridge Role

It was 2020 at i4cus Nigeria Limited. My title had evolved from "Software Engineer" to "Software Engineer / Business Analyst."


The Tuesday I Realized I Was Building the Wrong Thing

It was 2020 at i4cus Nigeria Limited. My title had evolved from "Software Engineer" to "Software Engineer / Business Analyst."

I sat in a meeting with stakeholders for a new patient management system. They explained what they needed. I took detailed notes. I prepared technical specifications.

Two weeks later, I delivered a perfect implementation. Clean code. Efficient algorithms. Beautiful user interface.

The stakeholders were... polite.

"It's... very impressive," the medical director said. "But this doesn't solve our problem."

I was confused. "You said you needed to track patient appointments. This system does that."

"Yes," he said. "But our problem isn't tracking appointments. Our problem is that patients miss appointments because they forget. We need reminders, not just tracking."

I had built exactly what they asked for. I had built exactly what they didn't need.

I was speaking technical language. They were speaking business language. And I hadn't learned to translate.

The Metaphor: The Architect and the Homeowner

Let me explain this with a metaphor that transformed my understanding.

Imagine you're an architect. A homeowner comes to you and says: "I need a kitchen."

You, being a good architect, ask questions about materials, layout, appliances, budget. You design a beautiful kitchen. Perfectly functional. Efficient workflow.

You build it. The homeowner walks in and says: "This doesn't solve my problem."

"Of course it does," you say. "It's a kitchen."

"No," they say. "My problem is that my family never eats together. We're always eating in different rooms. I wanted a kitchen that would bring us together, not just a kitchen."

You built what they asked for. You didn't understand what they actually needed.

This is the bridge between developer and business analyst.

  • The Developer hears: "I need a kitchen" and builds the kitchen
  • The Business Analyst hears: "I need a kitchen" and asks: "What problem are you trying to solve?"

Both skills are valuable. But they're different.

The Struggle: Feeling Like I Was Losing My Technical Identity

I'll be honest: this transition was uncomfortable.

I had built my career on being the technical expert. I knew my frameworks. I knew my algorithms. I took pride in my code quality.

Now, people were telling me that my technical skills weren't enough. They wanted me to ask questions. To understand business problems. To translate between worlds.

It felt like I was being asked to be... less technical. Less of an engineer.

I worried I'd lose what made me valuable.

Then I had a conversation with a mentor who changed everything.

"Omeiza," he said, "think about the best architects you know. Are they the ones who can design the most beautiful kitchens? Or the ones who understand what homeowners actually need?"

I thought about it. The best architects I knew weren't necessarily the best draftsmen or the most knowledgeable about materials. They were the ones who listened to homeowners and created homes that truly fit how they lived.

"Your technical skills are your foundation," he continued. "But business analysis is how you apply those skills to solve actual problems. You're not becoming less of an engineer. You're becoming a better one."

The Transformation: Becoming the Translator

I started thinking of myself differently. Not as a "technical expert" or a "business person"—but as a translator.

My technical skills gave me credibility. My business analysis skills gave me relevance.

Together, they made me someone who could understand both worlds and help them understand each other.

What Changed

Before: The Question-Answer Approach

Stakeholder: "We need a system to track appointments." Me: "Okay, I'll build an appointment tracking system."

After: The Problem-First Approach

Stakeholder: "We need a system to track appointments." Me: "What problem are you trying to solve with appointment tracking? What happens if we don't do this?"

The answers revealed the real need: reminders, not tracking.

Before: The Feature Delivery Mindset

I delivered features. I was done when the feature worked.

After: The Outcome Delivery Mindset

I delivered solutions. I was done when the problem was solved.

The tracking feature was delivered. But the missed appointment problem wasn't solved. I wasn't done.

The Framework: The Bridge Approach

I developed a framework that helped me bridge technical and business thinking.

The "Why Before What" Framework

Step 1: Ask "Why?" Before Every "What?"

Wrong approach: Stakeholder asks for a feature → Build the feature

Right approach: Stakeholder asks for a feature → Ask why they need it → Understand the problem → Build a solution

Example:

  • Stakeholder request: "We need a patient portal."
  • Developer response: Build a patient portal.
  • Business analyst response: "What do patients need to do through a portal? What problems are you trying to solve?"

The answers might reveal: patients need appointment reminders, prescription refills, and test results. The portal is a means to those ends—not the end itself.

Step 2: Translate Business Problems to Technical Solutions

You understand the business problem. Now, use your technical skills to solve it.

Business problem: Patients miss appointments → revenue loss, wasted time slots

Technical solutions (not features):

  • Automated reminders via SMS/Email
  • Online scheduling with confirmation
  • Patient self-service cancellation and rescheduling

These aren't "features"—they're solutions to a business problem.

Step 3: Technical Solutions Back to Business Value

After implementing a solution, explain its value in business terms.

Wrong explanation: "We built an SMS notification system that integrates with our appointment database and sends messages using our provider's API."

Right explanation: "We implemented automated appointment reminders. This reduces missed appointments by 40%, which saves approximately 20 appointment slots per week and increases revenue by approximately £8,000 per month."

The first explanation is technical. The second is business value.

Real-World Example: The Project That Changed Everything

Let me share the project where I truly embraced the bridge role.

The Request

A healthcare provider came to us wanting a "digital patient record system."

The Developer Approach

If I had approached this as a developer only:

  • Build a web application to store patient records
  • Include forms for all patient information
  • Ensure data security and compliance
  • Deliver the application

The Business Analyst Approach

Instead, I asked: "What problem are you trying to solve with digital patient records?"

The answers were revealing:

  • Problem 1: Paper records are lost or misplaced
  • Problem 2: Multiple locations can't access records
  • Problem 3: Doctors spend time searching for records
  • Problem 4: Patients have to repeat information at every visit

The Hybrid Solution (Bridge Role)

Using my technical skills and business understanding, we built:

  • Solution 1: Digital storage with automatic backup (solves lost records problem)
  • Solution 2: Cloud-based system accessible from any location (solves access problem)
  • Solution 3: Search and indexing functionality (solves search time problem)
  • Solution 4: Patient history summary view (solves repetition problem)

The Results

  • Lost records: Reduced to zero
  • Time to find records: Reduced from 15 minutes to 30 seconds
  • Patient satisfaction: Increased from 3.2/5 to 4.6/5
  • Doctor productivity: Increased by 25%

We didn't just build a digital record system. We solved the business problems that made digital records necessary.

Why This Hybrid Role Is Powerful

1. You Build What's Actually Needed

Technical expertise ensures you build it well. Business analysis ensures you build the right thing.

2. You Can Speak Both Languages

You can explain technical constraints to stakeholders. You can explain business needs to developers. You become the bridge.

3. Your Solutions Have Clear ROI

When you understand the business problem, you can measure the value of your solution. Technical solutions become business investments.

4. Stakeholders Trust You More

They trust that you're not just building features—you're solving their problems.

5. Your Career Has More Paths

You're not limited to "technical track" or "business track." You can move between them because you understand both.

The Common Misconception

I hear this often: "If I become a business analyst, I'll lose my technical skills."

Here's the truth: Business analysis doesn't replace technical skills—it applies them.

The best business analysts I know are technical. They understand what's possible, what's difficult, what's efficient. This knowledge helps them ask better questions, identify better solutions, and make better recommendations.

You're not leaving technical behind. You're adding business understanding to it.

The Metaphor: The Bridge Builder

I like to think of this role as building bridges.

  • Technical skills are your foundation. They give you credibility and capability.
  • Business analysis skills are your architecture. They help you design bridges that connect to the right places.
  • The bridge itself is your ability to translate, to understand, to solve real problems.

A bridge without a foundation collapses. A foundation without a bridge just sits there, not connecting anything.

Together, they create something valuable.

The Call to Action

If you're a developer considering this path, or a business analyst wanting to be more technical:

  1. Don't fear losing your technical identity – You're adding, not subtracting.
  2. Start asking "why?" before every "what?" – It's the most important habit you'll develop.
  3. Translate everything – Technical solutions to business value, business problems to technical solutions.
  4. Embrace the bridge role – Your value isn't being the best technical expert or the best business analyst. It's being the best bridge between them.

The Inspiration

After completing the patient record project, the medical director came to me.

"You know what I appreciate most?" he said. "You didn't just build what we asked for. You helped us figure out what we actually needed."

That's the bridge role. It's not about being the best at one thing. It's about understanding both worlds and helping them understand each other.

It's not about being a better developer or a better business analyst. It's about being a better problem solver.


Have you made a similar transition? How did you navigate the change?

#CareerTransition #BusinessAnalyst #SoftwareEngineering #HybridRoles #TechnicalBusinessBridge

The archive

Every article, 2013–2026

Thirty dated articles on application support, delivery, infrastructure and data — plus the recent writing on CI/CD reproducibility and offline-first design.

The recent work is written for a specialist audience, and it is where the measurement discipline is set out in full.

Recent writingOpen Source Impact