BME capstone project — how did you pick your topic and survive the process?
Coming into my senior year and the capstone is the one thing I've been dreading since freshman orientation. Our program gives us a lot of freedom to propose our own project, which sounds great until you're staring at a blank doc trying to justify why your idea is novel enough to pass faculty review. Did anyone else find the topic selection phase more stressful than the actual project work?
I'm leaning toward something in thermal systems or fluid mechanics because that's where I've done the best in coursework. My advisor suggested looking at heat exchanger efficiency optimization, which feels both manageable and substantial enough. But I've also seen teams go the mechatronics or robotics route and those projects seem to have more visible deliverables, which I think helps during final presentations.
Our capstone runs two semesters — about 30 weeks total. The first semester is mostly research, design, and prototyping; second is testing, iteration, and the final report. Teams are 3-4 people and we've been warned that team dynamic issues are the number one reason projects go sideways, not technical problems. Already a little worried about that going in.
Anyone willing to share what their project was, roughly how many hours a week you were putting in during peak crunch, and whether you'd pick the same topic if you could go back?
We did a variable-geometry wind turbine blade project and it was intense but worth it. Peak crunch during testing was probably 20-25 hours a week on top of regular coursework. The visible prototype definitely helped during our final presentation — examiners respond well to something they can see actually working.
Heat exchanger optimization is a solid choice. It's well-understood enough that you can find good literature, but there's still room to do something genuinely new if you narrow your focus. One team in my cohort did fouling rate modeling and their advisor loved the direction they took it.
I'd pick the same topic again but I'd spend way more time on the design phase. We rushed into prototyping and had to redesign twice, which ate about 5 weeks we didn't have. Front-load your analysis even when it feels like you're not making visible progress.
Team dynamics really are the make-or-break factor. We had one person who basically disappeared for 6 weeks mid-project and it nearly derailed everything. Set clear milestones and accountability checkpoints early — don't assume goodwill will carry you through a 30-week commitment.