Record of outcomes
Check what they owned: ERP migrations, M365 or cloud consolidations, uptime and MTTR figures, helpdesk SLA attainment, and IT budgets they held with headcount numbers.
Evidence to listen for
- Names organisations, budgets, and headcount they were actually accountable for
- Gives outcomes with numbers, not initiatives with adjectives
- Separates what they drove from what the market or a predecessor did
- Can describe something they owned that failed
Five-point scoring guide
Titles and initiatives only; no accountable outcomes.
Claims results the organisation would have had anyway; no scope clarity.
Real accountability with some numbers; attribution occasionally generous.
Clear scope and measured outcomes, including an honest failure.
Names specific programmes (for example Azure migration, Netsuite rollout) with before and after uptime, ticket volume, and cost figures they personally owned.