Most of us spend our days dealing with problems. Something breaks, a delivery is late, a deadline slips, a system crashes. We jump in, fix it, and move on. Another way to relate to problems is to work so they never show up in the first place.

This raises a simple question: what interest drives most agents, whether human or machine? Is it mainly about solving the problems that appear, or about preventing them from happening at all?

In practice, most people, teams, and agents focus on solving problems when they arise. It is visible, concrete, and easy to point to. You can say: “Here was the problem; here is what I did; here is the result.” The work is tangible and easy to recognize. This kind of problem-solving often creates heroes: the person who steps in when something goes wrong and fixes it.

Preventing problems is different. It is about noticing risks in advance, planning carefully, building good routines, and improving systems so that certain problems simply never occur. When prevention works, nothing dramatic happens. There is no crisis, no story, and usually no visible “before and after.” Because of that, very few people see the problems that never appeared. Preventive work is often taken for granted or not even noticed.

Ideally, we would prioritize both: solve the problems that arise and work to prevent them in the future. After fixing something, we would ask: “What can we change so this does not happen again?” Over time, prevention would reduce the number of issues that require urgent attention. But when an actor has to choose—because there is limited time, money, or energy—solving visible problems usually wins. It feels urgent. It is easier to justify. It is easier to measure.

This creates a pattern. Reacting to problems becomes the default. People get used to firefighting, and the organization learns to depend on crisis work instead of steady improvement. The better someone is at prevention, the less obvious their contribution becomes, making it even harder to justify preventive work when pressure increases.

A more sustainable approach is to make room for both. Keep solving the problems that arise, but also set aside time and attention for preventing new ones. Make preventive work a conscious part of the job, not just something you do “if there is time.” And when something does not go wrong—when a project runs smoothly or a system stays stable—recognize that this is often the result of invisible, preventive effort.

Solving problems is visible. Preventing them is mostly invisible. Both matter. The challenge is to resist the pull toward only what can be seen and praised, and to also value the problems that never have to be solved.