Presto Sketching

A book to help you think and communicate better with drawing

Problem solving

Draw more creatively with FLARE

by

If you want to find ways to draw topics more creatively, or you feel like you’re in a bit of a rut drawing things the same way all the time, then the FLARE prompts are for you.

How do you draw a person? Or a building? Or a tree? There are lots of ways to draw real-world objects, and we can use curiosity, observation and practice to draw these in satisfying ways.

A group of simple drawings depicting common objects like a lightbulb and cloud

Some simple images of simple real-world objects

But how do you draw more complex and abstract concepts, like ‘innovation’, ‘strategy’, or ‘diversity’? It’s much harder, isn’t it?

A couple of years ago, Axelle Vanquaillie (a masterful visual practitioner, facilitator and leadership coach, and owner of the company Visual Harvesting) and I were discussing how to help people in our training workshops with this common challenge: how do you illustrate abstract concepts in more creative ways? We realised that many of us anchor on to one idea, and find it hard to go beyond that. My design background has always taught me that it’s always better to use divergent thinking, and that the way to have one great idea is to have 100 so-so ideas first. 

With that in mind, we pooled our knowledge, sketched a lot, and swapped stories of various training sessions we had run and examples we’d come up against. And that’s how FLARE was born.

We’ve since used FLARE with a variety of different groups in training sessions, with a variety of levels of confidence in drawing, and it has always helped everyone be more creative and get more satisfying results from their drawing. And now it’s your turn to learn!

A photo of a participant in one of our training sessions reflecting on the experience of using FLARE to illustrate a tricky concept

A participant in one of our training sessions reflecting on the experience of using FLARE to illustrate a tricky concept

What is FLARE?

FLARE is a set of prompts you can use to help you move beyond the way you’re used to thinking about a topic you want to draw, and think about it in new ways. What you get is a much greater range of ideas that you can then refine and combine into one final image.

A drawing of the process of coming up with ideas without FLARE and with FLARE

The FLARE process gets you more initial ideas from which to create your final visual

FLARE stands for:

  • Feel – What does it feel like? What emotions does this trigger?
  • Look – What does it look like? What are the real-world objects at play?
  • Another word – What’s another word (or words) to describe this?
  • Result – What is the result of this? What is the end-game of this topic or scenario? Is there a benefit realised? Or a negative impact that might happen?
  • Experience – What is the experience of this? Is it something where there are several steps involved? Or several devices, places, people or roles involved?
A drawing of the word FLARE with text expanding on what each letter stands for

How to use FLARE

It’s really important to understand that when you use FLARE, you don’t try to come up with The Perfect Image first. What we’re doing here is generating lots of different ideas first, to help us explore the topic in better ways, and then we go back and refine and combine our best ideas.

1. Write your topic in the middle of a big page

Start with a topic – especially a complex or abstract topic – you have in mind to draw. It’s best if it doesn’t include any clichés or existing visual metaphors. If it does, try to restate it in a clearer way. Then, write it down in the middle of a big blank page.

Now, write the letters of FLARE around it. We’re going to make a mindmap. You can also do this as a grid if you like; the main thing is to give yourself plenty of space to write first, and then draw your ideas.

In this example, I’m going to go with “Teams struggle to understand each other”…

A drawing of a prompt in the middle, surrounded by the letters FLARE around the outside

2. Ask yourself the first FLARE prompt and draw your ideas

The first FLARE prompt is F: “What does it feel like?” Too often, concepts are – well – too conceptual, and it’s easy to forget that whatever the concept is, it probably affects people in ways that might actually be relevant to capture. Jot down some words that describe how your topic feels.

A drawing with a prompt in the middle surrounded by the letters FLARE

3. Jot down ideas for the other four prompts

Repeat step 2, and write down any ideas you come up with for the other four prompts. Allow each prompt to help you think about the topic in new ways, from new perspectives. You should have a set of descriptions around your original topic.

A drawing with a prompt in the middle surrounded by the letters FLARE

Don’t worry if you can’t think of several things for each of the five prompts. Some prompts won’t suit the topic as well as others. If you get stuck, just move on.

4. Draw lots of different ideas based on what you wrote

Now we get drawing! Go back over everything you wrote, and do some quick sketches to capture what you wrote. Remember, this isn’t about trying to draw the One Perfect Image now, or even to draw the entire topic or concept in one go; this is still just brainstorming.

