Cense

Innovation to Impact

Designing for Awful

by

One of the most profound, fun, and engaging techniques for creating an attractive service or product design is oddly focused on the exact opposite: Designing for Awful.

How to use this

This strategy is as simple as it is effective. When workshopping ideas allot some time to have participants develop ideas and designs for the worst possible version of the thing they are designing.

This is a flip of a traditional ideation session where people try to develop suggestions for what to focus on, whom, and what the best use of resources might be. In Designing for Awful, we do the opposite. It is used usually in tandem with ideation sessions that are focused on surfacing ideas in general.

This can be used to frame a service, product or describe the experience of doing something like a survey or participating in an event. It’s a simple, fun, and sometimes counter-intuitive way to surface assumptions, biases, and qualities in what we want, need and don’t want in our design.

Like any ideation-focused exercise, it must be managed appropriately. Individuals need to feel safe in surfacing ideas, free to discuss them, and preferably, offer an opportunity to share at least some of them anonymously. People generally have a lot of fun with this simple exercise.

Benefits

The benefits of this are many.

Firstly, it focuses on the things we tend to avoid — unpleasant feelings, experiences, or sensation — and thus, might be missed in consideration of our design.

It also overcomes an optimism bias. Design is largely a positive-oriented practice where we look to solve problems, not make them. Designing for Awful helps us to move around this bias by looking at what is not addressed.

This approach is also excellent for helping surface values in practice and in specific terms. To illustrate, it’s one thing to speak in a positive or affirmative tone such as a statement like “we value inclusivity.” Designing for Awful could lead us to be specific “Our service is inaccessible to someone with a mobility disability” or “it is sexist” or “our product can only be used by people who are right-handed.” By surfacing what makes something not work we are better able to see what will.

This approach is also excellent in helping, paradoxically, surface what we want by framing things in terms we don’t want. How often have you met someone who first tells you what they don’t want in something before they get to describing what they want?

This allows people to have a little fun and we find that some people are more bold and assertive with their creativity in the negative, than the positive and this technique lets that come out.

Lastly, the exercise can be a useful way to surface who needs to be at the table moving forward. We find that the need for having the voices of certain individuals, groups, roles, or departments in the discussion is better clarified when we consider how bad things would be without them.

Try this out at your next design session or team meeting as part of a check-in and you might find some laughs and some deep insight along with it.

If you want to inspire new thinking and better design in your organization for engagement and impact, reach out and contact us. This is what we do.

Persistence: The Innovation Process Outcome

by

When looking to evaluate innovation many seek to find numbers related to product adoption, revenue generated, people reached, when what they ought to consider first is process outcomes.

Sustainable innovation — a process, practice, and culture of design-driven creation — is the most valuable outcome for any organization. Innovation is not about creating a single item — product, service, policy — it’s about doing it regularly, consistently, over time.

Regular innovation only comes from persistence or what Seth Godin calls The Practice.

Measuring the practice — the amount of activity, persistence, and consistency of effort — is what any organization should be evaluated against. It fits with what we know about design thinking, performance and innovation: the more ideas you generate, the more prototypes you create, and the more attempts you make the more likely you are to have better ideas, more successful products, and create transformation.

Coming up with a single successful innovation is mostly good if you’re seeking to be bought up by a competitor and, while that can be lucrative, it’s not a sustainable strategy and is contingent on having one very good idea. Having many good ideas and having them implemented into practice is what creates sustainable, resilient organizations. It is what allows organizations to adapt in times of crisis and create new opportunities in times of contraction within your market.

This is what a culture of innovation is all about.

Metrics of Effort

There are many metrics and methods that can help capture the effort of your team in developing that culture of innovation. These can be used to complement questions we might ask about design thinking. Here are a few:

  • Number of attempts
  • Number of ideas generated / ideation sessions engaged in
  • Number of concepts proposed and prototypes developed
  • Background research gathered (e.g., artifacts)**
  • Consistently of application (i.e., ongoing use of a process and fidelity)
  • Number of solicitations for feedback from internal and external sources
  • Integrations within existing processes and tools
  • Materials used
  • Evaluation designs created for products or services
  • Evaluations implemented
  • Number of products launched outside of the organization
  • Number of new innovations generated (may be products, processes, or policy improvements)
  • Persistence of effort (e.g., continuity of activity, sequencing, and time-spent)

** note that research can be a trap. It’s easy to get stuck in over-researching something. While important as a product, it’s only useful if the research converts to real process or product efforts.

