The Problem Pyramid

Note: These are my opinions alone. I'm not employed or associated with The Problem Pyramid, Xmind, or Microsoft.

Looking for a technique to create User Stories in Agile/Scrum? After checking out The Problem Pyramid, you may never get stuck again.

Looking for a technique to create Software Designs which ensure the application works but allows developers the creativity they crave/need? Using The Problem Pyramid to define interfaces may be just what you need.

I'm surprised by The Problem Pyramid's muted reputation relative to its ability to equip everyone from business leaders to software engineers in taming unruly ambiguity and focusing everyone's attention appropriately.

Did I mention it's simple but effective?

One recurring challenge in business (and software) is separating "what needs to be done" from "how it should be accomplished". The Problem Pyramid fixes this.

The Problem Pyramid is an effective tool for guiding Stakeholders, Scrum Product owners, and Technical Leads through story creation and acceptance criteria. It allows teams the freedom to deliver creative solutions while the Stakeholder and Product Owners talk in terms of business metrics (instead of designing software which happens too often) during Release and Sprint Planning. (Software design should get worked out during Tasking, not in front of the Product Owner.)

Here is an oversimplification (but hopefully a fair treatment). Applying this mindset simplifies problem solving considerably because it helps everyone agree to a common vocabulary and context.

Part 1 - The problem

• There is a problem. (I need cash.)
• The problem can be measured as it stands today. (I only have 5 dollars.)
• The problem can be measured as solved. (I need 15 dollars.)

Part 2 - The cause

• What are the reasons the problem exists? (I borrowed money and need to repay a coworker.)

Part 3 - The requirements

• Are there any constraints to how the problem can be solved? (I need the money in the next ten minutes.)

Part 4 - The solution (aka The How)

• What is the best way to satisfy the requirements so the problem is resolved. (Go downstairs to the ATM .)

In addition, this enables groups of people to brainstorm, weigh options, and agree on the best solution by attaching pros/cons to the requirements and solutions.

Need a tool to wrestle all this information, try XMind (for brainstorming) or SmartArt (for summarizing/presenting).

Official explanation of The Problem Pryamid