Cense

Innovation to Impact

Innovation Talent Inventories

by

Faced with a situation or opportunity that demands you try something new or change what your organization does, the type of knowledge, skills, and experience required is often different than what is used to maintain the status quo. One of the most overlooked places to look for this talent is right under our noses — or beaks — and that your birds of a feather might be closer together than you knew.

An innovation talent inventory is an exercise that organizations are advised to undertake every 6-12 months (depending on the level of dynamism within the organization and industry) to assess the talent within your organization.

Why an Inventory?

Talent acquisition and retention is a costly part of organizational development. Hiring staff often means looking at a variety of skills, yet may only enlist a few of them for a specific job. Over time it becomes easy to lose track of or forget that your team may have skills and experiences that can be brought to bear on your current project.

The process of undertaking an inventory is also a means of recognizing and reminding your team of who is on it. By looking at your staff through the lens of innovation, it’s also possible to identify attributes that were not germane at hiring or recruitment but have evolved into a need at the present day. Whether its a certification course, extra-mural activities like coaching sports, or experience working in a particular sector, these previously non-recognized experiences can now serve to support your team’s innovation project.

Undertaking an Inventory

There is no prescriptive means of undertaking an inventory and we recommend the following:

Informal interviews. Simple coffee-time conversations can make a big difference and have the added benefit of allowing your team to build trust and commitment to the innovation project in the process. Toronto-based software firm Freshbooks encourages their team to go on ‘blind dates’ (not real ones) over coffee with staff in other departments so that they can learn from each other. Informality allows for conversations to wander to different parts of a persons’ career that might have been previously unexplored.

Resume reviews. Whether it is looking over your team’s personnel files or LinkedIn pages (all with permission and consent of your team, of course), a review of the current set of listed skills, experiences and certifications can jog your memory about what talent your team already has. Being transparent about why you’re doing this and ensuring that any exploration is done solely for the purpose of the innovation talent inventory is essential. This can be a powerful means for team and trust-building if done right and harmful if done poorly.

Surveys. A simple exploratory survey asking individuals to identify skills and abilities (less about knowledge) can catalogue your teams’ ideas and suggestions. The one risk with this approach is that many staff might still see themselves in their current role and frame their responses according to that. Like with the interviews, focusing on a person’s journey rather than their current destination is key.

Visual Mapping. Another fun and informative strategy is to use visual maps where individuals either self-plot or are plotted on a map of the situation. Plotting out the needs, wants, and opportunities on a simple large-sheet of paper and then having individuals place themselves closest to where they fit related to those needs, wants, and opportunities can be highly participatory. This works by having the page posted on a wall in a common area for a few days (e.g., coffee room) or using an electronic tool such as Miro or Mural.

Together, you will find yourself and your team learning much from what you already have and putting underused or unknown talents to work to help take your idea forward. You’ll know so much more about what you already know (and didn’t realize).

Need help putting this together? Contact us and we can show you how to engage your team and learn more, together, to set yourself for innovation, by design.

Innovation Implementation Index

by

What does it truly mean to say that you are an innovative organization? One of the simplest, most powerful measures is implementation. How many innovative initiatives have you launched and put into the world?

There are arguments why the QWERTY keyboard is inferior to other designs, but there’s no argument that its the best innovation we’ve ever had when it comes to typing. Why? It’s the one that was implemented into practice.

Success Marks

Checkmarks on a list usually imply some kind of rote behaviour that isn’t suitable for innovation, although checklists themselves are useful for quality control. We prefer the idea of ‘success marks’ which indicate that an idea has been successfully taken from concept and put into practice — whether or not it yields desired outcomes.

