Reimagine hub rollouts as solving XY problems

[jmunroe]

Context

In https://github.com/2i2c-org/meta/issues/2966#issuecomment-3998068597 we learned that our interactive computing service (hubs) are an opportunity for our PS team to interact with our communities. Our expertise as 2i2c is so solve 'XY problems': matching infrastructure and open source tooling to the needs and wants of education and research communities. To be able to co-solve these XY problems with communities, we need to rethink about how we structure the interactions and timeline between 2i2c engineers and its communities when deploying a a hub.

What we need to do

We want the 'hub rollout' process to leverage PS expertise as 'sales engineers' when rolling out a new hub to a community.

This means have a repeated able process that we can follow when deploying hubs. We need to refine the model that we are using and get alignment within PS on how the process we are designing will work.,

(Possible) Broad steps:

• 1. PS participating as sales engineers as early as possible in the sales cycle leading to the decision for the community to become a 2i2c member.
• 2. BD takes responsibility for the closing the financial and contractual aspects of the deal and PS takes lead in requirement gathering with community
• 3. PS communicates with community (sync or async) to assess needs
• 4. PS develops solutions as GitHub issues (typically New Hub Deployment tickets)
• 5. PS executes on GH issues
• 6. PS communicates with community (sync or async) to confirm the needs are met. If not, go back to step 3.
• 7. Community is receiving value from 2i2c.

Definition of Done

Sub tasks:

• Draw this out as a flow chart and ask for validation from @yuvipanda and other members of PS
• Refine needed as needed
• Share proposed model with BD and the rest of 2i2c
• Decide on next steps

[jmunroe]

In this restructuring of the hub roll process, PS is involved much earlier in the process and is primarily responsible for the needs assessment of each community.

---
title: 2i2c Hub Rollout Process
---
flowchart
    subgraph BD["Business Development (BD)"]
        BD1["1. Identify Communities\n─────────────────\nBD identifies communities\nwith hub needs"]
        BD2["3. Close the Deal\n─────────────────\nBD closes financial &\ncontractual aspects"]
        BD3["9. Track Value\n─────────────────\nBD tracks value received\nby community"]
    end

    subgraph PS["Product & Services (PS)"]
        A["2. Sales Engineering\n─────────────────\nPS participates early in\nsales cycle to help community\ndecide on 2i2c membership"]

        C["4. Needs Assessment\n─────────────────\nPS communicates with community\n(sync or async) to assess needs"]

        D["5. Solution Design\n─────────────────\nPS develops solutions as\nGitHub issues\n(New Hub Deployment tickets)"]

        E["6. Execution\n─────────────────\nPS executes on\nGitHub issues"]

        F{"7. Validation\n─────────────────\nPS communicates with\ncommunity (sync or async):\nAre needs met?"}

        G["8. Value Delivered\n─────────────────\nCommunity is receiving\nvalue from 2i2c"]
    end

    BD1 --> A
    A --> BD2
    BD2 --> C
    C --> D
    D --> E
    E --> F
    F -- "No" --> C
    F -- "Yes" --> G
    G --> BD3

    classDef hidden fill:none,stroke:none,color:none

    style BD fill:#e8f0fe,stroke:#4a90d9,color:#2c5f8a
    style PS fill:#e8fee8,stroke:#50c878,color:#308050

    style BD1 fill:#3a7bc8,color:#fff,stroke:#2c5f8a
    style A fill:#4a90d9,color:#fff,stroke:#2c5f8a
    style BD2 fill:#5ba0e0,color:#fff,stroke:#3670a7
    style C fill:#6db3e8,color:#fff,stroke:#4080b5
    style D fill:#7fc4f0,color:#000,stroke:#4a90c3
    style E fill:#91d5f8,color:#000,stroke:#5aa0d1
    style F fill:#f0c040,color:#000,stroke:#c09830
    style G fill:#50c878,color:#fff,stroke:#308050
    style BD3 fill:#3a7bc8,color:#fff,stroke:#2c5f8a

Loading

[jmunroe]

I've begun rewrite content in the team compass regarding interactive computing / hub roll out and pushed it as

• 2i2c-org/team-compass@72107a9

(My mistake here: I thought I was on a feature branch and didn't intend for the this to be commit to the main branch without a PR. I'll fix that for the next commit!)

Revised hub process docs: https://compass.2i2c.org/services/interactive-computing/hub-rollout-process/