PROJECT: Partner Relationship Management

[sethmcknight]

We work with Partners across multiple Projects and Staff Members over time. This leads to the creation of a lot of important individual/tribal knowledge, important communications, decisions, and other information.

To manage our Partner Relationships well and facilitate healthy transitions among Staff Members, we need to capture and interact with information about Partners that facilitates healthy Relationship Management.

Objective: Allow SC to better steward resources and partner relationships

• Track interactions with Field Partners over the lifetime of our partnership
• Knowledge management
• Partner capacity over time
• Holistic view of interactions with partners

Draft Schema can be found here.

Below are the key entities that need to be connected to the Partner basenode and added to the Partner scene in CORD. These have been prioritized top to bottom.

• [ ] Posts
• [ ] Projects (where a Partner has a Partnership)
• [ ] Abbreviation/Acronym
• [ ] Contact Information
• [ ] Financial Transfers
• [ ] Partner Staff Members
• [ ] Organization (Seed Co) Staff Members
• [ ] Category
• [ ] Related Partners
• [ ] Languages

Each entity/functionality can be released as it is ready.

┆Issue is synchronized with this Monday item by Unito

[sethmcknight]

Design:

First version of data schema/fields here: https://docs.google.com/spreadsheets/d/1vSZY24nR8HDl0DlhwSKbtGp4j-1E7UhP_iEncjlBvKI/edit?usp=sharing

• [ ] Posts: See Posts designs. Need that ability to capture/track conversations, interactions and other information about a Partner.
• [ ] Projects: A list of Projects that a Partner has a Partnership in. This is a relationship based on Partnership that already exists.
• [ ] Abbreviation/Acronym: Related to Partner Name. This is a user managed text field.
• [ ] Contact Information: This is a user input data set that includes Address, Business Email, Business Phone and Contacts. Contacts are a link to People.
• [ ] Financial Transfers: Tracks the information to make financial transfers to a Partner. Is Partner in PMC? If so, PMC Number. If not, wire transfer data
• [ ] Partner Staff Members: Link to each Person who's Organization is this Partner. On People need to add 'Other Contact Info', Location, Mailing Address, and link to Partner.
• [ ] Organization (Seed Co) Staff Members: Link to Person made by users, relationship(s) to Partner (type and timeframe), and Partner Staff Members this Person interacts with.
• [ ] Category: User input field. Alliance, Organization, Parent, etc.
• [ ] Related Partners: User input link to Partners + all partners that are associated with an Alliance.
• [ ] Languages: List of each Language a Partner has had a Partnership with, Start Date, Anticipated End Year, Currently Engaged.

[ParkeBrown]

@AmyRickwartz you can take a look at this

[sync-by-unito[bot]]

➤ Seth McKnight commented:

We work with Partners across multiple Projects and Staff Members over time. This leads to the creation of a lot of important individual/tribal knowledge, important communications, decisions, and other information.

To manage our Partner Relationships well and facilitate healthy transitions among Staff Members, we need to capture and interact with information about Partners that facilitates healthy Relationship Management.

Objective: Allow SC to better steward resources and partner relationships

• Track interactions with Field Partners over the lifetime of our partnership

• Knowledge management

• Partner capacity over time

• Holistic view of interactions with partners

  Draft Schema can be found here.

  Below are the key entities that need to be connected to the Partner basenode and added to the Partner scene in CORD. These have been prioritized top to bottom.

• [ ] Posts

• [ ] Projects (where a Partner has a Partnership)

• [ ] Abbreviation/Acronym

• [ ] Contact Information

• [ ] Financial Transfers

• [ ] Partner Staff Members

• [ ] Organization (Seed Co) Staff Members

• [ ] Category

• [ ] Related Partners

• [ ] Languages

  Each entity/functionality can be released as it is ready.