Identify Leadership Readiness Through Role Evidence

Reviewed and updated October 8, 2026.

Assess readiness for a named responsibility rather than label a person as universally high potential. Leadership work changes across roles. Evidence that someone handles a service escalation does not establish that they can manage a technical release or lead a larger team.

Define the responsibilities before choosing a method. Consider the decisions, collaboration and judgment the role requires, the skills that must be present now and those that can be learned with support. Keep development opportunities distinct from a consequential selection decision.

Gather comparable evidence

Use work examples, structured scenarios and feedback tied to the role. Ask comparable questions and apply a defined rubric. OPM describes structured interviews as using the same predetermined questions and rating standards. This provides a clearer comparison than an unstructured impression, without guaranteeing a fair or accurate decision by itself.

A nine-box grid can organize a discussion, but its labels are judgments. Record the underlying evidence, uncertainty and disagreements. Avoid turning a manager's subjective potential score into a permanent trait.

Illustrative readiness exercise

A hypothetical team needs a deputy who can manage an AI-assisted workflow during the owner's absence. Candidates review a scenario with a rising exception queue, conflicting policy sources and an unavailable vendor. The rubric looks for evidence gathering, containment, clear ownership and communication of uncertainty.

A candidate who pauses the risky action and preserves manual service may demonstrate better judgment than one who keeps the system running to protect a usage target. The exercise is illustrative, not a validated assessment or reported predictor of performance.

Create a development opportunity

Give the person a bounded responsibility with support: lead a review meeting, coordinate a small rollout or investigate a documented exception pattern. Specify decision limits and the experienced person available for escalation. Observe the work and discuss what changed after feedback.

Do not treat willingness to work longer hours, visibility in meetings or familiarity with a particular AI tool as a proxy for leadership readiness. Check whether people have comparable access to assignments that generate evidence.

Readiness record

• Responsibility: name the role-specific work.
• Required evidence: describe observable behaviors and acceptable outcomes.
• Current evidence: record examples, context and limitations.
• Development needs: separate skill gaps from missing opportunities or resources.
• Trial responsibility: define scope, support and decision limits.
• Review: compare later work with the same criteria and document uncertainty.

If the assessment affects hiring or promotion, involve the appropriate employment and assessment specialists. A learning exercise should not silently become a selection test.

Revisit readiness as the role and evidence change. The purpose is a defensible development decision and a supported next assignment, not a claim that software can predict a person's future.

Bring the decision into a project review

Bring the responsibility a rollout needs someone to own. A review can clarify its decision limits and the capabilities required to perform it. Explore ALLTIPLY AI roadmap and enablement, or request a project review with the workflow, systems and constraints you need to assess.