Talent Pipeline and Strategy Pace: Strategy Moved in Quarters, Hiring Moved in Years

Behind this page: one organisational change programme, read through four independent leadership retros instead of a scored survey. Five talent-and-capacity dimensions carry no scored question on this assessment: Hiring/Recruitment, Capacity, Training/Onboarding, Knowledge Sharing / Info Silos, and Attrition/Retention. What follows is read entirely from what leadership volunteered, coded independently across four retros that never compared notes and still describe the same three clocks the same way.

Five talent dimensions carry no scored question in this assessment, so nobody rated the talent clock-speed mismatch (Hiring/Recruitment, Capacity, Training/Onboarding, Knowledge Sharing / Info Silos, Attrition/Retention). What is left is qualitative only: 50 from the leaders stream, for a total of 50 meaning units. Everything that follows comes from what people said unprompted, never from a distribution of scores that does not exist here.

Within the talent clock-speed mismatch (Hiring/Recruitment, Capacity, Training/Onboarding, Knowledge Sharing / Info Silos, Attrition/Retention), no unit puts the name of another measured dimension into its own words. No cross-topic pairing is asserted here. A qual-only dimension carries no shared per-unit key linking the leadership and team-survey streams, so a co-mention count cannot be computed, and this page does not invent one.

The leaders described three clocks running at three different speeds. Strategy resets every quarter. Delivery runs in sprints. Hiring runs in years:

“Strategy is moving faster than the hiring.”

They named the mechanism in specific months, not a general complaint:

“The approval process before you can begin to recruit. We start requesting people in Sept and in May is when I can start! No idea why this takes so long.”

“(approval process that precedes) & recruitment process itself. Roles take 8 (September to May) months to approve, hiring happens in August/September (entire process takes about 12 months) – general problem across [the client].”

“It takes 8-10 months to hire & onboard someone.”

Twelve to twenty months from opening a role to a productive hire, against a strategy cycle measured in quarters: the slowest clock governs every commitment made against it.

“Cannot grow, means cannot scale, means struggling to deliver.”

Onboarding adds its own tail once a role is finally filled:

“The onboarding process is currently too slow. If we hire 3-4 new employees, we lack the capacity to effectively train and onboard them, especially considering that the current process takes 8 months. To support our ongoing growth, we need to streamline this process and reduce the onboarding timeline to 3 months.”

“Onboarding people quicker (3 months to onboard new ppl).”

Knowledge silos raise the price of every one of those months, because tenure, not documentation, is where the expertise actually lives:

“There are significant knowledge silos within the team, limiting the ability to easily share expertise across members.”

“If we lose these few subject matter experts, it’s a risk because of the knowledge they hold.”

Underneath all of it sits a flat capacity floor, described the same way across independent retros: not a shortage of one skill, a shortage of people to point at anything. It is the same capacity-ownership gap the technical-debt case study found deadlocking debt work, here deadlocking the org itself, one open role at a time:

“There’s never enough capacity. There’s a real resource crunch.”

“The team currently has only the capacity to provide service in a maintenance mode.”

The stopgap is people borrowed from elsewhere:

“We don’t have software engineers that go on the ground, we borrow from the maintenance team. And they give us a list of items that need to be fixed/addressed.”

Against all of that, one number holds the whole thing together: a positive, coded twice, in two different sailboat categories, both at the top of the scale.

“Zero attrition.”

“North star everyone appreciates: this year we committed to giving everyone 15% of their time for training and personal development.”

Retention is not a footnote here. With a twelve-to-twenty-month pipeline to replace anyone, zero attrition is the load-bearing wall: it is currently substituting for the hiring pipeline the leaders describe as broken. Nothing in this dimension is scored; the evidence is that four people running four separate retros, comparing notes to no one, described the same three clocks the same way.

Qualitative-only evidence: None of these five dimensions carry a quantitative score in this assessment, which is why this page has no scored distribution. Every count and chart on this page is drawn from the leaders stream alone, entity-extracted into meaning units and verified against the source workbook each time it renders. A real engagement; an unnamed client, and it stays that way. Team names and identifying details are removed, and quotes are lightly edited for anonymity. Every quoted phrase is provenance-anchored to its workbook row. One organisation, read once, from what people actually volunteered.