Talk it through with Aurelius
Why do we just post jobs and wait, instead of finding people?
You post the job. You wait. The board fills with resumes, or it does not — either way, you have let strangers come to you instead of choosing who you want. This is comfortable. No one can reject you if you never ask. But comfort is not a strategy. Somewhere your team already knows people worth hiring. You have simply not gone to find them. Sourcing is not a skill you lack. It is an action you have not scheduled. Fix the calendar, not the character.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
The team already understands sourcing in theory; what's missing is the will to act, so coaching carries more weight than teaching.
How the two dials adapt to you →What’s really going on
Posting a job and waiting is not sourcing — it is hoping. The work you are avoiding is naming real people and asking them directly. Choose ten names today. Assign one to each person on your team. Reach out this week. Waiting is a choice too, and a worse one.
🔒 What you’ll build togetherUnlock by starting
A moveName ten real people right now — not job titles, actual names.
A moveAssign one name to each person on your team before the meeting ends.
A moveWrite the outreach message together, then send it before anyone leaves the room.
A moveBlock one hour every week for the whole team to do outreach at the same time.
A moveLog every 'no' and why — refusal teaches more than silence ever will.
PractiseThe Ten Names · a Pod of 4 · 30 min
What changes unlock by starting
- A real list of candidates, not a job posting sitting in silence.
- A weekly habit of reaching out, instead of waiting for applicants to arrive.
- Clear evidence, within weeks, of whether your target candidates exist at all.
- Less fear of rejection, because it becomes routine data, not a verdict on you.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.