Update Team Compass to include Partnerships Charter and new org structure

administration/airtable.md

@@ -17,7 +17,7 @@ If you need edit permissions, use the [shared AirTable account](airtable:shared)
 We have a single account on the "Pro" plan of AirTable.
 It is the only account with edit permissions.
 
-To access this account, use our [shared passwords account](accounts:bitwarden) for credentials.
+To access this account, use our [shared passwords account](account:bitwarden) for credentials.
 
 The rest of this page describes an overview of AirTable's structure in general.
 

administration/index.md

@@ -13,5 +13,6 @@ google-workspace
 github
 airtable
 authentication
+passwords
 zoom
 ```

administration/passwords.md

@@ -1,4 +1,4 @@
-(accounts:bitwarden)=
+(account:bitwarden)=
 # Shared bitwarden account
 
 We use [bitwarden](https://bitwarden.com/) to share passwords and secrets across the team.

communication/index.md

@@ -1,6 +1,6 @@
-# Communication and outreach
+# Marketing and outreach
 
-These sections describe our external communications strategy and operations.
+These sections describe our external marketing, communications, and outreach strategy and operations.
 
 ```{toctree}
 overview

index.md

@@ -48,7 +48,7 @@ operations/index
 people/index
 open-source/index
 finance/index
-communication/index
+product/index
 administration/index
 ```
 
@@ -63,8 +63,6 @@ Functional areas each have their own leads, goals, and structures.
 
 leads/index
 engineering/index
-product/index
-community/index
 partnerships/index
 ```
 

leads/structure.md

@@ -7,7 +7,6 @@ The team leads group is composed of leaders from various areas of 2i2c.
 Below is the current list of team leads:
 
 - **Organization-wide**: {role}`Executive Director`
-- **Product** / **Community**: {role}`Product and Community Lead`
 - **Partnerships**: {role}`Partnerships Lead`
 - **Engineering**: {role}`Engineering Manager` / {role}`Technology Lead`
 

organization/structure.md

@@ -24,6 +24,7 @@ They are led by the {role}`Executive Director` and responsibility is delegated t
 - **[People group](../people/index.md)**: Policies and practices for personnel, hiring, salaries, benefits, and time off.
 - **[Open Source](../open-source/index.md)**: Our upstream and open source engagement strategy to ensure we have healthy relationships with communities we rely on.
 - **[Finance](../finance/index.md)**: Our accounting and financial systems and strategy.
+- **[Product](../product/index.md)**: Understand the perspective of our partner communities and guide the evolution of our infrastructure and services, in order to ensure they have a positive impact.
 - **[Communication](../communication/index.md)**: Strategy and practices for communicating 2i2c's impact and operations with external communities.
 - **[Administration](../administration/index.md)**: Carry out ongoing organizational tasks that are needed to keep 2i2c running on a daily basis.
 
@@ -36,8 +37,6 @@ Reporting lines are within a functional area, meaning that team members should r
 
 
 - **[Engineering](../engineering/structure.md)**: Develop and operate our technical and cloud infrastructure, to ensure that it is reliable and scalable.
-- **[Product](../product/structure.md)**: Understand the perspective of our partner communities and guide the evolution of our infrastructure and services, in order to ensure they have a positive impact.
-- **[Community](../community/structure.md)**: Guide and support the partner communities that we serve, to help them utilize our infrastructure in a way that aligns with 2i2c's mission.
 - **[Partnerships](../partnerships/structure.md)**: Identify opportunities for impact, cultivate new relationships, and oversee our sustainability plan to ensure that we have sustainable and scalable impact.
 
 ## Cross-functional teams

partnerships/index.md

@@ -1,11 +1,12 @@
 # Partnerships
 
-Partnerships and sustainability oversees the strategy and systems that 2i2c uses to sustain itself via partnerships with other communities.
-This includes partnerships via paid contracts, as well as via informal and formal collaboration.
+Partnerships oversees the strategy and systems that 2i2c uses to sustain itself via partnerships with other communities.
+This includes partnerships involving paid contracts, as well as via informal and formal collaboration.
 
 ```{toctree}
 overview.md
 structure.md
 workflow.md
-communication.md
+../communication/index
+community_success/freshdesk.md
 ```

