Diagnostic
Capability DiagnosticThe diagnostic that comes before any program
The Capability Diagnostic shows where behavior is getting stuck in your organization, before you invest in a program. Over two to four weeks we measure the 12 capabilities through scenarios, a questionnaire and interviews, and give you a map, three findings and a recommendation.
- Duration
- 2–4 weeks
- For
- a team, a department or the whole organization
- Sources
- scenarios, questionnaire, interviews
- Outcome
- a capability map and a recommendation
Who it’s for
When does a Capability Diagnostic make sense?
The question usually sounds like this: “we know something isn’t working, but we don’t know where to invest.” Day to day, it shows up like this:
- You have run training on the same topic before, and the problem came back.
- Every director has a different explanation for the same execution problem.
- Several teams are asking for training, and it isn’t clear which requests really matter.
- A reorganization, a growth phase or a new leader is coming, and you want a measured starting point.
- You need to justify the development budget to leadership with data, not impressions.
- It isn’t clear whether the problem lies with people or with how the work is organized.
Already know the problem is how managers lead? Manager Operating System →
Is the problem inside one team? Team Performance Architecture →
The journey
How does the diagnostic work?
The diagnostic measures the behaviors that produce the problem, not opinions about it. We combine four sources: written scenarios, where people show what they would actually do; a questionnaire; interviews; and, in larger organizations, manager observation and working documents. When the sources disagree, what people do outweighs what they report, and the gap is often the most valuable finding.
01
Scoping
A conversation with the sponsor: what you want to understand, which population we measure, and which domains are showing signals. We also agree the size of the diagnostic and the calendar.
02
Collection
The sponsor announces the questionnaire inside the organization, then the questionnaire and the scenarios go out from our app, straight to each person. People know why they’re being asked, and reminders go only to those who haven’t answered yet. In parallel we hold the interviews, asking for concrete examples from recent weeks.
03
Analysis
We score the scenarios against rubrics, code the interviews and combine them with the questionnaire into a map of the 12 capabilities, with the critical areas marked. We separate explicitly what is about behavior from what is about how the work is organized.
04
Debrief
We present the three findings that matter, not all 12 capabilities at equal weight, plus the recommendation: where to start, why there, and what success looks like in 90 days. In larger organizations, a two-hour roadmap workshop with the leadership team follows.
Length: about two weeks for one team, three for a department, and four for a whole organization, including interviews with executives and the roadmap workshop.
Deliverables
What do you get at the end?
The diagnostic stays yours, whatever you decide next. Each deliverable stands on its own.
- The capability map
- the 12 capabilities by team, with critical, working and solid areas marked.
- The three findings that matter
- each with its score, an example from the scenarios and an anonymized voice from the interviews.
- What to train and what to redesign
- behavioral problems, separated from structural ones (unclear roles, double reporting lines) that training will not fix.
- The recommendation
- where to start, why there, what comes next, and what success looks like in 90 days, in observable behavior.
- The debrief with the sponsor
- a 45–60 minute conversation with the decision on the table; in larger organizations, also the roadmap workshop with the leadership team.
How it runs
The same spine, adapted to the program.
The program spine: from diagnostic to review
Measurement
What do we measure, and how?
- Applied scenarios
- real situations, answered in writing: how you would align a team hit by four urgent requests at once, how you would brief a delegation that tends to come back different. They show what people do, not what they believe about themselves, and they carry the most weight.
- The questionnaire
- recurring behaviors over the last four to six weeks, across all 12 capabilities, completed in a few minutes.
- Interviews
- with the sponsor, managers and, in larger organizations, executives: the context, concrete examples, and what success would look like.
- Observation and documents
- in larger organizations: how meetings close, what written delegations look like, what happened to the last lessons learned.
Individual answers are confidential. We report only in aggregate, and teams with fewer than four respondents never appear separately. When the response rate is low, we say plainly how far the map can be relied on.
Frequently asked questions
Two to four weeks, depending on size: about two for a team or a group of up to 30 people, three for a department, and four for a whole organization, including interviews with executives and a roadmap workshop.
Not much. The questionnaire takes a few minutes. The written scenarios take 10–15 minutes each, and only an agreed sample answers them. Interviews last 35–60 minutes and involve a few key people, not everyone.
The capability test (the Capability Snapshot) is a five-minute self-assessment by one person: a first impression. A first conversation with us, 30–45 minutes, clarifies the problem. The Capability Diagnostic measures the organization from four sources and ends with a recommendation you can base a budget on.
No. The map, the findings and the recommendation are yours whatever you decide. Working on it internally is a legitimate choice: we leave the recommendation with you and, if you want, check in after 60 days.
Individual answers are confidential. We report in aggregate by team, and teams with fewer than four respondents never appear separately. Interview quotes are anonymized. We may use AI to summarize anonymized open answers, but the interpretation and the recommendation stay with the consultant.
We say so. Some problems come from how the work is organized: roles that are unclear by design, double reporting lines, incentives that pull against each other. We separate them explicitly from behavioral problems and treat them as a separate recommendation, because training people on a design problem burns both the budget and the trust.
Yes. The questionnaire and the scenarios are online, interviews can be held remotely, and the diagnostic can run in Romanian or English.
Pricing depends on size: how many people answer, how many interviews we hold, and whether we include observation, document analysis and the roadmap workshop. We give you a concrete price after the first conversation.
Further reading
- Training needs analysis: how to tell whether training is the right instrument
A training needs analysis is not a survey of what people want to learn. What Arthur and colleagues found, and the need chain, link by link.
- Training doesn't fail because of bad content. It fails because of architecture.
Training rarely fails because people aren't motivated or the content is weak. It fails because there is no transfer layer. Here's the research and the fix.
- 10 factors that raise team effectiveness (and how to find your constraint)
Most lists mix symptoms with causes. Here are the factors that genuinely move team effectiveness, and how to identify the one blocking your team now.
Start with a conversation
Tell us the behavior you need to change. We’ll show you the system that changes it.
A 30–45 minute diagnostic conversation, no pitch deck. You’ll leave with a sharper read on the capability gap, whether or not you work with us.