Community Operating System

GDGoC NF ran programs through separate tools while member motivation dropped during the middle of an operating term. I wrote a PRD and built an MVP prototype to connect member learning, event operations, project records, and division goals.

Problem

The PRD identified a lack of a shared operating structure. Members needed a clear path through programs, while the core team needed records for events, progress, and division work.

Role and scope

I authored the PRD and built the Next.js and Supabase prototype. I implemented public pages, member authentication, events, profiles, projects, materials, kudos, member management, and an admin OKR area.

Process and decisions

I defined three personas, grouped requirements into public, member, and admin epics, then marked each requirement as must-have, important, or nice to have. The MVP scope centered on registration, member learning, event management, and OKRs.

The PRD lists adoption, attendance, satisfaction, and division use as success targets. The prototype code also contains hard-coded OKR progress and a simulated active-member calculation. I exclude those interface values from the results.

Prototype output

I finished a dated PRD, Supabase schema, authentication paths, member pages, and admin tools. The prototype turns the prioritized user stories into a navigable product rather than leaving them in a requirements document.

I have not piloted the product with GDGoC members, so I cannot report completed profiles, event attendance, satisfaction, or division adoption.

Limits

The application contains prototype metrics and needs a production security review. Its Git history also contains an environment file, so I must rotate the credentials and remove the file before deployment. A member pilot should replace target and simulated values with measured outcomes.