Why Problems and Opportunities Are the Same Thing

A tech company decides to build a new internal platform.

The pitch is excellent. The investment modelling is careful. The business case has been sharpened over three rounds of review. The capital investment is large but defensible. Nobody doubts the opportunity — a unified system, lower integration overhead, a cleaner foundation for everything that comes next.

Twenty-four months later, the platform ships. The launch is a success. Everyone involved can point to it as a career highlight.

Three years after that, the platform is consuming more engineering time than any other single thing the organisation does. Not to deliver new capability — to keep what has already shipped running. Maintenance, patching, security, compliance, upgrades, vendor management, on-call rotas, deprecation work, licence renewals, capacity planning, internal support tickets. The OpEx cost has quietly exceeded the original CapEx investment several times over. And it will keep doing so, every year, for as long as the platform exists.

Nobody budgeted for this. Not because anyone was being dishonest — because at the point of decision, the opportunity was the thing in focus. The shadow the opportunity was dragging behind it did not enter the business case. It arrived later, unannounced, and kept arriving.

This is the quieter mathematics of most organisational decisions. Not the ones that went wrong, but the ones that went right — and then kept presenting a bill nobody had planned to pay.

The same door, viewed from opposite sides

Most organisations talk about opportunities with excitement and problems with reluctance. The language itself betrays the imbalance — opportunities are things you pursue, problems are things you manage. One looks forward. The other looks backward. One suggests ambition. The other suggests weakness.

But they are rarely separate things. They are the same door, viewed from opposite sides. Every opportunity carries a shadow. Every problem contains a seed. The prior article, What Problem Are We Trying to Solve?, establishes the discipline of asking whether a problem exists in the first place. This piece takes the next step: once you've named the problem or the opportunity, you have named only half of it.

And most of the expensive decisions in organisational life are made by people looking at only one side of the door.

Opportunities cast shadows

The under-examined half of the dual frame is the problem side of the opportunity. It is the quieter half because nobody in the room wants to be the person who punctures enthusiasm with consequences. The business case is already written. The senior sponsor is already excited. Surfacing the long-tail costs feels like obstruction rather than rigour.

It isn't. It's the other half of the honest conversation.

The pattern repeats across almost every category of organisational decision. A tech platform promises unification and introduces a perpetual operational tax. A move into a new geography promises revenue growth and introduces employment law, regulatory exposure, time-zone complexity, cultural translation, and a local management layer that didn't exist the week before.

A global sales launch promises scale and introduces global support desks, twenty-four-hour coverage, multilingual service capability, and the ongoing cost of keeping up with customers in markets the organisation doesn't yet understand.

A new product promises revenue and introduces everything that comes after the first sale — support, evolution, incident response, documentation, training, the slow accumulation of technical debt that every successful product carries.

None of these are reasons not to do the thing. They are reasons to do the thing with full awareness of the shadow it will drag behind it. The difference between a leader who succeeds with these decisions and one who inherits a slowly compounding operational burden is not the quality of the opportunity. It is whether the shadow was acknowledged at the point of yes.

A useful test for any exciting opportunity is the same one you'd apply to a new pet. The decision to acquire it is a single moment. The decision to feed it, walk it, clean up after it, and take it to the vet is a commitment that will span years. Most organisational opportunities are the same shape. The pitch is about the acquisition. The honest conversation is about the feeding.

Problems contain seeds

The other direction of the door gets a shorter treatment here because the prior article covers it. Briefly, though, it deserves naming.

A persistent problem, seen clearly, is almost always an invitation to something better. A system that keeps breaking is an invitation to redesign it. A customer complaint that keeps arriving is an invitation to understand what the product is actually doing to the people using it. A communication gap that keeps producing misalignment is an invitation to rebuild how information moves. A team that keeps underperforming is an invitation to ask whether the environment around them is working.

Problems are not merely things to be solved. They are information. They are the system telling you where the leverage is. A good organisation is not one without problems — it's one that has learned to read them as signals rather than annoyances, and to choose the ones worth opening up.

The point of the dual frame is that both sides of the door exist simultaneously, for every significant piece of work. An opportunity you accept carries problems you will have to manage. A problem you address opens opportunities you didn't have before. Either can be the entry point. Both should always be examined.

The practice — two-sided work statements

The operational move that follows from this is smaller than it sounds and harder than it looks.

Stop describing work only as what is being created. Start describing it as two things.

The problem we are addressing, and the opportunity we are opening.

Or, equally:

The opportunity we are opening, and the problem(s) we are creating.

This dual framing is not decoration. It changes the quality of the conversation. It forces the room to articulate both halves before work is agreed. It surfaces the shadow at the point of yes, rather than leaving it to arrive uninvited eighteen months later. It gives the people executing the work a clearer sense of why it matters — because they can see the whole shape of what they're serving, not just the upside that got it funded.

A platform replacement is rarely, on its own, meaningful work. Replacing our platform to eliminate the weekly outages our customers are experiencing, while opening the opportunity to support three new product lines we have been unable to build on the legacy system — that is meaningful work. It has weight. It has context. It tells the person carrying it why it matters.

The difference between the two framings is the difference between work that feels like delivery and work that feels like progress. The task is the same. The understanding is different. And work that is understood gets done better, by people who know why they are doing it.

Why does this matter?

Every meaningful piece of organisational effort answers a question that most teams never have made explicit: why does this matter?

When the answer is thin — when the only framing is "because someone senior asked for it" or "because it's in the plan" or "because it felt like a good idea at the time" — the work itself becomes hollow. People execute because executing is what they're paid for. But the work doesn't connect to anything larger, so care gets withdrawn, quality slips, and the downstream costs arrive later as a surprise nobody connects back to the original decision.

When the answer is thick — when the team can say, clearly, this work addresses this specific problem and opens this specific opportunity, and these are the shadow costs we have chosen to accept — the work holds its shape. People know what they're doing and why. Trade-offs are visible rather than hidden. The organisation is able to decide, honestly, whether the work is still worth it when circumstances change.

The dual frame is how the why gets made explicit. Not as a motivational slogan, but as a structural discipline at the point where work gets agreed.

Awareness, not paralysis

A final note, because the dual frame can be misread as a brake on decision-making.

It isn't. It is not a case against pursuing opportunities. The tech platform might still be the right investment. The US expansion might still be the right move. The global sales launch might still be the right direction. The point is not to avoid the shadow — it is to see it clearly before the yes is given, so that the decision being made is the actual decision, not the sanitised version of it.

Leaders who do this well are not cautious. They are honest. They pursue bold things with their eyes open, having weighed the weight that comes with them. They stop being surprised by the OpEx tail on the CapEx decision, because they named the OpEx tail before the CapEx got approved. They stop being surprised by the support burden of international customers, because they priced the support burden into the expansion case.

That is what awareness looks like in practice. Not hesitation. Not pessimism. A clearer read on the full shape of what is being chosen, so that the choice itself can be made well.

Better bets

Ideas are easy. Understanding what comes with them is where value is shaped — and where costs are understood.

Inside the Idea to Value, this is where better bets are made. Not by chasing brighter ideas. By seeing each idea whole — the opportunity it opens and the problem it creates, or the problem it solves and the opportunity it unlocks — and choosing with full awareness of both sides of the door.

Problems lose their stigma. Opportunities lose their naïveté.

What remains is better work, chosen with intent, carried with care, and measured honestly against the full shape of what was always going to be true.