Internal Mobility Skills Matrix: How to Map Roles, Skills and Readiness for Moves

An internal mobility skills matrix gives you one shared view of roles, skills, and move-readiness. That helps managers make fairer move decisions, and it helps employees understand what “ready” looks like for a lateral move, a stretch assignment, or a promotion. Used well, the matrix becomes a practical system for feedback, development plans, and succession discussions.

Competency area	Mobility Coordinator	Mobility Partner	Senior Mobility Partner	Internal Mobility Program Lead
Role & skill architecture	Maps roles to a short, consistent skill list; flags unclear or duplicated skills.	Builds role profiles with 8–12 skills; aligns definitions with managers and HRBPs.	Designs role families and cross-role skill links; reduces overlap and “title inflation.”	Sets enterprise standards for role/skill taxonomy; ensures it stays usable at scale.
Assessment design & evidence standards	Collects self/manager inputs; ensures each rating has a concrete example attached.	Introduces evidence rules (projects, outcomes, feedback); raises rating consistency across teams.	Builds behavior anchors and “what good looks like”; reduces debates in calibration.	Defines audit-ready standards for ratings, evidence, and decision logs across cycles.
Readiness modeling for moves	Tracks readiness labels and timelines; keeps constraints visible (notice periods, part-time).	Connects readiness to skill gaps and development actions; updates after check-ins.	Separates proficiency from readiness; improves accuracy for stretch moves and gigs.	Owns readiness governance; ensures readiness is comparable across functions and countries.
Marketplace matching & opportunity design	Maintains a clean opportunity list (roles, projects, gigs); removes outdated postings quickly.	Improves matching inputs (must-have vs. learnable skills); increases fit and completion rates.	Designs mobility pathways (role → role); expands project-based mobility capacity.	Sets marketplace operating model; aligns supply/demand planning with strategy and budgeting.
Talent reviews & calibration facilitation	Prepares review packs; ensures required data is complete before sessions.	Facilitates structured discussions; keeps outcomes actionable (moves, plans, owners, timelines).	Runs cross-team calibration; addresses borderline cases with evidence and bias checks.	Owns governance for talent reviews; ensures decisions are consistent and documented.
Stakeholder management & change	Communicates updates clearly; resolves basic process questions fast.	Aligns managers, HR, and employees on expectations; reduces “hidden job market” behavior.	Builds manager capability (coaching, mobility conversations); improves adoption in hard teams.	Creates sustainable change plan; secures buy-in across leadership, HR, and employee bodies.
Data governance (GDPR/works council) & trust	Applies data minimization and access rules; escalates sensitive cases early.	Designs transparent data use messaging; ensures employees can correct skill profile errors.	Aligns with Betriebsrat inputs; implements safeguards (retention, purpose limits, audit trails).	Sets compliance-by-design approach; keeps trust high while enabling mobility analytics.
Analytics & decision support	Reports basic coverage: who has profiles, who is “ready now,” which roles lack bench.	Finds bottlenecks (common gaps, stuck talent); converts insights into targeted development plans.	Connects mobility outcomes to performance and retention signals; improves prioritization.	Defines KPIs and review cadence; uses insights to shape workforce and capability planning.

Key takeaways

Use one matrix to connect roles, skills, evidence, and readiness.
Separate proficiency from readiness to avoid “promote the best specialist” mistakes.
Standardize evidence to reduce bias in internal move decisions.
Run short calibration sessions to align managers on borderline cases.
Keep GDPR and Betriebsrat trust topics visible from day one.

Definition of the framework

This skill framework defines what strong internal-mobility work looks like across levels, from coordinator to program lead. It is used to build and run an internal mobility skills matrix, align role profiles and ratings, and support consistent decisions in performance conversations, talent reviews, succession planning, and internal marketplaces. For practical templates, start with skill matrix templates and adapt the fields to mobility use cases.