These are part of an Innovation Implementation Index that can help you to assess what innovation activities that you are undertaking and whether they are leading to an actual output or outcome.

By looking at not only what you do but how often and persistent your efforts are you will later be able to assess how your organization adopts, builds, and benefits from a culture of innovation.

Are you looking to build this with your organization, unit, or team? Contact us and we can help you build, assess, and sustain a culture of innovation in your organization.

7 Questions to Evaluate Design Thinking

by

Design thinking is much more than sticky notes, whiteboards and creative exploration. It’s impact can be felt in the outputs and outcomes tied to actual product or service and much further if we allow ourselves to focus on that.

Here are 7 questions that we ask of design thinking that focus on the learning outcomes and uncover the true impact of creation, design, and execution, which is a big part of what design thinking is all about.

By asking these we can better tap into the true return on investment of design thinking as a transformative approach to learning, not just product or service design.

  1. What do people learn in the process of engaging in design thinking?
  2. What new skills to people acquire, develop, or refine through design thinking?
  3. How are the lessons from engaging in design thinking applied to other subsequent products?
  4. What is the effect of design thinking on the mindset of those involved in a design-oriented project?
  5. How does the co-design process influence team development, cohesion, creativity, and innovation performance?
  6. What role does design thinking play in shaping the innovation culture (e.g., creation, execution, delivery, and evaluation) with an organization?
  7. How does design thinking contribute to the implementation of innovations?

Evaluating the impact of your products or services is always important, but if you focus only on that you will miss some of the biggest benefits that design thinking offers your organization when done well.

If you need or want help in learning how your team learns and amplifying the effects of design thinking, contact us and we’ll help you out.

Note: This article was inspired by a recent post on our sister blog, Censemaking, which focuses on ideas, commentary and issues tied to innovation.

Innovation Design Quality Control

by

You want and need help in transforming your organization or business line and are seeking a consultant to help you. What should you look for? Let’s look at questions and issues you may want to consider when starting an innovation journey.

We break it down into three (plus) areas: Design research and foresight, service development, and evaluation.

Design Research

Design research is about exploring the problem or circumstance that you’re looking to intervene in through introducing a new product, service offering, or policy (which we’ll refer to as an innovation).

Design research is much more than ‘doing your homework’ and is meant to work with any marketing and financial studies you may have done. Design research is about exploring your end-user(s) — both identified and potential additional users. Responsible design research is also about looking at who else your innovation affects.

It will incorporate systems thinking into the process by considering the various ways in which your innovation affects and is affected by the various interconnections around it. For example, your service might be tied to other things (e.g., supply chain, regulatory issues, community norms) and good design research will help articulate these and allow you to map and model systems using visual tools.

Your innovation design team should have skills in design and research and understand a variety of methods and approaches such as quantitative analysis, qualitative data collection, sensemaking (for innovations dealing with complex situations), and behavioural science. The last point — behavioural science – is what allows you to understand what, why, and how an individual or group will choose to engage with your innovation and serves as a foundation for the next stage of work: service development.

But first, let’s go a little ahead into the future to look at the other part of design research: foresight.

Foresight

Strategic foresight is an approach to research that looks at the trends and drivers that influence specific domains of interest like your market, community, or social life as a whole. It draws on a variety of data sources such as published reports, publicly available (or privately held — if you have access) databases, as well as a series of exercises and activities that allow you and other stakeholders to envision what possible futures might look like.

The UK Social innovation agency Nesta has a useful, accessible primer on some of the methods that are used to envision futures.

Future-thinking is important because your innovation will always be applied to tomorrow, not today. Sustainable, effective innovations are those that meet emerging needs not just present ones. Foresight considers how and why things might change and, when combined with strategy and behavioural science, allows you to shape the design of your innovation to better anticipate and (hopefully) meet those changes as they emerge.

Service Development

Service development can include everything from exploring the physical space where your innovation will be deployed to undertaking usability research on digital platforms. The range of practices associated with what is more commonly called service design are many and when enlisting support to design your innovation it’s critical to ensure you have the right talent.

Service design often seeks to develop models of your intended users based on the design research you’ve undertaken. This can result in tools such as personas that provide evidence-informed caricatures of your users that you can use to develop and test scenarios.

Service design methods incorporate visual thinking methods and tools and design thinking by exploring the research, developing ideas, testing and trying these ideas out in ways that inform strategy, and then deploying them into the world. Having a design team with skills in design methods, facilitation, and visual presentation will make this much easier.

