Collaborative Product Build

One product, one class, one semester. We’ll design, build, and iterate a real software product together, with ongoing customer feedback driving what gets built next. The users are real, the feedback is real, and shipping is the assignment.

How it works: you’ll serve in rotating squads—product (roadmap and prioritization), research (user interviews and synthesis), design (flows and interfaces), build (implementation with AI tools), and growth (adoption and feedback channels). Squads rotate at each build day, so everyone touches every part of making a product. Build days are marked in the schedule, and squads carry work between them.

No coding experience is required—frontier AI tools have made building accessible to anyone willing to learn, and half the squad roles aren’t about code at all. Your grade reflects three things, logged in a contribution tracker on eLC: what you shipped (features, research findings, designs, docs, growth experiments), how you responded to real user feedback, and how your squadmates evaluate your contribution at each rotation.

Still reading the fine print? Excellent instinct—founders read everything. Email me by the close of drop/add with the word hustle and “ENTR 5000” in the subject line for two extra points on a sprint deliverable of your choosing. Kindly keep this one to yourself.

---

Source: Fall 2026 course syllabus — Collaborative Product Build, copied October 6, 2026.