Relationship map and gaps

A relationship map identifies routes to knowledge and collaboration. It is not a list of “important people.” Begin with the decision in the relationship brief and ask what kind of experience the team lacks. You might need someone who performed similar work, someone affected by its outcome and someone who owns an internal decision. These roles are not interchangeable. A participant-experience specialist may describe difficulties at an event but have no authority to release participant names or approve a partnership. Each node should represent a known professional role and context, not a judgment about a person’s worth.

Draw three kinds of link. A direct link records actual prior professional contact and its setting. A possible introduction names an intermediary who might agree to connect two parties; it is not an established route until both the intermediary and recipient agree. A public-source link points to an article or open session that helps you understand expertise before making contact. This distinction prevents a common leap: seeing a name in a colleague’s list and writing as though the colleague endorsed you. If your own contact is old, record the last real setting rather than implying a closeness that did not develop.

Put one question above each knowledge gap. Does the team need to understand a criterion, test a hypothesis, carry out a step or approve a decision? Connect that question to relevant experience and state what the contact can establish. An event organizer can describe how her event was planned; her account alone does not prove that her approach is best for every event. If three nodes offer the same kind of experience, check whether another perspective is absent, such as a participant or an implementation team. That is a case-specific check of perspective, not a numerical quota for people.

Avoid an opaque score for individuals. Transparent criteria can help compare contact routes: relevance to the question, strength of the contact context, amount of data needed and burden on the recipient. Record reviewable facts for each criterion. “I attended her public session about forum design” is stronger evidence of relevance than “she looks influential.” If relevance is unknown, start with public material or an internal clarification. A job title or follower count does not repair a missing link to the actual question.

Use a five-column table: role, link type, answerable question, evidence of relevance and disclosure boundary. Planning may use role labels instead of names. Add a name only when necessary for the next authorized step and appropriate to store at work. Do not copy account details, email addresses or private conversations to a personal tool merely for convenience. Specify who can view the table and when it is reviewed or deleted. If the team’s data policy differs, follow it; this lesson does not create permission to process personal data.

The map should yield a short sequence: read a public source, clarify with an authorized colleague, then ask the suitable contact a bounded question if the gap remains. Update a link after a reply using a fact, such as “answered two audience-fit questions,” rather than “supports our project.” If the intermediary declines to introduce you or the recipient does not reply, do not treat a possible link as a route around their choice. Return to the same knowledge gap and seek another legitimate source. This preserves both respect and record accuracy.

Test the map by removing one name. If the work question remains, the role matters more than that individual, and another expert or public source may be suitable. If the choice rests on a witness to a specific decision, state the decision, date and permissible question; do not make that person a representative of all participants. When colleagues disagree whether a link is direct, return to a checkable event. Attending a public talk makes the speaker a public source, not automatically a team friend. Keep the link “unverified” until contact or introduction permission is established. Link direction matters too: reading someone’s work does not mean they know your project. A later message must use only the direction actually supported by evidence.