Internal mobility skills matrix: define the moves you want to enable

Mobility programs fail when “an internal move” means ten different things across teams. Start by naming your mobility archetypes and deciding what evidence counts for each. Then you can assess readiness without guessing, and you can explain decisions without defensiveness.

Mobility archetypes (practical baseline): lateral move, stretch move, promotion, project/assignment. Each archetype needs a different risk tolerance, a different time horizon, and different onboarding expectations.

Hypothetical example: A Finance Analyst wants to move into FP&A. As a lateral move, you may require strong Excel modeling and stakeholder updates; as a stretch move, you may accept gaps but require mentoring and a 90-day proof plan.

Define 3–4 mobility archetypes and write one sentence “success criteria” for each.
Decide which skills must be present pre-move vs. learnable within 3–6 months.
Add one field for constraints (notice period, working hours, location) to prevent mismatches.
Agree on a standard onboarding expectation per archetype (30/60/90 milestones).
Document “what triggers a re-assessment” (new project, new manager, performance shift).

Design the matrix structure: columns, data sources, and ownership

A usable internal mobility skills matrix is boring by design: few columns, clear definitions, and one owner who keeps it clean. The goal is decision support, not a perfect “skills universe.” If the matrix cannot be reviewed in 15–20 minutes in a talent discussion, it will rot.

Use a standard column set so people can compare like with like across functions. Keep optional fields optional, and avoid capturing sensitive data you cannot justify under GDPR principles (Datenminimierung).

Standard columns for an internal mobility skills matrix

Column	What you capture	Why it helps decisions
Employee	Name/ID, team, location (as needed)	Lets you group by org unit and mobility constraints.
Current role	Role title + role family	Shows the starting point for lateral vs. step-up moves.
Target role(s)	1–3 realistic next roles or gig types	Prevents “anything is possible” and forces trade-offs.
Key skills/competencies	6–10 skills linked to target role	Makes gaps visible without listing everything the person can do.
Proficiency (per skill)	1–5 rating + evidence link	Turns opinions into comparable inputs.
Potential (growth capacity)	Simple 1–3 scale + rationale	Clarifies who can grow into bigger scope vs. who prefers depth.
Mobility preferences	Interest areas, timing, location/remote, contract constraints	Reduces wasted matching and “surprise” moves.
Readiness level	Ready Now / 6–12 / Emerging / Not Yet	Enables planning and realistic timelines.
Risk-of-loss (optional)	Low/Med/High with reason category	Supports retention planning without turning it into pressure tactics.
Development actions	2–4 actions with owner and due date	Turns the matrix into execution, not just classification.
Target timeline	Quarter/month	Creates accountability and reduces stale “someday” entries.

Matrix examples (tool-agnostic)

These examples show how the same internal mobility skills matrix can work at employee, team, and portfolio level. They stay compatible with spreadsheets, HR suites, or an internal marketplace platform.

(a) Individual view: one employee across three internal move options

Employee	Current role	Target role	Must-have skills (sample)	Proficiency snapshot	Potential	Preferences	Readiness	Development actions (next 90 days)	Timeline
M. K.	Customer Support Specialist	Customer Success Manager (SMB)	Onboarding, QBR basics, stakeholder comms	Onboarding 3/5; comms 3/5; commercial 2/5	2/3	Remote; EMEA; no travel	Ready in 6–12 months	Shadow 3 onboarding calls; run 1 QBR; pricing module	Q4
M. K.	Customer Support Specialist	Support Team Lead	Coaching, prioritization, incident comms	Coaching 2/5; ops 3/5; comms 4/5	2/3	Same location; people management interest	Emerging (12–24 months)	Lead weekly triage for 6 weeks; mentor new hire; feedback training	Next year
M. K.	Customer Support Specialist	Project gig: Help Center overhaul (8 weeks)	Writing, process mapping, cross-team coordination	Writing 4/5; process 3/5; coordination 3/5	2/3	8-week capacity; prefers async work	Ready Now	Define success metrics; stakeholder map; weekly progress updates	Start next month

