The hiring toolkit

Use these pages to investigate, recommend and record a hiring decision. A people leader, operator, recruiter or founder can run the sequence. Name who can decide the role's scope and budget, who can authorise the offer, and who will manage the work after the start. These may be different people.

If you have not decided whether to hire, begin with the First-Move Worksheet. If the role is agreed, complete the Role Decision Sheet before sourcing. Use the interview guide and work sample with shortlisted candidates, then complete the decision and handover records. The renewal worksheet and team check are for the work that follows.

The filled examples continue Chapter 9's hypothetical 15-person agency hiring a client-delivery coordinator. The company events, candidate answers and later observations are invented teaching material. They are separate from the real strategist failure described elsewhere in the book.

The First-Move Worksheet

Before opening a vacancy, write down the outcome that is missing. A job title can wait until you know which work needs doing and why it is not happening.

The missing outcome. What should happen, for whom, and what evidence shows that it is not happening now?

In the example, client hand-offs are late and risks become visible too late for the delivery lead to act. The team examines four recent delayed jobs rather than starting with the founder's request for an operations manager.

The cause you need to test. Is the problem capacity, unclear ownership, missing authority, a skill gap, an unnecessary task or something else? Write the competing explanations. Do not settle this by choosing the most confident person in the room.

The founder thinks a senior operator is missing. The delivery lead thinks approvals and changing priorities are the main problem. They reconstruct who could decide at each delayed hand-off.

The alternatives to a hire. Consider removing work, simplifying it, reassigning it with realistic capacity, providing support for a temporary need or waiting. Name the cost of each option, including the work displaced and the burden on the people already there. Use Chapter 3's cost example where it helps.

The agency tries one shared delivery list, an approval owner and deputy, and removes a duplicate report. It runs the trial for two weeks before deciding what remains.

The decision and its condition. What would justify hiring? What would make you pause? Who decides, and on what date will you inspect the evidence?

Approvals improve, but necessary coordination still takes two account managers away from client work. Neither has spare capacity. The delivery lead proposes a coordinator, with the full employment and training cost included in the budget. The founder approves the hire and the authority arrangement. Without that agreement, the lead would recommend changing the role or pausing the search. Record the decision and any unresolved condition. Do not describe unapproved authority as part of the offer.

Your completed worksheet should end with a decision: hire this work, test a smaller change, use temporary support, or do not hire now. "We need someone good" does not yet tell you what to do.

The Role Decision Sheet

This short teaching form helps you settle a role before meeting candidates. It is not a substitute for a specialist role standard. Answer the prompts plainly, then ask the people who do and depend on the work to challenge them.

In our fuller method, the Job Map describes the role and the Right Person Profile, or RPP, records the assessment requirements. This sheet is a teaching aid, not a replacement for either complete client template.

Purpose and work. Why does the role exist, and what will the person spend time doing?

The client-delivery coordinator keeps the delivery list current, checks dependencies, confirms owners and dates, follows up and raises risks early. The role exists to make delivery problems visible while there is still time to act.

Ownership and authority. Who owns each important outcome, who contributes, and who decides when priorities conflict? What belongs to an adjacent role? Who acts when the decision-maker is absent?

The coordinator owns the current delivery record and agreed follow-up. The delivery lead allocates capacity and decides priorities, with a named deputy. Account managers own client promises and updates. Specialists own work quality. The founder retains contract and price exceptions. The coordinator cannot commit the team to a new client deadline.

Requirements and evidence. Which capabilities are essential on arrival? What could be learned, with what support? What evidence will you seek for each requirement?

Essential evidence: tracking dependencies, setting out priorities, writing clear updates and escalating within authority. The interview examines relevant prior examples. The fictional work sample examines a specific pressured hand-off. Agency terminology can be learned through guided work with the delivery lead. Familiarity with the agency's particular task software is useful, but not a separate rejection rule.

Conditions and promises. What pay, hours, location, support, authority and difficult conditions can you actually offer? What can be negotiated, and what cannot?

Publish the pay range and required overlap window. Explain routine chasing, changing client requests and the emergency rota. Offer training in agency dependencies. Do not promise permanent availability, instant autonomy over priorities or a guaranteed promotion.

Measures and unresolved questions. What work will show whether the role is helping? What remains uncertain? Who will settle it before the offer?

Check whether records are current, risks reach the delivery lead before promises fail, and follow-ups close. Distinguish delays within the coordinator's control from decisions owned elsewhere. Resolve the deputy arrangement before the search. Review whether the role has enough authority during onboarding.

