Compensation, Talent & Org Planning
The EdTech company in Karachi has a problem that most growing companies recognise: a Team Lead, Data Engineering vacancy has opened, and the instinct is to post it externally. Bilal Ahmed's performance review last quarter — which the team ran using /performance-review — raised the question of whether he is on a leadership track. Meanwhile, Zara Hussain, a Senior Data Engineer who has been with the company for three years, led the data warehouse migration project last year and has been quietly mentoring two junior engineers. The Head of Analytics, Omar Farooq, has a gut sense that Zara might be ready. But a gut sense is not a succession plan.
The question is not "should we hire externally?" The question is "have we properly assessed internally first?" External hiring, according to industry research, typically costs several times more than an internal promotion. A new external hire often takes many months to reach full productivity. And if Zara is passed over for a role she could have filled, she will probably start updating her CV — taking three years of institutional knowledge with her.
This lesson brings together three skills that work in sequence: /comp-analysis to benchmark what the role should pay and whether a promotion offer would be internally equitable, /match to systematically assess Zara and a second internal candidate against the role requirements across six dimensions, and /org-planning to model what happens to the team structure when someone moves up.
The Internal Mobility Imperative
Before reaching for the job boards, the arithmetic of internal mobility deserves a clear look.
| Factor | External Hire | Internal Promotion |
|---|---|---|
| Recruiting cost | Agency fees, advertising, sourcing time | Minimal (internal process) |
| Time to fill | Typically weeks to months | Immediate (or defined transition) |
| Productivity ramp | Research suggests many months to full output | Shorter — context already held |
| Cultural integration | Requires active management | Already embedded |
| Institutional knowledge | Starts from zero | Accumulated |
| Retention signal | Neutral | Strongly positive for remaining staff |
The financial case is compelling. But there is a second cost that rarely appears on a spreadsheet: the signal that external hiring sends to every high-potential employee who was not considered. Each external hire for a role that could have been internal is a message to every ambitious person in the organisation: your growth here has a ceiling.
The internal mobility assessment is not just good HR practice. It is a retention strategy.
Benchmarking Compensation with /comp-analysis
Before assessing candidates, you need to know what the role should pay. A promotion that lands Zara at an uncompetitive salary is a short-term win and a medium-term retention risk. And a salary that creates an internal equity problem — where Zara suddenly earns significantly more than peers with similar scope — creates a different set of problems.
/comp-analysis provides percentile bands across four reference points:
| Percentile | Signal |
|---|---|
| 25th | Below market — retention risk for strong performers |
| 50th | Market median — competitive for most candidates |
| 75th | Above market — attracts and retains strong performers |
| 90th | Top of market — appropriate for critical or scarce roles |
Worked Example: Team Lead, Data Engineering (Karachi)
/comp-analysis Team Lead, Data Engineering — Karachi, Pakistan
Role context: EdTech company, ~250 employees. Role manages 2-3 engineers,
reports to Head of Analytics. Requires Spark, Airflow, dbt expertise plus
people management responsibility. Pakistan market.
A benchmarking output would look like:
## Compensation Analysis: Team Lead, Data Engineering — Karachi, Pakistan
### Market Benchmarks (Pakistan EdTech/Tech sector)
| Percentile | Monthly Base (PKR) | Annual Total Comp |
|------------|--------------------|-------------------|
| 25th | 180,000 | 2,160,000 |
| 50th | 240,000 | 2,880,000 |
| 75th | 310,000 | 3,720,000 |
| 90th | 390,000 | 4,680,000 |
Sources: Market research, Pakistan IT industry benchmarks, recruiter data.
Note: Verify current figures against local salary surveys before use.
### Band Analysis
Current salary (Zara Hussain as Senior Data Engineer): 200,000 PKR/month
Proposed promotion salary: 270,000 PKR/month
→ Position: 62nd percentile — competitive; above median; no internal equity flag
for this band.
### Recommendations
- 270,000 PKR/month is a credible offer at the 62nd percentile
- Internal equity: check against other Team Lead equivalents in the org
- Consider a 3-month performance-in-role review with a pre-agreed salary
step to 290,000 PKR if targets are met — reduces initial cost while
maintaining motivation
What to verify in the output:
| Element | Check |
|---|---|
| Percentile bands | Do they feel realistic for the local market? Cross-check one data point. |
| Internal equity | Does this salary create an anomaly vs. peers at the same level? |
| Benefits | Has total comp (bonus, benefits, equity) been captured, not just base? |
| Source currency | Are these figures current? Salary data dates quickly in growing markets. |
/comp-analysis is only as good as the market data available for the role, level, and location. In less benchmarked markets, the output will note lower data confidence. Always cross-check one reference point against a local salary survey or recruiter before presenting the figure to a candidate.
Assessing Internal Candidates with /match
With the compensation band established, the question shifts: who should be offered this role? /match provides a structured six-dimension assessment for each internal candidate.
The Six Dimensions
| Dimension | What It Assesses | Rating Scale |
|---|---|---|
| Critical skills | Must-have capabilities for the role | DEMONSTRATED / DEVELOPING / ABSENT |
| Experience | Relevant background | RELEVANT / PARTIAL / LIMITED |
| Performance trajectory | Direction of travel, not just current level | ASCENDING / CONSISTENT / VARIABLE |
| Readiness indicators | Evidence of next-level behaviour already present | Specific instances required |
| Development areas | Gaps and their type | EXPERIENCE GAP / SKILL GAP / MINDSET GAP |
| Motivation and career intent | Does this person want this direction? | Expressed intent + retention risk |
The gap classification in Dimension 5 matters because each gap type requires a different development response:
- Experience gap: Has the aptitude; needs the opportunity. A structured project assignment bridges this.
- Skill gap: Needs to build a specific capability. Coaching, training, or a targeted secondment addresses this.
- Mindset gap: Operates with assumptions that need to shift. Harder to bridge quickly; mentoring from someone who made the same shift helps.
The Readiness Classification
| Classification | Meaning | Recommended Action |
|---|---|---|
| READY NOW | Can take the role immediately | Have the conversation; move quickly |
| READY IN 6 MONTHS | Specific, bridgeable gaps | Design a development plan before posting |
| READY IN 12 MONTHS | Meaningful development required; strong potential | Invest now; manage expectations |
| DEVELOPING | Strong pipeline; 18-24 months | Acknowledge and build a runway |
| NOT A FIT | Skills or motivation not aligned with this direction | Redirect to alternative pathway |
Worked Example: Team Lead, Data Engineering
/match Team Lead, Data Engineering
Role requirements:
Critical: Technical leadership; Spark/Airflow/dbt expertise; ability
to manage 2-3 engineers
Important: External stakeholder communication; strategic thinking
Nice-to-have: Experience at scale; cross-functional influence
Candidates:
Candidate 1: Zara Hussain — Senior Data Engineer, 3 years at the company
- Led the data warehouse migration project (30TB, 6-month delivery)
- Mentors two junior engineers informally; well-regarded by peers
- External stakeholder communication is a known development area
- In last performance review, expressed interest in a leadership role
Candidate 2: Ahmed Malik — Data Engineer, 2 years at the company
- High potential; technically strong; fast learner
- No formal management experience; early in career for this level
- Unusually strong stakeholder communication skills for his experience
- Has expressed interest in growth but not specifically people leadership
Sample /match output:
TASK: Internal Talent Assessment -- Team Lead, Data Engineering
DOCUMENT TYPE: Talent Assessment
JURISDICTION: Pakistan
CONFIGURATION: hr.local.md loaded
SENSITIVITY: CONFIDENTIAL -- HR AND HIRING MANAGER USE ONLY
INTERNAL TALENT ASSESSMENT: Team Lead, Data Engineering
================================================================
ROLE REQUIREMENTS:
Critical: Technical leadership; Spark/Airflow/dbt expertise; people management (2-3 engineers)
Important: External stakeholder communication; strategic thinking
Nice-to-have: Experience at scale; cross-functional influence
--- CANDIDATE: Zara Hussain -------------------------------------
Current role: Senior Data Engineer, 3 years
Fit assessment: STRONG MATCH
Readiness: READY IN 6 MONTHS
Critical requirements:
DEMONSTRATED Technical leadership: led data warehouse migration — 30TB
delivery, on time, peer-endorsed project ownership
DEMONSTRATED Data infrastructure: 3 years on Spark/Airflow/dbt stack;
project-level expertise confirmed
DEVELOPING People management: informal mentoring of 2 engineers is a
positive signal; no formal management yet — EXPERIENCE GAP
Important requirements:
DEVELOPING Stakeholder comms: identified as development area in review;
gap is real but manageable with structured coaching — SKILL GAP
DEVELOPING Strategic thinking: not yet evidenced at org level; shows
at project level
Development gap: Experience gap in formal management; skill gap in
external stakeholder communication
Career intent: Expressed leadership interest in last performance review
Retention risk: HIGH if passed over for this role
RECOMMENDATION: Strong internal candidate. Have the succession conversation
before posting externally. If Zara is interested, design a structured
6-month plan: assign formal line management of two engineers now, pair
with a management mentor, and create 3 stakeholder-facing opportunities
in the next quarter.
Suggested development plan:
Month 1-2: Formal line management of two junior engineers (with support)
Month 1-3: Weekly coaching session with Head of Analytics on stakeholder dynamics
Month 2-4: Lead two cross-functional project status meetings with business stakeholders
Month 5-6: Solo stakeholder presentation to EdTech leadership team
Review at 6 months: re-assess readiness for full Team Lead appointment
-----------------------------------------------------------------
--- CANDIDATE: Ahmed Malik ---------------------------------------
Current role: Data Engineer, 2 years
Fit assessment: DEVELOPING — not ready now; strong pipeline
Readiness: READY IN 12 MONTHS
Critical requirements:
DEMONSTRATED Data infrastructure: technically strong on stack; 2 years
of solid delivery
DEVELOPING Technical leadership: early signals positive; not yet
demonstrated at project level — EXPERIENCE GAP
ABSENT People management: too early in career for this role now;
no evidence of readiness
Important requirements:
DEMONSTRATED Stakeholder comms: unusually strong for his experience —
genuine differentiating asset
LIMITED Strategic thinking: not yet applicable at his level
Development gap: Experience gaps across leadership and management dimensions;
timeline to bridge: 12-18 months with structured investment
Career intent: Interested in growth; not specifically in people leadership
— motivation alignment needs exploration
Retention risk: MEDIUM — growing; will need a development signal soon
RECOMMENDATION: Not for this role now. Invest in the pipeline.
Have a development conversation: acknowledge his trajectory, explain
the timing honestly, assign one junior engineer for informal mentoring,
and set a 12-month checkpoint. His stakeholder skills are a genuine
asset — consider a Business Analyst rotation to develop complementary skills.
-----------------------------------------------------------------
OVERALL RECOMMENDATION:
Assess Zara for this role before posting externally. Her management
experience gap is an EXPERIENCE GAP, not a SKILL GAP or MINDSET GAP —
bridgeable with structured support in 6 months. Retaining and developing
Zara costs less and carries less risk than an external hire. Ahmed is a
strong pipeline investment; make that visible to him with a development plan.
================================================================
The /match output is a structured analysis, not a hiring decision. HR and the hiring manager review it together, consider factors the assessment may not capture (team dynamics, business timing, candidate conversations), and make the final call. Never share a talent assessment with the employee being assessed without HR and manager review.
The Succession Conversation
The /match output gives Omar the analysis. The succession conversation with Zara requires something the tool cannot do: a human conversation that builds commitment without creating a legal or relational promise.
The /match skill provides a conversation guide:
| Stage | What to Say | What NOT to Say |
|---|---|---|
| Opening | "We see you as someone with significant potential here and we want to invest in your development." | "We've been watching you for the Team Lead role." |
| Middle | "If your performance continues on this trajectory and you develop [specific areas], a leadership role becomes realistic in [timeframe]." | "You will definitely be promoted to Team Lead in six months." |
| Invite | "What does your career ambition look like? Is people leadership something you actively want?" | Assuming they want what the org wants to offer. |
| Close | Agree one concrete next step. Set a follow-up date. | Leaving the conversation without a specific commitment. |
The distinction between "a leadership role becomes realistic" and "you will be promoted" is not semantic evasion. It is the difference between a pathway and a promise. Promises that cannot be kept damage trust more severely than no conversation at all.
Modelling the Structural Impact with /org-planning
If Zara accepts the Team Lead role, two structural questions emerge immediately: who inherits her current position (or does that position disappear?), and does Zara's new span of control fall within healthy benchmarks?
/org-planning model the impact of promoting Zara Hussain to Team Lead
Current state:
Head of Analytics (Omar Farooq): 3 direct reports
- Senior Data Engineer (Zara Hussain)
- Data Engineer (Ahmed Malik)
- Data Analyst (position)
Proposed state:
Head of Analytics (Omar Farooq): 2 direct reports
- Team Lead, Data Engineering (Zara Hussain): 2 direct reports
- Data Engineer (Ahmed Malik)
- [Backfill: Junior Data Engineer — to be hired]
- Data Analyst (position)
Check: span of control, IC-to-manager ratio, structural risks
Sample output:
## Org Planning: Data Engineering Team — Proposed Restructure
### Current State
Omar Farooq (Head of Analytics)
├── Zara Hussain (Senior Data Engineer)
├── Ahmed Malik (Data Engineer)
└── [Data Analyst]
Span of control: 3 | IC-to-manager ratio: 3:1
### Proposed State
Omar Farooq (Head of Analytics)
├── Zara Hussain (Team Lead, Data Engineering) — NEW ROLE
│ ├── Ahmed Malik (Data Engineer)
│ └── [Junior Data Engineer — backfill hire]
└── [Data Analyst]
Span of control (Omar): 2 | IC-to-manager ratio (org): improving
### Benchmark Analysis
| Metric | Healthy Range | Proposed State | Assessment |
|--------|---------------|----------------|------------|
| Span of control (Omar) | 5–8 reports | 2 reports | ⚠️ Narrow — consider scope expansion |
| Span of control (Zara) | 5–8 reports | 2 reports | ⚠️ Narrow — plan for growth |
| IC-to-manager ratio | 6:1–10:1 | 2:1 initially | ⚠️ Top-heavy until backfill hired |
### Structural Risks
1. Omar's span drops to 2 direct reports — below healthy minimum
→ Consider whether Data Analyst should also report to Zara, or add scope
2. Zara managing 2 engineers is a light load for a Team Lead role
→ Backfill hire and growth plan should be concurrent with promotion
### Recommendations
- Proceed with promotion; flag that Zara's team needs to grow to 4–5 in
12 months for the role to have appropriate scope
- Review whether Omar should absorb additional scope (cross-functional
project leads, a third team) to restore healthy span of control
- Revisit org structure at 6-month mark once backfill is in seat
Exercise: Internal Talent Review
Type: Applied Practice
Time: 35 minutes
Plugin commands: /comp-analysis, /match, /org-planning
Goal: Identify the highest-priority succession risk in your organisation and produce a structured internal assessment for the most viable internal candidate
Step 1 — Map Your Succession-Critical Roles
Identify three to five roles in your organisation (real or scenario-based) where an unexpected vacancy would create significant operational risk. For each role, note:
- Role title and current holder
- Why it is succession-critical (unique skills, key relationships, critical knowledge)
- Estimated tenure remaining (low / medium / high certainty)
- Known internal candidates (name, current role, rough assessment of readiness)
Step 2 — Benchmark Compensation for the Highest-Priority Role
For the role you assess as highest-priority, run /comp-analysis:
/comp-analysis [Role title]
Role context: [Company size, sector, location, management scope]
Internal candidate context: [Current salary if known; equity considerations]
Review the percentile bands. Identify where a promotion offer would land, and whether any internal equity issues arise.
Step 3 — Run /match for Two Candidates
For the highest-priority role, assess two internal candidates:
/match [Role title]
Role requirements:
Critical: [list]
Important: [list]
Nice-to-have: [list]
Candidates:
Candidate 1: [Name] — [Current role, years in role]
- [Relevant strengths]
- [Known development areas]
- [Career intent if known]
Candidate 2: [Name] — [Current role, years in role]
- [Relevant strengths]
- [Known development areas]
- [Career intent if known]
Review the six-dimension output for each candidate. Identify the readiness classification and the primary development gap for each.
Step 4 — Model the Structural Impact
If your strongest candidate were promoted, what changes in the org structure?
/org-planning model the structural impact of [Candidate name] moving to [Role]
Current structure: [describe current reporting lines]
Proposed structure: [describe proposed reporting lines]
Check: span of control, single points of failure, backfill requirements
Step 5 — Draft a Succession Recommendation
Write a one-page succession recommendation covering:
- Which candidate you recommend, and at what readiness classification
- The development plan for the READY IN N MONTHS gap (if applicable)
- The compensation range based on
/comp-analysis - The structural adjustments needed based on
/org-planning - Whether you recommend having a succession conversation now, and what you would say
Deliverable: A succession recommendation document with /match output, /comp-analysis benchmarks, /org-planning structural model, and a one-page HR recommendation narrative.
The succession recommendation and candidate assessments you produce here feed directly into the people analytics work in Lesson 13 and the capstone lifecycle exercise in Lesson 14.
Try With AI
Use these prompts in Cowork or your preferred AI assistant.
Reproduce: Assess two internal candidates for a leadership role.
I need to assess two internal candidates for a Team Lead role.
Role: Team Lead, Data Engineering
Critical requirements: Technical leadership, Spark/Airflow/dbt expertise,
people management of 2-3 engineers
Important requirements: Stakeholder communication, strategic thinking
Candidate 1: Zara Hussain — Senior Data Engineer, 3 years
- Led the data warehouse migration project
- Mentors two junior engineers informally
- Development area: external stakeholder communication
- Expressed leadership interest in last review
Candidate 2: Ahmed Malik — Data Engineer, 2 years
- High potential, technically strong
- No management experience; early in career for this level
- Unusually strong stakeholder skills
- Interested in growth but not specifically people leadership
Assess each candidate across six dimensions: critical skills, experience,
performance trajectory, readiness indicators, development areas, and
motivation. Classify each as READY NOW / READY IN 6 MONTHS / READY IN 12
MONTHS / DEVELOPING / NOT A FIT. For the strongest candidate, design a
3-step development plan.
What you are learning: The six-dimension framework forces a structured assessment that surfaces the type of gap (experience, skill, or mindset) — not just whether a gap exists — because each gap type requires a different intervention.
Adapt: Apply the assessment to a role in your own organisation.
I need to assess an internal candidate for a role in my organisation.
Role: [Your role title]
Critical requirements: [List 2-3 must-haves]
Important requirements: [List 1-2 significant requirements]
Candidate: [Name or anonymised description]
- Current role: [Title, years in role]
- Known strengths: [2-3 specific examples with evidence]
- Known development areas: [1-2 specific gaps]
- Career intent: [What they have expressed, if anything]
Assess across the six dimensions. Classify readiness. Identify the gap
type for each development area (experience gap / skill gap / mindset gap).
Recommend one specific development action for the most critical gap.
What you are learning: Moving from a textbook scenario to your actual organisation's people reveals how much contextual knowledge HR holds — and how a structured framework helps surface and communicate that knowledge more consistently.
Apply: Design a succession plan for a critical role.
I need to design a succession plan for a role that is critical to my
organisation.
Role: [Title]
Why critical: [What makes this role hard to replace — key relationships,
unique skills, institutional knowledge held]
Current holder: [Context — tenure, estimated longevity in role]
Internal candidates (at any readiness level):
[Candidate 1]: [Brief profile]
[Candidate 2]: [Brief profile — or "no current internal candidates"]
Please:
1. Classify each candidate's readiness
2. Design a 12-month development roadmap for the strongest candidate
3. Identify whether external hiring needs to run in parallel with
internal development
4. Propose the structure for a succession conversation with the
strongest internal candidate — what to say and what not to say
What you are learning: Succession planning is not a one-time assessment — it is an ongoing programme. This prompt produces a plan that can be revisited quarterly as candidates develop and circumstances change.
Flashcards Study Aid
Continue to Lesson 10: Institutional Knowledge Capture →