Context

Not all launches should use the exact same channels or strategy. This document outlines the different “tier” of launch based on a few criteria:

<aside> <img src="/icons/book-closed_orange.svg" alt="/icons/book-closed_orange.svg" width="40px" /> We use the following codes to evaluate a launch:

• Does it align with our company narrative?
  • A little Somewhat Very Much So
• What’s the goal of the launch?
  • This is color agnostic
• How many users does it effect?
  • Few Some Most
• How newsworthy is it?
  • A little Somewhat Very
• Is it good / neutral/ moderate change?
  • This is color agnostic
• Is it a temporary or permanent change/addition/update?
  • Temporary Unknown Permanent </aside>

Our system

1. Mostly Green = Tier 1 launch
2. Mostly Yellow = Tier 2 launch
3. Mostly Blue = Tier 3 launch

The specific tactics for each tier will differ depending on what exactly we’re launching, but this is a good guideline to help.

Tier 1

Our biggest and most important launches, no more than 3-5 a year

<aside> <img src="/icons/die1_orange.svg" alt="/icons/die1_orange.svg" width="40px" /> Narrative changes, Major product updates or releases, Maker Fest, Brand Refresh, Golden Kitties

</aside>

Tier 2

Our most common launch strategy, likely on the order or 10-20 a year

<aside> <img src="/icons/die2_orange.svg" alt="/icons/die2_orange.svg" width="40px" /> Success Stories, Beta Program Launch, Launcher Hub, Launching Discord channel, Web3 Feed

</aside>

Tier 3

Our most common launch strategy, likely on the order or 20-30+ a year

<aside> <img src="/icons/die3_orange.svg" alt="/icons/die3_orange.svg" width="40px" /> Renaming feature, UX/UI minor changes

</aside>