A drawing with a prompt in the middle surrounded by the letters FLARE

As I sketched various ideas based on what I’d written for this example, I made sure not to self-edit as I went. The more rough sketches, the better.

5. Refine and combine

Now comes my favourite part! This is where you channel your inner editor, look over all your various sketches from across the prompts, and choose the ones you think are most relevant, most compelling, and/or most insightful. There might be one that just nails it on its own, but typically there are a few. 

A drawing with a prompt in the middle surrounded by the letters FLARE

As I went back over what I’d written and sketched in this example, the bridge idea really resonated with me, as well as showing several different languages. The going-around-in-circles also appealed to me.

Now, draw something that unites those several good ideas into one single cohesive picture.

Two different drawings illustrating the prompt

As you can see here, I landed on two different ideas. The first idea to illustrate the topic of “Teams struggle to understand each other” uses speech balloons and thought balloons… No surprises there, but positioning them on a roundabout double arrow added some more meaning. As I thought about my second idea with the bridges, it occurred to me that it could look interesting if either ‘side’ basically built their own different bridge, and even though both bridges are complete, they never meet in the middle. This speaks to the inward-looking nature that some teams have when they struggle to communicate with one another.

Which one do you prefer? What do you think you would draw for this topic?

Some tips to help

Here are a few other things to consider about the FLARE method

  • Trust the process! Too often we’re hard-wired to try to draw just one image that works the first time. Embrace the fact that it’s better to create and explore many options first, and then you’ll have more to choose from. And who knows, you might have some a-Ha moments about the concept itself you’re trying to draw along the way, as well as how to draw it.
  • Not all prompts have to be present in the final image. Try not to force an image that includes something that speaks to every prompt. It’s totally fine if your final image ends up just being about how your topic feels. It’s also fine if you land on an image that combines feel with look and result.
  • Feel free to skip step 3 if you like, and jump straight to drawing your answers to each prompt. I put this step in to help you if you’re more comfortable with writing as well as drawing.
  • Not all prompts will make sense all the time and that’s okay. They’re just prompts; if you’re stuck on a prompt because it doesn’t seem to work for your topic or context, just move on.

Taking FLARE further

I encourage you to give FLARE a go the next time you need to illustrate a tricky topic, or if you want to try illustrating a familiar topic in a more creative way. The FLARE prompts help you think deeper about the topic, and maybe help you to clarify your point of view, too.

With that in mind, there are other ways you can use the FLARE prompts.

  • Group drawing – FLARE is fun in pairs! Two heads are better than one, as they say, and if you try these prompts with someone else, you’ll both benefit from each other’s different experiences and points of view.
  • Facilitation questions – If you run any meetings at work, you probably know that great facilitation is often about asking great questions, to help your group have a better conversation. The FLARE prompts might give you ideas about how to enrich your next conversation, by helping everyone think about their topic in different ways.
  • Problem solving – As Charles Kettering is said to have said, “A problem well stated is half solved”. So often, a great solution lies in the way a problem is articulated in the first place. Using the FLARE prompts can help you and your team approach any problem or challenge from a different point of view, to perhaps reveal a hidden solution.

Feel free to drop me a line and let me know if this helps your drawing. 🙂

Discover how your customers tick with the Decision Factors sketch

by

It can be really hard getting a handle on what factors affect your customers’ decisions, or how to get buy-in from your stakeholders. The Decision Factors sketch can make it easier.

Why do we buy the products and services we buy? Why do we choose one brand over another? Why do some factors influence us more than others? Or why is it so hard to get teams to use a new system, as part of change management?

If you’re a researcher, designer, marketing professional, product manager, or change manager, you probably spend a lot of your time thinking about these sorts of questions. There’s an incredibly complicated soup of factors and biases going on in the way we make decisions, large and small, as well as various forces that play on those factors and biases. There’s also a huge body of ongoing research into the cognitive psychology and behavioural economics involved in decision-making.

I want to show you a simple framework that has helped me apply the essence of this research: the Decision Factors sketch. It helps you visualise the various factors going on as we make decisions for behaviour change, whether that change is to make a purchase, to join a meeting, to approve a design… anything at all.

What’s in the Decision Factors sketch?

