Solving for the Why: Innovation as a Response to Friction

The Blue-Collar Nature of Innovation

We often talk about innovation as if it’s a lightning strike. A moment of brilliance that hits the right person at the right time. The myth of the lone genius—scribbling an idea on a napkin or having a revelation in the shower—still dominates how we imagine progress.

But real innovation doesn’t look like that.

Real innovation is blue-collar work. It shows up in patience, repetition, and a willingness to pay attention to irritation. It isn’t born from inspiration; it’s born from friction. If you want to innovate, don’t start by scanning competitors or chasing trends. Start by listening for sighs. Watch for the pause before someone says, “I guess this is just how it works.”

Pay attention to the spreadsheets, sticky notes, and side documents people build just to survive your systems. Those workarounds are not failures of discipline or compliance. They are signals. Innovation, at its core, is simply the act of removing them.

At Veritas, we don’t innovate for the sake of the “new.” New is cheap. New is easy. We innovate for the sake of the “better.” That distinction matters. Better is respectful. Better starts with the belief that the user’s time, energy, and attention are finite—and worth protecting.

The Friction Audit

Innovation doesn’t begin with a roadmap. It begins with an audit.

Where does the process slow down for no good reason? Where does information get entered twice, copied manually, or re-sent because “the system didn’t sync”? Where do approvals stall, emails pile up, or responsibility blur just enough to create delay?

These moments are rarely dramatic. They’re small. Repetitive. Easy to ignore if you’re not the one dealing with them every day. That’s why so many organizations miss them. Leadership dashboards don’t show annoyance. Metrics don’t capture frustration.

But those friction points compound. A thirty-second annoyance repeated a hundred times a week becomes real cost—financial, cognitive, and emotional. Multiply that across teams and years, and you’re no longer talking about inconvenience. You’re talking about burnout, disengagement, and quiet resignation.

Solving these problems doesn’t require a lab. It requires an observation deck. You have to be willing to watch how work actually happens, not how it’s described in policy manuals or slide decks. Real processes live in the gaps between official steps.

Solving for the Why

When we set out to improve EMS training, we didn’t start with technology. We started with frustration. Providers told us they felt unprepared—not because they hadn’t studied, but because training didn’t reflect the reality of the street. The problem wasn’t effort. It was mismatch.

Linear education was being asked to prepare people for nonlinear environments. That friction showed up as anxiety, second-guessing, and lack of confidence in high-stakes moments. The technology—the AI-driven simulations—came later. It wasn’t the innovation. It was the tool we used to remove the friction.

This is where many innovation efforts fail. They skip straight to solutions. New platforms. New dashboards. New AI features layered onto old problems. It feels productive, but it’s backwards.

You can’t solve a problem you don’t understand. And you can’t understand it if you haven’t asked why the friction exists in the first place.

Why does this step exist? Why does approval take this long? Why does this task require three systems and two emails? Most of the time, the answers have nothing to do with user needs. They’re artifacts of legacy decisions, risk aversion, or tools that were never designed to work together.

Empathy as a Technical Specification

We tend to think of empathy as a soft skill—something cultural or interpersonal. In reality, empathy is a technical requirement. If you don’t deeply understand the person on the other side of the system—their constraints, pressures, and cognitive load—you will design friction into the product whether you mean to or not.

Every extra click is a tax. Every unnecessary field is a tax. Every ambiguous instruction is a tax. Individually, they seem minor. Together, they shape how people feel about their work.

True innovation is an act of care. It’s choosing to fix the small things because you recognize their cumulative weight. When you stack enough of those fixes together, something important happens. You don’t just improve a workflow. You change the emotional experience of the work itself.

That’s the difference between a “Eureka!” moment and a “Thank God you fixed that” moment. The first flatters the creator. The second serves the user. And over time, it’s the second kind of innovation—the quiet, respectful kind—that actually lasts.