Review the Talent Framework Every Quarter

This is the full playbook from “Hire and Develop for the Skills You’ll Need Next.” The book prints a shorter version at the end of that chapter, and this page keeps every step and every example.

The Talent Acquisition and Development Framework is a working template, not a form you complete once. Review it every quarter.

Part 1. Skills-gap map. For each team member, record four things: current core competencies, each rated execute, teach, or architect; stretch competencies in active development; and single-point-of-failure flags, the capabilities only that person holds; and what this person is unusually good at relative to the rest of the roster, the strength “Put People Where Their Strengths Matter Most” will position around. For the team, record two: the capabilities your commitments for the next twelve to eighteen months require, mapped against current bench strength, and the junior-pipeline item, whether your AI-assisted workflow still generates the practice that produces the next cohort of senior judgment. Rank the gaps by how soon each becomes costly, not by how loudly people feel it now. The output is a ranked hiring and development list, each item tied to a specific business commitment and a specific date. Do not write a headcount number.

Part 2. Recruiting scorecard. For each open role, define what it must do eighteen months out, not only on day one. Cut the generic algorithmic screening question; replace it with a scoped, realistic problem drawn from sanitized real work, scoring the reasoning as well as the answer. Ask two standard questions: for a real past mistake, reconstructed in detail with the lesson stated, and for a real disagreement with a decision made above the candidate. Set one onboarding requirement: a real contribution that reaches production in week one, scoped in advance, with a mentor assigned before the start date.

Part 3. Trajectory tracking. Keep this record continuously, not at an annual review. Note who is accelerating, who has stopped improving, and who asks for scope beyond their role. Give each high-trajectory person three things: one stretch assignment with real visibility, one mentor who has done the work in question, and one explicit conversation about the next level, stated as specific evidence rather than a vague quality.

Part 4. Retention system. State every career-ladder criterion as an observable behavior or outcome, not an adjective. For example, replace “shows strong technical leadership” with “leads design reviews, resolves cross-team technical disagreements, and documents decisions others can execute without them.” Review the criteria on a fixed cadence, tied to real staffing decisions. Formalize mentor pairings, protect calendar time for them, and choose mentors for teaching ability rather than seniority alone. Allocate the training budget against the skills-gap map first and individual preference second. Address underperformance within a stated window of weeks, not quarters. Delay is itself a retention risk for everyone who performs.

Run this framework honestly and the output tells you something most staffing plans never will. Instead of how many people you are short, it tells you which future your current team is unprepared for, and how much runway you have before the business finds out.

All of the playbooks are listed on the playbooks page.