Owner decision
Did the hire fail, or did the business withhold context, authority, and support?
A hire did not receive a fair operating test when the business hid material context, kept normal decisions with the owner, denied access, changed the mandate, or left cross-functional resistance unresolved. Separate role fit from the conditions the company created.
Use this now: Map mandate clarity, context, authority, access, support, resistance, output, and elapsed time before deciding what failed.
Owner worksheet
Failed-hire attribution review
| Check | Write down |
|---|---|
| Expected performance | State the capability, behavior, decision, and result the role was expected to produce, with the evidence and time available. |
| Context supplied | List strategy, priorities, history, customer facts, constraints, and success criteria provided to the hire and when each arrived. |
| Authority released | Compare the written decision rights with approvals the owner retained in practice, including frequency, waiting time, and reversed decisions. |
| Resources and support | Record people, budget, systems, access, onboarding, and cross-functional support promised versus actually available. |
| Feedback and correction | Log the performance feedback, coaching, operating cadence, explicit warning, and opportunity to correct before the conclusion. |
| Attribution decision | Separate evidenced capability or conduct failure from missing context, authority, resources, or support; name the repair required before rehiring. |
Close the decision: Do not label the person or system as the cause until the same review shows what was expected, enabled, observed, corrected, and still failed.
Worked example
Illustrative senior-hire failure attribution test
Illustrative only: Illustrative operating example only; replace inputs with verified business evidence and do not present the example as a universal benchmark or achieved result.
| Step | Illustrative input | Replace with your evidence | Completed test or status |
|---|---|---|---|
| Expected result | Illustrative sales leader was expected to establish a qualified pipeline review and forecast by day 60. | Signed role scorecard and start-date baseline. | Expectation is time-bound and observable. |
| Context and access | CRM access arrived on day 24; pricing exceptions and customer-history files remained owner-only. | Access logs and information inventory. | The business withheld inputs needed for the expected result. |
| Authority and support | Leader could coach reps but could not change territories, approve normal discounts, or require forecast updates; sponsor skipped three of four check-ins. | Delegation record and meeting history. | Authority/support defects are tested separately from competence. |
| Competence evidence | Leader produced a usable pipeline definition but two submitted forecasts omitted documented close criteria after feedback. | Work samples, feedback, and revision history. | The illustrative evidence shows both system and role-performance defects. |
| Falsification close | If a further trial is appropriate, agree a review period based on the work and risk, repair access and authority, and check the same output again. | Repair receipt and post-repair work sample. | Decision: do not label the hire alone as the cause yet. |
Decision produced: Where continued work is appropriate, correct confirmed role defects and review performance again. Do not delay urgent safety or misconduct action for this illustrative exercise.