(b) Team view: critical function mapping across target roles

Team	Critical target role	Bench candidate	Key skill gaps	Readiness	Risk if role opens	Mitigation action
Data	Analytics Engineer	A. S.	dbt production patterns (gap 1 level)	Ready in 6–12 months	Medium	Assign to one production model refactor; code review buddy
Data	Data Platform Lead	J. P.	Stakeholder alignment, budgeting exposure	Emerging (12–24 months)	High	Give ownership of quarterly roadmap and vendor review
RevOps	Sales Ops Manager	L. H.	Forecast governance, stakeholder pushback handling	Ready Now	Low	Document handover plan; run one quarter end-to-end
RevOps	Deal Desk Specialist	T. N.	Contract basics, pricing approvals	Ready in 6–12 months	Medium	Shadow legal clinic; run supervised approvals for 4 weeks

(c) Portfolio view: talent marketplace / succession bench snapshot

Target role family	# Ready Now	# Ready in 6–12	# Emerging	Top recurring gap	Suggested pipeline move
People Management (first-line)	6	14	22	Coaching conversations with evidence	Add “team lead gigs” + manager shadowing rotations
Finance (FP&A)	2	5	9	Business partnering with non-finance leaders	Run cross-functional planning projects as stretch assignments
Engineering Management	1	3	8	Hiring + performance calibration experience	Create interview panel lead roles and calibration participation
Customer Success (Mid-market)	4	7	10	Commercial negotiation	Pair with renewals role for one quarter; structured deal coaching

Assign one matrix owner per business unit with a clear “clean-up” SLA.
Limit skills per target role; store “nice-to-have” skills outside the core matrix view.
Define a single source of truth for role profiles, even if skills live in multiple systems.
Schedule a monthly stale-data check: roles, readiness dates, and evidence freshness.
Decide where the matrix lives: spreadsheet, HR suite, or marketplace workflow.

Readiness is not proficiency: combine skills, potential, and constraints

Proficiency answers “can this person do the skill today?” Readiness answers “is this person likely to succeed in this move, in this context, on this timeline?” Mixing them leads to predictable mistakes: over-promoting specialists, under-using high learners, and underestimating context shifts.

Hypothetical example: Two employees both deliver a strong project. One needed daily guidance and reused an existing template; the other created a repeatable approach and coached others. The outcome looks similar, but readiness for a stretch move differs.

Readiness levels (with “what good looks like”)

Readiness level	Definition (observable)	Typical development plan
Ready Now	Can perform core responsibilities with normal onboarding; gaps are minor and explicit.	Role transition plan; 30/60/90 outcomes; mentor for edge cases.
Ready in 6–12 months	Has most must-have skills; one or two gaps block independent performance today.	Targeted assignments; shadowing; skill verification with evidence.
Emerging (12–24 months)	Shows learning speed and motivation; needs repeated exposure to core tasks.	Step-stone gigs; foundational training; feedback loop every 6–8 weeks.
Not Yet	Either low interest, repeated performance instability, or missing foundations for the move.	Stabilize current role outcomes; clarify preferences; reassess after a defined period.

Rate proficiency per skill, then derive readiness from must-haves plus constraints.
Add one field for “learnability” (learn fast / learn steady / learn slow) when useful.
Write readiness rationales in plain language, tied to evidence, not personality labels.
Use readiness dates; force an update when the date expires.
Separate “wants to move” from “ready to move” to keep conversations honest.

Use the internal mobility skills matrix in talent reviews, succession, and marketplaces

The matrix becomes valuable when it changes decisions: who gets a gig, who enters a succession slate, what development is funded, and which managers need coaching on mobility conversations. The best use cases share one trait: they require trade-offs, and the matrix makes those trade-offs explicit.

