Relationship support
Key takeaways
- operating rings
- meaningful trigger
- contact card
Operating data
Playbook
A relationship map should help an executive keep promises, not rank people by influence. Use operating rings: active decisions and obligations, recurring or long-horizon collaborators, and contextual relationships needing history but no routine outreach. People move when the work changes.
Record relationship owner, organization, role, last substantive exchange, open promise, next meaningful trigger, approved channel, source, and access class. Keep notes factual and attributable. Do not collect sensitive details merely because they could someday appear useful.
Choose cadence by condition: recurring review, milestone, promised deliverable, or no outreach without an authentic purpose. The stakeholder cadence guide expands these triggers. Return vague “check in” reminders until they name real purpose.
Before contact, prepare why now, last exchange, commitments, current context, and prohibited assumptions. HubSpot record guidance explains mechanics, while organizational privacy rules control. Coordinate other owners and connect promises to operations follow-through.
Review the map quarterly for stale roles, duplicate records, excessive permissions, and commitments without a responsible closer. Remove context that no longer serves an approved purpose rather than carrying it forward indefinitely.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.