Cense

Innovation + Impact

Visual Thinking

by

Service and product design involves creating something, envisioning it’s use, consideration of its effects, and hopefully seeing it achieve a goal. When we are creating or planning our project we need to consider all of that on top of the many ideas we have about what that product or service ought to involve. That is a lot to hold in our heads at one time.

This is why designers often rely on visual thinking and communication to help illustrate these ideas as systems. The benefits of this approach are many and include:

  • Providing a way to communicate your thoughts in multiple dimensions. Time, space, sequence, and effects are all different considerations for service design and visualizing that allows us to see these all in one space. Our language is linear, visualizing allows for linear and non-linear effects.
  • It creates a space for everyone to participate. Whether you are a skilled visual communicator or someone who hasn’t drawn anything by hand in 20 years, nearly everyone can draw. Visual thinking tools can provide a means to literally get people working on the same page. Simple methods like the Sketch Map are easy to employ and get everyone sharing ideas together.
  • Visual language – such as that illustrated by XPlane in their useful guide to visual thinking transcends spoken words and allows us to communicate even when our shared spoken language isn’t strong.
  • Visual thinking allows us to use metaphors, express complex emotions, and connect physical and emotional things together during a service journey in a way that is difficult to convey through oral or written language.
  • Visuals provide an artifact that can be interrogated, explored, and reviewed from many different perspectives allowing people to point to objects, relationships, and structures and ask about their purpose, illustration, and meaning without requiring much technical understanding of the problem-domain (allowing outside and alternative perspectives to meaningfully contribute).
  • It also provides a means to generate a shared understanding of the system boundaries, components, and purposes that guide your development of the service. It gets people on the same page metaphorically and literally.

Visual communicator Angelika Skotnicka provides a strong case for why we want to consider visual thinking and how it is done from the perspective of graphic recording.

Consider ways to bring in visual thinking to your project planning, service design, evaluation, and strategy development. It is low-risk, high-reward and is an engaging, low-cost, and often enjoyable way to generate enormous insight quickly and effectively.

Want to learn more? Contact us and we can help you bring your ideas to light visually and more.

Systems Diagrams Made Simple

by

Sketch diagrams are powerful tools for visualizing complex programs and systems. This simple technique literally gets people on the same page.

Mapping out a service or product ecosystem can be a complicated endeavour. There is the entire field of systemic design that focuses on tools and strategies to engage users for starters. There are approaches like synthesis mapping and service design canvases that can help us walk through the various aspects of a system to find points of leverage, threat, and opportunity.

Nearly all of these methods and tools require user orientation and training — sometimes a little, sometimes a lot. However, in many of our engagements, particularly in healthcare, we find the time (and attention) is so limited it becomes difficult to engage participants using methods that require considerable instruction.

It’s here that we introduce a technique and tool called the system sketch map.

Sketch mapping

A sketch map is a multimedia system map that is created by using any form of representation such as blocks and arrows, stick figures, or elaborate illustration and can be developed at any moment. A sketch map gets participants past the challenge of having to learn a technique or representation convention and can be particularly useful for those participants who feel unskilled at drawing or visualizing their thoughts.

This works well with professionals who may find themselves uneasy about using visual media or do not consider themselves ‘creative’. (Note: Everyone can draw. It’s important to emphasize that this is not an art project).

The exercise works like this:

Begin with the instructions: Draw your system.

That’s it.

Some guidelines: 

  • Any visual formalism can be used. One can even combine visual approaches together.
  • Emphasize the simplest media possible: Pens and paper (or crayons), sticky notes (or stickers) are among the best tools because they are flexible, colourful, and can be combined easily. These are also inexpensive and easy to obtain.
  • Large format paper (e.g., newsprint) or whiteboards are best to use as a canvas to facilitate group participation
  • Group participation is key
  • There are no right or wrong ways to do this. Whatever participants wish to include in that system is all that matters.
  • Give participants a time frame (usually 30 – 50 minutes works best) and try and ensure there are between 4 and 6 people in the group.
  • Emphasize DOing over THINKing. It’s easy for groups to try and do this ‘right’ and analyze everything. The use of simple, inexpensive materials allows people to create ‘do-overs’ easily, erase material, revise and recreate things.
  • Lastly, strive for ‘good enough’ and ‘coherent’ over ‘excellent’ and ‘complete’ (which are highly relative in this context).

What is interesting is that the participants define what their system is and what goes in it. In making these choices it becomes evident what they see as most essential, important, or relevant.:

A completed sketch map then allows everyone (the facilitator and participants) afterward to ‘interrogate’ the map (not the map makers) and ask questions like “does this choice of colour mean anything?“, “is the distance between these two things represent some kind of scale?“, “what might be missing from all of this?”

This interactive discussion process allows everyone to explore what gets placed at different positions, sizes, in different colours, and what gets included and left out of the map. It allows for the use of symbolism (conscious or not), metaphor, and representation without having to shape or bias the participants toward using a particular way of visualizing the system.

What it is, is what it is.