To connect mobility to broader talent processes, align the matrix with your talent review cadence and the evidence you already collect in performance cycles. If you run an 9-box, keep it as a separate view; use the mobility matrix to explain “next role readiness” with skill evidence.

Hypothetical example: During an annual talent review, a business unit sees a weak bench for first-line managers. Instead of nominating people based on tenure, they filter for coaching evidence, stable delivery, and “Ready in 6–12 months,” then assign team-lead gigs as proof points.

Run talent reviews with the matrix visible; timebox each person to force clarity.
Convert every “ready in 6–12” into 2–4 actions with owners and due dates.
Link succession slates to readiness, not only potential; store rationale in a decision log.
Feed marketplace matching with must-have vs. learnable skills to increase placement quality.
Audit outcomes quarterly: move success, time-to-fill internally, and post-move performance.

If you need structured assets for key-role continuity, adapt succession planning templates and use the same readiness labels to avoid parallel systems. For marketplace design patterns and governance, use an internal talent marketplace guide as a reference point for roles, gigs, and mentoring supply.

DACH governance: GDPR, Datenminimierung, and Betriebsrat alignment

In DACH contexts, internal mobility data touches co-determination and trust quickly. People will ask: Who can see my profile? Will my manager block me? Is this used for performance ratings or layoffs? If you cannot answer clearly, adoption drops, and the matrix becomes political.

Plan for Betriebsrat involvement early and treat it as product design input. You typically need agreement on assessment principles, transparency rules, retention, access roles, and whether algorithmic matching is used (and how humans override it). A Dienstvereinbarung can make expectations durable across leadership changes.

Hypothetical example: HR wants to add “risk-of-loss” to the matrix. The works council agrees only if reasons are category-based (no free text), access is limited, and reporting is aggregated with minimum group sizes.

Apply data minimization: capture only what you use for mobility decisions.
Define access by role (employee, manager, HR, marketplace owner) and document it.
Give employees a correction path for skill data and readiness labels.
Separate development data from disciplinary processes; state the purpose in writing.
Agree retention rules and export controls before scaling beyond a pilot.

If you support mobility with software, evaluate it with DACH-specific governance checks (permissions, audit logs, EU hosting, works council readiness). A neutral overview like an internal mobility software comparison can help you structure requirements without locking into one operating model.

Keep it alive: operations, adoption, and skill drift

A matrix is only as good as last quarter’s evidence. If updates depend on hero HR effort, it will decay. Build lightweight rituals: refresh points, automatic prompts, and simple definitions that managers can repeat without training decks.

Hypothetical example: A business unit requires one evidence update per key skill every six months. In exchange, HR commits to quarterly mobility discussions and publishes a list of gigs and projects with clear must-haves.

Set an “evidence freshness” rule (for example: at least one recent example per key skill).
Use manager 1:1s to update mobility preferences and constraints, not only performance topics.
Run a quarterly “matrix hygiene” sweep: remove outdated target roles and expired readiness dates.
Train managers with two scripts: how to rate with evidence, and how to discuss blocked moves.
Store development plans next to matrix entries; use IDP templates to standardize actions and timelines.

For broader skill visibility beyond mobility, align your matrix with a shared skills approach so role profiles do not fork. A structured skill management setup helps you keep definitions consistent and reduces duplicate assessments across HR processes.

Skill levels & scope

Mobility Coordinator: Owns data hygiene and execution. Works with limited decision freedom, and escalates ambiguity. Typical impact is reliable completeness: people can find profiles, evidence, and next steps without chasing.

Mobility Partner: Owns end-to-end mobility cases and role/skill alignment for a unit. Has freedom to propose role profiles, readiness criteria, and development actions, then align with managers. Typical impact is higher-quality matches and fewer “surprise failures” after moves.

Senior Mobility Partner: Owns cross-team consistency and complex edge cases. Can change how readiness is evaluated and how calibration works across multiple leaders. Typical impact is reduced bias and faster decisions, because standards are shared and defensible.

