Insight · September 2026
Why capacity diagnostics come before curriculum design
Most training requests arrive as a course title. "We need IFRS training for the finance team." "We need a leadership programme for directors." "We need Power BI for the analysts." Each request is reasonable — and each, taken at face value, will train the wrong people on the wrong thing.
The question underneath the request is almost always: what is the organisation trying to be able to do that it cannot do today? Until that is named, the curriculum is a guess. And a guess in executive education is expensive — not just in fees, but in the opportunity cost of every week a directorate spends in a classroom not building the capability the institution actually needs.
What a diagnostic actually does
A capacity diagnostic is a structured conversation with the people who will be trained, the people they report to, and the people they serve. It surfaces three things a course title cannot: the actual work the team does (not the job description), the bottlenecks that limit that work today, and the institutional constraints that will determine whether new capability survives the first week back at the desk.
In a recent engagement with a central bank supervisory unit, the brief was "advanced credit risk training for 24 supervisors." The diagnostic found that 19 of the 24 had never opened the bank's own loan-level dataset, and that the unit's reporting cycle depended on a single analyst who manually reconciled three spreadsheets. The "advanced credit risk" course would have trained 24 people on theoretical PD/LGD modelling while the unit's actual bottleneck — a manual reconciliation that consumed 18 person-days per month — went untouched.
The cost of skipping it
A training needs analysis that takes three weeks and surfaces the wrong problem is more expensive than no training at all — because the institution then believes the capability gap is closed, and the real gap continues to compound. We have seen institutions return from "leadership training" with no change in the decision-making rhythm that was the actual complaint, and from "Power BI training" with dashboards no one uses because the underlying data was never governed.
The diagnostic is the cheapest insurance against this. It typically takes two to four weeks, costs a small fraction of the eventual programme, and produces an artefact the institution can use whether or not it proceeds to training: a capability map, a bottleneck analysis, a list of the three to five changes that would shift performance most.
When it is safe to skip
Almost never for cohort training. The exception is open-enrolment training, where individuals self-nominate against a published syllabus — there the curriculum is the product and the diagnostic is the participant's own. But for any engagement where the institution is paying to upskill a team against an institutional outcome, the diagnostic is the engagement.
If you are commissioning training today and have not run a diagnostic, ask your provider one question: how do you know? If the answer is a syllabus, you are about to train the wrong people on the wrong thing. If the answer is a capability map, a bottleneck analysis, and a list of the three changes that would shift performance most — you are in the right conversation.
By SDI Training Faculty · Published 2026-09-12 · Back to insights