This simple technique can yield enormous insights into the assumptions, structures, relationships, actors, and core components associated with a system and do so within one or two hours and with a small budget.

For more information about sketch mapping and how it can help you with your work or just for more on innovation methods, tools, and strategies, feel free to contact us. We’d love to hear from you and can help.

Photo by Danae Paparis on Unsplash and Kaleidico on Unsplash

Three Questions for Evaluative Thinking

by

Evaluative thinking is at the heart of evaluation, yet it’s remarkably challenging to do in practice. To help strengthen those evaluative neural pathways, we offer some questions to aid you in developing your evaluative thinking skills.

To begin, let’s first look at this odd concept of ‘evaluative thinking’.

Tom Grayson’s recent post on the AEA 365 Blog looked at this topic more closely and provided a useful summary of some of the definitions of the term commonly in use. In its simplest term: evaluative thinking is what we do when we think about things from an evaluation perspective, which is to say, a point of view that considers the merit, worth, and significance of something.

Like many simple things, there is much complexity on the other side of this topic. While we have many methods and tools that can aid us in the process of doing an evaluation, engaging in the evaluative thinking supporting it is actually far more challenging. To help foster evaluative thinking we suggest asking three simple questions:

What is going on?

This question is about paying attention and doing so with an understanding of perspective. Asking this question gets you to focus on the many things that might be happening within a program and the context around it. It gets you to pay attention to the activities, actors, and relationships that exist between them by simple observation and listening. By asking this question you also can start to empathize with those engaged in the program.

Ask: 

What is going on for [ ] person?

What is going on in [ ] situation?

What is going on when I step back and look at it all together? 

Inquiring about what is going on enlists one of the evaluator’s most powerful assets: curiosity.

By starting to pay attention and question what is going on around you in the smallest and most mundane activities through to those common threads across a program, you will start to see things you never noticed before and took for granted. This opens up possibilities to see connections, relationships, and potential opportunities that were previously hidden.

What’s new?

Asking about what is new is a way to build on the answers from the first question. By looking at what is new, we start to see what might be elements of movement and change. It allows us to identify where things are shifting and where the ‘action’ might be within a program. Most of what we seek in social programs is change — improvements in something, reductions in something else — and sometimes these changes aren’t obvious. Sometimes they are so small that we can’t perceive them unless we pause and look and listen.

There are many evaluation methods that can detect change, however, asking the question about what’s new can help you to direct an evaluation toward the methods that are best suited to capturing this change clearly. Asking this question also amplifies your attentive capacity, which is enormously important for evaluation in detecting large and small changes (because often small changes can have big effects in complex systems like those in human services).

What does it mean?

This last question is about sensemaking. It’s about understanding the bigger significance of something in relation to your enterprise. There can be a lot happening and a lot changing within a program, but it might not mean a whole lot to the overall enterprise. Conversely, there can be little to nothing happening, which can be enormously important for an organization by demonstrating poor effects of an intervention or program or, in the case of prevention-based programs, show success.

This question also returns us to empathy and encourages some perspective-taking by getting us to consider what something means for a particular person or audience.  A system (like an organization or program) looks different from where you sit in relation to it. Managers will have a different perspective than that of front-line staff, which is different for clients and customers, and different yet from funders or investors. The concept of ‘success’ or ‘failure’ is judged from the perspective of the viewer and a program may be wildly successful from one perspective (e.g., easy to administer for a manager) and a failure from another (e.g., relatively low return on investment from a funder’s point of view).

This question also affords an opportunity to get a little philosophical about the ‘big picture’. It allows program stakeholders to inquire about what the bigger ‘point’ of a program or service is. Many programs, once useful and effective, can lose their relevance over time due to new entrants to a market or environment, shifting conditions, or changes in the needs of the population served. By not asking this question, there is a risk that a program won’t realize it needs to adapt until it is too late.

 

By asking these three simple questions you can kick-start your evaluation and innovation work and better strengthen your capacity to think evaluatively.

Photo by Tim Foster on Unsplash

Dashboards for innovation evaluation

by

A dashboard system is a way of tracking project activities across a range of different lines of inquiry. This is of particular benefit to those interested in developmental evaluation. Developmental evaluation (DE) is an approach to evaluating programs with an innovation focus and can be used as a means of generating data to support strategy development and deployment. That’s how we use DE.

Developmental evaluations often have multiple components to them that include a variety of methods, data sources, tasks and duties, and sensemaking requirements. All of this information can make a DE difficult for the client to gain a sense of what is happening and even confuse the evaluator at the same time. One way to manage this is to create something we refer to as a dashboard system.

Dashboards: Making strategy and evaluations visible

A dashboard is a means of showcasing multiple information streams in a simple, accessible manner that is easily understood. It might include notes from a meeting, data collection summaries, schedules of activities, and reflective notes. It is not a wholesale repository of all data, rather a higher-level summary that includes enough detail to get a sense of what activities are happening, when, and to what degree.

Among our favourite tools is Trello. Trello is organized into a series of ‘boards’ that allow you to organize content based on a topic or theme and create a simultaneous ‘stream’ of content within each board.

