Definition | What is a nine-box talent grid?
The nine-box grid is a shared framework for talent reviews. Performance reflects demonstrated results. Potential needs evidence related to future roles and more complex work. Agree on assessment criteria for different roles and levels before discussing placement.
- Assess and classify performance and potential as separate dimensions.
- Review placements as roles, results and development needs change.
Uses | Connect talent reviews with development and succession
A nine-box grid can support discussions about talent deployment, professional growth, management experience and succession preparation. Managers explain their observations, calibrate differences and translate the discussion into suitable development opportunities.
- Agree on assessment periods, role requirements and category rules.
- Discuss missing evidence and different perspectives, recording the reasons for judgments.
- Connect the discussion with individual development plans, assignments and succession support.
To understand the second axis, explore potential indicators and five areas of behavioral observation. Define future roles and evidence, then use an individual development plan to arrange follow-up development.
Example | Map separate performance and potential ratings
Form a performance score and a potential score from agreed evidence, classify each as low, medium or high, then map the intersection. The example below uses a 0–100 scale and matching thresholds to explain placement. These are illustrative values; the two axes are not merged into a single total.
Illustrative categories and placement
This example uses a 0–100 scale and the same thresholds for both axes. These categories are illustrative, not a universal standard.
Low0 ≤ score < 60Medium60 ≤ score < 80High80 ≤ score ≤ 100
Performance 85, potential 82 → high performance / high potential
Example nine-box placement| Potential / Performance | Low performance | Medium performance | High performance |
|---|
| High potential | · | · | Example 85 / 82 |
|---|
| Medium potential | · | · | · |
|---|
| Low potential | · | · | · |
|---|
For an example of two-axis category configuration, see SAP official documentation. The numeric example here was created for this guide.
- Performance scores reflect goals, results and agreed assessment rules.
- Potential scores draw on future role requirements, behavioral standards, observations and assessment evidence.
- Managers or a review committee examine placements and their supporting evidence, then review development needs over time.
Frequently asked questions
Can nine-box placement be calculated?
Yes. Once separate performance and potential ratings are available, thresholds on each axis determine the matrix position. Confirm automatic placement, rating sources and settings against the available product and implementation configuration.
Should grid placement directly determine promotion?
Placement informs a discussion. Formal decisions should also consider role requirements, capability evidence and organizational procedures.
Should every organization use the same category thresholds?
Set thresholds around the purpose, rating scale and available evidence, with clear and consistent standards. The numeric values in this guide are illustrative.
How TalentOnline supports nine-box talent reviews
TalentOnline provides nine-box talent reviews and assessments. Combine performance, leadership and other assessment information within the agreed scope to inform development, career and succession discussions.
- Build a shared foundation of work results and competency records.
- Support calibration across managers and identify gaps in evidence.
- Confirm rating sources, automatic placement, category thresholds and external assessment integrations against available product settings and implementation scope.
For additional insight into capabilities and characteristics, explore talent assessment uses and behavioral examples. Assessments provide information; the nine-box grid organizes discussions of performance and potential. Use them together as complementary perspectives.
Features and workflows are based on supplied product information. Confirm configuration and implementation scope during a demo.