As you can see in the sketch below, there are four main elements going on:

  • SUBJECT – Your customer, persona, stakeholder, staff-member… the person who you want to make a decision for change
  • OFFERING – The thing (idea, solution, product, proposal) that you want the subject to buy, or buy into
  • ATTRACTORS – The factors that attract this person to your offering
  • INHIBITORS – The factors that inhibit, distract, or otherwise prevent this person from making the decision to buy/buy into your offering

By mapping out the factors in this way, you can really put yourself into the mind and shoes of that person, spot gaps in your understanding, and enrich your own thinking about the relationship between your offering and your customers/stakeholders. Let’s take a closer look…

Attractors

By using this sketch to list out the factors that encourage someone to make a decision in favour of your offering, you pull the focus of the offering from its features (usually what we think about the most) to what those features are for. These tend to do with things like:

  • GOAL – What would this person achieve with your offering? This is the main factor that everyone thinks about, and is at the foundation of user-centred design and jobs-to-be-done theory. A decision cannot take place without the recognition of a need of some sort, to help solve their specific problem.
  • OBJECTIVE BENEFITS – What is better about your offering than the competition, or what the person is doing already? You should be able to list some differences your offering affords them, e.g. to do some task easier/ faster/ cheaper, to do better, gain more, save more.
  • SUBJECTIVE BENEFITS – What emotional need lies on the other side of the goal (above)? This is the factor we like to think drives everyone else except us… but we know that’s not really true. This is the factor at play in marketing messages and advertising. These are the ’emotional jobs’ in JTBD theory. Things like: make me look good in front of others, make me more popular, make me feel smarter/ sexier/ cooler/ more powerful. Make me more…complete.
  • TRUST – How much would the person rely on your offering? Past experience of something is our best predictor of the future performance of something similar. The trust earned from a previous positive experience is a strong attractor in itself.

Inhibitors

Inhibitors are the forces that turn us off, hold us back, or get in the way of deciding to buy or change, things like:

  • HABIT – People’s habits — their regular entrenched way of thinking and/or doing things — can be a powerful thing to have to overcome.
  • OBJECTIVE DRAWBACKS – There may well be specific disadvantages that are worth highlighting in the array of factors affecting the person, such as increased cost of time and resources. But sometimes behind these objective drawbacks, lie factors that actually affect that person more…
  • SUBJECTIVE DRAWBACKS – These factors don’t apply to all buying or behaviour change decisions of course, but they can still be powerful deterrents. What might the person be afraid of, if they decide to do/buy/use your offering? Is there a fear of change? Fear of loss of control? Or any limiting beliefs in the way, e.g. “I don’t know if I actually deserve this”, “I’m not worthy of it”, “It’s out of my reach”…?

Visualise the factors at play with different-sized arrows

I hope you can see that the Decision Factors sketch is more than just listing pros and cons for the subject. This is a visual, so we can map how big/small each of the factors are, with different-sized arrows. This helps you (and others you show it to) understand how these various factors might work together, or counteract each other, more quickly, accurately, and comprehensively.

What do I use the Decision Factors sketch for?

You can use this to:

  • Help explore how to make your product/service more desirable to your customers
  • Help analyse research results about customers’ needs and buying habits
  • Help dig into why people are/aren’t adopting a new product/service/way of doing things in your organisation
  • Help yourself prepare for a pitch to stakeholders, to attune your communications to what they care about the most
  • Have a more productive discussion in any 1:1s with staff or stakeholders

How do I do the Decision Factors sketch?

1. Draw up the framework

Start by drawing the basic framework of the Decision Factors sketch on a whiteboard, flipchart, or even just a piece of office paper. You can even put these elements together in an online collaboration space like Miro or Mural.

2. Use the areas as prompts for discussion

Now, use each area to help structure your thinking and prompt group discussions, all with the aim of gaining a deeper understanding of how to maximise the likelihood of a particular subject adopting your offering. You can ask yourself or your group questions like:

  • What’s in it for this person to buy/use our offering / solution?
  • What is holding them back from buying it/using it?
  • What might distract them from making this decision?

Note! You don’t have to solve anything right now. Resist the temptation to justify your offering, or falsely ‘jack up’ the power of some attractors over others, or to rationalise any of the inhibitors away.

3. Capture and visualise the factors

