In the high-pressure theatre of organisational redesign, one question consistently surfaces: “Where should the Business Analysis (BA) capability sit?”
For many, this feels like an administrative checkbox. But for Business Architects and BA leaders, this decision is foundational. It dictates whether your BAs are viewed as “order takers” documenting technical requirements or “value shapers” steering the enterprise toward its strategic north star.
Historically, BAs were the “IT translators,” tucked away in technology departments. But as we move through 2026, the boundary between “the business” and “the technology” has evaporated. If your BA function is still reporting through a legacy lens, you aren’t just misaligned, you’re actively leaving strategic value on the table.
1. The First Principle: BA as a Change Capability
To determine placement, we must first define the essence of the craft. According to the IIBA’s BABOK® Guide, business analysis is the practice of enabling change by defining needs and recommending solutions that deliver value to stakeholders.
If we accept this definition, then Business Analysis is fundamentally a value-realisation discipline. It is the bridge between strategy, operations, and technology. Therefore, placing it solely within a sub-function (like IT) risks narrowing its lens to “project support” rather than “enterprise transformation.”
2. Analysing the Structural Archetypes
There is no “universally correct” answer, but there are strategically sound trade-offs.
A. The Delivery Engine (Reporting to CIO/CTO)
Historically the most common, this model aligns BAs with the engineering cadence.
- The Win: Tight integration with Architecture and the SDLC.
- The Risk: As noted by Modern Analyst, this often creates a “requirements for IT” bias. BAs are brought in after the business problem has been defined, limiting their ability to influence the “Why” of the investment.
B. The Strategic Navigator (Reporting to Strategy/ Transformation/ COO)
This model positions BA as a peer to Enterprise Architecture.
- The Win: Stronger influence in portfolio shaping and capability-based planning.
- The Insight: Aligning here supports BABOK’s Governance framing, emphasising decision rights and investment assurance before a single dollar is spent on delivery.
C. The Embedded Specialist (Reporting to Product/Customer Domains)
In product-led organisations, BAs sit directly within Value Streams.
- The Win: Incredible domain intimacy and faster discovery cycles.
- The Risk: Radical fragmentation. Without a central “home,” standards diverge, and the enterprise loses its ability to see cross-functional dependencies.
3. The 2026 Design Pattern: The Federated CoE
Current research and practitioner guidance (from Modern Analyst and PMI) increasingly point toward a Hybrid/Federated Model as the gold standard for mature organisations.
The Architecture of the Federated CoE:
- Centralised Reporting: A “solid line” to a BA Center of Excellence (ideally within Strategy or the COO’s office). This ensures consistent standards, career paths, and quality assurance.
- Decentralised Delivery: A “dotted line” to specific business domains or product teams. This ensures the BAs remain close to the customer and the technical reality.
| Feature | Centralised CoE | Distributed / Embedded | Federated (Hybrid) |
| Governance | High/ Standardised | Low / Fragmented | Balanced / Scalable |
| Domain Expertise | Generalist | High | Targeted |
| Flexibility | Rigid Resource Pooling | Rigid Silos | Dynamic Allocation |
4. Strategic Considerations for Leaders
When redesigning your operating model, ask these three “Provocation Questions”:
- Where is the money? If investment decisions are made in Strategy but your BAs live in IT, you are missing the chance to shape the business case.
- Who owns the “Change Governance”? If BA sits under Finance, expect a focus on cost-cutting. If it sits under Strategy, expect a focus on value-shaping.
- Are we aligned with Architecture? If BAs report to the CIO but Business Architects report to the Strategy Office, you have built a structural silo that guarantees friction.
Conclusion: Structure is a Signal
Where you place the Business Analysis function tells the rest of the organisation what that function is for.
- Under IT? They are a delivery support tool.
- Under Finance? They are an investment controller.
- Under Strategy? They are an architect of the future.
For organisations undergoing enterprise transformation, the optimal positioning is a BA Center of Excellence reporting into Strategy/Transformation, partnered deeply with Enterprise Architecture, and deployed into value streams. This elevates Business Analysis from a documentation task to a strategic change discipline.
🔗 Read more insights at analyst-ally.com
🔗 Join the conversation by following our LinkedIn or YouTube Channels
Sources & Deep Dives
- IIBA: The Importance of Org Structure when Delivering Projects
- IIBA:Global Business Analysis Standards, Regulations and Best Practices
- IIBA: Understanding the impactful role of Business Analysis in an Organization
- Modern Analyst: The Role of the BA Center of Excellence
- Medium: Where Should Business Analysts fall in your Organizational Chart
- PMI: Centres of Excellence
- MoldStud: The influence of organisational structure on business analysis process
