The Problem Framework
A problem is not a thing. It is a position. And once you see that, you can solve almost anything.
Eighteen, running on fumes
At 18 I was head of marketing at Adagio, living away from home for the first time, running a team of ten. Some of them had masters degrees and reported to a kid who had not finished his undergrad. Laundry, groceries, payroll, branding calls, family fights, money on the line. Stress was arriving from every direction at once, all day, every day. My brain, which likes patterns more than it likes comfort, noticed something. I am facing problems everywhere. Not one big problem. Problems as a category. And that word, problems, started to feel suspiciously vague.
When everything is a problem, the word itself is hiding something from you.
First, a useless question made useful
Most people treat the word problem as a fixed property of a situation. Payroll is a problem. The fight with my family is a problem. The branding decision is a problem. As if problem-ness lived inside the thing, like mass or colour. I want you to suspect that for the next few slides. Because if a problem is just a property of a situation, then nothing you do to yourself could ever change it. And that is plainly false, as you are about to predict.
If problem-ness lived in the thing, you would be its prisoner forever.
Picture a live bomb planted in the middle of a packed stadium. Same bomb, same timer, two observers. Observer A is sitting in row 12, close enough that the blast would reach them. Observer B is watching from a hill three kilometres away, completely out of range.
The bomb is identical for both of them. So is it a problem for both of them?
This is the thought experiment that cracked it open for me. The bomb is only A's problem because A is in the unknown about it. Will it go off? Can I get out in time? Which exit? B knows the answer with certainty: nothing reaches me here. Same bomb. For A it is a problem. For B it is a headline. The thing that differs is not the bomb. It is each person's relationship to the unknown around it.
A problem is not in the object. It is in your distance from the unknown.
The Problem Framework
So here is the model, and it is the single realization that changed how I think about all of this, the one that made me feel like I finally understood what a problem actually is. A problem is not a thing. It is a state. Specifically, it is the state of facing the unknown. The moment your familiar mental map runs out and you are standing on a frontier with no instructions, that is a problem. Not the bomb. Not the payroll. The unknown wrapped around it. Take the costume off the word and underneath there is always just one thing: something you do not yet know.
The same situation, three different words
Once a problem is a position on an unknown axis and not a property, you can slide a situation along that axis and watch its name change. Unknown to you: it is a PROBLEM. You do not know how to face it or how to escape it. Known to you: it is a CHALLENGE. You know exactly what it is and what to do, you simply have to execute. Mastered by you: it is an ASSET. It is not just painless, it is now a thing you can point at others and use. Same situation. Three different words. The only variable that moved is how much of the unknown you have eaten.
Problem, challenge, asset. Same thing at three distances from the unknown.
Fire, to an early human, was a calamity. It ate the forest, it killed, it was a thing you ran from screaming. Today the exact same chemical reaction cooks your food, smelts metal, sterilises wounds, and runs the engine that got you to work.
What changed between then and now to turn fire from a problem into the thing civilisation runs on?
Fire is the cleanest proof of the whole framework. Same fire. The calamity our ancestors ran from is the asset our entire civilisation now runs on. Not because fire changed, but because we walked it from unknown, to known, to mastered. Whatever is stressing you out today is a candidate for the exact same journey. It was a problem before it was a tool, just like fire.
Mastery does not change the thing. It changes where you stand relative to its unknown.
So the only real job is converting unknown to known
If every problem is just unknown wearing a costume, then solving any problem is one move repeated: convert unknown to known. That is it. That is the whole game. And here is the part that surprised me when I derived it sitting in my Adagio chaos. There are not a hundred ways to do that conversion. There are exactly two. Everything you have ever called problem-solving is one of these two methods, or a mix of them.
Every problem reduces to one task: turn the unknown into the known.
You are stuck on a hard problem at work. A genuine unknown, the kind that makes your stomach tight. You have two clean options. Option 1: go wide. Ask people who have done it, copy a pattern that already exists, borrow a solution from the system around you. Option 2: go deep. Sit with the problem yourself, alone, long enough to derive its structure from scratch.
Both make the unknown known. So are the two methods basically interchangeable, just pick whichever is convenient?
Wide and deep are not the same move with different speeds. Wide means ask around, scan, borrow. It is fast and it circumvents the problem. You get past it and you are exactly as capable as you were before. Deep means sit, derive, suffer. It is slow and it converts the problem into an asset, because now you own its structure. Wide frees you. Deep makes you rich. Knowing which one a situation deserves is half of being good at this.
Wide bypasses the unknown. Deep converts it. Same problem, two completely different exits.
You can solve a problem two ways: ask around, or sit with it. The first frees you. The second makes you rich.
Why this is your fastest tool under stress
Here is where the framework stops being philosophy and starts paying rent. Any time you are anxious, stuck, spiralling, do one thing before anything else. Pause and ask, what exactly is unknown to me here? Strip the emotional label off. Do not say this is a disaster. Just point at the unknown. Nine times out of ten you will find the stress was downstream of one specific thing you did not know, and the moment you name it, it shrinks from a fog into a target. The fog was never the problem. The unknown inside it was.
Stress is just an unknown you have not pointed at yet.
You sit down and audit your stress map. You write out everything you currently call a problem: a client conversation you are dreading, a tax filing, a pitch you keep not making, a workout you keep skipping.
When you tag each one as unknown, known, or mastered, what do you predict most of your so-called problems will turn out to be?
This is the most useful and most humbling thing the framework does. When you actually label your stress map, most of what you have been calling problems are knowns you do not feel like acting on. You know what to do. There is no unknown left. There is just discomfort and avoidance. And the fix for a known is not more thinking, it is execution. Do not dignify procrastination by calling it a problem. A real problem has an unknown in it. Most of yours do not.
Most of what you call problems are knowns you are avoiding. Discomfort is not the same as the unknown.
The leverage move: someone else's problem is your asset
Now the part that turns this from a calm-down tool into a money tool. Because problem-ness sits on a personal axis, the very same situation can be a screaming problem to one person and a quiet asset to you, simply because you have already eaten that unknown. This is the entire structure of a business. Find a problem that is unknown to most people but knowable by you, because of your background, your network, or your skill, and you are sitting on the highest-leverage asset there is. I did exactly this. I narrowed my agency down to surgeons of a particular kind, a market whose unknowns I had already converted, where almost nobody else had. Low competition is just other people's unmastered unknown.
The fastest way to multiply your leverage is to convert someone else's problem into your asset.
Two ways to waste the framework
Two failure modes will quietly eat you if you let them. Wide forever: asking around becomes a substitute for ever understanding anything. You bypass every problem and convert none, so you stay shallow and replaceable. And deep with no end: sitting with a problem curdles into wallowing and rumination, depth with no checkpoint and no exit. The discipline is matching the method to the stakes. Bypass wide by default. Save the slow, painful deep work for the handful of problems whose mastery actually compounds into an asset. Spend depth like money, because it is.
Wide forever keeps you shallow. Deep forever keeps you stuck. The skill is knowing which problem deserves which.
- A problem is not a thing or a property. It is a position: the state of facing the unknown.
- Slide a situation along the unknown axis and its name changes. Unknown is a problem, known is a challenge, mastered is an asset.
- Same fire, same bomb. What moves is your distance from the unknown, never the object itself.
- Solving anything is one move: convert unknown to known. There are exactly two ways to do it.
- Go wide (ask, copy, borrow) to bypass fast. Go deep (sit, derive, suffer) to convert into an asset.
- Under stress, point at the unknown before reacting. Most of your problems are misclassified knowns you are avoiding.
- A problem unknown to most but knowable by you is the highest-leverage asset there is.
Your turn
Do this with a pen, not in your head. Write down the five things weighing on you most right now, the ones you would call problems. Next to each, write exactly one of three words: unknown, known, or mastered. Be brutally honest about the knowns. Then for every one you tagged unknown, write a single letter: W or D. W if you should go wide and just borrow a solution to bypass it. D if this unknown is worth converting into an asset you will own for life. You will usually find one D in the pile and a stack of knowns you have been calling problems to avoid doing them. That one D is where your real work is. Everything else is either a quick ask or a thing you already know how to do and just have not.
Most of your list is execution in a costume. Find the one true unknown, and decide: bypass it or own it.
