The Six Pathways: How to Simplify Project Management Without Losing the Big Picture

The Six Pathways: How to Simplify Project Management Without Losing the Big Picture

CONTEXT (Why this matters)

Most people approach project management as a mountain of checklists and technical terms. You open the pmbok-guide, see dozens of processes, and immediately feel overwhelmed. It feels like you’re trying to build a plane while flying it.


THE PROBLEM: THE JARGON TRAP

The mistake most beginners make is focusing on the “tools” before they understand the “landscape.” They worry about Gantt charts and Earned Value Management before they’ve even defined why the project exists.

When you lose sight of the big picture, you start “managing the paperwork” instead of managing the project. You get bogged down in administrative tasks, and when a stakeholder asks a simple question about the project’s direction, you find yourself lost in a sea of spreadsheets.


THE SOLUTION: THE SIX PATHWAYS

To manage any project successfully—from building a software app to constructing a skyscraper—you need a simple mental model. I call it the Six Pathways.

Think of your project as a pie. To see the whole picture, you need to balance these six slices:

1. Who & What (Stakeholders & Scope)

  • Who: Identify every stakeholder who can influence or is impacted by the project.
  • What: Define the product, service, or result. If you don’t know what you’re building, you’re already lost.

2. When (The Schedule)

  • Time: This is your most rigid constraint.
  • Milestones: It’s not just about the deadline; it’s about the sequence of events and managing the flow of work.

3. How Much & How Many (Resources & Quality)

  • Resources: This covers your budget, your people, and your materials.
  • Quality: What does “done” look like? Quality ensures your resources aren’t wasted on something that doesn’t meet requirements.

4. Where, Risk & Organization (The Environment)

  • Environment: Where is the work happening? What is the organizational culture?
  • Risk: What hurdles are in your way? This pathway is about looking ahead to avoid the “landmines.”

5. How (The Methodology)

  • Delivery: Choose your path. Are you using a Predictive (Waterfall) approach or an Agile one?
  • Process: This is the mechanics of how the team will actually execute the work.

6. Why (The Business Case)

  • Rationale: This is the most important pathway.
  • Value: If the project doesn’t have a clear business justification or ROI, it shouldn’t exist. The “Why” is the anchor for everything else.

EXAMPLE: THE PYRAMID PROJECT (Make it real)

Imagine you’re the Project Manager for the Great Pyramid of Giza.

  • Why: To build a royal tomb for the Pharaoh’s afterlife (The Business Case).
  • Who/What: The Pharaoh is the key stakeholder; the Pyramid is the “What.”
  • When: It must be finished before the Pharaoh passes away (The Schedule).
  • How Much/How Many: Estimating thousands of laborers and millions of tons of limestone (Resources).
  • How: A massive, stone-by-stone predictive construction effort (Methodology).

When you break it down this way, even the most complex projects in human history become simple to understand.


READY TO MASTER THE BIG PICTURE?

Stop drowning in jargon and start leading with confidence. Whether you are just starting out or preparing for your certification, we have the resources to help you succeed.