# [Mempool Track & Fellows Track](https://cryptowhatever.com/post/606) Communications

Communication Media Checklist:

- [ ] Slack
- [ ] Calendar
- [ ] Airtable
- [ ] Convo
- [ ] Email
- [ ] Telegram
- [ ] Forums
- [ ] Zoom/Jitsi

***Assuming final convergence occurs March 3 & accounting for preparation time required for application, #mempool-defending & #fellows-endorsing Slack channels, Slack/Matrix, forums, comms materials (copy, glossary, calendar), writing blogposts, The Book outreach, Fireside outreach***

# Week of March 27, 2023

## Kernel Website: Blogpost for Public
**What is the comms?**
Post blog about the new Kernel shape with Mempool Track & Fellows Track. Include our desired outcomes & why this shape is likely to accomplish them & how prior programming did not, also share the nemawashi convergence process & be as transparent as possible - including diversity metrics, role of defenders, role of endorsers, enrollment fees & scholarships. (Shall we describe the new rituals too?)
**What is the purpose?**
To inform public about the work Kernel has been engaged in since end of KB7, our whys, our goals & transparency about the process.

## Twitter: Tweet for Public
**What is the comms?**
Post Tweet explaining silence with a link to the blogpost. Share that we'll be opening applications in 2 weeks & to stay tuned - we look forward to this new Kernel chapter with y'all!
**What is the purpose?**
To give the public interested in KB8 a timeline & details about applying to KB8.

## Email 1: Message to All Kernel Fellows
**What is the comms?** ***(maybe multiple emails?)***
Explain the new Kernel program shape to all fellows & include:
- blogpost linked to glossary of new Kernel terms & description of new rituals & roles (?).
- Airtable forms asking who would like to participate as defender and/or endorser. Describe in detail the expectations of the roles & their long-term hourly commitment. ***OR in a separate email, invite (i) all people who have reviewed before + (ii) most active slack members in the last 4 months + (iii) other picks we know would be caring, helpful and insightful to seed #mempool-defending & endorsing fellows well.***
- all fellows will receive 2 passes annually (?) to admit a friend directly into the Mempool Track, but they cannot buddy up with this friend in Fellows Track.
- in 2 weeks they can invite a few friends to apply to the Mempool Track via the Typeform application we will send.

**What is the purpose?**
To update fellows how Kernel is changing, how they can participate in the new continuous Kernel, & to recruit defenders & endorsers to seed the new shape well.

## Email 2: Message to Friends in 'The Book' (mentors, former guild leaders)
**What is the comms?**
Explain the new Kernel program shape & include:
- blogpost (& glossary?).
- how their role is shifting in the new shape, specifically in the Fellows Track & other tracks if they wish to lead any.
- the process to request advising from 'The Book.'
- request 1:1 calls to confirm interest in participating & answer questions about new shape.

**What is the purpose?**
To retain & engage mentors & former guild leaders, perhaps hear feedback, & confirm their support in the Fellows Track.

## Email 3: Message to KB7 Applicants w/ Deferred Interview to KB8
**What is the comms?**
Explain the new Kernel shape to all KB7 applicants who we deferred to interview for KB8. Include a link to the blogpost. Inform them there is no longer an interview & encourage them to apply to the Mempool Track in 2 weeks.
**What is the purpose?**
To maintain trust and communication with applicants whom we didn't have the opportunity to interview for KB7 but communicated that we wished we could have.

## Email 4: Message to KB7 Fellows who Deferred to KB8
**What is the comms?**
Explain the new Kernel shape to all KB7 fellows who deferred to KB8 due to life circumstances. Include a link to the blogpost. Inform them that we will enroll them in Mempool Track when it opens in 2 weeks.
**What is the purpose?**
To maintain trust and communications with KB7 fellows who were unable to participate & are keen to participate in KB8.

# Week of April 3, 2023
## Email 1: Message to All Kernel Fellows
**What is the comms?**
Reminder email asking who would like to become a defender and/or endorser & attach the respective Airtable forms.
**What is the purpose?**
To recruit defenders & endorsers to seed the Mempool & Fellow Tracks.

## Email 2: Message to Friends in 'The Book' (mentors, former guild leaders)
**What is the comms?**
Reminder email informing mentors & former guild leaders of the Kernel shape, their new role in the Fellows Track & potentially other tracks, & request the 1:1 call with a Steward to increase retention.
**What is the purpose?**
To retain & engage mentors & former guild leaders, perhaps hear feedback, & confirm their support in the Fellows Track.