Visuals can include everything from simple (but illustrative) maps like the image above to more sophisticated visual models, ‘gigamaps‘, and storyboards.

Evaluation

Last and certainly not least is evaluation. It’s one thing to design an innovation, it’s another to know whether it does what you think it does. Evaluation allows us to assess what kind of impact our innovation has on the world, what processes lead to that impact, and what aspects of our service, product, or policy are most likely influencing this impact.

It is through evaluation of our innovation that we are better able to fine-tune, amplify, or retract our offering to ensure it’s creating the most benefit and not doing harm. Evaluation also allows us to understand what hidden value our innovation might be offering, to articulate your return on investment (ROI), and to widen your perception of what your innovation does and could do.

Bringing in design firms that do not build in professional-grade evaluation to the project is like doing half the work. What good is your new product or service if you have little idea how or whether it works in the real world over time?

These are some of the things that anyone looking to develop an innovation in-house or with a consultant team needs to consider. We have a lot of resources on our learning page on some of these methods and tools as well as overall approaches to supporting groups in asking better questions prior to engaging a contractor.

This is what we do. If you want help with any of this and doing good, quality service design, design research, evaluation and foresight, please reach out and contact us. We’d love to hear from you.

Design for Living: A Day in the Life

by

Product and service developers can easily be fooled into thinking all they need to focus on is the moment of engagement with their product. The design method “A Day in the Life” can help us put our potential audience (customer, client, or “user”) into a clearer perspective.

A Day in the Life is a simple activity that seeks to catalogue the activities and contexts that your audience might engage in within a typical day to help shed light on the life circumstance and situations that could influence your product.

Begin at the Beginning

Let’s illustrate this simple method with an example: education and training. When we design for education and training, the actual service might be a class, webinar, or workshop. However, the total experience of learning may involve much more than that.

Rather than assume your service starts at the moment people sit down (in person, at the computer etc..) go back to the start of their day.

Start with imagining a ‘user’ — be as specific as possible about this person with as much detail as you can provide that reflects a ‘typical’ or a particular (e.g., specific segment) service or product user.

Then ask: What happened the moment they woke up?

This question tells you a lot and invites other questions: Did they get a good sleep? What were the conditions that they slept in? What time did they wake up?

This matters because one of the assumptions behind your education and training service might be that people are attentive, able to listen and process the material, participate when necessary, and able to codify what’s learned into their brain and apply that later to whatever problem is at hand.

If you want your service to be useful, it needs to fit the circumstances of your user. If your participants didn’t sleep well, had to get up early to commute, are living in a state of fear or violence, or have no good place to sleep at all they are already facing some challenges before they start.

Continue the Story

The first question will lead you to a series of other questions that continue with: What happened next?

You continue this story as you progress through the day in the life of your participant up to and through the actual service event you’re involved in. After that? Continue the story through to the end of the day.

Along the way you will identify such things about your audience like:

  • Demographics
  • Social life and network
  • ‘Touchpoints’ with other systems and services
  • Preferences
  • Social and psychological circumstances.

These are imaginations of sorts based on what you think is a ‘typical user’. To increase the likelihood of reflecting the experience of a diversity of users it is best to conduct some background research to ensure you are reflecting the true characteristics of your audience. This method also works for identifying qualities about non-typical or non-users to help you understand why they might not use or desire your product or service.

Putting it into Practice

This exercise is best done as a group and can be conducted within 2 hours comfortably with more time for more granular exploration. It is meant to be participatory, engaging and allow for some creative reflection.

Materials include:

  • Whiteboards or large flipchart paper
  • Markers
  • Sticky notes
  • Stickers (optional)

Over the course of a morning or afternoon, you can bring your team into a place of greater understanding of your users — current and potential — and help set the context for your service. If we consider our example of education and training, the lessons we learn from this might be that we break programming into different chunks, change the distribution model, provide additional or alternative means to access content, or perhaps follow-up with reminders and tips to aid memory or application.

This simple, engaging and powerful method will help you tell better stories about your product or service and those of the people you wish to influence and serve.

A Day in the Life is one of the methods that we teach as part of the Design Loft Experience pop-up held as part of the annual American Evaluation Association annual conference each year. It’s one of many methods we use to help our clients understand the bigger picture and gain new insights into their work. Want help implementing it? Contact us — this is what we do.