Problem-Oriented or Solution-Oriented: It’s More of a Problem Than You Think

by | Aug 14, 2025

Recently, I ran into a frustrating situation with a vendor who was building something custom for us. And as anyone who’s ever worked with a custom solution knows — hiccups are part of the deal.

That said, when you’re a professional, it’s your job to navigate those hiccups. You don’t always have to know the answer, but you do need to keep moving toward a workable solution — or at least offer options to get to the finish line.

In this case, the vendor hit a thorny coding issue. He tried different things, searched online, even consulted ChatGPT. Nothing worked. Eventually, he came to me and said, “I’ve tried everything. I’m getting nowhere. I’m moving on.”

I asked, “You mean you’ll work on another part of the project and circle back?”

“No,” he replied. “I’m done.”

Just like that, the problem was dumped in my lap — and trust me, coding is nowhere near my wheelhouse. But I am creative, and I immediately started thinking about possible workarounds — even if it meant doing something manually that should’ve been automated.

Except I didn’t get the chance.

The vendor shut down the conversation. He was problem-oriented. He had reached the limits of what he could do, and instead of pivoting or brainstorming with me, he quit.

Here’s the thing: I don’t care that the software is buggy. I don’t care that the interface is clunky or that it’s “not supposed to behave this way.” What I care about is how we make it work anyway.

That moment helped crystallize something for me: I’m solution-oriented.

I don’t mean that to sound like a brag. I just honestly didn’t realize how rare that mindset can be — until I started seeing how often people get stuck spinning around the problem.

They say things like:

  • “This isn’t working the way it should.”
  • “I already tried X, Y, and Z — nothing worked.”
  • “This whole thing is unfair.”

They think they’re troubleshooting. But they’re really just circling the issue — staying rooted in what’s wrong instead of moving toward what could be right.

Being solution-oriented isn’t about ignoring problems. It’s about moving through them. It’s about asking:  “Given the circumstances, what can we do?”

One of my favorite examples comes from the movie Apollo 13. There’s a famous scene where NASA engineers on Earth are tasked with solving a life-threatening problem aboard the spacecraft. The astronauts have only a handful of items at their disposal — and the team on the ground has to figure out how to make a square filter fit into a round hole to save their lives.

There’s no time to moan, blame, or get philosophical about design flaws. The team gets to work. They dump the available parts on a table, roll up their sleeves, and say, “This is what we’ve got. Let’s build a solution.”

(If you haven’t seen the scene, it’s worth a watch: Apollo 13 – Square Peg in a Round Hole.)

That’s the kind of thinking I want to bring to every challenge — in work and in life. And it’s the kind of thinking I want to cultivate in the leaders and teams I work with.

Because when you’re building a business, managing a team, or navigating any kind of meaningful change, problems will show up. Every time. What defines your success isn’t how many problems you have — it’s how you respond.

So the next time something goes sideways, ask yourself:

Am I focused on the problem? Or am I working toward a solution?

One of the greatest tools I know for staying solution-focused is a simple framework called POM: Purpose – Outcome – Method.

  • Purpose is why you’re doing the thing — whether it’s a meeting, an email, or a customized solution.
  • Outcome is what success looks like — what you want to have at the end.
  • Method is how you get there.

In my vendor situation, we were clear on the purpose — and we definitely knew the desired outcome. We had mapped out the methods. But when those methods didn’t work, the whole thing came to a screeching halt.

Instead of giving up, a better next step would have been to return to POM:

  • Is our purpose still valid? If not, then maybe we scrap the whole project.
  • If the purpose is still valid, then we ask: Do we need to redefine the outcome?
  • If the outcome stays the same, then it’s time to explore new methods — different routes to get where we’re trying to go.

The power of POM is that it gives you structure without rigidity. It’s not about forcing a square peg into a round hole — it’s about stepping back, reassessing the mission, and choosing the next best move.

And that’s what being solution-oriented really means. It’s not about having all the answers — it’s about staying in motion, with purpose.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Archives

Find the Right Fit