What a Working Process Looks Like

Rather than a summary, a description of the arrangement these notes point toward.

The principles in “What a Working Process Looks Like” become easier to maintain when ownership and time spent are visible. Teams evaluating this project guide can use it to coordinate the administrative work around assessment, identify stages that repeatedly expand and plan capacity, while keeping the hiring decision tied to job-relevant evidence instead of raw activity totals.

For an independent benchmark, compare the process with U.S. OPM assessment resources; the useful test is whether the local method remains job-related, proportionate and explainable.

The foundation

A written job analysis: five to eight requirements, each with why it matters and what evidence would demonstrate it.

Produced with people who do the job, from real incidents rather than from the advertisement.

Reviewed before each hiring round and rewritten when the role changes.

The design

Each requirement assigned to exactly one method that can actually assess it.

At least one assessment resembling the actual work.

Two or three stages, not five.

Total candidate time under about four or five hours, published at application.

And any stage that cannot state what decision it makes is removed.

The instruments

A short work sample, scoped to hours and using the tools the job uses.

A structured interview: the same questions, the same order, drawn from critical incidents, with written follow-ups.

Rubrics with three to five criteria and a short scale, each level described in terms of what the answer contains.

Thresholds rather than rankings on small differences.

The people

Assessors trained on judgement rather than briefed on the form.

Calibrated before each round and quarterly.

Scoring independently before any discussion.

And nobody assessing alone on a decision that matters.

The candidate experience

The full process, the time commitment and the salary published before application.

Format, length and criteria sent in advance.

The adjustment question asked of everybody in the same words.

A date for a decision, met.

And feedback for anybody who invested substantial time.

The records

Individual scores with evidence notes, not impressions.

The decision and its reason.

Adjustment records kept separately from assessment.

A stated retention period that somebody applies.

The measurement

Pass rate by stage, and by group, aggregated across rounds.

Dropout with reasons.

Assessor agreement.

Scores against how hires actually performed.

Seen annually by somebody who can change the process.

What is deliberately absent

Unstructured conversation carrying the decision.

Personality profiles used as scores.

Unpaid work you would use.

Proxies nobody can justify.

And any stage that has never changed an outcome.

The test

Can you state what each stage decides?

Could two assessors score the same answer the same way?

Do you know your pass rates by group?

And has anybody ever checked whether your scores relate to performance?

A process failing these is a sequence of meetings rather than an assessment.

The point

A process that cannot state what each stage decides is a sequence of meetings rather than an assessment..

Underlying all of this

Almost everything in this collection reduces to one discipline: write down what the job requires, assess that thing directly, record the evidence, and look at your own outcomes afterwards. None of it requires buying anything, and organisations that do those four things consistently outperform ones running longer processes built from instruments chosen before the requirements were known.

The recurring pattern

The recurring failure across every section here is the same: measuring what is convenient rather than what matters, then never checking whether it predicted anything. The check is an afternoon of work once a year, and it is the step that separates a process that improves from one that merely persists.