Being “Helpful” Can Be Harmful

Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.

Highlights

If your project stalls when you go on leave, you’re not indispensable – you’ve become a single point of failure.

The “Hero BA” trap feels like success, but it quietly weakens organizational accountability and decision-making muscles.
Real seniority in business analysis isn’t about fixing everything – it’s about giving ownership and tough decisions back to the people who hold the risk.

There is a specific silence many experienced Business Analysts recognize instantly. It is the silence that follows your departure.

You step away from a project—perhaps going on well-deserved leave, transitioning into another initiative, or simply stepping out of a key decision loop—and suddenly, the gears of the machine begin to grind. Meetings are postponed. Decisions that were supposedly "final" are revisited. Risks that were once managed escalate into crises. Eventually, a Slack message or an email arrives: “Can we wait until you’re back?”

For years, I viewed that sentence as a badge of honour. I thought it meant I was essential. I thought it meant I was a "Rockstar BA."

I wish someone had told me earlier that it was actually a warning sign.

If your presence is the only thing keeping a project upright, you haven't built a solution; you’ve built a dependency. You aren't enabling the organization—you are compensating for its dysfunction.

The Version of “Helpful” We’re Rewarded For

Most BAs did not become senior by accident. We are the architects of clarity. We are naturally gifted at:

Making sense of ambiguity: Taking the "word soup" of a brainstorming session and turning it into a structured roadmap.
Translating competing views: Finding the middle ground between a CTO who wants scalability and a Product Owner who wants speed.
Keeping momentum: Stepping into the vacuum when others hesitate to lead.

On one particular high-stakes program, I was brought in as a lead analyst because “things kept getting stuck.” It was a classic scenario: stakeholders were frustrated, requirements were a moving target, and the dev team was spinning their wheels.

I did what I was trained to do. I facilitated the workshops. I clarified the priorities. I resolved the contradictions. I documented every decision with surgical precision. Delivery stabilized. Stakeholders were relieved. My performance reviews were glowing.

What I didn’t notice—at least not at first—was how quickly the organization’s "muscle" for decision-making began to weaken. Because I was so "helpful," the stakeholders stopped doing the hard work of alignment themselves:

When priorities conflicted, they didn't debate; they asked me what I thought.
When accountability was unclear, they didn't define it; they looked to me to “help align.”
When political tension surfaced, I didn't let it breathe; I absorbed it and reframed it into something neutral and safe.

I was being helpful. I was also quietly becoming indispensable. As Peter Drucker famously said, “There is nothing so useless as doing efficiently that which should not be done at all.”

I was doing the wrong thing very well.

The Day It Became Obvious: The "Leave" Test

The realization finally hit home when I took planned leave during a critical phase of that same program. I had prepared a handover, updated the Jira boards, and ensured the RAID log was current. I thought the train would keep moving.

Within three days:

Steering meetings were postponed. Without the BA to "summarize the status," the executives felt they didn't have the "full picture" to make calls.
Design decisions were “parked.” The architects and business owners couldn't agree on a data flow, so they decided to wait for my "input."
Risks escalated. A minor integration issue became a blocker because no one felt empowered to sign off on a workaround.

When I returned, I wasn't greeted with a "welcome back"; I was greeted with a pile of work and a request to “get things moving again.”

Nothing fundamental had changed while I was away. The information was still there. The people were still there. The budget was still there. What was missing was me.

That was the moment I realized: A BA who is a single point of failure is not a successful BA. If progress depends on your personal heroics, you have failed to build a sustainable system.

The Psychological Trap: Why We Over-Help

Why do we do this? Why do we fall into the trap of over-functioning for our teams?

1. The Validation Loop

As BAs, we are often "people pleasers" by nature. We want to be the "go-to" person. There is a massive dopamine hit that comes from being the person who "has all the answers." When a stakeholder says, "I don't know what we'd do without you," it feels like success. In reality, it’s a symptom of a systemic illness.

2. The Fear of Conflict

True business analysis often requires surfacing uncomfortable truths. It’s easier to "soften" a requirement or "tweak" a process than it is to tell two Senior Stakeholders that their strategies are fundamentally incompatible. By being "helpful" and smoothing things over, we avoid the immediate discomfort of conflict, but we sow the seeds of long-term project failure.

3. The "Doing" vs. "Enabling" Fallacy

We confuse output with outcome. We think our job is to produce a 50-page BRD. It’s not. Our job is to ensure the organization understands the problem well enough to solve it. If we produce the document but the organization hasn't learned how to own the solution, the document is just paper.

What Is Actually Happening When BAs “Help”

As you progress into senior and consultant-level roles, you realize that delivery challenges are rarely about the "what" (the requirements). They are almost always about the "who" and the "why":