## Email 3: Message to Mempool Track Defenders
**What is the comms?**
Introductory message including:
- welcome packet explaining the defender role & Slack channel #mempool-defending.
- provide diagrams & video demonstration of the application & review process.
- include metrics - how many votes or vetos they have each week, & how many apps they must admit weekly, or reject weekly with constructive feedback.
- invite to Slack channel #mempool-defending.
- arrange regular calls in Zoom or Jitsi to orient the review and rating process with defenders, & begin with one mandatory recorded introductory meeting first, with later meetings optional to jam together & receive feedback from others in the review process.
- **Emphasize the need** for additional peer support mechanisms and clearer criteria in the review process for defenders, as documented [here](https://miro.com/app/board/uXjVPJoVGFs=/).
- Continue the conversation weekly to maintain diversity targets & adjust according to prior week's admissions.

**What is the purpose?**
To clarify the #mempool-defending process, familiarize defenders with procedures, & provide consistent mechanisms for peer support throughout.

## Email 4: Message to Fellows Track Endorsers
**What is the comms?**
Introductory message including:

- welcome packet explaining the endorser role & Slack channel #fellows-endorsing.
- provide rubric for evaluating mempers to buddy up with.
- include importance of participation in & hosting of rituals, developing a question to explore in fellows track.
- invite to Slack channel #fellows-endorsing.
- arrange introductory & recorded call in Zoom or Jitsi to orient the buddying up process , with later meetings optional to jam together & discuss insights from endorsers' experiences.
**What is the purpose?**

# Week of April 10, 2023
## Twitter: Tweet for Public
**What is the comms?**
Post Tweet announcing the apps to the mempool track are open on a rolling basis with the Typeform link. In a thread below the Tweet, reference the importance of being aware of the new shape & link the blogpost describing it.
**What is the purpose?**
To provide free, open & accessible education, invite the greater web3 ecosystem to apply to the Mempool Track, & begin the application flow, review process, & open the Mempool Track.

## Email 1: Message to All Kernel Fellows
**What is the comms?**
Inform all current fellows that:
- applications are open & we encourage them to invite 1-2 friends to apply to the Mempool Track.
- consider if they'd like to use any of their 2 annual passes (?) to admit a friend directly into the Mempool Track. Remind them that they will be unable to endorse this friend in the Fellows Track.
**What is the purpose?**
To provide free, open & accessible education, invite friends of the Kernel community to apply to the Mempool Track, to begin the application flow, review process & open the Mempool Track.

## Email 3: Message to KB7 Applicants w/ Deferred Interview to KB8
**What is the comms?**
Send the mempool track application link to all KB7 applicants who we deferred to interview for KB8. Include a link to the blogpost again to remind them of the new shape and process.
**What is the purpose?**
To give an opportunity to applicants whom we wanted to interview for KB7 but couldn't a chance to be in the mempool track.

## Email 4: Message to KB7 Fellows who Deferred to KB8
**What is the comms?**
Remind all KB7 fellows who deferred to KB8 that the mempool & fellows tracks will open in a few weeks & send welcome packet to orient them well.
**What is the purpose?**
To maintain trust and communications with KB7 fellows who were unable to participate & are keen to participate in KB8.

## Email: Enrollment & RSVP

The refinement of your question is how you enter the fellow's track. what apps are we introducing?

**What is the comms?**
**What is the purpose?**

# Gate I Communications Overview: Reviewing
## Email
- **Weekly Email 1:** accept or reject applicants. Rejected applicants can apply again next week.
- **Weekly Email 2:** accepted applicants & inducted fellows receive welcome email describing the mempool program, & process for consideration to chain, focus on 'what is your question/adventure?'. Include mempool master reference PDF & video illustrating navigation among mempool & tools used. We share access privileges to:
- mempool calendar
- mempool slack
- mempool convo
- mempool forums
- opt-in notification streams
- **Weekly Email 3:** inform inducted fellows who will buddy up which applicants have been admitted to the mempool including their profile info.

# Phase II Communications Overview: Mempool
## Email

- **Weekly Email 1:** emphasize importance of attending intention circles & research clinic in first week to orient yourself well but there are no limits - go wherever you like! describe mempool rituals.
- **Bi/Weekly Email 2:** reminder to sponsoring fellows to give attention to whom hosts convos & posts thoughtful contributions on forums to consider whom to invite to the chain.

- Invite mempers to be multi-channekl guests in Slack:
- #mempool-vibes
- #mempool-intros
- #mempool-support
- #wip-wednesdays
- Slack bot: reports weekly high interaction conversations in public mempool channels, perhaps in a Slack channel entitled #mempool-emergent-conversations.

## Calendar
- Mempool Calendar provides all details to participate in mempool rituals such as research clinics, intention circles, open spaces, paper parties, LT juntos, WIP Wednesdays.

## Convo
- Convo App: RSVP to convos, propose convos. These events are additional to the mempool Calendar. Will it be a separate calendar? Keeping all mempool rituals and convos in one calendar reduces the likelihood of an 'official calendar' mental model & reduces steward management (i hope).

## Forums
- Flocks to find the others asking similar questions, sharing similar interests, surfacing debates - place for intros.
- Other type(s) of forums?

## Typeform
- We Applications are closed once we receive a sufficient number of applications that enable us to reach X inducting fellows for the chain. We aim to close apps at least 2-3 weeks before the chain is finalized.

# Gate II Communications Overview: Buddying Up - [EDIT HERE - BUDDY BUFFER](https://app.excalidraw.com/l/9SphoQKY1iv/6ONBdmxBaMB)
## Email
- **Weekly Email 1:** inducted fellows invite mempool fellows to the chain & agree to personally take responsibility & care for them in the chain. Arrange cadence for interaction & support throughout the chain; set relationship tone.
- **Weekly Email 2:** update inducted fellows which mempool fellows have been invited to the chain & include estimation of proximity to closing the mempool & opening the chain to begin the block.
- **Email 3:** once chain is full of X inducting fellows, inform remaining mempool fellows to try again in the next mempool round.
- **Email 4:** to all inducting fellows & inducted fellows explaining the chain program & schedule. Include chain master reference PDF & video illustrating navigation among chain & tools used. Email includes details about Big Huggy Unconference welcome event. We share access privileges to:
- chain calendar
- chain Slack (full Slack access)
- convo
- chain (flock) forums
- opt-in notification streams
- black book requests

- **Email 5:** to all Kernel fellows to remind them about the chain if anyone would like to participate (?) & invite to Big Huggy Unconference.

## Slack
- Endorsing fellows use Slack bot command /buddyingup when they agree to sponsor a fellow --> triggers acceptance email to fellow

# Phase III Communications Overview: The Chain (Cycle)

## Email
- **Weekly Email 1:** chain rituals, convos & themes, relevant syllabus references. Try to surface & connect asks, offers, opportunities.
- **Weekly Email 2:** for inducted fellows buddying up, tracking progress & providing tools for them to assist inducting fellows well.

## Slack
- Full Slack access to inducting fellows.
- Slack bot: reports weekly high interaction conversations in all channels, perhaps in a Slack channel entitled #chain-emergent-conversations.

## Calendar
- Chain Calendar provides all details to participate in chain rituals such as big huggy, orientation, topic tracks, firesides, celebration, hackathons, contract safaris, A teams.

## Convo
- Convo App: RSVP to convos, propose convos. These events are additional to the Chain Calendar. Will it be a separate calendar? Keeping all chain rituals and convos in one calendar reduces the likelihood of an 'official calendar' mental model & reduces steward management (i hope).

## Forums
- Flocks to find the others asking similar questions, sharing similar interests, surfacing debates.
- Other type(s) of forums?

## Opt-in Notification Streams
- Telegram: regular reminders before rituals & convos begin.

## Chain Schedule
- W1
- Big Huggy Unconference
- orientation
- topic tracks
- A teams
- fireside
- contract safaris
- W2
- topic tracks
- A teams
- fireside
- contract safaris
- convos: WIP wednesdays, intention circles, open space, vibe hour, juntos
- hackathon

- W3
- topic tracks
- A teams
- fireside
- contract safaris
- convos: WIP wednesdays, intention circles, open space, vibe hour, juntos
- W4
- topic tracks
- A teams
- fireside
- contract safaris
- convos: WIP wednesdays, intention circles, open space, vibe hour, juntos
- hackathon
- W5
- Celebration
- graduation, regeneration

# Gate III Communications Overview: Graduating & Regenerating

## Email
- **Email 1:** to all newly inducted fellows inviting them to stay involved by joining the next mempool/chain by participating in gate I and/or II.
---

Welcoming squad happens every 2 weeks

Every 150 inductions or 3 months, whichever happens first, KB block # goes up by 1
ritual : big huggy unconference when 150 new fellows reached or 3 months passed
-mempool closes for 2 weeks (responsive to current circumstances - what’s happening in #mempool-defending)

5 welcoming squads over the course of 10 weeks = 150 new fellows
Happening continuously

Block is 12 weeks