Presto Sketching

A book to help you think and communicate better with drawing

problem framing

Solve the right problem with the Problem Pyramid

by

Get clarity on a problem to be solved – either by yourself or as a team – by exploring it, reframing it and articulating it in a more insightful way using this simple visual pattern.

Ambiguity and confusion? You probably don’t have a proper problem statement

Have you ever had those times where you’re lying awake at night, with your mind gnawing on a problem, and you just can’t seem to think it through properly? You toss and turn, and as much as you want to turn your brain off, you can’t!

Or, you might have a project at work where you (and probably others too) can’t really say why you’re doing it. The project might have a goal, but still there’s no clear purpose. Sometimes people might even say smart things like “We need to know what problem this project is solving” (very true!) but still, nobody can actually articulate what the problem is.

Or you might even have a problem statement – or inherited a problem statement from somebody else – but it still just sounds like a goal.

If this is a problem statement, what’s the actual problem?

A proper problem statement – and I can’t believe I have to say this – should contain a problem. Something that is in the way of someone (or a business, or a system) achieving a goal. Yes, the statement itself can contain the goal, and yes it should say something about who has the problem, and no it should definitely not already contain the solution. Here’s a good guide that has always helped me:

[Persona / Customer type] wants to [Goal] but [Problem]. This is unacceptable because [Impact].

Note how adding the impact of the problem helps to say why we need to solve this particular problem, and maybe why we need to solve it now.

Is it hard to come up with such a succinct, insightful problem statement? Usually, yes. Do you come up with it just by getting a group of people to talk? Probably not. Problem framing by definition is all about describing a problem from a specific point of view, and we all know how likely it is that everyone is going to have a different point of view!

That’s why it makes so much more sense to visually map out the problem space, to get clarity and alignment first, before being able to distill it all into a problem statement. And that’s where the Problem Pyramid comes in!

What is the Problem Pyramid?

The Problem Pyramid is a visual pattern you can draw to help you explore and clarify a particular problem space, especially if that problem space is complex, ambiguous or misunderstood. You use it give more structure and meaning to any conversation about the problem space, so that you have a better chance of distilling a more insightful problem statement.

When do I use the Problem Pyramid?

You can apply this to all sorts of problems and in different situations, such as:

  • You have a problem, you’ve tried one or more solutions, but you can’t crack it yet
  • A team is struggling with the scope and purpose of a project, and needs a shared clear understanding of its intent
  • You’ve been given a problem statement, but it’s not helping to point the way to a solution
  • You’re ‘selling a solution’ about a particular problem to management, and you want to check your thinking by asking yourself the hard questions up front

What is the Problem Pyramid made up of?

Take a look at the sketch below:

In the triangle you write whatever you think is the problem you need to solve (this is the existing problem statement). The triangle (or pyramid) has 3 sides, which symbolise 3 different ways to explore that problem:

  • 5 Whys – root cause analysis
  • 5 Whos – perspective analysis
  • 5 So whats – impact analysis

How do you do the Problem Pyramid?

You can draw this Problem Pyramid on a whiteboard, paper, even in an online collaboration space (like Miro or Mural). You can do it with your team as a session on its own, or as part of an existing meeting.

Let’s take a look at how you and your team can tackle a problem by visually exploring each of these ‘sides’ together. Be sure to share some markers and sticky notes around for different people to add what they want to, at different points throughout this activity.

Start by drawing a large triangle in the centre of a whiteboard, and write what you think is the problem you’re trying to solve so far inside the triangle. This may well change… but you have to start somewhere!

5 Whys

Problems are usually tackled more effectively when they’re addressed at the source, rather than tackling just a symptom of the problem. The ‘5 Whys’ activity is well known in the design and product innovation domains, and helps us do root cause analysis. For more information about 5 Whys, see the Gamestorming 5 Whys activity or IDEO.org’s 5 Whys activity.

Ask everyone why the problem written in the large triangle is happening (or what is causing the problem), get them to write their responses on sticky notes, and stick them in the area below the large triangle. For example: if the problem is “We didn’t reach our quarterly target of selling 15 thousand shinklebots“, ask them “Why didn’t we sell 15 thousand shinklebots?”

There’ll probably be several different answers to this question that you can read on the sticky notes that people wrote, and you may need to group any duplicates. Now, take each response, and ask why again. For example, if one of the responses was “The factory couldn’t make the shinklebots fast enough“, ask “Why isn’t the factory making shinklebots fast enough?”, and so on. The ‘5’ in the ‘5 Whys’ is to get you and your team to really push your thinking beyond the default top-of-mind cause. The deeper you dig, the better insights you’ll get.

Before long, you’ll unearth some juicy root causes to the original problem that as a team you’ll want to focus on more than others. It’s tempting to now race off and solve one of those causes, but hold up! We have to explore the other two sides first…

5 Whos

Next, ask everyone who is affected by this problem, and get them to write on sticky notes (one per sticky note) who they think is most involved, and group as necessary. Depending on the nature of the problem, it’ll be a mix of particular types of customers, or types of staff members, or partners…maybe even you and your team.

