How a project moves through the lab
Six steps, in a loop. What we ship raises the next round of questions, and the people who built it help the ones who come next.
- 01
A problem comes in
From a partner company, a faculty researcher or a CPE team. We ask who feels the pain, how often, and what better would look like.
Leaves behind: Problem brief
- 02
Frame it with experts
Faculty and practitioners help define the data, the constraints and the measure of success before anyone writes code.
Leaves behind: Scope and success measure
- 03
Form the team
Students are matched by skill and interest, with a lab lead and a domain mentor. Everyone knows what they own.
Leaves behind: Student team and mentors
- 04
Build in short sprints
Working software every week, demoed to the people who asked for it. Feedback lands while it is still cheap to change.
Leaves behind: Weekly working demos
- 05
Prove it before it scales
We test with real users and check accuracy, accessibility, privacy and cost. If it is not better than the old way, it does not ship.
Leaves behind: Evaluation and sign-off
- 06
Ship it and pass it on
The system goes into daily use with an owner and a way to measure it. Students leave with shipped work, and the next cohort picks up the roadmap.
Leaves behind: A system in use, and the people who built it