As an index, we propose the following six metrics:

  1. The number of new initiatives that have been implemented into practice
  2. The number of projects that have developed prototypes that have been tested
  3. The prototype ‘death rate’: divide the number of terminated prototypes by the total number of prototypes developed
  4. The number of prototypes moved into implementation (* which is a similar, but not necessarily the same number as #1)
  5. The number of new initiatives started:
  6. The initiative death rate: divide the number of ‘new’ projects started by the number of projects implemented

Number 1 is the most important of all of these.

The reason we count all six as part of an index is that each of these represents some form of concerted action and effort toward moving ideas out of concept into action with the lowest number (Number 1) representing the highest value to the organization.

While having ideas is a precursor to prototypes we don’t we count this because it is easy to game this metric.

We also don’t believe in coming up with metrics about innovation or even prototype quality because the success of implementation and the quality of the prototype don’t always match. You can implement an idea that is still in development, yet still has value that can be realized right away.

Want to show how innovative you are? Consider scoring yourself on these metrics to see how much of what your organization does is talk and how much of it is action.

Want to move ideas into action? We can help. And we can develop the metrics to show what kind of impact your innovation has in the world. Let us show you how.

Forecasting

by

You might not have a crystal ball, but you can still envision the near-future by using a simple strategy called forecasting to plot your strategy for the coming months. Here is how.

Fundamentals

A forecast is a data-driven prediction of possible outcomes that can be used to generate scenarios. The first item required is data. This can be qualitative, quantitative, or mixed and from primary or secondary sources. Most often, forecasts are a combination of these.

Checklists have been found to be useful tools to help organize data that contribute to forecasts. Pull together those sources you have and then organize them in a manner that allows you to build a narrative — a story — of what has happened to allow you to better anticipate what might happen.

Forecasts work when there is some expectation of a linear progression from time to time (with some variation). Time series data — data gathered on the same topic/issue/item multiple times over in succession — is among the most popular sources of data. This will allow you to see patterns and spot trends that lead you to now.

Add Imagination

Once you’ve developed a model of the present situation, the next stage is to imagine what might happen in the near future. Forecasts are generally useful for predicting near-term (e.g., 3-, 6-, or 12-months) outcomes and are less useful for longer-term assessments.

Next match data from other sources — social trends, government policy documents, census data — to create scenarios. For example, seasonal trends can change the near term. ‘Seasons’ like ‘back-to-school’, holidays, flu trends, weather changes can all affect how present data can mislead us for future activities. The COVID-19 pandemic provided an example of the various ways in which an economy can re-open, a healthcare system can respond, and what ‘back-to-school’ looks like.

From these data points, work together as a team (this is always better done in groups because different people will see data differently) we can start to envision possible futures and outcomes.

Look for amplifiers and dampeners. What things might make an existing trend more pronounced and what might dampen that trend, or extinguish it altogether. In discussion as a group you can

Structuring Forecasts: Tips & Tricks

Begin your group work together with a few simple ‘rules’ to guide your discussion. Start with limiting any feedback or critique of ideas at the start. You want to explore why something could happen, not assess the likelihood of such activities at first. This opens our minds up to unlikely scenarios.

It’s helpful to have someone on the team who can play the role of the ‘black hat‘ – the person whose role is to illustrate why something won’t work. Edward DeBono’s ‘thinking style’ roles can be useful here in helping us structure a way to look at the data and ideas from different points of view. Building on these different perspectives, it’s important to build a variety of scenarios and attach a level of anticipated likelhood to them. (e.g., high, medium, or low) and timing (e.g., imminent, soon, long-term, etc..)

Build out as many scenarios as the data suggests might be useful. This is often three to five, but rarely nine or ten.

From these scenarios, ‘walk them back’ to the present using an approach of asking “what happened just before X” and repeating that of each answer until you find yourself at the present. This allows you to start building pathways of potential causality.

While it may be that none of the scenarios come into reality, there are likely to be pathways that resemble them. When you find these, your team can use those to examine the assumptions that you hold with each one of them and use that to develop a strategy around them to better increase your anticipatory awareness and adaptive capacity to learn and act.

Taken together, this method can help you to see what might be coming and plan accordingly. It is a powerful means to explore near futures and design your organization to be better suited to living in them rather than having to play catch-up.

To go even deeper, the Future Today Institute has developed this useful ‘Funnel’ model to guide forecasting that might be useful to you as well.

FTI-Funnel ToolDownload

If you want to develop forecasts, contact us. We can help you see what might be coming and design your team to better meet it.

Camera Work and Cultural Probes

by

Gathering insights about how people live, work, socialize and experience their world is one of the principal challenges facing innovators, design researchers or those looking to do design-driven evaluation. It’s easy to forget that most of us have access to a powerful tool for data gathering on our phone or in the body of a camera.

Camera work can be a great means for capturing social life and patterns. Whether it is through using a process like Photovoice or using it as part of an array of data gathering tools, cameras are often forgotten when we think about how to learn from our users. Let’s look at one way we can use cameras to support understanding our users’ context better: The cultural probe.

The Probe

A camera (or phone camera), notebook, and instructions are all that’s needed for your prospective users to turn their lives into an anthropological adventure. This method is user-focused and meant to involve your prospective users taking pictures and notes and thoughts about what they are recording. The instructions are tied mostly to the basics of photography (e.g., consideration of light, framing, and ethics of taking pictures of others, in certain settings, etc.).

Instructions can also focus participants’ attention on specific things. For example, you may wish to have your participants focus on a topic, setting, context, interaction, or situation — anything you want to learn more about. Keeping it too general is often not a good idea and can be anxiety- or confusion-provoking in your participants. If they are too specific, you might lose some of the creative possibilities.

The probe part of this method is the ‘thing’ you want your participants to focus on. The cultural part comes from what context, framing, explanation, or interpretation participants (and others) bring to the photos.

Interpretation & Expression

What makes the cultural probe method useful is that it allows for a guided activity that has a standard format while producing artifacts — pictures — that delve into the uniqueness of your users’ lives.

What participants choose to take pictures of can be instructive. It provides an opportunity to discuss why something was included and why other things might not be.

What context the photos were taken is also helpful as it indicates priorities, habits, situations, or choices that the participant makes.

Photographs provide a means to ask questions about what is in the pictures, how things are framed, and what kind of reflections are made by participants from the photos.

This method can also be used in group settings where people agree ahead of time (with the right to withdraw agreement, of course) to share some of the photos they take. It can be useful in times of conflict or ambiguity when participants themselves aren’t sure what is going on and collective sensemaking is needed.

The camera is a powerful tool. Its insights can help us design services and products better, create and learn more from people, and provide a means of qualitative evaluation data, too.

We love this method. If you want help using cameras as a storytelling, design, or evaluation tool contact us and we can help you along.

After-Action Review: Learning Together Through Complexity

by

Complexity science is the study of how systems behave when under conditions of high dynamism (change) and instability due to the number, sequencing, and organization of actors, relationships, and outcomes. Complex systems pose difficulty drawing clear lessons because the relationship between causes and consequences are rarely straightforward. To illustrate, consider how having one child provides only loose guidance on how to parent a second, third or fourth child: there’s no template.

An After-Action Review is one such way to learn from actions you take in a complex system to help shape what you do in the future and provide guidance on what steps should be taken next.

The After-Action Review (AAR) is a method of sensemaking and supporting organizational learning through shared narratives and group reflection once an action has been taken on a specific project aimed at producing a particular outcome — regardless of what happened. The method has been widely used in the US Military and has since been applied to many sectors. Too often our retrospective reviews happen only when things fail, but through examining any outcome we can better learn what works, when, how, and when our efforts produce certain outcomes.

Here’s what it is and how to use it.

Learning Together

An AAR is a social process aimed at illuminating causal connections between actions and outcomes. It is not about developing best practice, rather it is to create a shared narrative of a process from many different perspectives. It recognizes that we may engage in a shared event, but our experience and perceptions of that event might be different and within these differences lie the foundation for learning.

To do this well, you will need to have a facilitator and a note-taker. This also must be done in an environment that allows individuals to speak freely, frankly, and without any fear of negative reprisals — which is a culture that must be cultivated early and ahead of time. The aim isn’t to point blame, but to learn. The facilitator can be within the team or outside the team. The US Military has a process where the teams undertake their own self-facilitated AAR’s.

To begin, gather those individuals directly involved in a project together in close proximity to the ‘end’ (e.g., launch, delivery of the product, etc..). As a group, reflect on the following three question sets:

  1. The Objectives & Outcomes:
    • What was supposed to happen?
    • What actually happened?
    • Practice Notes: Notice whether there were discrepancies between perceptions of the objective in the first place and where there are differences in what people pay attention to, what value they ascribe to that activity (see below), and how events were sequenced.
  2. Positive, Negative, and Neutral Events:
    • What created benefit / what ‘worked’ ?
    • What created problems / what ‘didn’t ‘work’?
    • Practice notes: The reason for putting ‘work’ in quotes is that there may not be a clear line between the activities and outcomes or a pre-determined sense of what is expected and to what degree, particularly with innovations where there isn’t a best practice or benchmark. Note how people may differ on their view of what a success or failure might be.
  3. Future Steps:
    • What might we do next time?
    • Practice notes: This is where a good note-taker is helpful as it allows you to record what happens in the discussion and recommendations. The process should end with a commitment to bringing these lessons together to inform strategic actions going forward next time something similar is undertaken.

Implementing the Method

Building AAR’s into your organization will help foster a culture of learning if done with care, respect and a commitment to non-judgemental hearing and accepting of what is discussed in these gatherings.

The length of an AAR can be anywhere from a half-hour to a full-day (or more) depending on the topic, context, and scale of the project.

An AAR is something that is to be done without a preconceived assessment of what the outcome of the event is. This means suspending the judgement about whether the outcome was a ‘success’ or ‘failure’ until after the AAR is completed. What often happens is successes and ‘wins’ are found in even the most difficult situations while areas of improvement or threats can be uncovered even when everything appeared to work (see the NASA case studies with the Challenger and Columbia space shuttle disasters).

Implementing an AAR every time your team does something significant as part of its operations can help you create a culture of learning and trust in your organization and draw out far more value from your innovation if you implement this regularly.

If your team is looking to improve its learning and create more value from your innovation investments, contact us and we can support you in building AAR’s into your organization and learn more from complexity.