When writing innovation proposals or reviewing them, it is often not the big ideas that cause problems, but the seemingly trivial details that everyone assumes are obvious. Reviewers regularly stumble over unclear definitions, implicit assumptions, or small inconsistencies that teams no longer notice themselves. These “non-trivial trivialities” are not just proposal artefacts; they are recurring patterns in collaboration in innovation projects, where overlooked assumptions and hidden misalignments quietly undermine execution long before technical challenges emerge.

A few years ago, I had to explain communication delays in a 750-meter train to a renowned academic. To me, the problem was obvious. His response? “But the delay across that distance is just microseconds. What’s the issue?”

That’s when I realized I’d skipped over a key detail—so basic in my domain that I didn’t think to mention it. The train wasn’t a single, continuous structure. It was composed of 20 modular units, linked by 30 different systems, each introducing a bit of latency. Once I explained that, the professor nodded. “Ah, now I understand. That’s a real challenge.”

That moment gave me a crucial insight: in innovation proposal writing, assuming shared context is a risky shortcut. What feels too simple to include—those non-trivial trivialities—can be exactly what others need to see the full picture.

This is especially clear in my role as a reviewer for innovation funding proposals. I often see well-established companies, brimming with sector expertise, fall into the same trap. Their proposals fail not because their ideas lack value, but because they skip over foundational explanations. Evaluators are left guessing about critical assumptions. The result? Missed funding opportunities—not from a weak concept, but from weak communication.

So, how do you write a winning innovation proposal?

Spell it out. Be explicit. Contextualize your problem. Explain your innovation clearly, including what might seem “too basic.” Highlight the structure, the systems, the environment in which your solution operates. By addressing these overlooked details, you make it easier for reviewers to understand the challenge—and the value of your solution.

Remember, clarity builds confidence. A well-explained proposal not only scores higher but also sets the stage for stronger collaboration in innovation projects down the line, and delivers the results you want.