Early in my career at Dow, I presented sophisticated thermal analyses of epoxy resins for printed circuit boards demonstrating how well our product worked. The customer mixed the resin and curing agent in a paper cup, pulled long strings from the mixture, and said, “See, it doesn’t work.” Our measurements were technically sound, but they had not answered the customer’s practical objection. We were evaluating performance through our technical framework rather than fully understanding what mattered to the person using the product.
My father taught me that when the terrain does not match the map, ignore the map. That advice has stayed with me throughout my career in research and development. It captures one of innovation’s most expensive traps: organizations can become exceptionally good at solving problems that do not reflect what customers or the business actually need.
The challenge is that once a problem becomes a specification, a funded program, and a set of performance targets, questioning its assumptions becomes increasingly difficult. Teams are rewarded for executing the plan, even when new evidence suggests that the plan itself deserves reconsideration.
In my first column on signal-to-action discipline, I argued that organizations must translate intelligence into better decisions. But recognizing an opportunity is only the beginning. Leaders must also determine what problem deserves to be solved and remain willing to change that definition as they learn.
Defining the Problem Is Not the Same as Understanding It
One of the most common mistakes in innovation is confusing a customer’s stated request with the underlying need. A customer asking for a stronger material may actually need greater equipment reliability. A manufacturer requesting a more durable component may be struggling with maintenance practices. A business demanding a cheaper product may have a cost problem rooted in its distribution system. Accepting the initial request as the definitive problem can narrow the range of solutions before the organization understands what truly matters.
I have seen this happen in large organizations. R&D, manufacturing, marketing, and finance can endorse the same project while holding different assumptions about why it is necessary and what success should look like. A charter may specify technical requirements, performance targets, timelines, and budgets with extraordinary precision while leaving the underlying customer or business need inadequately understood.
A strong project charter should therefore explain the customer or business need, identify the assumptions supporting that diagnosis, and establish what evidence could justify changing direction. It should distinguish the desired outcome from the particular solution being pursued.
My father’s map-and-terrain advice is especially relevant here. A project charter is a map, not the territory itself. It helps guide the journey, but it cannot anticipate everything a team will discover along the way.
Let the Problem Evolve as You Learn
I used to tell R&D teams not to enter the laboratory until they could explain the consumer insight, its alignment with the brand promise, and the claim we hoped to put on the box. These were working hypotheses, not demands for absolute certainty. They connected technical work to a meaningful consumer benefit. The investment case also needed a compelling value proposition, a viable business model, and a credible route to market.
I saw the value of remaining open to new possibilities at Kimberly-Clark, where a research team exploring gecko-inspired surfaces for diaper fasteners developed microstructured and nanostructured materials intended to mimic the remarkable adhesion of gecko feet. Geckos adhere to surfaces through intricate structures that exploit intermolecular forces. The team attempted to translate this biological capability into an alternative to conventional hook-and-loop fasteners, but the technology did not perform well enough for its intended application.
At that point, the team could have continued refining the technology against its original specifications. Instead, investigating how those structures interacted with skin opened an entirely different line of inquiry involving drug delivery. That work helped lead to Sofusa, an investigational platform designed to deliver medicines through the skin for uptake into the lymphatic system.
Consider the significance of that pivot. Research originally intended to fasten diapers helped open an opportunity to fundamentally change how medicines could be delivered. The original application did not succeed, but the knowledge and capabilities developed through that research created the foundation for a potentially more valuable opportunity.
The team recognized that the terrain had changed. Rather than continuing to follow the original map, it explored where the science was leading.
The lesson is not that the fastener problem was necessarily wrong. It is that experimentation can reveal opportunities beyond the application for which a technology was originally developed. Leaders must recognize when new evidence justifies redirecting resources rather than continuing to optimize the original solution.
Understand the Need Beyond the Product
Sometimes the problem is not technological at all. It is that organizations misunderstand what customers are trying to accomplish.
Kimberly-Clark’s development of Pull-Ups training pants illustrates this principle. Researchers investigating parents’ frustration with toilet training discovered that the challenge involved more than absorbency and leakage. Children wanted the independence and pride associated with becoming a “big kid,” while parents wanted to encourage that transition without the inconvenience of cloth training pants.
Research revealed how painful it could be for a mother to hear that her toddler was “still in diapers.” The emotional dimension of toilet training mattered as much as the functional requirements. Kimberly-Clark already knew how to manufacture diapers, but the opportunity was not simply to make a better diaper. It was to help children move beyond them.
Pull-Ups combined protection with a product children could pull up and down themselves, supported by positioning that reinforced confidence and independence. Understanding the broader human need created an innovation fundamentally different from another incremental improvement in diaper performance.
A similar principle applied to Kleenex Cool Touch tissue. I remember phase-change research that had struggled to find a meaningful commercial application. The technology was scientifically interesting, but novelty alone did not give consumers a compelling reason to purchase it.
That changed when the Kleenex team recognized an opportunity to soothe sore noses during cold and flu season. What had been an interesting technical capability suddenly had a clear consumer benefit, transforming an underutilized technology into a differentiated product experience.
These three innovations followed different paths. Pull-Ups training pants emerged from understanding an emotional and developmental need. Kleenex Cool Touch tissue connected an existing technology to a compelling consumer benefit. Sofusa drug delivery grew from recognizing an entirely different application for a technology initially developed for diapers.
Consumers do not buy technologies. They buy better outcomes and experiences. The technology gives them a reason to believe.
For innovation leaders, the implication is straightforward: challenge teams not only to explain how a product or technology works, but why the outcome matters to the people it is intended to serve.
Measure Success in the Real World
Even when teams identify a valuable opportunity, they can lose sight of it through the measures used to evaluate progress. Technical specifications, schedules, budgets, and development milestones are necessary, but they do not independently demonstrate customer or business value.
I learned this lesson from that Dow customer holding a paper cup. We had invested considerable effort in developing and characterizing the epoxy chemistry for FR4 laminates. Our analytical tools demonstrated how the material performed, yet the customer’s simple demonstration exposed a disconnect between what we measured and what they expected.
Our laboratory data represented the map. The customer’s experience was the terrain.
This disconnect becomes especially costly as projects approach commercialization. A team may meet its laboratory specifications while manufacturing struggles with reliability, cost, or scale. Another may exceed its technical targets but provide too little additional consumer value to justify a higher price. In both cases, technical success can coexist with disappointing business results.
For a Chief R&D or Innovation Officer, technical measures must remain connected to commercial and operational outcomes. Product quality, manufacturability, customer adoption, total cost, and the actual benefit delivered may all matter, depending on the innovation.
One particularly revealing question is: Can this metric improve while the customer’s or business’s actual situation remains unchanged?
If the answer is yes, leaders should reconsider whether the team is measuring the right outcome or has correctly diagnosed the problem.
Make Reconsidering the Problem Part of Every Funding Decision
Traditional project reviews often focus on whether milestones have been achieved, technical risks reduced, and spending kept within budget. Those questions are necessary, but insufficient. A project can perform well against all three while becoming progressively less relevant to the opportunity that originally justified its investment.
I would add a question to every significant funding review: “What have we learned that could change our understanding of the problem?”
That question requires teams to distinguish observations from assumptions. Leaders should understand what evidence supports the current diagnosis, what alternative explanations remain plausible, and what customers or manufacturing operations have taught the organization. Most importantly, they should establish what evidence would justify continuing, redirecting, or stopping the investment.
Throughout my career, I challenged teams to get to “KnoW quickly,” playing on the distinction between “no” and “know.” Either we understood why an investment deserved to proceed and how, or we could explain why it should not. I also wanted to understand the value of saying yes and the risk of saying no. The objective was disciplined learning that informed consequential decisions, not endless analysis.
A productive funding review should result in a decision, an accountable owner, and a defined next step. Where significant uncertainty remains, leaders can fund targeted experiments rather than automatically committing to a full development program.
Equally important, teams must feel empowered to challenge their original project charters. If changing direction is treated as failure, people will hesitate to present evidence that could prevent wasted investment.
The cost of persisting with the wrong problem extends beyond the money spent. Every dollar committed to an increasingly questionable opportunity is a dollar unavailable for something more promising.
This becomes even more consequential as artificial intelligence expands what R&D organizations can accomplish. AI can help teams investigate possibilities, evaluate alternatives, analyze complex information, and develop technical solutions faster. But greater problem-solving capacity does not guarantee that the problems being pursued are worth solving. Without disciplined judgment, organizations risk becoming faster and more efficient at solving the wrong problems.
The Leadership Challenge
I believe the purpose of business is to improve people’s lives. For innovation leaders, that means judging success not simply by technical achievements, completed milestones, or successful product launches, but by the value created for the people we serve.
At your next portfolio review, ask each team to present two kinds of evidence: evidence that its solution is progressing and evidence that it is still solving the right problem. The first demonstrates execution. The second establishes whether the investment still deserves to be made.
My father’s advice continues to guide me: when the terrain does not match the map, pay attention to the terrain. In innovation, the map represents our assumptions, plans, and specifications. The terrain is what we learn from customers, experiments, manufacturing, and the marketplace.
The best innovation leaders know when to trust the map, when to question it, and when the evidence demands a different route.
The goal is not to defend the problem we originally defined. It is to keep getting closer to the problem worth solving.
Click here for more columns from Pete Dulcamara on All Things Innovation.
Contributor
-
Pete Dulcamara is the author of High-Tech Heroes: Why Gen Z Is Our Last and Best Chance to Save the Planet and has more than 35 years of experience leading innovation, research and development, engineering, and business transformation. He previously served as Chief Scientist and Vice President of Corporate Research & Engineering at Kimberly-Clark and held multiple global R&D leadership positions at Dow Chemical. Today, he advises organizations on innovation strategy, emerging technologies, artificial intelligence, and the systems required to convert insight into sustainable competitive advantage. Visit www.petedulcamara.com.
View all posts


















































































































































































































































































