Community 👥
Phoenix
IIT Delhi · Product community
By Arush Bansal
Community as a product
At IIT Delhi, interest in product far outpaced structured paths to practice it. Phoenix filled that gap: talks with practitioners, build nights, peer feedback, and a culture where "I shipped" mattered more than "I attended."
Scale without quality is just noise — we optimized for builders who finish.
As lead, I owned programming, partnerships, and the tone of the room. The goal was simple — lower the activation energy for students to go from idea to demo. That meant clear rituals (weekly builds, demo days), accountable leads, and campaigns that had deadlines, not open-ended enthusiasm.
The innovation campaign
The two-month innovation campaign was the flagship beat: teams formed around real problems, iterated in public, and presented outcomes to peers and mentors. It compressed the product loop — problem, prototype, feedback, ship — into a campus-sized sprint.
- 01
Recruit for finishers
We biased toward people who had shipped something small before — a bot, a landing page, a hackathon repo — because momentum compounds.
- 02
Create forcing functions
Open-ended communities decay. Campaigns with dates, demos, and lightweight prizes kept attendance honest.
- 03
Bridge to industry
Alumni and founder visits turned abstract advice into concrete next steps — hiring loops, GTM mistakes, and tech choices.
The best communities do not hoard inspiration — they convert it into shipped work.
Suggested next read
NovaGPT
AI · LLM applications