On the surface, the pond looks alive and thriving. The water ripples gently. Children lean over the edge, their nets dipping in and out, pulling up long strands of green. That green is algae and it’s doing its job incredibly well. Too well, in fact.

Algae’s “job” is to capture sunlight and grow. It has succeeded so wildly that it’s now blanketing the surface, blocking sunlight from reaching the plants below and starving the water of oxygen. The pond isn’t failing because something went wrong, it’s failing because one part of the system is winning too much.

This is why the kids are here. Their work isn’t about punishing the algae for thriving. It’s about protecting the system. If they don’t remove it, the fish will die, the plants will rot, and what was once a healthy pond will become a stagnant pool.

Organizations face this same pattern all the time. Marketing generates leads faster than sales can convert them. Product launches new features that overwhelm support teams. R&D races ahead while the rest of the business struggles to catch up.

Organizations face this same pattern all the time. Marketing generates leads faster than sales can convert them. Product launches new features that overwhelm support teams. R&D races ahead while the rest of the business struggles to catch up.

"People seek services that help them get more of their job done, better." - Jim Kalbach

Jobs-to-Be-Done (JTBD) thinking is powerful because it gives us a way to understand what something is trying to do. It asks us to look beyond features, functions, and roles, and instead focus on the progress being made.

In the case of algae, its job is simple:

Job to be done: Capture sunlight and grow.

This is exactly the kind of statement JTBD excels at revealing. It strips away noise and makes the intent clear. From this perspective, it’s easy to see how the algae is succeeding: it’s capturing abundant sunlight, reproducing rapidly, and expanding its population.

Organizations use this same logic:

• Marketing’s job might be to generate qualified leads
• Product’s job might be to launch new features quickly
• R&D’s job might be to develop breakthrough solutions

By defining and optimizing for these jobs, each team can show measurable progress. Everyone has data proving they’re winning.

But here’s the blind spot: JTBD is designed to isolate the job, not to understand the system. It helps us make one part succeed, but it doesn’t ask what happens to the system if that part succeeds too much.

And that’s how well-meaning optimization becomes dangerous. The algae isn’t failing because it’s weak. It’s threatening the pond precisely because it’s strong, because it’s doing its job incredibly well.

If we zoom out from the algae’s job, we can see the system it lives in and the invisible consequences of its success.

As algae covers more of the water’s surface, less light reaches the aquatic plants below. Those plants produce less oxygen, and oxygen levels in the water drop. Fish and plants begin to die off, nutrient recycling slows, and eventually, even the algae’s growth is limited.

The pond doesn’t fail because the algae is weak. It begins to fail because the algae is stron and isolated from the system’s needs.

This is the part traditional Jobs-to-Be-Done thinking doesn’t capture. JTBD is designed to optimize the job itself, but it doesn’t ask how the job interacts with the rest of the system or what happens if it succeeds too much.

From a systems perspective, the pond has a different job entirely:

Job to be done: Maintain biodiversity in balanced conditions

This system-level job depends on many parts (algae, plants, fish, oxygen, nutrients) staying in dynamic balance. When one part over-optimizes for its own job, it destabilizes the rest.

This is where causal dynamics becomes essential. It helps us see how jobs, outcomes, policies, and even mindsets are linked in feedback loops. How optimizing one element can ripple through the whole system.

If we only focus on jobs, we risk local wins and systemic collapse. If we see the system’s job, we can design for balance not just growth.

• How does this local win ripple across the system?
• If this job succeeds at scale, does it strengthen or destabilize the system around it?
• What is the system’s “job,” and how can we help it succeed?