1. Outcome definition

Outcomes linked to strategic KPIs, with baseline data & tracking planned. Success defined with specific, measurable targets (time/cost). General goals exist (e.g. “improve efficiency”), but not quantified. Outcome is vague or described differently by stakeholders.

2. Process & Knowledge Readiness

Process optimised; required knowledge (PDFs, DBs) is digital & centralised. Process understood; key knowledge exists digitally but needs consolidation. High-level process known; knowledge is scattered/siloed. Process or knowledge sources are undocumented/tribal.

3. Scope boundaries

Detailed MVP scope locked; future phases defined; exclusions signed off. Clear boundaries—what is in scope vs. excluded is agreed. Mostly clear, but edge cases often creep in during discussions. Scope fluid; stakeholders expect solution to “do everything”.

4. Executive sponsorship

Sponsor is active, holds budget, and attends regular steering updates. Named sponsor committed with allocated resources. Senior interest exists, but support is verbal only (no budget). Driven by single individual/team with no executive visibility.

5. Stakeholder alignment

All groups (IT, Business, Compliance) co-designed solution & are champions. Key stakeholders are aligned and engaged in solution design. Some stakeholders engaged, but alignment is fragile or siloed. Stakeholders are passive, conflicting, or unaware.

6. Urgency and priority

Critical priority linked to external deadline (Compliance) or strategy. Documented priority with a clear business driver. On roadmap, but frequently displaced by “BAU” fires. “Nice to have” or exploratory with no timeline.

7. Current state measurement

Granular, verified data (dashboards/logs) shows exact costs/friction. Baseline data or strong anecdotal evidence of current impact. Rough estimates based on interviews, but no hard data. Current performance is assumed, not measured.

8. Expected impact

Validated financial model (ROI/NPV) approved by finance. Benefit articulated in business terms and justifies investment. Value believed, but business case is assumptions-based. Benefit is speculative, unclear, or negligible.

9. Success metrics

Real-time dashboards will track adoption/value post-go-live. Success metrics agreed (adoption, time saved, etc). Intention to measure, but specific metrics not defined yet. No plan to measure outcomes.

10. User feedback loop

Continuous feedback loop (Champions network, in-app) + resources to iterate. Plan exists to gather user feedback during and after rollout. Feedback will be gathered informally or ad-hoc. Fire and forget—no feedback mechanism planned.

11. Your primary strategic focus for the next 90 days

Option A: External Engagement (Portals, Customer-facing Agents, Digital Forms) Option B: Internal Efficiency (Workflow Automation, Employee Copilots, Ops Reporting)

12. Path Selection

Option A: Governance and foundations first (secure env, ALM, standards, then build) Option B: Pilot first (prove value quickly with a working solution, scale governance later)

FutureAbility Readiness Scorecard

Who this is for

Why use this

Your Details

CLARITY: Can people describe success in plain language?