Internal Mobility Program Lead: Owns the operating model, governance, and enterprise outcomes. Has freedom to set standards, KPIs, and escalation paths, and to align with works councils and legal. Typical impact is a repeatable system: mobility increases without turning into chaos.

Skill areas

Role & skill architecture: You define roles in a way that supports comparisons and paths (role → role). Output is a role profile set with consistent skill definitions, so “Senior” means similar scope across teams.

Assessment design & evidence standards: You define how ratings are made and what counts as proof. Output is faster calibration and fewer disputes because examples, not opinions, anchor the discussion.

Readiness modeling for moves: You turn skills and context into a clear “ready when” story. Output is a realistic timeline with a small set of actions that actually close gaps.

Marketplace matching & opportunity design: You shape internal roles, gigs, and projects so matching works. Output is higher completion and satisfaction because opportunities state must-haves, outcomes, and time demands.

Talent reviews & calibration facilitation: You run sessions where leaders align on readiness and move decisions. Output is a documented set of outcomes: placements, development plans, and next-cycle priorities.

Stakeholder management & change: You handle the human side: manager incentives, employee trust, and process clarity. Output is adoption: people use the system instead of backchannels.

Data governance (GDPR/works council) & trust: You design transparent data use and permissions. Output is participation without fear, because people understand who sees what and why.

Analytics & decision support: You turn the matrix into patterns leaders can act on. Output is targeted investment: training, gigs, hiring, or succession actions based on recurring gaps.

Rating & evidence

Use two separate scales: one for skill proficiency (what someone can do today), and one for potential (capacity to grow into bigger scope). Then set readiness as a derived label that considers must-have skills, constraints, and time.

Skill proficiency scale (1–5)

1 – Basic awareness: Can explain concepts; needs close guidance to deliver usable outputs.
2 – Working level: Delivers parts of the work with review; outcomes meet baseline quality.
3 – Independent: Delivers end-to-end outcomes reliably; anticipates common risks and trade-offs.
4 – Advanced: Improves standards and reduces team risk; coaches others with repeatable methods.
5 – Expert: Sets direction across teams; solves novel problems and raises organizational capability.

Potential scale (1–3)

1 – Solid in current scope: Sustains performance; prefers depth or stable scope.
2 – Growth capacity: Learns fast; can take on bigger scope with structured support.
3 – High growth capacity: Repeatedly scales impact; thrives in ambiguity and expanding scope.

What counts as evidence (pick what fits your org)

Documented outcomes: OKRs, project deliverables, retrospectives, before/after metrics.
Work artifacts: proposals, process docs, customer communications, training materials.
Quality signals: stakeholder feedback, peer feedback, escalation notes with resolution.
Execution proof: delivery logs, incident postmortems, handover quality, follow-through.
Observed behavior: structured interview notes from gigs, shadowing, or rotations.

Mini example: Fall A vs. Fall B (same “result,” different level)

Fall A: An employee delivers a cross-team report on time, but relies on repeated manager nudges and cannot explain trade-offs. That can still be strong execution, but it is often a 2–3 on stakeholder management and planning evidence.

Fall B: Another employee delivers the same report, aligns stakeholders up front, documents assumptions, and reduces rework in the next cycle. That is typically a 4 because it creates repeatable outcomes and lowers team risk.

Growth signals & warning signs

Growth signals (ready for next level): Sustains outcomes over time; expands scope without quality drops; creates reusable assets; gets pulled into higher-stakes work; resolves conflict with evidence; coaches others; communicates trade-offs early.
Warning signs (promotion/move blockers): Results depend on hero effort; repeated missed handovers; poor documentation; avoids cross-team accountability; blames context without proposing options; inconsistent collaboration; unclear ownership; ratings without evidence.

Check-ins & review sessions

