Approach #1 - Stacks Brand Update
What is it: “Conservative brand refresh”. Current Stacks brands with proposed fixes (toning down the brand, starting with a small visual approach to Bitcoin, simplifying, quick visual fixes, etc)
| 🟢 Pros | 🔴 Cons |
|---|---|
| Honest, straightforward | Slow / More expensive |
| Working with what we’ve got / real problems / real solutions | Could create confusion right as people are finally finding Stacks |
| Saves on doubling-up work/resources | Risk of alienating some community |
| Alleviates pressure from certain important stakeholders | Adjustments may not solve many of the original ‘problems’ |
Approach #2 - Mock Brand Exercise
What is it: Create or grab an existing “Bitcoin layer brand” and apply the desired specs, goals, and objectives that we’d think such a brand should have. Then, see what from that exercise/experiment/learnings can be translated to the Stacks brand.
| 🟢 Pros | 🔴 Cons |
|---|---|
| Fast | Could be hard to later apply to the Stacks brand as it’s not made to its measure |
| Disposable / a test we can pivot from | Waste of time/money if disposable |
| More information gathered with less upfront work | |
| ‘Safe’ place to experiment rapidly | Could create confusion and fragmentation (seeing this happen w/Ordinals) |
| ⭐️ Probably solves the ‘real’ problem more based on Mitchell’s learnings |
Notes
Next steps: