The Golden Halo Effect: When Expertise Is Mistaken for Perspective
Key takeaways
- Deep expertise doesn't automatically translate into enterprise-wide perspective. Organizations often assume that a domain expert also understands the dependencies, integrations, and downstream impacts affecting other teams, but depth and breadth are fundamentally different capabilities.
- The Golden Halo Effect creates transformation risk that competent teams don't see coming. When organizations rely on subject matter experts for perspectives that require connector-level analysis, gaps emerge at integration points even when every individual contributor is doing their job well.
- Subject matter experts and business analysis professionals are complementary, not interchangeable. SMEs anchor initiatives in operational reality; business analysis professionals connect that reality across the wider enterprise—one sees the trees, the other sees the forest.
- Integration testing is often where the Golden Halo Effect surfaces. Functionality that works cleanly within individual workstreams frequently fails when workstreams come together, revealing dependencies that no single SME could have anticipated.
- Business analysis contributes most at the connection points. Uncovering assumptions, exposing dependencies, aligning stakeholders, and maintaining traceability across workstreams is where complex transformations succeed or fail, and it's the business analysis professional's home ground.
Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.
The subject matter expert versus business analysis professional conversation isn’t a new one. Yet I’ve always felt that we’re often debating the wrong issue. The real challenge isn’t whether one role is more valuable than the other, but whether organizations understand the fundamentally different perspectives they bring.
That’s where the Golden Halo Effect begins.
We love experts (and we should)
Subject matter experts (or SMEs) are essential to successful transformation delivery. They provide operational knowledge, historical context, business rules, regulatory insights, and experience that help organizations understand what needs to change and why.
Without SMEs, requirements lack depth, designs lack context, and solutions risk solving the wrong problem. The challenge emerges when organizations allow expertise to become a substitute for delivery disciplines and competencies that require breadth.
The Golden Halo Effect
The Golden Halo Effect occurs when organizations assume that deep expertise in one area automatically translates into understanding across multiple areas. Because someone knows their domain exceptionally well, it’s often assumed they also understand dependencies, integration points, upstream and downstream impacts, and how decisions affect other teams.
In reality, depth and breadth are different things. A finance SME is expected to understand finance deeply. A reporting SME is expected to understand reporting deeply. That depth is their value. The problem arises, however, when organizations expect that depth to automatically provide enterprise-wide perspective.
Why transformation makes this problem worse
Large transformation initiatives rarely involve a single process, team, or technology platform. They operate across multiple business units, stakeholder groups, technologies, governance structures, and streams of work.
Everything becomes interconnected. A seemingly simple decision within one area can affect processes, reports, interfaces, training materials, data models, security roles, and downstream operational activities in many others. When nobody owns the complete picture, gaps begin to emerge even when highly competent people are involved.
Seeing the trees and seeing the forest
One of the simplest ways to explain this distinction is through a familiar analogy: subject matter experts often see the trees, while business analysis professionals see the forest.
Both roles are equally capable and important. The distinction is one of perspective and role. SMEs naturally focus on business rules, operational exceptions, policies, regulatory requirements, and historical context within their domain. Their perspective is deep.
Business analysis professionals focus on dependencies, stakeholder alignment, assumptions, interfaces, decision impacts, and connections across workstreams. Their perspective is broad. The SME helps the team understand a domain, while the business analysis professional helps the team understand how domains connect.
The cost of getting it wrong
During one transformation initiative, functionality had already been built and successfully unit tested when issues surfaced during integrated testing. What appeared clear within individual workstreams didn’t hold together once those workstreams were brought together.
As a result, functionality had to be reopened, requirements revisited, design decisions reconsidered, and additional testing conducted. Delivery slowed, costs increased, confidence declined, and go-live timelines were affected.
The lesson was that deep expertise didn’t automatically translate into understanding the wider web of dependencies surrounding the solution.
Why business analysis matters
This experience reinforced something I had been struggling to articulate for years in the SME/business analyst conversation. It was a genuine eureka moment and helped me understand why I had always been somewhat hesitant with the phrase "Domain BA."
Far from replacing expertise, structured business analysis connects it. SMEs are anchors who keep initiatives grounded in operational reality, while business analysis professionals are connectors who ensure that reality is understood, aligned, and connected across the wider enterprise.
Business analysis helps organizations uncover assumptions, expose dependencies, clarify decisions, align stakeholders, translate perspectives, and maintain consistency as delivery unfolds. These activities are often the difference between success within a domain and success across the enterprise.
Expertise and analysis are better together
One of the risks in conversations like this is creating a false choice. There’s no competition between the SME and the business analysis professional.
Organizations shouldn’t choose one because they need both.
SMEs bring expertise, while business analysis professionals provide integration. Architects provide design direction. Project managers provide execution discipline.
Each discipline contributes something different, and each fills a different gap. The value lies precisely in complementarity. When that balance exists, organizations can make better decisions, identify risks earlier, and sustain alignment throughout delivery.
Conclusion
The Golden Halo Effect is ultimately about assumptions. More specifically, it’s about the assumption that expertise automatically includes perspective. In my experience, that assumption has contributed to more delivery challenges than many organizations realize. Transformation succeeds when expertise and analysis work together. One provides depth, and the other provides connection. One helps us understand the trees, while the other helps us understand the forest.
Organizations should continue to value deep expertise while recognizing that expertise alone isn’t enough. Complex transformations require both anchors and connectors. By understanding and respecting the distinct contribution of each role, organizations can improve alignment, surface dependencies earlier, make better decisions, and increase the likelihood of successful transformation outcomes.
Explore what's new
Looking for more practical business analysis tools and templates? Check out IIBA's KnowledgeHub—the community-built library of templates, techniques, and applied resources for the situations you face in your day-to-day work.
Explore it today
About the Author
Olabisi (Bisi) Adesina is a senior project and transformation delivery consultant with more than 12 years of experience leading enterprise-wide modernization initiatives across government and complex organizational environments. With a background spanning business analysis, solution architecture, project management, and transformation delivery, she specializes in aligning business and technology outcomes, managing complex stakeholder environments, and sustaining delivery alignment throughout large-scale change initiatives. Bisi is also a business analysis instructor and published contributor to the International Institute of Business Analysis.
