The question I kept getting asked

For years, people asked me some version of the same question. Someone would have an idea for a device, or a way to fix a problem they saw every day at work, and they wanted to know how to turn it into something real. I didn’t have a short answer. That’s part of why I wrote “Innovation in Translation, How Big Ideas Really Happen.” I wanted to give people the long answer, in a form they could actually use.

The short answer, the one people want, is usually wrong anyway. It goes something like: have a great idea, find funding, build it. That’s not how translation works. It’s not even close.

Translation is the part nobody names

I use the word “translation” in the title on purpose. An idea is not a product. A product is not a company. Moving from one stage to the next is a distinct kind of work, and it’s different work each time. Most people think the hard part is having the idea. In my experience, the hard part is everything after that.

Translating an idea means taking something that lives in one person’s head, usually shaped by their own frustration with a problem, and turning it into something other people can build, trust, and use without that original person in the room. That’s a real skill. It’s not the same skill as spotting the problem in the first place.

I wrote the book because I kept meeting smart people who had the first skill and assumed the second one would follow naturally. It doesn’t.

Why I didn’t write a success story

I could have written a book that just walks through the deals I’ve been part of. That’s not what “Innovation in Translation” is. It’s a book about the mechanics: how big ideas move from concept to something a patient, a doctor, or a customer actually holds in their hands.

I think books that only tell you what worked leave out the part that matters most, which is how the person figured out what to do when the plan stopped working. So the book spends time on the mechanics of translation itself: how you decide what to keep from the original idea, what to change, and who needs to be in the room before you build anything.

What “big ideas really happen” means to me

The subtitle isn’t a tagline. It’s a claim I believe: big ideas don’t happen the way most people picture them. There’s no lightning bolt moment where the idea shows up fully formed and the rest is execution. The idea shows up rough, gets pushed on by people who don’t agree with it, gets rebuilt two or three times, and only then starts to look like the thing that eventually reaches people.

If you’ve only ever seen the finished product, that process is invisible. That’s exactly why I wanted to write it down. I wanted the messy middle to be on the page, not just the outcome.

Who I wrote it for

I didn’t write this for people who already run large companies. I wrote it for the person early in the process, the one staring at an idea and a blank page, trying to figure out what step one actually is.

That reader might work in a hospital, a lab, a garage, or an office that has nothing to do with medicine at all. Translation isn’t unique to any one field. Anyone moving an idea from their own head into something other people can use is doing the same basic work, whether the end result is a device, a service, or a piece of software.

What I hope someone takes from it

If you read the book and walk away thinking “translation is a skill, not a moment,” I’ve done my job. That single shift changes how you plan. You stop waiting for the idea to arrive finished. You start building the process that will turn a rough idea into something usable, because you know that process is where the real work lives.

I also hope people finish it with less romance about the whole thing. Big ideas don’t really happen the way we tell the story afterward. They happen slower, messier, and with a lot more people involved than the final version lets on. Knowing that going in doesn’t make it easier. It just means you’re not surprised when it isn’t easy.