Capture what you’re thinking, or what others are saying, on the sketch as you go. Messy is totally OK; this is definitely a case where the process of using this sketch is often better than the final product. remember to play with the size of the arrows, to indicate what factors are greater than others, or what factors you know you need to focus on. This can also expose some blind spots that you or your group might not have thought about.

4. Discuss next actions

Once you or your group have laid out and assessed the array of various attractors and inhibitors, now you can switch to ‘solution mode’, and think about what you need to do, to increase the chances of this person adopting your offering.

  • Is there something about your offering that needs to be introduced? Or dialled up? Or taken out?
  • Is there a benefit of your offering that just isn’t clear enough?
  • How might you change any marketing or communications to help people decide?
  • Are there any specific messages you need to put out there, to help people deal with the inhibitors?
  • Is there something you can do to help with a specific inhibitor, that would tip the balance in your offering’s direction?

Try it yourself

As I hope you can see, the Decision Factors sketch can be a powerful analysis and re-framing device. It can be fast and light – like using it right before you go into a pitching presentation – or it can be thorough and in-depth, like in a product strategy workshop.

However you use it, I hope it brings you might insight and success!

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!

Nail your product strategy with the Product Pyramid

by

Features! Story points! Sprints! UIs! It’s all too easy to let the detail of product management drown out the actual product strategy. The Product Pyramid can help.

Strategy is a tricky game. The more complicated the product(s), service(s) and business(es), and the more people involved, the trickier things get. Trying to get shared understanding about vision, direction, risk, priority, and so on is hard enough, let alone getting shared alignment, decision, and execution.

But so often I find that it’s all about connecting the various pieces of product management into a cohesive product strategy story. This usually involves visual framing, and getting everyone involved using a shared perspective and vocabulary that describes where we want to play and how we want to win.

Lots of product managers, designers and entrepreneurs struggle with strategy, because they jump into details too soon, or find it hard to separate what they know from what they believe/suspect/assume. Japanese master swordsman, author, philosopher and all round legend Miyamoto Musashi put it well: “Perception is strong and sight weak. In strategy it is important to see distant things as if they were close and to take a distanced view of close things“.

What is the Product Pyramid sketch?

With that in mind, the Product Pyramid sketch is a way for product managers, designers and founders to visually relate the detail of any product (or service) to the rest of what’s important about that product: the experience it provides, the benefits it gives to customers, and the value it creates for customers and the business.

It’s a simple pattern that you can draw on a whiteboard in a strategy meeting, and it looks like this:

How does it work?

The Product Pyramid is a visual guide to remind you and others how all of the parts of your product are related.

  • P = PURPOSE of the product, usually to increase some value to your business and your customers; the change your product is trying to make in the world
  • B = BENEFITS to your customers; what they talk about to others that’s so good about your product
  • J = JOURNEY people go through when evaluating, buying, using, getting help and sharing your product
  • F = FEATURES of the product; what people use in the journey
  • P = PERSONAS that interact with the product; the different types of people that go through different parts of the journey. JTBD and needs (i.e. the jobs-to-be-done framework) fit in here.
  • C = COMPETITION that also attracts the same personas with the same needs

When should I use the Product Pyramid sketch?

Use this sketch (or visual framework) if these sorts of scenarios happen:

  • You can’t seem to focus product conversation at the right ‘level’ (i.e. people get bogged down in talking about user interfaces, bugs or features when you actually need to talk about benefits)
  • You don’t have a shared understanding of the product’s strategy across the team
  • You need to come up with good research questions
  • You can’t remember all your user stories

How do I use the Product Pyramid sketch?

Make sure you have a whiteboard. If any of the symptoms above start to happen in a meeting:

  • Draw a nice big triangle
  • Draw in some horizontal lines to separate the triangle into the different zones (Benefits, Journey, etc)
  • Make some notes in the zone (or beside the zone) that reflect the conversation you’re hearing. It could be questions, assumptions, or things you’re trying to understand better
  • Listen for connections in what’s being talking about, and visually reflect this with arrows from one zone to another

The Product Pyramid is a map

The Product Pyramid is a map. It’s there to help you know where you’re at in a product discussion, and where you want to be. It’s not meant to contain lots of detail, but it does serve to point the way to that detail (that would live elsewhere). For example, the Journey layer should ‘link’ to any customer journey maps you have created.

It’s also there to highlight any gaps, vagueness, or disagreement in your product strategy.

