Thought of the Day

The Problem You Are Supposed to Carry

2026-07-13

Every tool in the stack is optimized for resolution. Close the loop. Produce the answer. Fix the thing. But there is a category of professional challenge that is not meant to be solved — it is meant to be carried. And the premature solution is often worse than the unresolved tension.

There is a category of problem you are not supposed to solve.

Not because it cannot be solved. Because solving it is the wrong response. The right response is to carry it — to hold it open, to sit with the tension, to resist the pull toward premature closure — because the information that matters lives inside the unresolved state. And the resolution destroys it.

Almost nobody names this. Because the entire technology industry — including the one I operate in — is organized around one assumption: problems exist to be solved. Input arrives. Analysis processes. Output delivers. Loop closes. Ticket resolved. Case closed. Problem eliminated.

That architecture works for technical problems. It works for logistical problems. It works for every problem that has a clean boundary and a definitive answer.

It does not work for the problems that actually determine whether a business, a relationship, a career, or a life is heading in the right direction. And those are exactly the problems that the tools are now arriving at first.

Here is what a carried problem looks like. The client relationship that is not broken but is not healthy either — and the right move is not to fix it or to leave it but to hold it in a specific state of honest tension while both parties figure out whether the foundation can support what comes next. The strategic direction where two competing priorities are both genuinely valid — and choosing one prematurely destroys the information you would have gotten from holding both. The team dynamic where the discomfort is not dysfunction but signal — the felt sense that something real is forming and needs more time in the open before it can be named. The market ambiguity that resolves only through patient observation — not through the aggressive analysis that collapses the uncertainty into a false certainty.

These are not problems that need solutions. They are tensions that need carriers. People willing to hold the weight of not-knowing long enough for the deeper pattern to reveal itself.

And here is what almost nobody is naming: the tools are destroying the capacity to carry problems.

Because the tool always produces a solution. Always. That is its architecture. You give it the input, it gives you the output. The analysis arrives. The recommendation forms. The answer presents itself — clean, structured, actionable, complete. And the person sitting with the problem feels the relief of resolution before they have asked whether resolution was the right response.

The tool does not know the difference between a problem that needs solving and a problem that needs carrying. The tool does not know that some tensions are productive. That some ambiguities are informative. That some discomforts are the exact state where the deepest insight is being formed — and that arriving at an answer too early is not a success but a loss. A foreclosure. A closing of the space where the real thinking was happening.

I see this playing out in every leadership team I work with now. A complex challenge surfaces. Before anyone has sat with it — before anyone has let the tension teaches its lesson — someone has already put it through the tool. The tool has produced a framework. A recommendation. A set of options weighted by probability. A path forward.

And the room exhales. Because the tension was uncomfortable. And the tool removed the discomfort. And the room mistakes the removal of discomfort for the arrival of clarity.

It is neither.

The problem was not solved. The problem was collapsed. The information that lived in the unresolved state — the slow-forming pattern, the deeper read, the insight that needed another week of ambiguity to arrive — that information has been sacrificed on the altar of premature resolution. And the team moves forward with a clean answer that is missing the thing that mattered most.

This is the hidden cost of a tool that always produces solutions. The solutions arrive faster than the understanding. And the understanding cannot be rushed because understanding is not production. Understanding is a state of being. It requires time. It requires discomfort. It requires the willingness to sit with a problem that has no clean answer — and to trust that the sitting is the work. Not the prelude to the work. Not the inefficiency in the work. The work itself.

Here is what I have learned from building tools for people who make hard decisions: the most expensive problems are never the ones that look hard. They look hard and they have clean solutions. The most expensive problems are the ones that feel like they should be resolved but resist resolution. The ones where the answer is not yet available — not because you lack information but because the situation has not yet revealed its shape. And the shape reveals itself to the person who is willing to hold the question open long enough.

The person who cannot hold the question open reaches for the tool. The tool gives them an answer. The answer feels right because it is clean. The cleanliness is the trap. Because the real answer was forming in the tension. And the tension has been resolved before it had time to teach.

So here is the diagnostic that should change how every professional thinks about the problems they face. Look at what is on your plate right now. How many of the items on your list actually need to be solved this week? And how many of them need to be carried — held open, sat with, allowed to teach before they are allowed to close?

If almost everything on your list needs to be solved, one of two things is true. Either you have an unusual run of clean technical problems — which is unlikely — or you have already collapsed the complex problems into clean ones by putting them through a tool that does not know the difference. The tool took something that needed to be carried and turned it into something that could be resolved. And in the process, it destroyed the information that lived in the carrying.

The people who are going to make the best decisions in the next decade are not the ones who solve the most problems. They are not the ones who close the most loops. They are the ones who have developed the capacity to distinguish between the problem that needs solving and the problem that needs carrying — and who have the maturity to hold the second kind without reaching for the resolution the tool so eagerly provides.

Carrying is not passive. Carrying is not avoidance. Carrying is the active, disciplined, deeply uncomfortable practice of sitting with a problem that does not yet have an answer — and trusting that the answer will arrive on its own timeline, not the timeline of the tool. It is the willingness to be unresolved. To be in the tension. To feel the weight of not-knowing — and to understand that the weight is the information.

The tool will never carry a problem for you. It will only solve it. And solving it before its time is not leadership. It is the most expensive form of impatience available.

Learn to carry. Learn to distinguish the problem that needs resolution from the tension that needs a carrier. And protect the space where the unresolved problem does its slow, quiet, irreplaceable work — the work that no tool can accelerate because the acceleration is exactly what destroys it.

Some problems are not yours to solve. They are yours to hold. And the holding is the entire point.