Use two rhythms: lightweight check-ins to keep data fresh, and structured review sessions to make decisions. The goal is shared understanding, not perfect calibration.

Practical formats you can copy

Format	Cadence	Participants	Output
Mobility check-in (team)	Monthly (30 minutes)	Manager + HR/talent partner	Updated preferences, readiness dates, and 1–2 concrete development actions.
Calibration lite (function)	Quarterly (60–90 minutes)	Managers + facilitator	Aligned ratings for borderline cases; documented rationales; bias prompts applied.
Talent review / succession session	Biannual or annual (2–4 hours)	Leadership + HR	Succession slates with readiness labels; funded development plans; staffing priorities.
Marketplace matching stand-up	Biweekly (30 minutes)	Opportunity owners + marketplace owner	Open roles/gigs cleaned; must-haves clarified; placements tracked to completion.

Require pre-reads: ratings without evidence get marked as “incomplete,” not debated.
Use a speaking order that starts with evidence, not advocacy.
Maintain a simple decision log: what changed, why, and what action follows.
Run two bias checks: recency (“only last month?”) and similarity (“like me?”).
Keep escalation clear: who decides if managers disagree on readiness?

If you want a structured way to run these sessions, adapt a talent calibration guide and reuse the same evidence packet format every cycle.

Interview questions

Use these questions to collect concrete examples for each competency area. Ask for context, actions, and outcomes, then probe for evidence (what changed, who confirmed it, what you would do differently).

Role & skill architecture

Tell me about a time you simplified role profiles without losing decision usefulness. What changed?
How did you decide which skills were must-have vs. learnable for a target role?
Describe a time role titles masked different scope. How did you fix comparability?
Tell me about a role family redesign you supported. What outcomes improved?
What’s your approach to preventing skill lists from becoming endless?

Assessment design & evidence standards

Tell me about a time ratings were inconsistent across managers. What did you change?
Describe an evidence standard you introduced. How did you drive adoption?
When did you challenge a rating because evidence was weak? What happened next?
Tell me about a calibration session that went wrong. What did you adjust?
How do you handle self-assessments that are much higher than manager ratings?

Readiness modeling for moves

Tell me about a move that looked “ready” on skills but failed. What did you miss?
How do you separate proficiency from readiness in your assessments?
Describe a time you recommended a stretch move. What safeguards did you set?
Tell me about how you used constraints (timing, location) to prevent a poor match.
What evidence do you require to label someone “Ready Now”?

Marketplace matching & opportunity design

Tell me about a time you improved matching quality for gigs or internal roles.
How do you write opportunity descriptions so they attract the right candidates?
Describe a case where managers tried to “hoard” talent. What did you do?
Tell me about a time a placement failed. What did you change in the matching inputs?
How do you measure whether marketplace matches are successful after 60–90 days?

Talent reviews & calibration facilitation

Tell me about a borderline promotion/move decision you facilitated. What evidence mattered?
How do you keep talent reviews from becoming opinion battles?
Describe your approach to documenting decisions without creating fear or bureaucracy.
Tell me about a time you identified a weak bench for a critical role. What changed?
How do you handle disagreement between two senior leaders about readiness?

Stakeholder management & change

Tell me about a time you improved manager adoption of a mobility process.
How did you communicate “not ready yet” without damaging engagement?
Describe a time you shifted a culture from backchannel moves to transparent moves.
Tell me about resistance you faced from a high-performing team. What worked?
How do you support employees whose manager is not supportive of mobility?

Data governance (GDPR/works council) & trust

Tell me about a time you applied data minimization in a talent system. What did you remove?
How did you explain data use and permissions to employees in plain language?
Describe a time you worked with a Betriebsrat on assessment principles.
Tell me about a disagreement on transparency or access. What compromise worked?
How do you ensure employees can correct skill data or readiness labels?

Analytics & decision support