The Product Pyramid is a story

Because the Product Pyramid ‘connects the dots’ of your product’s purpose, benefits, journey and features, it also doubles as a great way to tell your product strategy as a cohesive logical story. Two examples:

Pitch to leaders (top-to-bottom) – “The most important change we want to make in this business is [Purpose]. To do that, we need to help [Persona(s)] with [Benefits]. As they use our product, they [Journey], and they way they experience [Benefit] is through [Features]. If we invest in [Feature], this will unlock greater [Benefit].”

Rationale for a feature improvement sprint to engineering (bottom-to-top) – “This particular [Feature] in our product might be small, but it’s the source of a disproportionate amount of support requests. At the moment, it gets in the way of [Journey], and stops too many customers from realising [Benefit]. That’s why we need to focus on improving it this quarter, so that [Purpose].”

Try it yourself

So, the next time any of your product team meetings include even a bit of product strategy – e.g. sprint planning, feature brainstorming, business review meeting – your team can now have a way to keep all the various parts of the product related, and optimise discussion for business benefit and customer benefit.

Use the Product Box sketch to improve any product or service

by

Picture yourself strolling down the aisle of your local supermarket, looking at the various products on the shelves. What catches your eye? What is it about the boxes, packaging and labels that gets that product into your trolley?

Not many of us get to design those boxes and packaging, but imagine if you got to do exactly that for your business, product or service?

Or imagine if you got to design a box for you?

That’s exactly what this Product Box sketch trick is all about. It’s a way to help you think about whatever it is that you’re selling, from a fresh point of view. You use the visual ‘language’ of boxed product design (like a box of cereal) as a way to express your product’s value to customers. And it goes a bit like this:

Decide on what it is that you want to sell. As an example, I’m going to use ‘Project Manager’ (I was having a conversation with a friend the other day about how she’s trying to help her team understand how a project manager can help them).

1. Start the box

Sketch a nice big rectangle. This is going to be the front of your boxed product.

2. Sketch the front of the box

Now it’s time to start getting creative! Write the name of the ‘product’ at the top of the box in nice big letters (in my case it\’s ‘Project Manager’), and sketch whatever your product is. Make sure you leave some area blank for the next step. Note how I\’m keeping my sketching really simple:

3. Add the benefits

Next, think about the benefits of your product. What’s your product going to do for your customers? Why should they care? Write those benefits on the front of the box, too (up to 3 benefits is fine). Try not to agonise over the benefits (or your sketching) too much. Progress is better than perfection at this point!

4. Add the ‘ingredients’

Now, let’s get 3D: draw a bit of a parallelogram on one side of your ‘box’. This is the side of the box where your ‘ingredients’ go. This can be the main features of your product; the sort of things that customers want to check that your product includes, when they’re comparing your product with others. Go ahead and write whatever those ‘ingredients’ are.

5. ‘Open here’

Finish off the box by drawing the top (like you can see below). Add in something about how customers start using your product. Do they just open the box and away they go? Or do you want to add the price?

6. Refine your design

As you sketch this ‘product box’, you may well have more ideas about how to make it better. You might also get into the metaphor of the product box a bit more too, and you might want to riff off product-y things like ‘batteries not included’, or ‘assembly instructions’, and so on. Go ahead and do another sketch, and work in your refinements. Here’s mine:

And there you have it! It’s amazing how often we forget to think about our business, our product, our service — whatever it is — from a customer’s point of view, and the product box is a great metaphor for getting us thinking differently. Here are some ways you can use this Product Box sketch as an activity:

  • Help you and your team get a shared understanding about what your product/service is now
  • Help you and your team think in a fresh way about what it could become
  • Galvanize your team, and get them thinking about their internal value to your organization in a new way
  • Help you think about yourself. What value do you want to be in the world? Why should people ‘buy’ you?
  • Sharpen up your resume: what are the benefits to your new employer if they were to give you the job?

So, give the Product Box sketch a go, first by yourself and then with your team. As always, let me know if you try it out, and how it went.

Amaze your team mates with radar charts

by

If you’ve been reading this blog for a while, by now you know that I’m keen on helping you use simple sketching in your work, to explore problems, explain concepts, and generate ideas. I cover a range of topics, including drawing icons, whiteboarding, making meetings more effective, exploring problems and plans with metaphor, and visualising data.

