Choosing the Right Project Management Style: Problem vs. Solution Clarity

When it comes to managing projects, one size definitely doesn’t fit all. Some projects start with a clearly defined problem but no clue how to solve it. Others begin with a solution in hand, but no idea what problem it's supposed to fix. And then there are the chaotic in-betweens.

The matrix in the image above breaks project management styles into four quadrants based on two key factors:

• How clearly the problem is understood

• How clearly the solution is defined

  
  

Let’s walk through each quadrant:

🔹 Agile: Problem Known, Solution Emerging

Example: Software development, product iteration

Agile thrives when the problem is well understood but the best way to solve it isn’t. It emphasizes iteration, customer feedback, and adaptability. You know what the users need—you’re just not sure which combination of features, workflows, and architecture will get you there. Think “build, test, refine.”

Agile project management is ideal for complex, evolving projects with changing requirements and multiple stakeholders.

🔹 Waterfall: Problem Known, Solution Known

Example: Building a bridge, traditional infrastructure

Waterfall is your go-to when both the problem and the solution are clear. It’s linear, structured, and optimized for predictability. With clearly defined scope, budget, and timelines, waterfall works well for projects that don't require much change midstream.

This is traditional project management at its most efficient—but it's less flexible when new information arises.

🔹 Extreme: Problem Unclear, Solution Unclear

Example: Organizational change, disruptive innovation

This is the chaotic zone. You’re not entirely sure what the problem is, and you’re even less sure how to solve it. Extreme project management is messy, but necessary for projects that involve major unknowns—especially when innovation, discovery, or cultural shifts are involved.

Here, facilitation, stakeholder alignment, and adaptive leadership are more important than any single methodology. The process is about finding both the problem and the solution.

🔹 Emertxe (yes, that’s "Extreme" backwards): Solution Known, Problem Unclear

Example: A tech feature built because it’s “cool,” not because anyone needs it. On the other hand, artificial intelligence or augmented reality are other more promising examples as well.

This quadrant is all about building a solution in search of a problem. Maybe your organization recognizes the potential of a new technology, but doesn't yet know where it applies. This zone can be a breeding ground for innovation—or a fast track to wasted effort.

Success here requires curiosity, market testing, and the humility to pivot or abandon if the problem doesn’t materialize.

So... Which One Are You In?

Before choosing a project management framework, ask yourself two questions:

1. Do we clearly understand the problem we're solving?

2. Do we already know how we’re going to solve it?

   
   

Your answers will help you determine not just what approach to use—but how to lead the project, who to involve, and what kind of flexibility to plan for.

The best project management isn’t rigid—it’s responsive.