If the team come up with more than 5 (there usually are more than 5), ask them: who is most affected by or involved in this problem?

Why do we do this? Because it’s important to get everyone out of their own mental bubble, and thinking of others. This isn’t a blame game at all; it’s about seeing who’s who in the whole system of the problem space. Identifying different kind of people affected by the problem then leads to helping to see and describe the problem through each of their perspectives, which is what re-framing is all about.

5 So whats

Thirdly, it’s good to do some impact analysis. Looking at the causes of the problem and types people who are most involved in the problem you have generated so far, ask “So what?” I don’t mean “So what?” in a glib, negative way, I mean: “What happens next for the people we identified? What’s the impact of that problem on each of them?”. Whatever the answer to that question is, ask “So what?” again, and so on.

For example: if the problem is “We didn’t reach our quarterly target of selling 15 thousand shinklebots“, asking “So what?” generates answers like:

  • Quarterly revenue will be less than expected (business impact)
  • We’ll need to work out why (action to take)
  • There are too many shinklebots taking up space in the warehouse (business impact)

…and asking “So what?” again generates answers like:

  • We don’t get the capital needed to open the new branch yet (business impact)
  • We’ll need to temporarily divert some resources to do customer research (action to take)
  • We need to find more warehouse space for the incoming products (business impact)

You can visually capture these in the same way as the other two ‘sides’ of the problem area, using a mix of writing, sticky notes and simple drawing on a whiteboard. You might like to ask “So what?” for each type of person you have isolated, too. Doing this impact analysis helps you and your team get a keener sense of urgency about the problem, as well as a sense of the impact if you delay action, or don’t do anything at all.

Step back and see the story

Now’s a great time to step back and get a sense of the whole problem space you and your team have generated. You now have a ‘map’ of the problem. It’s bound to contain some areas that are more tightly defined than other areas, as well as areas that may be completely new and insightful for you and others in the team.

You can use this ‘map’ to join up some elements that stick out as being more important. For example, there might be a specific customer type affected more than others, and the impact on them leads to more negative impacts on others. Or there might be an underlying cause that the team needs to focus on and fix, which will alleviate most of the impact for most of the people affected.

This is how the Problem Pyramid has visual storytelling power, as well as analytical power!

Here’s what a Problem Pyramid looks like in action. Note, it’s normal for it to get messy first, before you can ‘join the dots’ and home in on a particular story to distill into a problem statement.

Try it yourself

As with all of the visual patterns I share, do let me know if you try it out, and what worked well, and what didn’t work so well. I hope this Problem Pyramid helps you see your problems better, so that you can solve them better!

Get your problems all MOPT up with this problem-solving method

by

In the last post, we looked at an easy way to sketch out various aspects of a problem, according to three parts:

  • Rational – What do I understand about this? (objective, facts and data)
  • Emotional – How do I feel about this? (subjective, feelings and stories); and
  • Political – Who else is affected by this? (associative, connections and systems)

These three lenses give us a more structured way to approach and better understand a problem space.

Step 1: look for clues

So where does the MOPT come in? I’ll get to that. Firstly, you get the sheet you sketched before, where you jotted down notes and pictures about the rational, emotional and political parts of your problem. Then you go back over it, looking for clues that could give rise to ideas to solve that problem.

For this example, I’m going to change my initial problem to: I’m always late filling in my timesheet. Here you’ll see I’ve circled a few clues:

You might notice from my sheet that the two things I’ve circled in the rational space are like sub-problems, or problems within the larger problem. That’s good to highlight. You might also find connections that you hadn’t seen before. Notice the arrow in mine, where I’ve connected the fact that I don’t know how to classify all the things I do in the timesheet, with Sarah the Project Manager, who certainly does. This will lend itself nicely to an idea for a solution.

If you’re lucky, you might also find the odd valuable insight. One of the things I wrote in the political part of my sheet is that it’s hard for the business to track where time is spent. Afterward it occurred to me: if the business knows what projects we have on, and who is occupied on each project, then it should already have a pretty good idea of where people’s time has been spent, rather than starting each week blank.

Understanding MOPT

At the heart of this method is the now-famous innovation question: “How might we [solve this problem]?“. ‘How might we’ as an approach was invented by Procter and Gamble, and popularised by companies like IDEO and Google. I’m a big fan, because it’s a great way to have a positive mindset about any problem, and it moves ideas in more useful directions.

The things is, the ‘we’ in ‘How might we…’ is sometimes left out of that ideas-generation mindset. In other words: ‘we’ are the ones coming up with ideas, but ‘we’ may not be in the final solution. And that’s where MOPT comes in. MOPT stands for:

M = Me

You – either you individually, or the collective ‘you’ as the team taking on this challenge – might indeed be the one to solve the problem. Often those closest to the problem itself are the best qualified to solve it. For example, Kathy Bowles was a nurse (now at University of Pennsylvania School of Nursing) who was concerned that patients were five times more likely to be readmitted to hospital than those who received proper post-acute care when needed. This drove her to spearhead RightCare Solutions, where she and her team designed an end-to-end software solution simplifying the post-acute care referral process.