This post looks at a particular data visualisation pattern that is really useful but often gets forgotten.

Step forward if you would, radar chart, a.k.a. spider chart, star chart or polar chart. The radar chart is great for plotting multivariate data, or in other words: those times where there is more than one value or factor that you need to measure and compare. Plus, they just look really cool.

And they look a bit like this (left) or this (right):

Snazzy, hey? Each value you’re measuring has an axis that radiates out from a point (typically of value zero), with equivalent increments along each axis. Radar charts give you a much more compelling way of looking at data, rather than just in a table. Let’s take a look at where you can use radar charts, shall we?

Great for analysing products

Are you a product manager, researcher or designer? You’ll know that you can’t judge your product’s performance on just one metric; there might be a range of heuristics that you use, to do with usability, customer satisfaction, up-time, task completion speed, and so on. And sometimes these are a bit semi-quantitative, and a bit hard to hook a definite number on. Radar charts give you the flexibility to use other values like ‘high’, ‘medium’ and ‘low’, or ‘happy’, ‘meh’, and ‘anxious.

Here’s an example from a fictional social media website, where you can see how user satisfaction is rating for four major functions of the website:

Great for analysing you

Are you working on your own professional development? Plotting your skills on a radar chart is a quick and engaging way to see where you’re at now, and where you want to grow. Here’s another fictional example, using a mix of user experience designer skills:

Great for analysing staff and teams

Sports players and coaches have used radar charts to analyse players and teams for ages (and if bringing data and sports together is pure nerdy heaven for you, check out these charts for hockey and soccer/football!) This visual way of assessing team members’ skills is really handy for candidate interviewing in recruitment, and for helping team members to balance where they want to grow, and where the team needs skills.

What’s really nifty is that you can overlay several team members on the same radar chart, to build up a story of aggregate sets of skills in a team:

In the example above, we can instantly see the different levels of ability in teamwork, design and sketching, as well as where these two team members are complementary. Plus, this also helps us see that we don’t have much by way of development ability in the team.

So there you have it; aren’t radar charts amazing? Start using them by analysing yourself and your skills, then see how you can apply them in other areas of your work.

Sketch the resource Tank for better team efficiency

by

I’m sure you know the feeling of being absolutely overwhelmed. You’ve got so many things going on in your head, and then one extra simple thing comes along, and you’re just flummoxed. Stressed. Jammed. Stuck.

Welcome to cognitive overload.

Not fun, is it? But hey, aren’t you glad there’s a sketch you can try, to visualise all those things, and then work out how to make sense of it all? I know, right?

The Resource Tank visual framework

I’d like to introduce you to my friend the Resource Tank sketch, and it basically looks like this:

You draw a tank, with a wavy line to show that it’s full of liquid, and then some straws coming out of it, going to various things that are drawing on that resource. The resource itself – the liquid in the tank – can be different things, like fuel, or time, or attention, or patience, or money.

When we run into a problem, or have to make a decision, it draws from our ‘cognitive fuel tank’. A few things or a few decisions are okay, but when there are more and more, it can drain us dry. Visualising it on paper (or on a whiteboard) like this is a great way to bring all those unseen things out of the fog of your mind and into the light, and then think about what we can do about them. But wait, there’s more:

By putting levels in your ‘tank’, and straws that go to different depths, you can also explore how different things can drain more of the resource, whether we want them to or not. This is a really neat visual metaphor that you can adapt and use in a variety of ways, e.g.:

My ‘attention map’ – what are the things that matter the most to you? There should always be ‘fuel’ for those things, which is why they get the deepest straw. There are things that matter a lot less, so we should only let them have a shallow straw.

Budget and expenses comparison – what would it look like if you compared what your budget expenditure should be, to what it actually is? Are there types of expenses that are crowding out other types, draining resources away from the things that matter?

Team resources and expenditure comparison – What would the fuel tank look like if it were your team? Say you manage a support team; are you leaving enough fuel in the tank for your premium clients? Or is energy being sapped by lots of seemingly urgent and important tasks?

These are just a few examples of how you can use the Resource Tank visual framework, and I’m sure that if you applied it to your own situation, you could probably think of (and sketch!) some more. Whatever happens, we all want to move away from this situation (below)!

So have a go, and have a think about how deep all of those straws are sinking into your valuable energy and attention, and then have a think about what changes you could make to set those straws at more – ahem – fuel-efficient levels!

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)

