How Change Becomes Possible

FIELD NOTE 002 · TRANSLATION

What product development taught me about the work between understanding a need and getting an idea forward.

Early in my career, I believed that strong consumer understanding, good technical work, and disciplined execution would naturally lead to better products. The logic seemed straightforward: understand the problem, identify the unmet need, develop the technology, create the product, test it, improve it, and launch it.

Over time, I learned that the path was not nearly as linear as it looked.

I remember sitting in research sessions and hearing consumers describe what they wanted with remarkable clarity. Then we would return to the organization, and some of that clarity would begin to fade. People who had not heard the conversations questioned the conclusions. Those who had been there sometimes interpreted the same words differently. Others remained attached to the answer they had preferred before the research began.

By the time a decision had to be made, we were not only discussing what consumers had said. We were discussing what different people believed those words meant.

That taught me something important: understanding does not move through an organization untouched. It passes through people, and people interpret what they hear through their own roles, experiences, assumptions, and responsibilities. The scientist, marketer, manufacturer, retailer, and senior leader may all be looking at the same opportunity, but they are not necessarily looking for the same thing.

I began to understand that part of my job was helping people see the connection between the human need and the solution we were trying to create. I learned to start with the person experiencing the problem: what was happening in her life, what she saw and felt, what she wanted instead. Then I could connect that experience to what we could observe or measure and, finally, to the technology or product that might close the gap.

That changed how I thought about storytelling.

I had once thought of story mainly as a way to communicate an idea. I came to see it as part of how an idea moves. A story could help people who had not been in the research room understand why the problem mattered. It could connect a technical decision to a human need and help different parts of an organization hold onto the original intent as the work progressed.

Story helped meaning travel. That mattered because innovation was no longer just about creating the right solution. It was also about helping people understand why the solution mattered, what need it was meant to address, and what had to remain true as the work moved forward.

The more I worked across functions and teams, the more I saw that ideas could weaken without anyone deliberately changing them. A handoff could remove context. A technical decision could shift the experience. A business constraint could reshape the solution. A new person could enter the work without the history behind it. Each decision might make sense on its own, while the idea as a whole slowly moved away from what had made it meaningful in the first place.

That realization changed the questions I asked. I still cared about whether the research was strong and whether the technology worked, but I also began asking: Do people understand the same problem? Are we still solving for the same need? Has the original context survived the handoff? Are we making a tradeoff knowingly, or have we simply lost sight of what mattered?

Those questions were not separate from innovation. They were part of the work. I had started my career thinking mostly about how to create the right solution. I was beginning to understand that innovation also depended on what happened around that solution: how people interpreted it, talked about it, made decisions about it, and carried it forward. That was the beginning of a much broader shift in how I understood innovation.

The idea matters. But so does the way it moves forward..