partnerships/overview.md

@@ -1,57 +1,47 @@
 # Scope and responsibilities
 
-## Oversee sustainability strategy
+## Key goals
 
-- Collect feedback from major stakeholders and define major plans around sustainability at 2i2c
-- Define overall goals to guide sustainability efforts at 2i2c
-- Forecast revenue to inform overall strategy
+1. **Sustainability**: Establish, support and renew partnerships so that 2i2c has the financial resources to advance on its mission.
+2. **Community Success**: Deliver value to all communities in a consistent, repeatable, scalable way so that partners see the return on their ongoing investment and collaboration with 2i2c.
+
+## Major areas of responsibility
 
-## Represent this strategy internally and externally
+Partnerships defines strategy for the following areas and aligns it with the overall strategy of 2i2c.
 
-- Amplify [Voice of Partner](https://www.zs.com/insights/high-techs-new-challenge-hearing-voices-of-channel-partners) for 2i2c stakeholders in internal discussions (e.g. with 2i2c's engineering and support teams).
-- Collaborate with Product and Community Lead to represent Sustainability strategy in product/service decisions.
-- Communicate 2i2c's sustainability strategy and model to external stakeholders
+### Sustainability
 
-## Design and develop new revenue mechanisms
+Establish, support and renew partnerships so that 2i2c has the financial resources to advance on its mission.
 
-- Establish and sustain revenue-generating relationships with partner organizations
-- Establish ongoing relationships with cloud vendors or resellers
-- Collaborate with product and engineering teams.
+- **Marketing**: Describe 2i2c’s value proposition externally and attract new leads.
+- **Sales**: Generate new and renew agreements and service contracts.
+- **Grants**: Identify and apply for grant opportunities that align with 2i2c’s service strategy
+- **Invoicing and cost recovery**: Ensure 2i2c recovers the cost that it is due via contracts.
+- **Pricing and contract strategy**: Set pricing and agreement terms for partners so that paid services meet our growth goals.
+- **Market research and competitive analysis**: Understand 2i2c’s value proposition and business model relative to other services and products.
+- **Business aspects of joint ventures**: Understand the financial and strategic impact of partnerships with other services and products (e.g. with cloud vendors, cloud resellers, publishers, technology companies).
 
-## Identify, develop, and pursue funding opportunities
+### Community Success
 
-For example:
+Deliver value to all communities in a consistent, repeatable, scalable way so that partners see the return on their ongoing investment and collaboration with 2i2c. 
 
-- Partnerships that grow our capacity
-- Grants for the organization or for deliverables
-- Philanthropy and giving
+- **Onboarding**: Set expectations and provide guidance for new communities that are using our service.
+- **Training**: Help communities understand how to use our products and services to achieve value.
+- **Community satisfaction**: Understand the ongoing satisfaction that communities have with the service and identify ways to improve their experience.
+- **Account management**: Establish and sustain relationships with partner organizations to ensure they are successful.
+- **Grant management**: Ensure that the goals and deliverables of our grants are understood and met.
+- **Support**: React to community questions and requests for help and direct them to the appropriate team for resolution.
 
-## Manage our sales pipeline
+## Measures and definition of success
 
-- Oversee [our leads and sales process](../projects/managed-hubs/sales.md).
-- Ensure that our sales pipeline is efficient, distributed-friendly, and scalable.
-- Balance our revenue, costs, and ability to deliver.
-- Oversee processes and systems that balance leads, sales, etc. For example:
-  - `costs <= amount sold <= delivery capacity`
-  - `Leads --> opportunities --> sales --> service`
-- Collaborate with Product and Community Lead around onboarding new communities.
+### Sustainability
 
-## Manage our invoicing pipeline
+- Ratio of **monthly recurring costs** to **monthly recurring revenue**.
 
-- Ensure that 2i2c is reliably invoicing for the work it is doing, and getting paid for these invoices.
-- Oversee systems for contracting and invoicing in partnership with {term}`Code for Science and Society`.
-- Serve as a main point of contact for CS&S administrators that oversee billing.
+### Community success
 
-## Formalize our contractual relationships
+Not yet defined. Potential indicators below…
 
-Oversee the creation of contracts and legal documents that are needed as part of our services (in collaboration with {term}`CS&S`).
-For example:
-
-- Service Level Agreement
-- Support Expectations
-- Terms of Service
-- Privacy Policy
-- Right to Replicate
-- Information security breach response plan
-- HECVAT
-- Accessibility
+- [net promoter score](https://en.wikipedia.org/wiki/Net_promoter_score)
+- hub usage patterns over time
+- time-to-milestones in the leads-to-partner lifecycle.

partnerships/roles/community-success-manager.md

@@ -0,0 +1,7 @@
+```{role} Community Success Manager
+```
+# Community success manager
+
+```{warning} To add
+To add here.
+```

partnerships/roles/lead.md

@@ -1,3 +1,5 @@
+```{role} Partnerships Lead
+```
 # Partnerships Lead
 
 Ensures that 2i2c has effective relationships (sales, contracts, invoicing, service delivery) and the resources required to achieve its mission {role}`Partnerships Lead`.

community/roles/partnerships-community-lead.md → partnerships/roles/product-community-lead.md

@@ -3,6 +3,10 @@
 
 # Product and Community Lead
 
+:::{admonition} Archived!
+This role is no longer active within 2i2c, but we leave it here as a historical record.
+:::
+
 There are three key goals for this role:
 
 - Empower the communities we serve to have impact with our infrastructure.

partnerships/structure.md

@@ -1,26 +1,23 @@
 # Structure and roles
 
-:::{note}
-This is still a work in progress!
-:::
-
-Our product area is led by the {role}`Partnerships Lead`.
-
-We do not currently have any other formal roles or teams within it.
-
-Below are major roles and teams...
-
-```{role} Partnerships Lead
-```
-
-## Roles
+## Current roles
 
 ```{toctree}
-:maxdepth: 2
 :glob:
 roles/*
 ```
 
 ## Membership
 
 See [list of team members](../reference/team.md).
+
+
+## External communication
+
+### Partnerships e-mail address
+
+We use a [shared e-mail inbox](org:communication:shared-email) called `partnerships@2i2c.org` to collect any inbound communication from those that wish to partner with 2i2c.
+
+It is attached to the `2i2c Partnerships` Google Group.
+
+Access is also shared with {term}`CS&S` so that they have context for any handoffs to invoicing and administration.

product/index.md

@@ -5,8 +5,6 @@ They work alongside engineering teams to define ways in which we aim to improve
 
 ```{toctree}
 overview.md
-structure.md
-workflow.md
 pricing/strategy
 pricing/cost-model
 ```

product/overview.md

@@ -1,27 +1,5 @@
 # Scope and responsibilities
 
-Product guides the evolution of our service and technology in order to better achive our mission.
-It understands the perspective of the communities that we serve, and the kinds of individuals within those communities.
-It leads efforts to refine and prioritize our technical roadmap along with our engineering team.
-It leads efforts across the organization to refine our service model and how we talk about it.
+Product describes the services and technology that 2i2c provides, the value they are meant to provide, and the stakeholders and user archetypes that are meant for.
 
-Below are major areas of responsibility.
-
-## Understand and integrate stakeholder feedback
-
-- Identify key internal and external community stakeholders that are crucial to 2i2c's strategy.
-- Communicate with and learn from the stakeholders and partners that we serve.
-- Understand their pain points, needs, and how our services can help them have impact.
-- Align stakeholders on a shared plan for our services and products.
-
-## Guide and prioritize our deliverables
-
-- Create and refine enhancements and deliverables to our services and products.
-- Prioritize deliverables for our engineering team to work on.
-- Document and describe changes for end-users.
-
-## Communicate service changes with external stakeholders
-
-- Document our service and its functionality to external stakeholders.
-- Lead private or public communications that discuss new features, changes, and major ideas around our services and tools.
-- Serve as a point of contact for major development efforts or projects that involve external stakeholders.
+Currently, there is no dedicated product function within 2i2c, so this section is a place to collect broad product-related information and strategy.

reference/team.md

@@ -27,6 +27,7 @@ Below is a summary of the people on that page.
 
 <style>
 .people-widget .avatar {
+    display: flex;
     width: 100%;
     max-width: 150px;
     height: auto;