Before signing off, take one recent incident through these answers. If two people still claim the same decision, record the conflict and have the accountable leader settle it. Do not average conflicting accounts into language vague enough for everyone to agree.

A bounded route from sourcing to shortlist

Publish or share the role conditions and steps. Use applications, referrals and direct outreach where they can reach relevant people. Do not treat applying, being unemployed or needing a change as evidence against capability.

Set the first-screen criteria before reading responses. In the coordinator example, request a short description or existing example of managing competing hand-offs, plus confirmation of the essential working conditions. Do not demand client-confidential material. An account of the work can be acceptable when the candidate cannot share the original.

Record enough evidence to continue, needs clarification or does not meet a stated requirement, with the reason. An unfamiliar title, an employment gap or an awkwardly written answer is not automatically the missing capability. Ask a short follow-up where information could change the decision.

For a large response, use batches and the same criteria. Keep a manageable shortlist for deeper assessment. Check uncertain exclusions and a sample of other rejections for mistakes. If the first screen does not distinguish candidates usefully, repair it. Do not compensate by asking every applicant to do a large unpaid task.

The 12-question interview guide

These prompts help you investigate job-related evidence. They are not a validated personality test or a score that predicts a hire. Select the questions relevant to the role, decide their purpose before interviewing and use the same core questions for candidates in the same process. Follow-ups can differ because their accounts will differ.

The questions use the four headings in Chapter 5 as an organising aid. They do not divide performance into measured causal shares. A preference is not a capability, and fluent recall is not the same as good work.

Make notes on the example, action, result and uncertainty. A decision not to continue is still consequential, even if you call the conversation a filter. Explain it through the requirement and evidence rather than a character label.

Human energy: the work people want to sustain

1. "Tell me about a recent piece of work you wanted to keep working on. What held your attention?"

Use this when you need to understand the tasks a person finds engaging. Listen for what they did and which conditions helped, then compare those with the actual job. Losing track of time is not required evidence of commitment. A person may do excellent work with firm time boundaries, or enjoy a task they are still learning.

Ask, "Which part would you want regularly, and which part would become tiring?" The next step is to discuss how much of that work the role offers. Check capability separately. Do not reject someone because they lack an animated story.

2. "What kind of work drains you, even when you can do it well?"

Use this to examine recurring demands the role really contains. Seek a specific task or condition, how often it occurred and how the person managed it. A difficult period may reflect overload, poor tools or conflict rather than a lasting aversion to the work. Someone may also hesitate because they think honesty will cost them the opportunity.

Ask what changed the experience and describe the demand here. If a core task remains a concern, explore support and frequency. A reasoned mutual no can follow an unresolved condition. An admission of fatigue is not itself a failure.

3. "Tell me about a time a standard you cared about conflicted with a deadline or another person's priority."

Use this when the role requires balancing quality, speed or competing needs. Look for the standard, the consequences and the decision they made. Careful work can be necessary, and rapid work can be careless. Neither is a fixed personality flaw.

Ask, "What could you decide yourself, what did you discuss, and what would you change now?" Compare the trade-off with this role. If the example does not cover an essential situation, use a relevant scenario rather than inventing an interpretation.

Context: the actual conditions of this job

4. "Describe a situation where the brief or responsibility was unclear. How did you decide what to do next?"

Use this when the job involves incomplete information or shared authority. Seek how the person identified the uncertainty, the consequences of acting and the decisions they could make. Asking a manager to clarify scope may be responsible. Acting without waiting may also be responsible when the action is safe and within the role.

Ask what they clarified, what they could progress meanwhile and what happened. Pausing or escalating can be the right action. Judge the reasoning against the authority this role provides, then investigate any consequential gap. Do not reward enthusiasm for chaos as a substitute for judgement.

5. "This role needs these working hours and response windows. Can you meet them, and what needs clarifying?"

State the actual schedule before asking. You need a clear agreement about coverage and availability. A question about flexibility might reveal an adjustable process, a time-zone misunderstanding or a real incompatibility.

Ask which requirement is unclear and what arrangement could work. Do not seek health, family or financial explanations when the work arrangement answers the question. Confirm an agreed pattern, revise an unnecessary restriction or explain why an essential condition cannot be changed.

6. "Tell me about a decision you disagreed with. What did you do, and what happened?"

Use this where the role must question and carry out decisions made by others. Seek the concern raised, the evidence used and the person's authority. Supporting a settled decision can be sensible. So can continuing to raise a concern when new evidence, safety or serious misconduct requires it. Agreement is not always good judgement, and disagreement is not automatically stubbornness.

