A champion for brain injury patients

When you spend all day looking at code or liquidity pools, it is easy to forget that the end goal of technology is usually to solve a human problem. We talk about 'users' and 'nodes,' but rarely about the messy, unpredictable reality of human recovery. The story of Alissa Totman and the MIT BrainTrust is a necessary reminder that some of the most impactful solutions don't come from a fancy new LLM, but from bridge-building between builders and the people they serve.

The Proximity Gap in Product Development

Most founders I talk to are obsessed with scale. They want to build something that reaches millions of people instantly. But there is a massive downside to this mindset: distance. When you are far away from the actual suffering or challenges of your target demographic, you build features that look good on a pitch deck but fail in the real world.

Totman started as a sophomore at MIT joining a student-run organization called BrainTrust. The premise was simple: connect undergraduates with people who had suffered brain injuries. It wasn't about data collection or clinical trials; it was about socializing and support. It was about seeing the 'human experience' of a diagnosis that most people only read about in textbooks. For builders, this is the ultimate form of user research, though we rarely treat it with that kind of respect.

Moving Beyond the Clinical Lens

In the tech world, especially in the growing intersection of AI and healthcare, we have a tendency to treat patients like biological machines that need a software patch. We look at a brain injury and think about neural pathways, data recovery, and cognitive benchmarks. What Totman realized—and what every founder should take to heart—is that the technical recovery is only half the battle. The other half is the social and psychological reintegration.

If you are building a decentralized health platform or an AI-driven diagnostic tool, are you accounting for the isolation that comes with these conditions? A tool that solves a technical problem but ignores the human context is a tool that won't be used. BrainTrust succeeded because it filled a gap that medicine often ignores: the need for community. As builders, if we aren't creating community alongside our products, we are leaving the most important part of the architecture on the table.

The Founder's Journey and the Pivot to Empathy

Totman’s path from a student volunteer to a professional advocate shows a clear trajectory that parallels the founder's journey. You start with curiosity, you encounter the raw reality of the problem, and you realize the existing systems are insufficient. In her case, the 'system' was a medical approach that often leaves patients feeling like a collection of symptoms rather than a person.

For those of us in the crypto and AI space, we have a similar problem. We build complex systems and expect the public to just 'get it.' We blame the lack of adoption on poor education rather than poor empathy. We need more 'BrainTrust' style initiatives in tech—places where developers actually have to sit across from a non-technical person and explain why their work matters, or better yet, listen to why it doesn't.

Why Most Healthcare Tech Fails

I’ve seen dozens of startups try to disrupt healthcare with blockchain. Most of them fail because they are solutions looking for a problem. They focus on the efficiency of data transfer while ignoring the fact that the data represents a person in pain. Totman’s experience teaches us that you cannot innovate in a vacuum. You have to be willing to get your hands dirty in the 'human experience' aspect of the industry.

• Build for the person, not the patient: Labels like 'user' or 'patient' dehumanize the people you are trying to help.
• Proximity matters: If you haven't spoken to a real person dealing with the problem you're solving in the last week, you're building in the dark.
• Social layers are critical: Every successful tech platform eventually becomes a social platform. If you don't build that in early, you're missing the point.

The Long Game of Advocacy

Building a company is a marathon, but building a movement or a new standard of care is a decathlon. Totman didn't just volunteer for a semester and move on. She allowed the experience to shape her entire career path. That kind of long-term commitment is what separates the tourists from the founders who actually change things. We need fewer people looking for an exit and more people looking for a legacy.

When we look at organizations like MIT BrainTrust, we shouldn't just see a student club. We should see a model for how to integrate social impact into the very fabric of technical education. If every computer science major had to spend a year working directly with the people their algorithms would eventually affect, the tech landscape would look very different—and a lot more humane.

Bridging the Gap Between Code and Care

We are at a crossroads in technology. We can either continue to build increasingly abstract systems that treat humans as secondary, or we can follow the lead of people like Totman who prioritize the human connection first. For the builders reading this, the challenge is simple: look at your roadmap and ask yourself where the 'human experience' is accounted for. If it’s not there, you aren't building a solution; you're just writing code.

Technology should be a bridge to better human connection, not a barrier that replaces it.

The takeaways here are clear. Don't be afraid of the 'soft' side of development. The socializing, the support, and the storytelling are just as important as the backend. In fact, they are the only things that will make your backend matter in the long run. Let's stop building for the sake of building and start building for the sake of the people who are actually struggling.

Read the original at MIT Technology Review →