Tell me about a time your mobility analytics changed a workforce decision.
How do you identify recurring skill gaps that block internal fill rates?
Describe a KPI set you used to track mobility success beyond “number of moves.”
Tell me how you turned insights into funded development actions.
How do you avoid misuse of mobility data (for example, ranking individuals publicly)?

Implementation & updates

Implement in phases so you can fix definitions and trust gaps before scaling. Start with one unit, one role family, and one review cadence, then expand once managers can rate with evidence and employees understand the rules.

Rollout steps (practical sequence)

Kickoff (week 1–2): Define archetypes, readiness labels, matrix columns, and owners.
Manager training (week 2–4): Practice rating with evidence; rehearse mobility conversations.
Pilot (weeks 4–10): Run the matrix in one talent review and one marketplace matching cycle.
Review (week 10–12): Collect feedback, measure data completeness, adjust skill definitions.
Scale (quarter 2+): Expand role families and automate reminders for evidence freshness.

Ongoing maintenance

Owner: Assign a named program owner who can change definitions and enforce hygiene.
Change process: Use versioning (v1.1, v1.2) with a short changelog and rationale.
Feedback channel: Collect manager and employee friction points continuously, not annually.
Review cadence: Refresh the framework at least yearly, and after major reorganizations.
Tooling: If you use platforms (for example, Sprad Growth), keep the workflow simple: evidence, readiness, actions.

If you are also building a dedicated marketplace, compare approaches and governance needs using an internal talent marketplace software overview, then adapt your matrix fields to the matching logic you choose.

Conclusion

A good internal mobility skills matrix creates clarity: people know what skills matter, what evidence counts, and what “ready” means. It also increases fairness, because decisions rely less on advocacy and more on observable outcomes. And it keeps development practical, because every “not yet” turns into a small plan with owners and timelines.

Next steps can stay lightweight: pick one business unit this month, define your archetypes and readiness labels in week one, then run one pilot talent review within 6–8 weeks. In parallel, align early with your Betriebsrat and data protection stakeholders so permissions, retention, and transparency rules are stable before you scale.

FAQ

How often should we update an internal mobility skills matrix?

Use two rhythms: monthly light updates for preferences, constraints, and readiness dates; quarterly updates for evidence and skill ratings. Many organizations fail by updating only during annual reviews, which makes readiness stale and damages trust. Keep a simple rule: if a readiness date expires, it must be refreshed or downgraded until new evidence exists.

How do we avoid bias when managers rate readiness for internal moves?

Require evidence for every key rating, and standardize what evidence looks like (projects, outcomes, feedback). Then run short calibration sessions where borderline cases are discussed using the same rubric. Add two quick bias prompts: “Are we over-weighting the last few weeks?” and “Would we rate this differently if the employee were in another team?” Document rationales briefly.

Can we use the matrix for both development and selection decisions?

Yes, but be explicit about purpose. Development use focuses on gaps, actions, and learning opportunities; selection use focuses on readiness and constraints for a specific role or project. Keep access and visibility rules clear so people don’t feel punished for honest gaps. A simple safeguard is to separate raw notes from final labels and store only what you can justify.

What’s the difference between proficiency, potential, and readiness?

Proficiency is skill performance today (with evidence). Potential is capacity to grow into larger scope over time. Readiness is the move-specific prediction: can this person succeed in this role or assignment within the stated timeline, given must-have skills and constraints? Treat readiness as a derived label, not a direct rating, so it stays explainable and comparable across teams.

How do we keep employees from fearing their manager will block mobility?

Start with transparency: explain who can see what, how readiness is decided, and how employees can correct errors. Offer employees a path to register interest in gigs or roles without creating conflict, and define an escalation route (HR/talent partner) if a manager repeatedly blocks moves without evidence-based rationale. Pair this with a periodic pulse like an internal mobility survey to spot trust gaps early.

Jürgen Ulbrich

CEO & Co-Founder of Sprad

Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.