Ask what would have changed their view and which escalation route was available. Compare their actions with the responsibilities here. Follow up an unresolved concern about conduct or judgement. Do not require unconditional obedience as the preferred answer.

Behaviours: what happened when work became difficult

7. "Tell me about a request you had to question, renegotiate or refuse."

Use this where the job requires handling competing commitments. Look for what made the request difficult, how the person assessed its impact and what they offered instead. Not everyone has previously had authority to say no. A suitable answer may involve obtaining a decision from someone who did.

Ask what the requester needed, what alternatives were discussed and what followed. If no past example is available, give a short role-relevant situation. Assess the boundary and communication rather than insisting on a dramatic refusal. Take unresolved authority questions back to the role design.

8. "Tell me about competing deadlines you could not all meet as planned. How did you handle them?"

Use this when the job requires prioritisation. Seek how they checked impact, dependencies and capacity, who could change the plan, and when others were told. Extra hours may occasionally help, but they do not explain what happens when extra effort cannot solve the conflict. A revised scope or a pause may be the better answer.

Ask what slipped, who agreed and what happened afterwards. Compare the account with a short work scenario if prioritisation is essential. Do not equate willingness to overwork with the ability to manage commitments.

9. "Tell me about a project that was going wrong. What did you do when you first recognised the problem?"

Use this where the role must respond to emerging risk. Seek the first warning, how the person checked it, what they protected and whom they informed. Analysis can be the necessary first action, particularly when acting on the wrong diagnosis would cause harm. Documentation can preserve information needed to recover.

Ask what they knew at each step and what would have justified acting sooner or waiting. Judge whether the response was proportionate to the risk. Investigate an unexplained delay or reckless action.

Alignment: a workable agreement between two sides

10. "What do you want your next role to provide, and which parts matter most now?"

Use this to compare the person's stated priorities with what you can offer. Ask for concrete conditions rather than a rehearsed career vision. Wanting income, security, learning, meaningful work or predictable hours can all be legitimate. Uncertainty can mean the person is considering a change, not that they lack ambition.

Ask which conditions are essential and which allow trade-offs. Explain the role's limits, including advancement you cannot promise. Confirm the person's understanding. Continue where an informed agreement is possible, and accept a no where it is not. A ranking alone does not decide selection.

11. "What did a previous role get right about how work should work for you, and what would you want to change?"

Use this to explore concrete working conditions. Seek examples of support, authority, collaboration or workload, without inviting confidential material. A complaint about a manager might describe poor treatment, an unclear agreement or an unresolved disagreement. It is not proof that the candidate will be difficult.

Ask what happened, what the person tried and what condition they need next. Describe the closest situation in your business honestly. If the same problem is likely here, examine whether it can change. Make the decision about that condition, rather than about whether the person spoke positively enough about an employer.

12. "The pay range and conditions are as described. What would need to be agreed for this to be a workable move?"

Use this to establish terms, not to test whether a candidate values the mission more than money. Evidence is what each side can offer and accept. Asking for higher pay may reflect the market, the responsibility or the person's priorities. You do not need their private financial story to respond.

Ask which terms need discussion, explain your limits and consider a fair adjustment where possible. Agree them in writing or accept that the move does not work. Do not ask whether the person would take a pay cut to prove fit, or infer future disloyalty from a request for more pay.

Work Drivers: the full reference list

These 32 labels give people language for discussing what they want from work. The three groups organise the conversation. They do not establish that there are exactly 32 universal human motives, that the groups are independent, or that a particular ranking predicts performance or departure.

Ask which conditions matter to the person, what those labels mean in practice and how this role might provide them. Keep importance separate from fulfilment: wanting more autonomy and reporting little autonomy in a current job are different statements. Preferences can change, and trade-offs belong in a conversation. Do not compare two people's ranks as though they were ability scores.

Functional: practical conditions (11)

• Compensation & Rewards: pay and other financial rewards.
• Benefits & Security: benefits and the security around the work.
• Work-Life Balance: the relationship between work and the rest of life.
• Working Conditions: the physical and practical setting.
• Location & Flexibility: where work happens and the choice available.
• Company Reputation: the standing of the organisation.
• Industry & Sector: the field in which the work takes place.
• Role Clarity: understanding responsibilities and expectations.
• Advancement Path: opportunities to progress.
• Stability & Predictability: how dependable the work and its conditions are.
• Work Pace & Intensity: the speed and demands of the work.