Get to grips with your Inner Critic

by

We’ve all heard it, and you might’ve said it yourself: “I can’t draw!” You can, you just have to kick that inner critic. Here’s a great way how.

I’m afraid there’s an elephant in the room. I’ve been putting up these tips and techniques about using simple sketching to help you think better for quite a few weeks now, but all along I’ve ignored a very important factor in helping you sketch. You know what that is?

It’s your inner critic.

Yeah. That thing inside you that holds you back. That voice that silently says things like:

  • “You’re going to suck at this”
  • “You should be doing more productive things with your time”
  • “People are going to think you’re stupid” 
  • “Just give up”

You get the idea. Not fun to be around, hey? But we have to tame our inner critics if we’re ever to get ahead. Here’s a true story about making mistakes in front of bosses:

A true story about making mistakes in front of bosses

Once I was in a meeting with a couple of very senior executives and my immediate boss. While they were talking, I was trying to capture a summary of what they were saying on a whiteboard. I was really nervous and hesitant in front of these guys.

At one point, I drew a few boxes and arrows that I thought described their view of the technical system they were talking about. One executive looked at what I drew. He immediately blurted out, “No, that’s wrong, that’s not what I meant.” But then he paused, still looking at the boxes.

And then it happened. He asked me why I drew the boxes the way I had (it had to do with what part of the system conceptually ‘contained’ another part), so I explained. It turned out that I (and others in the room) had been carrying an assumption about the system, and once that assumption was called out, it unlocked a whole new – and much better – conversation about how the system should work.

See? Even though the sketch itself was ‘wrong’, it was a catalyst to a better conversation.

Never ever be afraid of other people seeing your sketches. Your sketches will be viewed through a different lens than your lens, and the catalytic potential they have is huge.

But back to that inner critic.

Your inner critic is just trying to keep you safe

There’s lots of advice around about kicking the inner critic, but to me it’s all mind games that don’t really work (at least not for me). But what is important to understand that as fun as it might be to externalise this urge for self-editing and self-criticism, it’s still actually an integral part of you. And what’s more, it’s being critical because it’s the part of you that is just trying to keep you safe from harm.

Safe from physical harm, sure. But also safe from judgement, safer from failure, and safe from disappointment.

Sketch your inner critic

A big part of taming the inner critic is to face up to the negative talk. Not dismiss it, ignore it, or manage it, but acknowledge its value to you, and deal with it as if it was a real conversation with a real person. And this is where sketching your inner critic comes in. When you make it ‘real’, on paper, in front of you, it’s out of your head and in front of you, for you to talk with it, and have true command over it.

It goes like this:

Think about your inner critic. What does he/she/it/they (insert fav pronoun) actually look like? Sound like? What does it say to you? What habits does it have? Think about the times it has held you back from something, anything.

Now sketch that critic in all its safe-seeking glory. No-one else is going to see this sketch, so go nuts. Is it small and dark? Big and pale? Horns? Bad teeth? Droopy eyes? Big mouth? Bad acne? Really pour what you think of it into that sketch.

Write a name there, too.

Take a good look at that inner critic that you have now made real on a piece of paper, and listen to what it’s saying. Try to find the gift in what it is saying; there might actually be an inner strength or a super-power hiding in there. For example:

  • From: “Your drawing looks dumb” – To: “I have great visual taste, and my drawing abilities don’t match my great taste yet“
  • From: “This is useless” – To: “I get to draw, which exercises my imagination and helps get ideas out of my head and into the world“
  • From: “Nobody is going to like this on social media” – To: “I like to share who I am and what I care about on social media, and people will appreciate my authenticity“

You get the idea? Bonus points for turning each critical statement into a power statement.

One of the best pieces of advice I ever got about getting rid of negative self-talk is to talk to yourself like you would your very best friend.

Once you’ve had this heart-to-heart with your (now visualised!) Inner Critic, you can thank it for its contribution, reassure it that you’re in command now, and that you don’t need it anymore.

Now screw up that piece of paper, and put it in the bin.

Go ahead and try it. It takes 5 minutes, and it might be the best 5 minutes you have today. And if you’re brave, why not share a photo of your inner critic sketch on social media? 😉 Let’s normalise being authentic about our drawing abilities!