Pick Your Problems

We are told to follow our passion, or to master the required skill set for a role. Both miss something basic. Every career is a specific flavor of problem solving in disguise.

Before you master the tools of a trade, you have to be fascinated by the exact type of problem that trade forces you to face every day. Engineers fight technical breakdown and optimization problems. Founders fight market uncertainty and value creation problems. Investors fight capital allocation and selection problems. Doctors fight diagnosis and patient care. Lawyers fight legal friction and negotiation. Product managers fight customer friction and prioritization. Operations leaders fight efficiency and execution. Sales and marketing people fight persuasion and attention. Data scientists fight pattern discovery and prediction.

The people who go furthest are not always the most skilled. They are the ones who enjoy fighting the messy problems that make everyone else want to quit.

I learned this before I had a name for it

I took a professional development course in business school, spread across two semesters, that studied the psychology of peak performance. One lesson stuck with me more than any other. Stop watching your title. Start watching your own state while you work.

I began tracking the moments where time disappeared. Where a problem was hard enough to hurt and somehow left me more energized than when I started. That tracking did not put me on a new path. I was already on it. What it did was show me, in plain terms, exactly what I loved about the work I was already doing. I was fortunate to be in the right lane before I had the language for why.

When a problem fuels you, the tools around it stop being a wall. You pick up the unfamiliar skills not because you are disciplined but because the problem won't let you put them down. That clarity is what I want to hand to anyone still trying to name what they are actually looking for.

The zone that actually matters

The best signal for your real problem type is not that the work is easy. It is that struggling with it leaves you more alive than when you started.

Think of it as a grid. Hard problems that leave you energized sit in Zone 1, your native problem domain. That is where you want to live. Hard problems that leave you drained sit in Zone 2, where you may be skilled but you are headed for burnout. Simple problems you can run on autopilot are Zone 3, maintenance that just needs to be systematized. Simple work that still drains you is Zone 4, delegate those immediately and reclaim the hours.

When your natural problem-solving style does not match the actual work in front of you, sustained performance becomes nearly impossible. A high salary only delays the burnout. The question that matters is what fills Zone 1 for you specifically.

Nobody lives in Zone 1 full time

If you are building a venture, managing infrastructure, or running any kind of organization, mandatory Zone 2 work finds you regardless. The investor who loves capital allocation still has to sit through board governance conversations that drain them. The engineer who lives for architecture still has to manage a roadmap. The founder who thrives in market uncertainty still has to handle compliance and HR.

The skill is not avoiding Zone 2. It is containing it. The operators who last are the ones who build systems, processes, and teams around their inevitable Zone 2 obligations so those obligations do not slowly colonize the calendar. You document and delegate the repeatable parts. You hire deliberately for the gaps that pull you into the drain. You protect the hours where Zone 1 work actually happens, because that is where your highest leverage lives.

The goal is not a perfect day. It is a portfolio where Zone 1 has a genuine majority stake.

How to find yours

You cannot read your problem domain off a resume. You have to audit yourself, and the honest data is already there if you know where to look.

Start with the friction. Most people try to find what they love first, but prestige gets in the way. We convince ourselves we love whatever sounds impressive. Flip it instead. Look back at the last two or three years and list what drained you fastest. If resolving conflict between people wore you down, you probably do not belong in a people leadership track, regardless of how good you are at it. If structural ambiguity exhausted you, no amount of equity will make you enjoy the chaos of early-stage building. The things you resent are data.

Then track the opposite. The work where time collapsed. Where the problem was hard enough to be genuinely uncomfortable and you came out the other side more alive than when you started. That is not inspiration. That is your signal.

The last test is the simplest. When something breaks on a project you are leading, what do you reach for first at three in the morning? Do you go straight to unit economics and runway? You lean executive or investor. Do you open the codebase or the architecture diagram? You lean engineer. Do you get on the phone to fix team morale? You lean operations or people. Do you pull up user data and the feedback log? You lean product.

Stop looking at the title, the perks, or the tools. Look at the ugliest problems that domain puts on your desk on an ordinary Tuesday morning. The people who go furthest are the ones who get genuinely fascinated by the exact problems everyone else is trying to get away from. If those are the puzzles you actually want to solve, you have found your field.

When the audit comes back red

Most people, when they realize they are living in Zone 2, assume the answer is to quit. Sometimes it is. But in most cases the first move is much quieter. It starts with understanding whether the drain is coming from misconfigured responsibilities, or from the fundamental nature of what that role actually requires every day. Those are not the same problem, and they do not have the same solution.

A technical lead spending sixty percent of their time in stakeholder conflict resolution and forty percent on architecture is not necessarily in the wrong career. They may simply be in the wrong configuration of one. That is fixable without leaving. You map what you actually do against what the role was supposed to require. You identify which Zone 2 tasks are structural and which are just accumulated incumbency that nobody has questioned in years. Then you propose the rebalance explicitly. Volunteer for the projects that pull you back toward Zone 1. Name what you want to hand off and build the case for why that handoff makes the team stronger. Managers keep people who know what they want and can articulate it without creating chaos.

But some Zone 2 problems are structural. If the drain is coming from the fundamental nature of what that industry, organization, or team needs every day, no amount of internal negotiation will fix it. The role requires a Zone 2 operator and you are not one. Build the bridge before you burn the one you are standing on. Take on Zone 1 work wherever you can find the surface area. Find the people already operating where you want to go and make yourself useful to them. You want to arrive with momentum, not desperation.

Let me stop here 😊. I hope you found a lens or two in this that you can actually hold on to.