Evaluating Digital Transformation Leadership
A structured set of evaluation criteria for VP of Digital Transformation and enterprise technology leadership roles — usable for assessing external candidates or reconfirming an incumbent.
Why most evaluations fail
Transformation leadership is usually assessed on narrative fluency. A candidate describes a large program, names recognizable technologies, and references culture change. Boards and executive committees rarely test the mechanics that determine whether the next transformation lands: who holds decision rights, how work gets stopped, how benefits are baselined, and how AI changes the workflow rather than decorating it.
The criteria below are written to be scored. Each dimension has an evidence requirement — something the leader either can or cannot produce. Applied consistently, the same framework works for external search, internal succession, and annual reconfirmation of an incumbent.
Six dimensions, each with an evidence requirement.
Transformation thesis and operating-model judgment
Can the leader state, in one page, what the transformation changes about how the business operates — and what it deliberately does not change? Weak candidates describe technology programs; strong ones describe operating-model outcomes with named trade-offs.
Evidence to requireA prior transformation thesis, the sequencing logic behind it, and the decisions they reversed as evidence arrived.
Delivery governance
Governance is decision-making, not status reporting. Look for defined decision rights, escalation thresholds, a fixed cadence, and written decision records that show issues were resolved rather than reported repeatedly.
Evidence to requireA governance calendar, decision log, and an example of an escalation resolved within one cycle.
Portfolio and investment discipline
The credible signal is subtraction. Ask what they stopped, descoped, or consolidated, and how funding moved as a result. Leaders who have never killed an initiative have not yet been accountable for a portfolio.
Evidence to requirePortfolio view with owners, dependencies, and stage gates; examples of stop and descope decisions with rationale.
AI and data integration
Assess whether AI is treated as an operating-model change or a pilot program. Strong leaders can describe use-case intake, data readiness assessment, human-oversight points, and how a workflow was redesigned — not merely augmented.
Evidence to requireA use-case intake with prioritization criteria, risk gates, and at least one workflow redesigned and measured.
Organizational change capability
Transformation fails in the middle layer. Evaluate how the leader equips managers, resolves role ambiguity, and sustains adoption after go-live — including what they do when adoption stalls.
Evidence to requireRole-based enablement plans, adoption metrics over time, and a documented recovery from an adoption shortfall.
Benefits realization
Benefits must be baselined before delivery and measured after. Require finance-agreed measures, a named owner per benefit, and a review cadence that continues past program close.
Evidence to requireA benefits ledger with baseline, target, actual, owner, and post-close review dates.
A five-step evaluation sequence.
- 01
Define the mandate first
Write the 18-month outcome the role owns before writing the profile. Scope, decision rights, and reporting line are part of the evaluation criteria, not context.
- 02
Score the six dimensions independently
Rate each dimension 1–5 with written evidence. Refuse composite impressions — they hide the single dimension that will cause failure.
- 03
Require artifacts, not stories
Ask for redacted governance calendars, portfolio views, and benefits ledgers. Leaders who have run governance can produce them; those who have attended it cannot.
- 04
Test with a live scenario
Give a real red program and ask for a 30-day stabilization plan: what they stop, who decides, what they measure, and what they escalate.
- 05
Set a 90-day evidence checkpoint
Convert the winning criteria into first-quarter deliverables so the evaluation continues after hiring or reconfirmation.
What should end the conversation.
- Ownership described through tools, vendors, or headcount rather than outcomes
- No example of stopping, descoping, or consolidating an initiative
- Benefits claimed with no pre-delivery baseline
- AI framed as pilots with no workflow redesign or oversight model
- Governance described as reporting rather than decision-making
- Program recovery attributed entirely to others
Questions boards ask us.
- What should a VP of Digital Transformation evaluation cover?
- Six dimensions: transformation thesis and operating-model judgment, delivery governance, portfolio and investment discipline, AI and data integration, organizational change capability, and benefits realization. Each should be assessed against documented evidence rather than narrative.
- How do boards evaluate an incumbent transformation leader?
- Use the same criteria applied to candidates, but score against the current portfolio: are decision rights clear, are milestones met against an approved baseline, are red programs surfaced early, and are benefits measured against a pre-agreed baseline?
- What evidence should a transformation leader be able to produce?
- A portfolio view with owners and dependencies, a governance calendar with decision records, a baseline-versus-actual delivery history including recovered programs, an AI use-case intake with risk gates, and a benefits ledger tied to finance-approved measures.
- What are the strongest disqualifying signals?
- Ownership described only in terms of tools or vendors, no examples of stopping or descoping work, benefits claimed without a baseline, AI framed as pilots without workflow redesign, and governance described as status reporting rather than decision-making.
Assessing transformation leadership?
We run independent evaluations of transformation mandates, portfolios, and leadership capability — and provide interim leadership where a gap exists.