Social: relationships and standing (11)

• Belonging & Community: feeling part of a group.
• Team Collaboration: working with others.
• Leadership & Management: the experience of being led and managed.
• Culture & Values: how the organisation behaves and what it values.
• Recognition & Appreciation: having contribution noticed and valued.
• Influence & Impact: having a voice that affects what happens.
• Mentorship & Support: help and guidance in developing.
• Diversity & Inclusion: a workplace that welcomes and includes difference.
• Service to Others: helping people through the work.
• Professional Network: the relationships the work creates.
• People Leadership: opportunities to lead other people.

Emotional: meaning and experience (10)

• Professional Authority: being trusted for expertise.
• Challenge & Achievement: difficult work and the experience of accomplishing it.
• Learning & Growth: developing knowledge and capability.
• Autonomy & Independence: room to decide how to work.
• Creativity & Innovation: opportunities to develop new ideas or approaches.
• Purpose & Meaning: finding the work worthwhile.
• Variety & Adventure: change, novelty and unfamiliar work.
• Mastery & Expertise: becoming deeply capable in a field.
• Risk & Entrepreneurship: creating or building under uncertainty.
• Passion & Fulfillment: finding the work personally engaging and satisfying.

Use the labels as prompts, not findings about someone who has not explained their meaning. An important preference the role cannot meet deserves a clear discussion. The person may consider a trade-off, or either side may recognise an essential conflict. Capability evidence remains a separate part of the decision.

Three roles, with the conditions left in

These are possible role designs, not personality profiles for everyone with the title.

An operations manager reducing disorder. If priorities change daily and authority is unclear, look for evidence of establishing a workable decision process while keeping essential work moving. Do not require someone who enjoys permanent chaos. Reducing that chaos may be the reason for hiring. If authority is already clear and the main need is careful maintenance, the evidence you seek will change.

An account manager balancing client and delivery needs. Where requests regularly exceed agreed scope, examine a real example or scenario involving a reasonable request the team cannot absorb. Look for how the person checks impact, offers options and obtains the right decision. Warmth alone does not show whether someone can hold a boundary. If account managers cannot negotiate scope, examine their escalation instead.

A media buyer responding to uncertain results. Where live spend needs close oversight, examine how the person checks data quality, investigates changes, limits exposure within their authority and communicates uncertainty. Pausing to analyse may be exactly right. If the role is mainly longer-term research with a separate incident team, constant crisis response may be the wrong test. Technical knowledge and demonstrated skill still need assessment by someone who understands the work.

A fair work sample: the Firefighter Morning

This is the coordinator exercise from Chapter 9. Adapt the problem to your role before using it. A coordinator should not be assessed as though they were the senior operations manager, the technical specialist or the person who owns the client contract.

The candidate brief

Purpose. Show how you would coordinate a difficult delivery morning. This is a fictional case. We are assessing your handling of information, priorities, decision rights and communication, not your knowledge of our clients.

Situation. You are the client-delivery coordinator at a 15-person agency. A client deliverable is due at noon. At 9 am, a reviewer finds an error that may affect the recommendation. The specialist needs 30 minutes to assess it. The account manager is on a call until 9.30 am. The delivery lead is available. Another client expects a routine update at 10 am.

Authority. You can organise hand-offs, update the delivery record and follow up actions. The delivery lead decides priorities and capacity. Account managers own client promises and messages. Specialists decide whether their work is technically sound. You cannot approve the recommendation or promise a new client deadline.

Deliverables. Give us your first-hour plan, a short internal update and one important uncertainty or action you would defer. Brief notes are enough. Explain your choices in the discussion.

Time and access. Allow about 30 minutes to prepare and 20 minutes to discuss. This is not a typing-speed test. Tell us if you need an adjustment or a different accessible format. Ask questions about the brief. You do not need information about our real business. If a clarification changes a material fact, we will give it to every candidate.

Tools. Normal tools and optional AI are allowed on this fictional material. Tell us what you used and check the result. We can provide equivalent tools if needed. We will not ask for personal account access or private notes. The discussion concerns your decisions and the submitted work.

Payment and use. This brief is the entire short exercise. It is not live client work and we will not use your output commercially. Any substantial additional assignment will have payment, scope and use agreed beforehand. Tell us if the stated time does not allow a fair attempt, so we can resolve that before adding work.

What follows. The delivery lead will assess the published criteria below, discuss your answer with you and combine that evidence with the interview. We will explain the next step and its date. You will have time to ask about the role and correct any factual misunderstanding.

