Outcome and relationship brief

Do not begin a networking plan with a target count of new contacts. Begin with a work decision that needs a perspective or collaboration outside your team. “Grow my network” gives a partnerships officer no way to select a relevant person or check progress. “Learn how local training partners are selected before drafting a proposal” identifies the knowledge needed and the decision it will serve. A relationship is not an entitlement to another person’s time. Both people may find value in the exchange, and either may decline. State what you hope to learn and what you can honestly offer. Employment at an organization does not authorize you to disclose its records or promise its support.

A relationship brief has six linked fields. First, name the operational decision: what might change after the conversation? It may be a research direction rather than a signed agreement. Second, identify the information or collaboration gap and the evidence that the gap exists. Third, describe the kind of person with relevant experience rather than selecting someone for rank or visibility. Fourth, specify shareable context: published facts or a general description of the task, excluding client lists, private correspondence and commitments made on behalf of the organization. Fifth, make a bounded initial request: one clear question or a short conversation that can easily be declined. Sixth, record authority and stopping conditions: who can approve a partnership, and when must the specialist stop or route the matter internally?

Keep output, effect and response separate. An output is something you can produce, such as a question map or a learning note. An effect is a subsequent change in work, such as better partner selection, which needs later evidence. The other person’s response is voluntary and outside your control; an accepted invitation cannot be promised as an outcome. One conversation that resolves a defined gap can be more useful than many names added to a list. Yet a count alone cannot establish value either way. Ask whether the knowledge informed an authorized decision and whether the record accurately describes it.

Scale the request to the relationship. A colleague from a joint project may understand a request to review one specific paragraph. A person who has never met you needs a reason for contact and a smaller ask. A shared acquaintance is not an endorsement; obtain that person’s permission before citing them. If the real need is organizational approval or confidential information, individual outreach is the wrong first step. Identify the decision owner and use the internal route. The brief is a planning aid for respectful contact, not a legal form or a promise of social success.

Test the brief before outreach. Could an independent reader distinguish the purpose from a job request or sales pitch? Can the recipient answer or decline without pressure? Is every contextual detail yours to share? If a test fails, repair the relevant field rather than adding vague courtesy. If you do not yet know what you want to learn, consult public material first instead of asking a stranger to define your task. Write one revisable hypothesis, such as “coverage area may be a partner selection factor,” then separate what the conversation confirms from what remains an assumption.

Turn the brief into a contact decision with three columns: information needed, a possible public source, and the part that still calls for a person’s experience. An event description may establish its subject and audience, for example, but may not explain how two similar proposals were compared. Ask about the comparison method rather than requesting the applicants’ identities or files. If the public source fully answers the question, close the interview request because the need has gone away. If two sources conflict, record the point of conflict in the question. The person can then see exactly what help is being requested. Selecting a contact follows a defined gap, not an algorithm’s suggestion of prominent accounts.

Set a completion test before the conversation. Two criteria, one example of how each was used and their limits may be sufficient. Do not automatically expand the exchange into a request for referrals or client data. After a response, classify each note as a fact verifiable from published material, the contact’s experience in a bounded setting, or a team inference that still needs testing. If the experience conflicts with team policy, route that conflict to the decision owner rather than applying the advice directly. If no answer comes, record the gap as open and seek another legitimate route. Repeated pressure does not turn silence into evidence or consent.