Member Relationships & Network Visibility

It connects members, groups, and organizations through relationships whose meaning, context, sources, and timing can be understood. The aim is to support a defined organizational question with an appropriately bounded view.

A directory identifies people and organizations. A relationship view also explains how they connect through affiliations, roles, activities, collaboration, or other relevant arrangements.

No. It establishes a shared affiliation. Direct interaction, collaboration, or a personal relationship requires additional information.

This module focuses on understanding existing relationships and gaps in what is known. Designing introductions, peer connections, or mentoring participation belongs in the relevant engagement work.

No. The exercise begins with one question and a bounded part of the community. A smaller map is often enough to establish useful definitions and identify practical next steps.

Relevant sources may include chapter and committee rosters, representative roles, shared project records, partnership arrangements, and appropriate participant accounts. The module examines what each source actually supports.

Yes, where appropriate for the purpose. The account should preserve who provided it, what relationship is being described, and what visibility or review is suitable for its intended use.

Record the relevant account with its source and context, then identify whether clarification is needed. Staff knowledge can be useful without being treated as complete or automatically confirmed.

Start by examining source coverage. The group may have relationships that are not recorded, use different systems, or have limited cross-group activity. The map alone may not distinguish those explanations.

No. Recorded connections can reflect formal roles, source coverage, or activity history. Influence, trust, and suitability for a particular request require their own context.

It can help examine where known coordination relationships pass through particular people or roles. Whether that creates a continuity problem depends on the work involved, alternative arrangements, and information available.

Preserve useful historical context while distinguishing it from current arrangements. Dates, ended roles, and review status help prevent past relationships from being interpreted as active.

Yes. The relevant entities can include people, chapters, committees, employers, member companies, and partners. Their relationships should remain clearly distinguished.

Not automatically. Relevance, willingness, and appropriate permission still matter. A relationship map can identify a question to explore without committing anyone to act.

The workshop does not assume replacement. It identifies the relationship information and context needed, then helps clarify what a subsequent implementation would require from existing sources.

The outputs can inform a scoped configuration connecting entities, relationship types, activities, and source context. Appropriate views, member input, and review processes would be considered according to the agreed purpose and available capabilities.

Your team will examine one bounded example and create a draft brief, contextual relationship map, coverage and clarification plan, and starting configuration brief. Wider rollout and implementation are subsequent steps.