Criteria set before the answers arrive

The assessor records evidence supports the requirement, needs follow-up or evidence raises a concern, with the passage or action behind the judgement. These labels organise notes. They are not a validated prediction score, and they should not be totalled into a supposedly scientific answer.

• Understanding the risk. Does the response establish what the error might change, without inventing facts? Does it distinguish checking from guessing?
• Priorities and dependencies. Is the order reasonable given the time and people available? Does it account for the routine update as well as the urgent issue?
• Decision rights. Does the response get the right person to decide, without making promises outside the coordinator's authority?
• Communication and uncertainty. Can another person see the current problem, owner, next action and unresolved question? Are assumptions visible?

Use a qualified assessor who knows the work. Read the answer against each criterion before discussing general impressions. Ask relevant follow-ups and retain the original response alongside any correction. A different sensible sequence can meet the criteria. There is no requirement to guess the author's favourite wording.

Two illustrative answers

Both responses below are invented. They show how evidence can differ without reducing people to good and bad types.

Candidate A:

I would ask the specialist what needs checking and confirm when they can report back. I would alert the delivery lead now that the noon delivery is at risk, without assuming it must move. I would leave a short update for the account manager before their call ends. I would check who is preparing the 10 am update and keep it on the list. At 9.30 I would bring the specialist's finding to the delivery lead and account manager so they can agree the next action and client message. I would not approve the recommendation or promise a revised deadline.

This supports the authority and communication requirements. It also gives the routine update an owner rather than ignoring it. The assessor still needs to ask how A would record and follow up the actions. Nothing here proves familiarity with the agency's technical work or consistent performance over time.

Candidate B:

I would reassure the client immediately that we will still deliver at noon. Then I would bring the specialist and delivery lead together, put the correction first and move other tasks until it is done. I would put all the actions on the shared list and ask someone else to send the routine update. The client needs confidence that someone is in control. Once the team has a plan, I would send a fuller update through the account manager.

B identifies coordination, a shared record and the need to protect the routine update. Those are useful parts of the answer. The concern is the initial promise and unilateral reprioritisation, before the error is understood and outside the stated authority. Confidence is not the evidence being assessed.

Both candidates get the same follow-up: "The specialist now says the correction needs two more hours. What changes in your response?" A asks the delivery lead to decide the priority and the account manager to agree the revised client message. B still assumes the coordinator can commit the team to a new deadline. The concern therefore remains after clarification.

The assessor records that limit, rather than diagnosing B as reckless in every setting. Another role might give B more authority. This one does not. If the answer had changed after clarification, that change would also belong in the evidence.

Before adapting this exercise

Choose a problem that represents important work and can be assessed fairly in the time. Tell candidates what they can use, what information is missing and how they can ask questions. Set the criteria before you see answers. Remove details that test accidental familiarity rather than the requirement. Agree payment for substantial work and never turn the process into a source of free client output.

The decision and offer record

For each essential requirement, record the relevant interview answer, work evidence, concern and follow-up. Write the recommendation after examining those rows. Two reviewers should make their first notes separately where possible, then compare the evidence behind differences.

Completed example. Candidate A has stronger evidence of coordinating priorities within authority and communicating uncertainty. A has less agency experience. Candidate B has more agency experience, but the work sample and follow-up leave an unresolved concern about client promises and priority decisions. A is preferred for this role, with training in agency dependencies named as a condition of the plan.

The trade-off. A needs to learn the agency's hand-offs from client approval through production and review. For the first two weeks, the delivery lead sets aside half an hour each morning to work through A's list, check dependencies and explain unfamiliar hand-offs. This replaces part of the lead's internal reporting work. If that time is unavailable, revisit the choice. The teaching period is an illustrative commitment, not a guarantee that A will have learned everything by its end.

The pause or no. Do not make an offer if an essential requirement remains unsupported in every candidate, or if the employer cannot supply a condition on which the choice depends. Record the missing evidence and choose whether to seek it, change the role or continue the search.

The offer conversation. Explain the role's value, difficult conditions, pay and support. Ask which terms need discussion. In the example, A and the employer agree a daily overlap window and an emergency rota. They agree pay within the published range and training support. The employer does not promise a promotion or continuous on-call work. If necessary hours cannot be reconciled, either side can decline.

The handover. Give the manager the role and authority record, work evidence, remaining uncertainties and commitments made to the candidate. Confirm who supplies each commitment and by when. Include the person's own account of what needs to work, with their understanding of what will be shared. Private interview notes do not all belong in a manager's file.

