How do you preserve good judgment after the people who developed it leave?
Hiring Compass is my answer — a system built to hold what great hiring managers already know, so it doesn't disappear when they do.
What problem did I notice?
Thirteen years of watching the same thing happen: a hiring manager builds real judgment about what "strong" looks like — then a search ends, a team changes, or a new partner comes on, and that judgment disappears. The next search starts from zero, rebuilding knowledge that already existed somewhere, in a conversation nobody wrote down.
The knowledge was never the problem. No system was built to hold it.
What did I choose to believe?
The insight didn't come from a product brief. It came from years of proximity to executive-level hiring decisions — watching what hiring managers noticed first, what made them hesitate, what made them move fast. That pattern recognition was the missing infrastructure.
"The tool wasn't built because I wanted to build AI. It was built because I kept seeing ambiguity repeated across hiring managers and wanted to make it teachable."
I decided institutional knowledge should compound instead of disappearing — and that a system could hold it without replacing the judgment that created it. Three beliefs shaped everything that followed:
How did I embody that belief?
This is easier to show than to explain:
Underneath both: every hiring leader's profile holds their actual rubric and calibration history — not the job description. Every session writes back before it closes, so nothing learned in one search has to be rediscovered in the next. And a strong candidate who isn't right for one role can surface for another, but only after a real fit check, never as a shortcut.
The first version lost context mid-session and had to be rebuilt — which is exactly why the structure holds up the way it does now. The system got better because it kept failing in public, not because I designed it correctly the first time. This was built solo — every architectural, aesthetic, and philosophical decision.
What changed?
What Changed in Me.
Building Hiring Compass didn't just change how I recruit. It changed how I understand my own career.
I stopped thinking of myself as a recruiter who uses tools and started thinking of myself as a designer who builds them.
I realized that the work I've always done — translating ambiguity into structure, earning trust to access real problems, building systems that outlast me — traces back to a discipline: service design. What I actually build, I call operating environments.
I understood that institutional knowledge isn't just a recruiting problem. It's an organizational design problem. And I know how to solve it.
I learned that AI doesn't replace what I do. It finally gave me the medium to build what I've always imagined.
I stopped waiting for someone to give me the title that matched the work I was already doing.
I build systems because I care about the people who have to use them."
Editorial Note: Names and identifying details have been changed to protect confidentiality. The work itself has not.