00
Hire Requests

Every hire justifiedby data, not urgency.

Before a single job ad goes live, Wudd decomposes the JD, polls the team, scores automation potential, and checks internal promotion paths. Only the residual gap – what nobody and nothing else can cover – becomes a hire.

01
Four-Way Alternatives

Challenge every line in the job description.

Each responsibility in the JD is tested against four alternatives before it can justify a hire.

Absorbed
Can the team absorb it?

Team members are polled. If someone accepts the responsibility – or is already doing it – the line is covered.

Automation
Can it be automated?

AI scores each line for automation potential: quick win, medium project, or engineering effort.

Promotion
Can someone grow into it?

Existing employees with adjacent skills are identified. A development quest can close the gap.

Residual
Is it a genuine gap?

Only lines that survive all three alternatives become the residual gap – the actual justification for a new hire.

02
JD Decomposition

Break the role into atomic responsibilities.

Instead of approving a vague job title, each line of the JD is individually assessed, polled, and dispositioned.

  1. 01
    Manager submits hire request
    Specifies basis: replacement, expansion, or new role. Names the team, department, and expected outcome.
  2. 02
    JD is decomposed into lines
    Each responsibility becomes an individual record with its own disposition workflow.
  3. 03
    Team poll opens
    Team members respond to each line: accept, already doing, refuse (with reason), or abstain. Responses are firewalled from performance reviews.
  4. 04
    AI scores automation potential
    Each line gets an automation score and effort estimate. Automatable work doesn't need a human.
  5. 05
    Statistical report generated
    A frozen readiness report captures the signal pack, coverage score, peer set, and AI narrative at decision time.
03
Approval Chain

Multi-tier, evidence-based approval.

Every approver sees the full alternatives sweep, the readiness report, and the residual gap before deciding.

  1. 01
    Requester
    Submits the business case with hire basis and expected outcome type
  2. 02
    Team Leader
    Reviews team poll results and confirms capacity constraints
  3. 03
    Manager
    Evaluates alternatives sweep and approves the residual gap
  4. 04
    Employer
    Final approval with full statistical report and budget impact
04
Post-Hire Accountability

Did the hire deliver what was promised?

Scheduled checkpoints at 90, 180, and 365 days. The requester self-assesses whether the claimed outcome materialised, and a recomputed signal snapshot tracks the delta.

Day 90
Probation check

Early signal: is the new hire integrating? Are recognition patterns emerging?

Day 180
Mid-year review

Did the operational gap close? Is the team performing better than before the hire?

Day 365
Annual accountability

Full outcome assessment: met, partially met, not met, or too early to tell. Builds requester track record.

Next step

Hire smarter. Hire less. Hire right.

A system that challenges every hire request with data before it becomes a headcount. The result: fewer bad hires, more internal growth, and full accountability.