What I Learned from the MIT and Veterans Health Hackathon: Innovation Needs More Than Just Great Tech

An empty lab while hackers take a break

Earlier last year, I participated in a national hackathon focused on improving healthcare for veterans—a cause that brought together hundreds of people from all over the country. The energy in the room was contagious. Clinicians, entrepreneurs, product thinkers, and developers gathered with one mission: to design solutions that could truly make a difference in the lives of veterans.

While the event was rich with good intentions and cutting-edge tools, it also exposed a few challenges we often overlook in fast-paced innovation settings.

Everyone Had Big Ideas—But Narrowing Down Was Hard

One of the first things I noticed was how hard it was for teams to focus their ideas. Many tried to tackle massive problems all at once—partly because they weren’t sure what the judges were looking for, and partly because they didn’t want to miss an angle. But trying to “boil the ocean” led to scattered concepts that lacked a clear problem-solving mindset. Focusing on a specific pain point and going deep just wasn’t intuitive for many.

Tech Was Available—but Not Always Helpful

Microsoft provided a wide array of tools, from Power Apps and Copilot Studio to integrations with OpenAI. However, these tools were introduced late in the process, and teams found themselves distracted by figuring out how to use them rather than deciding why or if they should.

This highlighted a recurring problem I see in tech-driven spaces: the solution gets picked before the problem is fully defined. Instead of designing for impact, many teams were caught up in assembling features.

AI Hype Was Everywhere—But Data Strategy Was Missing

Generative AI was the buzzword on everyone’s lips, but I noticed very little discussion around data modeling, infrastructure, or governance. Many teams assumed that data across different systems could be easily centralized, or that AI could just plug in and go. The reality, of course, is far more complex—especially in government or healthcare settings.

Without clear strategies around implementation, data quality, or policy, even the best ideas risk stalling.

What This Means for Future Hackathons

For me, this event reinforced how important it is to bring in design and systems thinking early on. It’s not enough to have powerful technology or enthusiastic teams—you need framing, facilitation, and structure that guides people toward viable, focused solutions.

This experience also made me think about how future events could be even more impactful:

  • Smaller scope, bigger impact. Narrowing the challenge leads to better outcomes.
  • Design before tools. Don't lead with the tech. Lead with understanding.
  • Bring in more cross-functional support. Especially people who understand systems, data modeling, and implementation realities.

I came away inspired by the passion I saw, but also deeply aware that tools alone don’t solve problems. People do—when given the right environment, the right support, and the right frame of mind.

Let’s connect

I’m always looking to collaborate with others passionate about thoughtful, real-world innovation in healthcare and public service. Reach out if you're interested in co-creating or sponsoring future events.