feature – how does visual thinking practically help an organization? the author discusses three different ways in which it can be used to benefit a business and help it to improve itself.
words: bruno pešec, industrial engineer, lean practitioner and martial artist.
vision is such a potent sense that we tend to recall pictures much better than we do written or spoken words. lean practitioners know the power of visual thinking well. for example, remember kaoru ishikawa’s seven basic tools of quality – pareto chart, cause and effect diagram, stratification, check sheet, histogram, scatter diagram, and graph and control chart? only one is non-visual (stratification). these simple, but powerful tools have stood the test of time, and are still useful today.
in this article, i want to talk about three practical applications of visual thinking that aim respectively at:
- rapidly testing our assumption and preconceptions;
- asking deeper and more pertinent questions;
- distributing knowledge that needs to be regularly used.
using visuals to test assumptions
let’s imagine a sales team in a software company that is looking to increase the revenue they generate. they have a digital product, which is primarily sold through the website. a fair assumption for them to make would be to think that if they can bring more traffic to their sales page, the revenue numbers will go up.
rather than jumping to a solution and spending money on advertising to bring more traffic to the website, the team decides to look at the numbers. they go into their web analytics dashboard and download data on the number of sessions and visits per month. they also download their sales data, organized by month and by product.
the first question they ask themselves is: “is there a correlation between the number of website sessions and sales?”
here is what the data says:
what do you see here? what would you answer? how would you proceed?
first, the team notices that there seems to be no correlation between number of sessions and monthly revenue. secondly, they become curious about outliers: three dots on the top representing the highest revenue and three dots on the right representing the highest number of sessions. finally, they start asking themselves how they can better understand the quality of their sessions.
by visualizing data, the team is able to rapidly test their initial assumption. they used a mix of quantitative and qualitative data to understand what was happening, why and how. in the end, they successfully improve their monthly revenue.
using visuals to ask better questions
imagine you have a brilliant idea that you want to refine. you could try to write it down, perhaps using a template, like a business plan or a suggestion card. if these templates are any good, you should be able to use them as a checklist of the items you need to address. you would go item by item, thinking each one through, writing down your answers, then refining them further until you are satisfied. or least that’s how it should go.
in most cases, however, we end up spending too much time on these tools, with very little to show for. too often, the essence of the idea gets lost somewhere in these documents, frequently together with the narrative and the story of how the idea came to be (which are critical for sharing it with others). this is exactly why a3 problem solving is so useful: it provides a structure that allows you to retain the narrative around the problem and its proposed solution and it forces you to ask all the difficult questions.
what if you were to try to use such a visual tool to describe your idea?
the good news is that there are a lot of them out there that you can choose from. the bad news is that… there are a lot of them out there that you can choose from! when selecting one, you should consider the tool’s clarity of instructions (do you understand how to use it?), usability (does it get in our way or make things easier?), and internal logic (does it support narrative explanation or is it all over the place?).
take a look at the photo below, referring to a music-sharing website. (the business model canvas was developed by alexander osterwalder, whereas the block illustrations are by lauris muzikants.) what is it telling you? what stories do you see? what would you ask next?
notice how on the right side we have a clear view of who the customers are and what value is provided to them. there is color-coding to differentiate customer groups: music lovers with a paid account, music lovers with a free account, and advertisers. we have a clear understanding of what each of these three groups bring back to the organization: a subscription fee from paying subscribers and advertisement fee from the advertisers. only free users get exposed to ads.
looking to the left, we can see key elements of the operating model, namely the activities, resources and partners required to deliver the value to customers. we can see that this idea is based on providing music, but without actually owning it. that means the company must partner with record labels and musicians. they focus on developing top-notch software and infrastructure, which they are keeping in-house. finally, looking at the bottom row, we can see what the key drivers of cost and revenue are.
let’s stop here for a moment and observe what just happened. with a single illustration and just a few words we were able to explain and convey an idea that would have otherwise taken pages and pages of text.
to continue with the example, the question i posed last is what we could ask next. a barrage of questions, really, depending on the direction in which we want to head. if you are happy with the idea on the canvas, you could ask what must happen to allow this idea to work as described. if you want to increase the scope, you could ask how the idea would change if you added podcast lovers as one of the segments.
the operating model is always a great place to ask provocative question. some example for this case would be what would happen if you removed the it infrastructure or what would happen if you made music yourself. if you are stuck, you can always go for one of my favorite questions – how does this make sense?
by visualizing the idea, we have created an artefact – object – that we can further discuss, analyze and test. it’s much easier, more respectful and less hurtful to discuss a piece of paper than to go at each other.
using visuals to distribute knowledge efficiently
the first two applications i described are about enhancing our learning and deepening our understanding by using visual methods. now i want to draw your attention to an opportunity to unlock even more value from visual thinking without “discarding knowledge” – something warn us against in lean product and process development.
in their recently-published , josé ferro and fernando rodrigues echo this idea when they write: “today’s highly competitive market requires companies to engage in ever faster technology development while maintaining costs under control, in order to cope with increased pressure from ever more elaborate customer demands. reusing knowledge is one of the most useful approaches to shorten time-to-market cycles, to reduce risks and costs, and to increase the chances of success.”
it is with this in mind that ward and sobek also advise us to make knowledge capture a priority and to train people and create systems that allow us to transform data into useful knowledge. are a great example of visualization that pack a lot of knowledge into a small space, so the information can be quickly digested and interpreted.
another concept discussed in the book is that of a knowledge brief, a single sheet on which all information relevant to the matter at hand is recorded. , a board game that supports innovation and entrepreneurship, deliberately includes simple visualizations to make said concepts tangible.
for example, to make knowledge capture easy and reusable, each team playing the game is given an innovation accounting sheet. it consists of a grid that mimics the market and customers, with blank fields in which teams can write the results of their experiment (for instance, what the customer wants). as teams run experiments, they populate the innovation accounting sheet, which then serves as a visual overview of what they know, which in turn enables them to take informed decisions.
******
in conclusion, written reports still have their role to play in documenting our learning, but if we want to create knowledge that can be used on a daily basis we truly need to consider visualizing it. engaging with trade-off curves, a3 storyboards, knowledge briefs, canvases, and other visual tools is less cognitively demanding, leaving us more brain power to ask the right questions.
the author
bruno pešec is an industrial engineer, lean practitioner and martial artist.