---
tags: Template
---
# Talisman Community Design V1
```
Author: Frothy
09/27/2021
```
:::danger
Wants: Attract the best contributors in a DAO, enable community ownership
:::
### Process
Acquisition and engagement
| Goal | Metric |
| ----------------- |:----------------------- |
| Community satisfaction through community experiences| Establish member lifetime value (MLV) |
| Funnel through a pipeline | Conversion Rate %|
| Retention | # of engagement |
### Want Created:
**Community Action**
Talisman - The wallet that is accessible for everyone in the DOTSAMA ecosystem
Through community design + user journey mapping, Frothy will uncover what key initaitives will drive Talisman's adoption.
For a wallet’s sustainability, we will target initatives that allows for the community to own and
## What do we want DAOs to do?
1. Enabling community ownership
2. DAO / open source framework
3. B2B2C funnel *(who represents the B2B relationship here?)*
## How do we get there?
- Incentivize to help each other onboard and contribute to the Talisman ecosystem
- Moving them along the “commitment curve” from DOT and KUSAMA holders into active wallet users
- identify and collect all the partcipants who have attended “hook” Talisman event
- Leverage and activate the Sentinals program
- Generate frothiness around building composeable dApps in Dot-Sama world

Move Talisman Wallet’s Passive members into Active Members

Convert lurkers into activity wallet holders
---
**Community Thesis V1**
**Incentive**: Ease of storing Kusama
**Purpose**: Accessible wallet
**Gather**: Conduct liquidity events?
---
## Proposal
1. Increase activity and volume of current users
2. Create pipeline and retaining wall of new participants
:::success
Identify onboard/engage
:::
Ideas:
- onboarding DAOs
- Rewards for acquisition
- accounts flow through the pipeline
- B2B play, need an institutional community
- "hook" event
---
**Initial Design Question:**
- How can a new web3 wallet offer a more user-empowered + stickier community experience?
- How do we make sure Talisman is the dominant portal in the Dot-Sama space?
- How do we ensure Talisman is the most loved community linked to the Dot-Sama ecosytem?
- ***Community-first UX Design Sprint*:**
Recruit, interview + deliver UX research into the subculture of wallet users : what differentiates a metamask vs rainbow user?
Synthesize findings and lay out community strategy
Community Strategy ⇒ de-risk the launch
- **Community Strategy**
⇒ community distribution channels
⇒ content creation
⇒ partnerships
⇒ relationship building + cultivation
⇒ new wallet market opportunities
- **Metaverse Vibe:**
Community froth for token distribution through online events / twitter spaces / discord jams
Strong metaverse presence + viral memes across main metaverse channels.
- **Memetic Desire around liquidity events**
Compare to what fresh memetic desire Rainbow has achieved in 2021 (https://medium.com/collab-currency/designing-rainbows-moat-d29f05ddcf8)
Get into the subculture of DeFi wallet users and know how their behavior is influenced by their fellow DeFi community
Enlist the most culturally relevant web3 / DeFi influencers to advocate for Talisman.
Creating the right context + conditions for Talisman social signaling to take off
Creating memetic desire around the Sentinals
- **First users Contribution Flywheel**
How to incentivize early community to be natural ambassadors, token fans + ecosystem allies of Talisman? How to create 100 true Talisman fans that scales to 10k true Talisman fans in first 60 days?
Find ways to enable collective co-creation of Talisman wallet (cc Rainbow) and iterate on community feedback. Mobilize community to feel deeply rooted in the development of Talisman.
- **Focus on the *fingerspitzengefühl (that 'fingertip feeling')***
Know what differentiates the different wallet user personas, how they’re thinking, behaving and know what will light them up.
Execute content that taps in precisely to the crypto culture that Talisman wants to appeal to.
---
### Initial Timeline
**Kick-off: October 11, 2021**
Week 1: Onboarding and Initial Strategy Assessment
Talisman team shares relevant information to map out community proposal
Consistent communication for any additional, missing, and follow-up information
Week 2: Incentive Creation vertically for roles, horizontally across roles
Drafting community funnel proposal
Week 3: Initial Alpha Launch (**NOV__?)**
Directing distribution channels to funnel
Scaling programming
Week 4: Outreach to current Lead community members
Implement community design
Delegating program owners
Week 5: Onboarding users with objectives and metrics
Scheduling deliverables and assigning points-of-contact
Fixing and preventing churn in the user journey
Week 6: Launch logistics and announcements
Directing distribution channels to funnel
Scaling programming
---
### Next Steps
- Meeting with Talisman for Proposal review
- Submit budget
- Start onboarding and knowledge download
---
# Review and Decision:

### Background
1. Enable community ownership
2. OSS - building composeability dapps in dot/sama world
composeability - currently seeing issues, writing developer libraries
### Objectives
1. incentive to help each other onboard and contribute to the Talisman ecosystems
2. Consumers to use the wallet, do they eventually become contributors? Feedback even like a Product Hunt
3. B2B developers building on the wallet
### Goals
1. Creating metrics needed of alpha numbers (25K - 50K users)
2. Launch high quality onboarding process (Superhero white glove process)
3. Community engagement, create distribution channel
### Scope
1. Growth strategy, eraticate polkadot.js as default wallet option
2. Focus on web3 natives
3. Build user adoption pipeline
4. Into non-English speaking Web3 adopters
5. Structuring community to Nov 22nd launch
6. Governance handover to community
### Future Considerations
1. Normie consumer adoption
2. Nov 22nd launch, Generate NFTs as kudos
3. Token Sale
### Out of Scope
1. Normie consumer adoption
2. 2000 adoption of Nov 22nd launch
3. Conversion rate
### Milestones
1. Chrome Extension - Nov 22nd
### Project Exit
1.
### Key Stakeholders
John & Nick decision
### Constraints/Assumptions/Risks/Dpendencies
### Payments
### Deliverables
1. Growth strategy, eraticate polkadot.js as default wallet option
2. Build user adoption pipeline
3. Structuring community to Nov 22nd launch
4. Governance handover to community
5. How structure community better