Start with a real target
Use people search when you already know the kind of person you want to reach:- a specific person
- a role at a target company
- a founder, investor, operator, or hiring contact
- someone who should be reachable through your extended network
What a result needs to show
| Field | Why it matters |
|---|---|
| Name, role, company, location | Basic target identification |
| Best connection | Who can credibly unlock the path |
| Confidence | Whether action is justified now |
| Evidence context | Why this person ranked above similar results |
| Action | Whether to request an intro, view path, save, or inspect |
Filter model
Use filters in this order:- Connection degree to control how close the route must be.
- Relationship strength to avoid weak paths.
- Current company when the target account matters.
- Role when searching by function.
- Location when geography affects access.
Good-result checklist
- target identity is clear
- strongest connector is visible
- route confidence is honest
- evidence freshness is present
- next action is obvious: view path, inspect company, or create request
Failure modes to avoid
- returning broad PDL matches ahead of reachable graph-backed targets
- showing a strong visual affordance when path status is only
limited - hiding why-ranked reasons
- making the user guess whether the result is warm, cold, or just adjacent
- showing confidence without explaining what evidence supports it
Suggested workflow
- Start with a search query and optional quick filter.
- Scan the ranking reason and connector recommendation, not only name recognition.
- Open View Paths for the top target.
- Only then move into Create Request.