Module 6 • 22 min
Organizational, Data, and Technical Readiness
Identify the readiness conditions that could block a viable opportunity.Core Concept
A sound opportunity can still fail if the organization lacks stable workflows, usable data, clear ownership, integration access, or governance capacity.
This choice influences the value case, implementation effort, governance requirements, and the organization’s ability to operate the system after launch.
How to Apply the Framework
Readiness findings should shape the scope and sequence of the roadmap, not appear as a late implementation surprise.
Use a current workflow, its measurable baseline, and the real people and systems involved. A strategy that works only in a simplified example is not yet a decision-ready operating plan.
Decision Checklist
- State the business outcome and the bounded workflow this decision will improve.
- Identify the accountable business owner, technical owner, and required human reviewer.
- Confirm the evidence, dependencies, controls, and decision gate required before moving forward.
Worked Decision Scenario
A promising service use case depends on customer status from three systems, but one system has no approved integration route. The opportunity is viable, but its timeline and first scope must reflect that dependency.
The roadmap assigns an owner to resolve the access path and designs a limited pilot using the systems already available. Readiness becomes a sequencing decision rather than a late surprise.
Apply it
Working Exercise
List the top readiness constraint for your opportunity.
Saved locally for this review prototype. Your response will become private account data when the approved course backend is connected.