Workforce analytics

Skills gap analysis

Scenario evidence reveals where judgment and execution break down in real situations. Analyze gaps by role and location, identify common failure patterns, and target development where it matters most.

Skills gap analysis
Problem
Skills data is often self-reported or outdated. Leaders can’t see which gaps are real, role-specific, or risk-relevant.
Outcome
Clear, role-based gap maps and measurable priorities for development and coaching investment.
Worked example

What it looks like at Nano Masters AI Telecommunication Services

Role: Network operations center (NOC) incident engineers across three regional operations centers
Format: 12-minute incident scenario run as a common benchmark, delivered by link, with results segmented by center and tenure
Fictional blueprint company, used for illustration.

The situation

The company has expanded AI operations so NOC engineers now receive automated triage and mitigation playbooks during incidents. Leadership wants to know whether engineers in every center use those playbooks with the right guardrails, or whether habits differ by location and experience. Self-assessments suggest everyone is comfortable with the new tools.

The decision

An alarm surge points to congestion and intermittent packet loss across several sites, and the system proposes an automated traffic re-routing playbook. The engineer must choose how much to automate and when to escalate.

Option A
Apply automated mitigation to the worst-affected sites with rollback ready, run a parallel root-cause check, and alert customer care so agents can answer incoming calls.
Impact is contained quickly with a safe exit if the change misbehaves, and the care team is not caught off guard. This combines trust in automation with control over it.
Option B
Pause automation and escalate to senior engineers for manual diagnosis.
The change is safe, but resolution waits on senior capacity and complaints keep rising. It suggests low confidence in the new tools rather than poor judgment.
Option C
Run the full playbook across all flagged regions at once to clear the alarms fast.
Alarms clear in some areas, but a policy change applied without a rollback check spreads to sites that were stable. This is the over-automation risk the program is meant to catch.

What the scorecard shows

Here the value is in the cohort report rather than any single scorecard. Segmenting by center and tenure might show, for example, that one center tends to escalate everything while another skips rollback checks, two different gaps that need two different interventions. Each gap cluster links to a specific follow-up such as a short re-simulation on guardrails or a coaching session on automation confidence.

What we measure

Automation judgment
Whether the engineer matches the scope of automated mitigation to the scope of the problem.
Guardrail checks
Whether rollback paths and monitoring are confirmed before an automated change is triggered.
Escalation calibration
Whether senior engineers and vendors are brought in when the situation requires it, not by default and not too late.
Root-cause reasoning
How the engineer uses correlated network and customer signals to narrow down the likely cause.
Cross-team communication
Whether customer care and other affected teams are told what is happening early enough to act.

FAQ

Common questions

Scenario performance mapped to competencies and rubrics—segmented by team, site, seniority, or role.

Yes—dashboards and exports can highlight patterns and outliers across groups.

Use gap clusters to assign targeted microlearning, coaching, or re-simulation on weak competencies.

Yes—map rubrics to your competency model (or start with a lean model and evolve).
Want this use case tailored to your roles?
We generate scenarios, decision points, and scorecards in days.