Your notebook is the tool you were missing for clarity in product development.

"I thought you meant..." is the most dangerous phrase in the room when developing a new product.

We have all been in that meeting. The R&D lead describes a new deployment mechanism. The vendor nods. The engineer takes notes. Everyone leaves the room convinced they are aligned.

Three weeks later, you see the prototype, and half the room says, "Wait, that’s not what I pictured."

In the high-stakes world of product development, we often rely on words to describe complex, three-dimensional systems. But words are slippery. As I discuss in the latest episode of Clarity Foundations, relying solely on verbal or written descriptions forces every person in the room to construct their own mental image.

And due to the diversity of human cognition, those mental images rarely match.

Visual thinking is not about making things look pretty. It is about creating a shared reality.

If you prefer to watch, you can find this episode on YouTube.

If you prefer to listen, you can find this episode on Spotify.

The burden of understanding is on you.

In a recent discussion on regulatory submissions, Michael Drues, Ph.D. made a blunt but critical point: If the FDA does not understand your device, it is your fault. It is not their job to decipher your text; it is your job to make the complex instantly understandable.

When you rely purely on text to describe a device’s mechanism, you introduce friction. You invite the regulator (or your investor) to guess. And when they guess, they might assume your device works differently than it does, leading to:

• Misclassification: They might view it as Class III instead of Class II.

• Unnecessary Testing: They might demand data for risks that don’t exist.

• Delays: They will send rounds of additional information requests just to clarify what a detailed drawing could have explained in seconds.
  

Visual thinking is THE universal tool

Visual thinking, the act of translating what is inside your head to paper, is the perfect way to explain and cut through jargon, language barriers, and cognitive differences.

When you take the idea out of your head and scratch it onto a piece of paper, you stop asking your team to imagine. You allow them to see it.

• A sketch removes the hierarchy of technical jargon. A clinician, an engineer, and a marketer can all point to the same line on a paper and say, "That interferes with the user's grip."

• Externalizing an idea forces you to confront reality. You might "know" how it works in your head, but once it is on paper, you spot the flaws that your brain was glossing over.

A picture is worth a thousand... mitigated risks.

You don’t need to be an artist to leverage this. In fact, rough-unfiltered visual thinking is often better in the early stages because it invites collaboration.

1. Use simple diagrams to map the flow and function (Physiology) before you obsess over the parts (Anatomy).

2. If a static image is worth a thousand words, a video is worth a thousand images. Even a simple storyboard or animatic can prevent the catastrophic failure of a live demo that goes wrong.

3. Draw the object AND draw the system. How does the user holding the device affect the viewing angle of the screen? Visualizing these relationships early prevents usability errors that usually aren't caught until validation.

Clarity is Confidence

Visual thinking is communication without even speaking. It ensures that the device you are thinking about is the device your team is building, and the device the stakeholders are approving. In short: It is clarity in product development.

So... Stop describing. Start drawing.