Module 8 • 22 min
Gap Analysis and Prioritization
Rank readiness gaps by impact, effort, dependency, and sequencing rather than trying to fix everything at once.Not Every Gap Deserves the Same Response
Some gaps block a use case completely. Others can be addressed during a bounded pilot, or are improvements that matter only after value is proven. Prioritization makes this distinction visible.
Use dependencies to determine sequence. A governance approval path may be a prerequisite for a system integration, while a dashboard refinement can wait until after launch.
How to Apply This in Your Organization
Use gap analysis and prioritization to make one real implementation decision, not as a theoretical scorecard. Bring together the business owner, the people who perform the work, and the technical or data owners who understand the current constraints.
Start with the next candidate workflow, document the evidence available today, and name the missing condition that must be resolved before the organization commits to a pilot or implementation.
Prioritization Matrix
- Impact: How strongly does the gap affect feasibility, risk, or value?
- Effort: What time, ownership, and investment are required?
- Dependency: What work cannot begin until this gap is addressed?
- Sequence: Is this preparation, pilot work, or optimization?
Worked Decision Scenario
A readiness review identifies five gaps, including an integration approval, inconsistent process ownership, and a dashboard improvement. Treating every gap as equally urgent would delay the first viable use case.
The team resolves the approval and ownership constraints first because they block the pilot, while deferring the dashboard refinement until there is operating data to improve.
Apply it
Top Three Gaps
Rank your three most important readiness gaps. For each, state its impact, owner, and the work it blocks.
Saved locally for this review prototype. Your response will become private account data when the approved course backend is connected.