For example, a developmental evaluation might involve something like the following boards:

  1. Interviews with key stakeholder groups
  2. Observations
  3. Document reviews
  4. Sensemaking and strategy notes and outcomes
  5. Meeting minutes
  6. Survey or other data collection results
  7. Reflective notes
  8. Data collection plan

These boards would include any project component that has a distinct, coherent set of activities associated with it. It could include methods, data components, meetings and activities, populations or key document groups.

Tools for thinking and seeing

Trello is just a tool. What we’ve illustrated above could be done as channels within Slack or even as a series of sections within an MS Word or Google Doc. Even an Excel spreadsheet can work. Anything that allows someone to visually track details about discrete areas within a larger project.

(Although tools like MS Word or Excel will work, they are less than ideal as they require strict version controls to articulate changes and this can be difficult to manage, particularly if there are multiple contributors to the document on a regular basis. The reason one might choose MS Word or Excel is less about its functionality and more because it is what people are used to.)

What makes a DE a challenge is that there is a lot of data being generated from many different sources within a complex context. This makes the management of information a challenge and that poses problems for the task of generating helpful insights from the data generated. It also makes it problematic for identifying emergent patterns.

By making data visible, a dashboard allows multiple eyes and multiple perspectives to ‘see’ the data and thus, expands the possibilities associated with seeing possibilities and emergent conditions. The dashboard also increases accountability for all parties. For clients, a dashboard allows them insight into what the evaluator has access to on a regular basis and avoids any surprises. For evaluators, it ensures that clients have the means to engage in the process and don’t sit back waiting for insights to be ‘served up’ to them. DE is best done when it is a collaboration between the client and the evaluator and a dashboard can help this.

Lastly, a dashboard system provides a means of organizing content and keeping track of what is collected, identifying what is needed, and providing a quick-look means to explore what is known and unknown in a project.

Cense employs the dashboard approach on its projects whenever possible. If this approach is of interest to your organization and you want a means of developing strategy and evaluations in a more engaging, transparent manner connect with us and we can show you how this works in practice.

 

Engagement for ideas

by

Engage everyone in idea creation

Among the biggest success factors in any organizational change initiative is engaging staff and stakeholders in participating in the change process; this is true for idea generation through the design cycle to implementation and evaluation. How do we overcome the challenge of disengagement to produce productive creative, innovative ideas in our organizations?

Beyond brainstorming

Ideas are usually the starting point for any change initiative. Ideas produce the raw content of problem identification and the seeds for solution generation. Brainstorming is often the means people first think of as a way to generate ideas and explore concepts. However, there are some substantial problems with this approach and some ways around it.

Brainstorming has been widely criticized for good reasons. Among them: it favours those voices who think (and speak) quickly, speak early, often and loudly. Those early suggestions drive the conversation for what comes next, creating a path dependency that’s hard to escape once initiated. If you’re a quieter, perhaps more contemplative person, you’ll find that you are either late to the conversation or not included. From Jungian Personality Theory, this indicates a bias towards extroversion over introversion, which excludes about 40 per cent of the population according to some estimates.

This approach also favours what Min Basadur would classify as an ‘generator’: someone who’s work style preferences favour idea generation. Those from the other quadrants in the Basadur Profile, particularly ‘conceptualizers’ and ‘optimizers’ (ones who’s work style preference leans toward processing and organizing information) are less likely to respond quickly.

Ideas in private and public

Another problem with many ideation strategies is that many really useful ideas are a bit heretical or outlandish. While design thinking writers often refer to the need to generate ‘wild ideas’ without criticism or judgement, the truth is that’s a lot harder to do in practice, particularly when there are power dynamics in the room, reputations, and the real fear that comes with change and challenges to established practices. The public nature of the ideation process favours transparency, but induces self-censorship and produces disengagement for many and hyper-engagement for a few.

A solution is to have those involved in the process generate ideas independently and anonymously contribute them via a suggestion box (digital or analog). Keep the suggestion box open for a defined period — we recommend no more than one week or as short as three days. This allows time for those who are more reflective to mull through their ideas and contribute them, while those who are more quick to generate ideas will not be affected.

These are then collated independently by someone neutral to the problem and solution set and organized thematically. This has the advantage of potentially embedding some of the wildest ideas within a small set of other ideas that might seem far less threatening. If you create a category of ‘wild ideas’ the risk is that the entire category will be dismissed. A more public, but elaborate, means of doing this can be found in the CoNEKTR Model described elsewhere.

This process can be repeated over the design cycle at different stages – anywhere diverse perspectives and feedback is needed.

Overcoming biases to better ideas

The bias toward ‘rapid ideation’ in design thinking systematically excludes people in favour of a well-meaning intention of trying to avoid participants ‘over-thinking’ a problem. While that might happen, it still prevents many from engaging in the process fully because of personality, work preferences, cognitive style and social pressures.

The strategy listed above is a simple, but highly effective means of getting lots of ideas and engaging your entire team in the process. Try it out. You might be surprised what ideas come from it all.