Back to portfolio
Community & GrowthSimulated project
Community Manager portfolio brief
A simulated community & growth exercise for Community Manager. Treat it as realistic practice, not real client or protocol work.
6 deliverables6 tools referenced3 linked interview questions
Objective
Audit one community and identify its actual jobs-to-be-done
Expected deliverables
Community strategyMonthly programming calendarHealth and sentiment reportFeedback taxonomyCrisis communication planEvent recap
Recommended workflow
- Audit one community and identify its actual jobs-to-be-done
- Build a 30-day programming and reporting system
- Document how one user signal should move from chat to an internal owner
- Review the result against the rubric, then package it as a case study.
Constraints and safety
- Use only public sources or clearly simulated data.
- Never include seed phrases, private keys, or wallet secrets.
- Redact private user, company, security, legal, or compensation information.
- State every assumption you make.
Tools in practice
- Discord
- Run programming, coordinate moderators, collect recurring user signals, and manage incident communication.
- Telegram
- Run programming, coordinate moderators, collect recurring user signals, and manage incident communication.
- Notion
- Draft, review, and maintain community strategy and monthly programming calendar, with owners, source links, and change history.
- Typeform
- Collect structured intake for community strategy and monthly programming calendar, with consent and ownership fields where needed.
- Dune or product analytics
- Compare community signals with product or onchain behaviour to see whether participation turns into useful action.
- event tools
- Manage registration, reminders, attendance, speaker details, and post-event feedback for recurring programmes.
What a strong submission shows
- A 30-day community plan
- A health dashboard with metric caveats
- An incident postmortem
- A case study showing feedback turned into a product or process change
Weak submission patterns
- Follower or member growth with no quality context
- Event photos without objectives or outcomes
- Generic engagement calendars copied across projects
Review rubric
- Accuracy of claims and sources
- Relevance to the target role
- Decision quality and trade-offs
- Completeness of the deliverable
- Clarity of communication
- Honest limitations and next steps
Present it as a case study
- Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
- Show the final artifact before the process notes.
- State what you owned and what belonged to other people.
- Label the work as simulated, and keep any real contribution clearly separate.
Interview questions this project helps you answer
How would you measure community health when token speculation drives most activity?
Describe a time community feedback should change product or policy priorities
How would you communicate during an incident when the technical facts are still incomplete?