A talent map is not a list of names. It is a picture of a market that tells you who moves, who decides, and what would make them move again. Most maps fail because they are built once, in a burst of effort, and then never touched.
What a specialist map actually holds
Four layers, in this order:
Companies. Not every employer in the sector. The twenty or thirty that actually produce the people your clients hire, plus the ones that quietly poach from them.
People. Named, with role, tenure, and the last observable change. Tenure without a date is guesswork.
Movement. Who joined, who left, who was promoted, and when. Movement is the layer that ages fastest and matters most.
Triggers. Funding, restructure, new leadership, a lost contract, a published paper. The reason someone becomes reachable.
Layers one and two are static work. Layers three and four are the map. If you only build one and two, you have a directory.
Build it from conversations, not from scratch
The cheapest map is the one assembled from work you are already doing. Every intake call, every candidate debrief, every rejection tells you something about who reports to whom and what a team is missing.
The discipline is capture. A note that lives in your head is not a map. A note pasted into your desk, attributed to the call it came from, is.
Holi builds this layer for you: paste a profile, a job spec, or call notes, and it pulls out companies, names, movements, and triggers, each with a visible source line so you can see where the claim came from. Nothing is asserted without an origin.
Keep it alive with a decay rule
Set a half-life on every entry. A movement observed six months ago is background. A movement observed last week is a reason to call today.
A simple rule that works on most specialist desks:
- Movement: useful for roughly ninety days
- Mandate or brief: roughly sixty days
- Funding or restructure: roughly six months
- Publication or public opinion: roughly thirty days
You do not need those exact numbers. You need any numbers, applied consistently, so the map surfaces recent things first instead of drowning you in every fact you have ever collected.
What to do with the map on a Monday
The map earns its place when it produces a call list. Filter on movement in the last thirty days, cross-reference against briefs you are running, and you have five conversations that are timely rather than speculative.
That is the difference between a map and a database. A database answers "who works there". A map answers "who should I call today, and what do I open with".
The failure mode to avoid
Do not map the whole market. Map the part you can actually service. A specialist desk with sixty live, well-sourced records outperforms a desk with six hundred stale ones, because the small map gets read and the big one gets ignored.
Start with your top twenty accounts and their nearest competitors. Add a layer every time you finish a call. Within a quarter it will be the most valuable asset on the desk, and it will have cost you no dedicated project time at all.