O = Others

Sometimes it’s clear that you (or those you work with) are not the ones to solve a challenge, but you can alert, support, and encourage others who certainly can, with some initial thinking about your perspective on the challenge.

P = Processes

When we try to come up with solutions to challenges, sometimes we think the solution lies in something completely new, ‘blue sky’, or radical, while the solution(s) may well lie in improving the humble day-to-day processes everyone takes for granted. Toyota has always made a name for itself with its focus on process optimisation. Its Toyota Way puts great emphasis on Lean principles of minimising waste (muda) and kaizen (continuous improvement).

T = Tools, technology and systems

This is often the first ‘idea territory’ that people reach for when generating ideas. Tools! Apps! A new website! Any solution you come up with will typically sit within a system of other solutions. It’s worth zooming out a bit, and noticing other adjacent parts of whatever system the challenge is a part of. Whatever you think of McDonalds, Ray Kroc – the man responsible for turning it into the global fast-food juggernaut it is today – can be credited with tons of great system improvement ideas. By focusing on systems improvement, he was able to streamline and scale not only how the kitchens and menu processing ran, but all other parts of the business including quality control, partner relations, and real estate tactics.

Step 2: draw up a MOPT table

Now that we have our heads around the idea of different territories of solutions, we can move on to step 2. We transfer our initial challenge over to a new piece of paper (or whiteboard, or area on an online innovation space like Miro), and draw up a table, with a row for each clue.

There are four other columns, for Me, Others, Processes and Tools:

Now, either by yourself or as a team, you can tackle each cell of the table separately, and come up with a range of ‘How might…’ questions, depending on the clue, e.g. “How might I improve this so that I can recall everything I do?” or “How might I solve this so that I don’t even need to recall everything I do?”

I really like this because straight away I’m going to get more ideas than I otherwise would have, because I’m setting up all these different cells to fill. And like all good brainstorming, not all the ideas need to be practical yet; it’s always good to go for quantity first, and see if some ideas lead to other ideas.

There’s not a lot of space in those little squares, so treat each cell as a placeholder for your thinking, a springboard to another piece of paper, or another part of the whiteboard. Here’s where I got to with mine:

Note how a couple of cells in my example above just didn’t apply, and that’s fine. Mixing written notes and pictures is also fine. What this does is it arranges our thinking spatially, rather than just as a list… or with no form at all. Once you fill your MOPT table, you can go back over it and pick out the ideas that are most resonant and relevant.

How was it for you?

Go on, give it a go, you might be surprised by the insight this reveals to you. If you do give it a try, let me know how it goes, and if you think it could be improved upon.

Here are 4 lines to help you understand any problem

by

As Albert Einstein might have said*, “Given one hour to save the world, I would spend 55 minutes defining the problem and 5 minutes finding the solution.” It’s so important to understand the problem before jumping in to tackle it, isn’t it?

When it comes to understanding (and solving) problems, we tend to think of ourselves as rational creatures, who form opinions and make decisions based on facts and logic. But as you probably know, our emotions play a much larger role in opinion-forming and decision-making. We have all sorts of unconscious biases and emotional triggers**. What’s more, a lot of problems don’t really exist in isolation, but are connected to other problems and solutions. We might come up with a solution to a problem, that then upsets something else. A great example of this holistic thinking in action is how pet stores in San Francisco (and other cities) can now only sell rescue animals, to combat the spread of inhumane ‘puppy mill’ breeding.

So there’s actually three parts to any problem:

  • Rational – objective, facts and data
  • Emotional – subjective, feelings and stories
  • Political – associative, connections and systems

So, how do we use only 4 lines to understand a problem? I’m glad you asked. Trying to understand all parts of a problem in your head is just too hard. Let’s look at how you can do a simple sketch to help. To start with, write a succinct sentence about your problem in the middle of a page, and draw a cloud around it, like this:

Next, draw three lines radiating out, pretty much equally spaced, and write these questions:

Now, fill each of those three spaces with whatever you think is relevant, to answer each question. You can write bullet points, or draw pictures, or maybe even a mind map of connected thoughts. Go nuts.

This is a simple visual way to explore a problem space. To really do this properly, I’d take Albert’s advice and spend at least 55 minutes on it, and I guarantee that you will have a much deeper, nuanced understanding of whatever your problem is. And feel free to adapt the prompt questions to your context.

Depending on the problem, your page should start revealing some insights to you. Maybe you don’t have much in the ‘rational’ space, but a lot in the ‘political’ space? Or maybe there’s SO MUCH on the page, that you need to scope the problem down a little bit?

Try it out; I hope you find this technique useful, for you and your team.

See, don’t you feel smarter already?

* There are so many of these sorts of quotes around, citing Albert Einstein, that I’m sure he couldn’t have come up with all of them. I mean, how would he have found time to work, in amongst all that brilliant commentary? Oh, yeah that’s right, he was a genius. 😉

** My go-to books on this topic are:

(These links have a referral code)