Designing MVP for Chapter Leaders platform 🚀
Closed this issue · 0 comments
Description
This project will consist of building a working MVP for the chapter leaders platform. This platform will serve as a place where chapter leaders can access and keep track of the members in their school's chapter and, more broadly, the national ColorStack members at their school.
Problem / Value Proposition
As the number of chapters (and chapter leaders) grows, it becomes increasingly clear how a centralized platform could simplify the process of starting and managing a school chapter. Furthermore, there have been recommendations for various features relevant to school chapters, but many of these tools can't be built without an initial platform for chapter leaders. By developing a basic platform, chapter leaders will immediately have a centralized manner to keep track of basic information about each member in the chapter, as well as contact information about ColorStack members that may not yet be part of the school's chapter (for the members that opt into sharing their email with local chapter leaders).
For this MVP, the focus can be on setting up a chapter member directory. Then, chapter leaders will be able to manually add/remove members from their school's directory, as well as update information such as email address or membership status. The value comes from providing an easier way for chapter leaders to manage members, distribute roles, access info such as emails, and gain perspective on size and growth of the chapter.
Additional Context
What features should be included?
As an initial MVP, we won't aim to implement every feature that we might think of yet, but figure out what are the essentials to begin with.
- A dashboard for chapter leaders
- Table to view/manage members in chapter
What information should be included within table?
Possibilities: Name, email, position/role in chapter, chapter membership status, ColorStack membership status - View/access emails of ColorStack members at university that aren't necessarily in chapter yet
- Integrates the new feature that can give chapter leaders access to emails of local ColorStack members that opt-in to sharing their email for local events and opportunities.
- Can be especially useful when starting a chapter at a new school to find current ColorStack members
- Quick way to export data such as email list, or CSV with member names
Which of these seem essential for the MVP? Anything that's not yet listed?
Where do we want to have the chapter platform?
- An app separate from the member profile app or the admin dashboard app.
- Integrated as a new page within the member profile app
In terms of scalability, (1) may be preferable because if we want to add more pages for more complex functionalities, it makes sense to have a separate app for this. For example, if in the future we were to add support for workflows such as managing applications or managing/scheduling events, it would make sense to have a separate app. However because chapters are still relatively small groups (compared to all of ColorStack) it's not clear if or when these workflows would be needed within the platform.
In terms of implementation, (2) is more favorable. With the current aim of building a page with a table containing the member directory, it would make more sense
Other thoughts
Do we want to create a platform that's exclusively for chapter leaders, or should there be support for university chapters to connect on the ColorStack platform? It might make more sense to start with just providing support for chapter leaders' administrative needs.
Once a basic platform is built, there will be a lot of opportunities to build upon it with various features. These are likely outside the scope of this project, but future features could include
- referral codes/application streamlining
- an easy way to export lists of members/emails (useful to contact members, but also to share with companies interacting with the chapter)
- scheduling/management of chapter events
(sample design):
