This is the last piece in a series that started with how to push back on stakeholders and moved through artifacts, discovery, and the written rhythm. It ends with the question underneath all of it: why do two BAs who start with the same skills end up, five years later, in completely different places.

I have watched this happen enough times to be sure it is not talent and not luck. The BA who compounds and the BA who plateaus are usually indistinguishable in year one. By year five the gap is enormous and nearly impossible to close. Something happened in between, repeatedly, that almost nobody can see while it is happening.

This piece is about what that something is.

The two BAs in year one

Picture two analysts hired the same month. Same training, same competence, same eagerness. Both write clean acceptance criteria. Both run reasonable stakeholder meetings. Both pass their probation comfortably.

In year one they are interchangeable. If anything, the one who plateaus often looks better early, because plateauing BAs are frequently the ones who optimise for visible output: more tickets closed, more documents produced, more meetings attended. The compounding BA can look slower, because they are spending time on things that do not show up in any metric.

That invisible time is the whole story.

What the compounding BA does with the invisible time

The compounding BA spends a portion of every week doing things that produce no immediate output:

They write down predictions and check them later. Not because anyone asked, but because they are building a private record of how often their judgement is right and in what specific ways it is wrong.

They sit with a requirement they have already shipped and ask what they would do differently. Not to revise it, since it is shipped, but to extract the lesson while it is fresh.

They notice when a stakeholder conversation went badly and trace back to the exact moment it turned, instead of blaming the stakeholder and moving on.

They keep a running file of patterns they have seen across projects, and they revise it when a new project contradicts an old pattern.

None of this shows up in a performance review. All of it compounds.

Why it compounds

The mechanism is calibration. Every prediction written and checked, every shipped requirement reviewed, every bad conversation traced back, adds one data point to the BA's internal model of how the work actually behaves. Over a year that is fifty data points. Over five years it is two hundred and fifty.

Calibration is the thing that cannot be taught in a course and cannot be faked in a meeting. It is the difference between a BA who says "I think this will be a problem" as a guess and a BA who says "I think this will be a problem, and here is the specific way it will go wrong, and here is roughly when we will know." The second BA is right often enough that senior people start to route decisions through them. That routing is what advancement actually is.

The plateauing BA never builds the calibration, because they spent the invisible time on visible output. They have five years of experience in the sense that they did the job for five years. They do not have five years of calibration, because they never ran the loop that produces it. They have, in a real sense, the same year of experience five times.

The compounding is invisible until it isn't

Here is the cruel part. For the first two or three years, the two BAs look similar to everyone including themselves. The compounding BA often feels like they are falling behind, because the plateauing BA has more visible output and gets praised for it. The compounding investments feel like a tax with no return.

Then, somewhere around year three or four, the curves separate visibly. The compounding BA starts being right about things before anyone else. Their one-pagers start landing because they have learned, through two hundred reps, exactly how to frame a concern so a senior person hears it. Their discovery conversations surface things others miss because they have traced enough bad conversations to know where the bodies are buried. Senior people start asking for them by name.

The plateauing BA, at the same moment, starts to feel stuck without understanding why. They are doing everything they did in year one, which worked in year one, and it is no longer producing advancement. They often conclude the problem is politics, or their manager, or the company, and they leave for a similar role elsewhere, where the same pattern repeats.

Why almost nobody does the compounding work

If the compounding work is this powerful and this simple, the obvious question is why almost nobody does it.

Three reasons, each real.

The first is that the feedback loop is too long. The compounding investments pay off in years three through five. Human motivation is calibrated for feedback in days or weeks. Doing something every week for three years before it visibly pays off requires a kind of faith that most people cannot sustain without evidence, and the evidence does not arrive until after the faith was required.

The second is that the work is invisible and therefore unrewarded. Organisations pay for visible output. A BA who spends three hours a week on private calibration that produces no ticket, no document, no deliverable, is spending three hours a week that the organisation does not value and cannot see. The incentive gradient points away from the compounding work at every step.

The third is that it is uncomfortable. Checking your old predictions means confronting how often you were wrong. Tracing a bad conversation back means owning your part in it. Reviewing a shipped requirement means seeing what you missed. The compounding work is, fundamentally, a practice of looking directly at your own errors, repeatedly, on purpose. Most people will do almost anything to avoid that.

What this means if you are early

If you are a BA in your first year or two, the entire content of this series reduces to one instruction: spend some of the invisible time on calibration, every week, even though it will feel pointless for a long time.

The specific practices are in the earlier pieces. Write predictions and check them. Keep the weekly artifact. Trace bad conversations. Review shipped work. Build the one-pagers and watch how they land. None of it is complicated. All of it is uncomfortable and slow to pay off, which is exactly why it remains rare, which is exactly why it remains valuable.

The BAs who do this do not have more talent than the ones who do not. They have a higher tolerance for delayed, invisible, uncomfortable work. That tolerance is the entire moat.

What this means if you are not early

If you are five or ten years in and you recognise yourself in the plateauing BA, the news is better than it feels. The compounding work produces results from the day you start it, regardless of how many years you spent not doing it. The calibration loop does not care that you are starting late. It only cares that you run it.

The version of you three years from now will have three years of calibration data that the current version does not. That is true whether you are in year two or year twelve. The only question the compounding work asks is whether you will start running the loop now, knowing the payoff is years out and invisible until it arrives.

That is the whole craft. Not the frameworks, not the templates, not the questions. Those are tools. The craft is the willingness to do the slow, invisible, uncomfortable work of looking at your own judgement, over and over, for years, until being right becomes a thing people can rely on.

Start this week. Check back in three years.