liveBook · Manning

Gap analysis

Gap analysis is the systematic comparison of a current state with a desired state to identify deficiencies or missing capabilities requiring remediation.

How 2 Manning books explain it

Think Like a Software Engineering Manager

Gap analysis is a technique for identifying differences between a person’s current capabilities and a target role’s requirements.

How it is used
Uses gap analysis to guide career growth, support the IC-to-EM transition, and prepare people for delegated work.
How deep it goes
Shows a competency matrix with SBI evidence and progress statuses, then connects identified gaps to goals and support.
Examples
Illustrates the technique with a competency matrix and an engineer mentored after missing a project milestone.
What you can do after
Practice/perform it by documenting competency evidence, identifying gaps, and agreeing on goals or resources to address them.

Read how Think Like a Software Engineering Manager explains gap analysis →

Data-Driven Cybersecurity

Gap analysis is the systematic comparison of a current state with a desired state to identify deficiencies that require remediation.

How it is used
Validates cybersecurity due diligence and due care by monitoring whether identified control gaps are being closed.
How deep it goes
Defines risk-control comparison and extends it to quarterly closure tracking, but stops short of proving mitigation through coverage alone.
Examples
Uses a TechGuardian dashboard showing coverage rising from 60% to 85% and performance problems falling from 20 to 10 quarterly.
What you can do after
Diagnose control deficiencies by tracking gap coverage alongside vulnerability resolution and closure.

Read how Data-Driven Cybersecurity explains gap analysis →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.