Product Strategy: Solve Problems or Create New Behaviors?

As a science graduate, I’m always impressed by the beauty of nature.

We see intricate systems everywhere, from the complex dance of a galaxy to the organized chaos of an ant colony. Recent studies show us how ants establish sophisticated paths using simple rules, creating emergent complexity. It means that we learn something from nature. Nature is just out there, and we look at it every day. What we are waiting for? We can learn much more by observing these natural systems. In the world of building products, we often find ourselves asking a fundamental question: Are we like engineers, meticulously fixing a known leak in a pipe? Or are we architects, envisioning and constructing entirely new ways for people to live and interact within a space? In other words, do we build products primarily to solve problems, or to create new behaviors?

Nature, in its wisdom, often does both simultaneously. Understanding this duality, much like understanding the dynamics of an ecosystem, is crucial for building impactful and lasting products.

The Engineer’s Path — Solving Problems

Let’s first consider the engineer’s approach. Think of a beaver diligently building a dam. It perceives a problem — perhaps inconsistent water levels affecting its lodge or food access. The dam is a direct solution to that specific problem. This is problem-solving in its purest form.

In product development, this translates to identifying clear user pain points, addressing unmet needs, or fulfilling well-defined Jobs-To-Be-Done. We learn to define things clearly, like in mathematics: If a user cannot easily share a file (Premise A), and needs to collaborate (Premise B), then we need a sharing feature (Conclusion). It’s deductive.

Why is this necessary? Because solving immediate problems provides tangible value, like fixing that leak prevents further water damage. It builds trust and meets immediate user expectations. Think of spellcheck fixing annoying typos, or accounting software automating tedious bookkeeping — clear problems, clear solutions.

But here lies a trap we often see in organizations, something I touched upon when discussing why problem-solving is misunderstood. If we only focus on fixing the obvious leaks, the visible “fires,” we might miss the underlying structural issues. We risk getting stuck in incremental improvements, constantly patching things up, while never fundamentally improving the system or exploring entirely new possibilities. We solve a problem, but perhaps not the right problem, or fail to see the potential beyond it.

The Architect’s Vision — Creating New Behaviors

Now, let’s consider the architect. They don’t just fix leaks; they design environments. Think back to the ant colony. The intricate network of tunnels and chambers isn’t just solving the “problem” of shelter; it creates an environment that enables entirely new, complex behaviors — specialized roles, efficient foraging, sophisticated communication, collective defense. This is behavior creation.

In product terms, this means introducing novel ways for users to interact, leveraging technology to unlock latent desires, or shaping new habits. It’s often about seeing potential others don’t, requiring a “trust in beauty” like the scientists who predicted Neptune or radio waves based on the elegance of their theories.

Why is this transformative? Because creating new behaviors can redefine markets and fundamentally change how people live or work. The smartphone didn’t just solve the problem of carrying multiple devices; it created the behavior of constant connectivity, app usage, and mobile computing. Collaboration tools like Figma didn’t just solve file-sharing issues; they are creating new, real-time collaborative design behaviors.

However, this path carries higher risk. Educating users on new behaviors takes effort. Predicting success is harder, like exploring unknown territory. There are also ethical considerations — are the behaviors we’re creating truly beneficial? It requires vision and a willingness to move beyond the immediately obvious problem.

The Ecosystem View — Problems and Behaviors Intertwined

So, engineer or architect? Problem-solver or behavior-shaper? When I look at thriving systems, whether natural ecosystems or successful product ecosystems, I see that this distinction is often blurred. A healthy ecosystem solves problems (like resource distribution through ecological niches) and creates new behaviors (complex food webs, symbiotic relationships) as a result. The two are interconnected.

Think about Google Search. It solved the clear problem of finding information online. But in doing so, it created the global behavior of “googling” — a new way of accessing and interacting with knowledge. Think about ride-sharing apps. They solved transportation problems (finding a ride, payment friction) and created new behaviors around mobility and car ownership.

It’s rarely just one or the other. Often, solving a deep, fundamental problem in a truly elegant way naturally gives birth to new behaviors. Conversely, a compelling new behavior often succeeds because it taps into an underlying, perhaps unarticulated, human need or solves a latent problem.

This doesn’t mean definitions aren’t important — quite the opposite. As we learned from the need for clear definitions, for any specific feature or initiative, we must be clear: Are we primarily fixing this known leak, or are we trying to architect this new interaction pattern? Understanding our primary intent helps guide our design, metrics, and execution.

Implications for Us — Navigating the Digital Ecosystem

How do we navigate this complex landscape as product builders? We need the skills of both the engineer and the architect. We need to ensure the foundations are solid (solving key problems) while also having the vision to build inspiring structures (creating new behaviors).

• Discovery: Our methods must adapt. User interviews and surveys are great for uncovering known problems (the leaks). But identifying opportunities for new behaviors might require broader observation, trend analysis, exploring technological possibilities, and perhaps ethnographic research — understanding the ‘why’ behind current behaviors to imagine future ones.
• Strategy & Vision: Our product strategy needs conscious balance. Are we solely focused on incremental fixes, or are we investing in potentially transformative, behavior-shaping innovations? This requires leadership with vision, willing to “trust in beauty” and explore beyond the immediate.
• Measurement: Success looks different. Problem-solving might be measured by task completion rates, time saved, or support ticket reduction. Behavior creation might need metrics around adoption rates, engagement frequency, habit formation (e.g., DAU/MAU ratios, retention cohorts), or the emergence of new usage patterns. We must define what success means for each approach.
• Team & Culture: We need teams with diverse skills, capable of deep empathy to understand user problems and imaginative foresight to envision new possibilities. A culture that values both meticulous problem-solving and bold experimentation, like the collaborative yet specialized meerkats, is essential. A design-driven culture, as I discussed before, helps bring this empathy and foresight to the forefront.

Conclusion: Beyond the Blueprint

Building products is a fascinating endeavor. We are both engineers ensuring stability and architects shaping interactions. While the immediate satisfaction of solving a well-defined problem is tangible, the potential to create entirely new, valuable behaviors is transformative.

Looking at the most impactful products, much like looking at nature’s resilient ecosystems, reveals a blend. They solve fundamental problems elegantly, and in doing so, often create environments where new, valuable behaviors can emerge and thrive.

So, the next time you approach a product challenge, ask yourself: Am I just fixing a leak, or am I designing a new way to live within this space? Understanding which role you’re playing, and recognizing the interplay between the two, might be the key to building something truly remarkable. What kind of digital ecosystem are you building?