🧠 Declarative vs. procedural knowledge – why some hiring processes fail?

Many companies know how to hire.

They’ve got the job spec, a clear EVP, and someone internally to manage the process.

That’s DECLARATIVE knowledge – knowing what to do.

But when the process stalls? When candidates ghost, offers fall through, and engagement quietly dies?

That’s when they realise they’re missing something else… aka PROCEDURAL knowledge – knowing HOW to apply that knowledge in real life.

How to:

➤ Read the subtext behind a candidate’s hesitation
➤ Spot a flight risk early and realign the offer
➤ Design a process that feels tailored, not transactional
➤ Communicate expectations without creating friction
➤ Keep momentum without pressure

These aren’t bullet points on a checklist.

They’re the skills that come from experience – the kind you build over hundreds of nuanced searches, not by following a script.

If your hiring process looks fine on paper but keeps stumbling in practice…

You’re not alone.

And it’s likely a procedural problem – not a declarative one.

Do you want to build a hiring process that actually lands the right people (and keeps them engaged until day one)?

Let’s talk. ðŸ“ž