Authority: Who actually has the right to say "yes" or "no"?
Risk: Who carries the weight when the deadline is missed?
Trade-offs: What are the leaders unwilling to sacrifice?

When a BA steps in to “help,” they are often inadvertently acting as a buffer for accountability. We clarify directions that leaders should be clarifying. We resolve tensions that managers should be confronting. We translate political discomfort into neutral, sanitized artifacts. This demonstrates strong stakeholder engagement skills, but it weakens the organizational spine.

As one executive once said to me, unintentionally revealing the depth of the problem: “As long as you’re comfortable with it, I’m comfortable signing it off.”

He wasn't signing off on the requirements; he was signing off on my confidence. He was outsourcing his accountability to me.

The Shift: From Facilitator to Catalyst

With experience, I learned that the true value of a BA is not keeping things smooth. It is making the right things visible—especially if they are jagged.

I started to change my approach. I moved from absorbing ambiguity to reflecting it back to the owners.

The Trade-off Meeting

On a later program, I encountered a similar deadlock. Two executives disagreed on the scope of a digital transformation. In the past, I would have spent a week "finding a compromise" and writing a proposal that hid the disagreement in clever language.

Instead, I took a different route. I documented the two competing options. I outlined the consequences of each. Option A would delay the launch but reduce long-term costs; Option B would meet the deadline but incur significant technical debt.

I presented them and said: “These are the two paths. I cannot recommend one, because this is a strategic choice regarding risk appetite. A decision is required before the team can proceed.”

The meeting was tense. There were long silences. Progress slowed for forty-eight hours. It felt like I was being "unhelpful." But then, a decision was made. Because the trade-offs were laid bare, the executives had to own the choice. And because they owned it, the decision stuck. It didn't get revisited the moment I went on leave.

The Trade-Off No One Warns You About: Being Less "Liked"

This approach is objectively better for the project, but it is harder on the BA.

If you stop being the "fixer," you might be seen as less “helpful” in the short term. Meetings may end without a neat resolution. Tension will become visible. Stakeholders who are used to you "just handling it" might feel frustrated.

But the alternative is the "Hero BA" cycle: projects that appear healthy on the surface while quietly depending on individual heroics. This leads to BA burnout and organizational fragility.

As leadership expert Ronald Heifetz notes, “Leadership is about giving the work back to people.” Business analysis is no different. Our job is to give the work of decision-making and accountability back to the people who own the business.

Practical Steps: How to Step Back

How do you know if you are over-helping? Start by looking at your calendar and your communications.

1. Watch Your Language

If you find yourself saying "I'll take that away and figure it out" more than "Who needs to make this decision?", you are absorbing work that isn't yours. Try shifting to: "I've surfaced the conflict; who is the owner of this choice?"

2. The "What If I Wasn't Here?" Test

Look at your current project tasks. If you disappeared tomorrow, would the project stop, or would it just be slightly less efficient? If it stops, you have work to do in delegating accountability.

3. Stop Sanitizing Conflict

When two departments are at odds, don't write a "neutral" requirement. Document the conflict as a risk. Force the stakeholders to see the friction. Only when the friction becomes uncomfortable will they be motivated to resolve it permanently.

What I Wish I’d Known Earlier

If you are a BA and people are constantly saying:

“Can you just clarify this for us?” (When they really mean: "Tell us what to do so we don't have to choose.")
“What would you recommend?” (When they are trying to avoid the risk of a wrong call.)
“Let’s wait until you’re back.” (When the project is paralyzed by your absence.)

Pause.

You may be doing excellent work, but you are doing it in the wrong place. You are providing a crutch where you should be providing a mirror.

The lesson I learned late, and the one I hope you take to heart today, is this: A BA’s job is not to make things easier in the moment, but to make accountability unavoidable in the long run.

True "help" isn't doing the work for the organization; it's building an organization that can do the work without you.

About the Author

Oupa Laka is a seasoned Business Analysis Consultant and strategist with over 15 years of experience driving clarity and change across complex environments. As a sought-after global speaker, Oupa has shared his insights at the IRM UK Business Analysis Conference, BA & Beyond, Global Africa Business Analysis Conference, and the Business Analysis Summit Southern Africa, where he also served as Track Chair.

He brings a rare blend of technical depth and authentic storytelling to his work, helping teams navigate ambiguity to deliver solutions that matter. With advanced qualifications in project leadership and agile product ownership, Oupa is the founder of AKILI, where he acts as the bridge between people, purpose, and performance. Whether facilitating high-stakes strategy sessions or mentoring the next generation of BAs, Oupa empowers organizations to thrive through a culture of collaboration, innovation, and decisive leadership.