This whitepaper is for BA managers, CoE leads, and organizational leaders who are responsible for building a business analysis capability and want it to still be there when they are gone. It draws on the frameworks I built at Manulife, Equitable Life, and Canada Life, all three of which are still operating years after I moved on.
Most of what is written about BA practice design is written by consultants who have observed practices from the outside. This is written by someone who built three of them from scratch and watched what happened over time.
A BA practice that dissolves does not usually fail visibly. It does not have a specific moment of collapse. It drifts. The intake process stops being used. The templates become optional. The community mechanism quietly stops meeting. New BAs arrive without structured onboarding. Senior BAs leave and take the institutional knowledge with them. Within two to three years of the founding leader's departure, what remains is a group of individuals who happen to share a job title.
The root cause is almost always the same: the practice was built around a person rather than a structure. The founding BA manager held it together through their own energy, relationships, and judgment. When that person left, the practice did not have enough structure to hold itself.
The practices that survive are the ones that were deliberately made independent of the person who built them. That independence has to be designed in. It does not happen by accident.
A BA practice that lasts needs to operate at three distinct layers simultaneously. Most practices operate at only one or two.
Layer 1: Delivery. The visible work. Requirements documentation, stakeholder facilitation, UAT coordination, change management support. This is what most organizations think of when they think of BA. It is also the layer that gets the most management attention, the most resources, and the most credit. It is necessary but not sufficient.
Layer 2: Governance. The standards, tools, and processes that define how delivery work gets done consistently across the team. The intake model. The elicitation approach. The documentation templates. The quality review process. This layer is what makes the delivery layer consistent and scalable. Most practices invest in it initially but let it drift over time as delivery pressure increases.
Layer 3: Capability. The mechanisms for learning, growth, and knowledge transfer within the team. Peer learning sessions. Structured onboarding for new BAs. Communities of practice. Mentorship structures. This layer is what makes the practice self-renewing rather than dependent on external talent acquisition.
A practice that operates only at the delivery layer is a staffing function. It produces BA output but does not produce a BA capability. When the team turns over, the capability goes with them.
A practice that operates at delivery and governance layers is more durable. The standards persist even when people change. But it is still dependent on external talent acquisition for capability renewal.
A practice that operates at all three layers builds its own capability over time. New BAs become experienced BAs through structured development within the practice, not through years of accidental learning. That self-renewal is what makes the practice genuinely independent of any specific person.
The governance layer is the one most likely to erode under delivery pressure. The mechanisms for keeping it alive require deliberate design.
The standards body. A formal or semi-formal group responsible for maintaining the practice's standards. It reviews tools, approves template changes, evaluates new methodologies, and decides what gets added to or removed from the standard approach. It needs a defined membership, a regular meeting cadence, and a defined process for how decisions get made. It does not need to meet weekly. It needs to meet often enough that standards do not drift between meetings.
The intake model with teeth. An intake process that is actually tied to delivery gates, not just documented as a best practice. The intake model needs to be embedded in the project lifecycle at a point where skipping it has a visible cost. At Equitable Life, we tied the BA intake session to the project kickoff gate. No BA intake session, no project kickoff. That single structural choice made the intake model durable across six years and multiple organizational changes.
Quality review with a defined standard. A peer review process for BA deliverables that is tied to an explicit quality standard, not to the reviewer's personal preferences. The standard needs to be documented, communicated, and applied consistently. The review process needs to be fast enough that it does not become a bottleneck and rigorous enough that it actually improves quality.
The governance layer erodes when delivery pressure increases and no one is accountable for maintaining it. The solution is to make governance accountability explicit and separate from delivery accountability. One person's job is to protect the practice. It cannot be a side responsibility of the person most buried in delivery.
The capability layer is the most neglected and the most important for long-term survival. It is what determines whether the practice can grow its own talent or is permanently dependent on hiring.
Structured onboarding. Every new BA who joins the practice should have a defined onboarding path that covers the practice's standards, tools, approach, and culture. Not a week of reading documentation. A structured, supervised first engagement where the new BA works alongside a more experienced practitioner and is explicitly coached on how the practice operates. At Equitable Life, this was a twelve-week structured onboarding that included paired delivery, tool walkthroughs, and a practice orientation with the BA manager. It produced BAs who were ready to work independently in a fraction of the time that unstructured onboarding produced.
Peer learning mechanisms. A regular cadence of knowledge sharing within the team. Not training. Not methodology updates. Practitioners showing other practitioners how they approached a problem. The format matters less than the regularity. Monthly is enough. Quarterly is not enough. The sessions should be informal and practitioner-led. Formal presentations kill the conversation that makes these sessions useful.
Mentorship with structure. Senior BAs mentoring junior BAs is only valuable if the mentorship has some structure. Left entirely informal, mentorship tends to happen only when the senior BA has time, which means it does not happen consistently. A light structure: defined matching, a suggested conversation cadence, and a set of topics that mentors and mentees are expected to cover over the course of the relationship, is enough to make mentorship consistent without making it bureaucratic.
The clearest indicator of whether a BA practice has been built to last is what happens when the BA manager leaves. Not immediately after, but six months later. Is the intake model still being followed? Are the peer learning sessions still happening? Is the quality review process still being applied? Are new BAs still receiving structured onboarding?
If the answer to those questions is yes, the practice was built at the governance and capability layers, not just the delivery layer. If the answer is no, the practice was built around the leader, and the leader's departure revealed the structural gap.
The preparation for leadership transition should start on the day the BA manager accepts the role, not the day they announce they are leaving. The structures that make leadership transition possible are the same structures that make the practice durable. Building them early is not planning for departure. It is building something worth staying for.
The hardest part of building a durable BA practice is not the design. It is getting organizational permission to invest in the governance and capability layers when the delivery layer always feels more urgent.
The argument that works is not the capability argument. Executives who are not BA professionals do not find the capability argument compelling. The argument that works is the risk argument. A BA practice that is dependent on a small number of individuals is a business risk. When those individuals leave, the delivery capacity drops and the institutional knowledge walks out the door. The governance and capability investment is risk mitigation, not overhead.
Framing it as risk mitigation changes the conversation from "can we afford to invest in this" to "can we afford not to." That is the conversation where executive support becomes available.
The BA practices I built that are still running share one characteristic: they were built to run without me. That was not modesty. It was the design goal. A practice that requires its founder to function is a fragile practice. A practice that functions independently of its founder is a genuine organizational capability. That is the difference worth building toward.