The First-90-Days Renewal Worksheet

Use this before the start, then update it with observed work. It does not assume that the original selection was right or wrong.

First useful work and support. What will the person own first? What information, access and learning do they need? Who provides each?

A begins with a bounded delivery list and guided review of dependencies. The delivery lead supplies training and introduces the deputy and client owners.

Promises to check. Which conditions did both sides agree? What uncertainty from selection needs watching?

Check the overlap window, emergency rota, training time and authority route. Observe the agency-specific learning that the work sample did not establish.

Observation and competing explanations. What happened, against which expectation? What does the person say? What evidence would distinguish a skill gap, workload, unclear authority, missing support or a mistaken initial assessment?

At day 30, the founder has sent urgent work directly to specialists outside the list. A has also missed a follow-up despite having the information. Record both. Do not turn either into the complete explanation.

Action, owner and date. What changes, who has agreed to it, who makes it happen, and when will you check? Record a requested change separately if the person who can authorise it has not agreed.

The founder agrees to route priority changes through the list for two weeks. The delivery lead checks whether this happens. A practises and uses a follow-up check. They review the next set of hand-offs on day 45. If the founder had refused the change, that condition would remain unresolved. It would not be recorded as support A had received.

Later observation and next decision. What changed? What remains unresolved? What do you do next?

At day 45, fewer priority changes are missing from the list, but one hand-off still slips. The manager examines that incident before expanding responsibility. The example does not claim a final success or retention result.

Set check-in dates that match the work and adjust them when needed. A quieter person, slower reply or change in language can prompt a respectful conversation, but does not diagnose disengagement. Keep the enquiry about work conditions and support. Do not demand a personal explanation to satisfy an employer's theory.

Four quick checks

1. Choosing a recruiter

Basic questions about salary, location and timing are necessary. They do not reveal the recruiter's motives by themselves. Ask how the recruiter will understand the work, test conflicting accounts, assess candidates and explain a recommendation. Inspect a suitably anonymised example of the reasoning, not only an attractive presentation.

Agree fees, responsibilities, communication, replacement terms and who owns the decision. Ask what happens when the brief is wrong or the search finds no suitable person. A useful answer makes the process and its limits visible. A confident promise is not a substitute.

2. The AI-Tool Buyer's Test

Ask what the tool actually does, which decisions it affects and what evidence supports that use in a comparable setting. Establish what data it needs, where that data goes, how it is retained and who can inspect an error. Then ask how a candidate can correct a mistaken record and who reviews a consequential exclusion.

Test failures as well as convenient outputs. If the tool screens for a required working window, check whether it confuses a person's current location with their availability. Review a sample of excluded records and investigate patterns in mistakes. A human approval button does not fix an unchecked recommendation, and a tool that keeps repeating a biased rule does not become fair through consistency.

Start with a bounded use, name the owner and decide what result would make you stop or change it. The division of work should follow evidence and accountability, not a vendor's promise that either a machine or a person is incapable of bias.

3. Reviewing a hire that is not working

Check the original requirements, evidence and promised conditions alongside what happened after the start. Ask what the person can do, what the role permits, what support arrived and what changed. Investigate conduct directly when conduct is the problem. Neither blaming the person nor blaming the system is a diagnosis.

Write the competing explanations and the next evidence needed. Use the renewal worksheet to assign an action and review date. If a central capability was never established, say so. If the employer broke a commitment, say that too. Learning from a failure does not make it a success.

4. The pre-action pause

Before a consequential decision, ask what you know, what you are assuming, who sees a different part of the situation and what could change your view. Then decide whether another question is worth the delay. Curiosity should improve the decision, not make it impossible to reach one.

The Team-Shape Check

Look beyond the next vacancy. What work does the team need to deliver, which roles contribute to it and where are ownership or capability missing? Examine dependencies and avoid making every good person responsible for compensating for an unclear role beside them.

Separate reliable contribution, unmet requirements and harmful conduct. Someone who meets a steady need well does not become a problem because their work is less visible. Ask what would stop happening if that contribution disappeared.

Use a few measures tied to the work, such as quality, delivery promises met, avoidable rework and unresolved hand-offs. Read them with the people doing the work so you understand their limits. Do not roll them into a single score that pretends to capture the value of a team.

Before the next hire, decide which role you would redesign, what capability is missing and what difference the hire should make. Give that decision an owner and a later check. The useful result of this toolkit is a clearer choice followed by action, with enough of the reasoning written down to learn from what happens.