Cense

Innovation to Impact

Using Timelines To Track Activities

by

Just as parents will use pencil notches in a wall to track the height of their children as a developmental marker, so too can innovators and evaluators use timelines to help gather and track the development of programs and projects over time.

A timeline is a simple linear visual that gathers activities together that uses time as the variable of distinction.

What makes a timeline useful is that it provides a visual display of temporal relationships between events, activities and outcomes. It makes explicit what we might have in our heads, but are also prone to confusing and forgetting over time.

When to Use Timelines

Timelines are useful in a variety of situations:

  1. Projects with activities that can be organized into a sequence (whether planned or not). They are less useful for projects where there are many activities happening simultaneously.
  2. Projects with a long time horizon.
  3. Projects operating in an environment with many different levels of activities and influences. For example, when there are external factors like policy decisions that have discrete times attached to them and can influence a project’s course, this is a good use of a timeline.
  4. Projects that have a story to tell that involves a beginning, middle, and end.

A timeline can help provide anchors between project activities and events — whether those are policy-related, tied to human (or other) resource use, environmental disruptions, seasons, or cycles. They can help provide hypotheses between causes and consequences or explain mediators.

For example, one non-profit project we worked on had a planned roll-out that was moving along well until their funder abruptly cancelled the program that they relied on. This meant that the six-months after that announcement involved finding new sources of revenue, reductions in staffing, and changes in some activities, yet also persistence in trying to adapt to the situation and still execute the original plan. By showing the data on a timeline it helped explain what happened to project activities, outputs, and outcomes within a certain time period and how that related to the overall project plan.

Examples

Below is an example of a timeline that illustrates distinctive markers along the route. These are clearly defined events that took place on specific dates. The selection of events includes those deemed to be meaningful and significant to the project.

What makes a timeline a powerful tool is that there are many different ways to illustrate events. The example above is a relatively straightforward set of data.

Below is another example that involves much more data and in different forms. This example creates a hybrid of timeline and categorization exercise.

Creating Timelines

There are many templates and tools that can be used to help develop visual graphics. The examples above are from Lucidchart, however, tools like Miro, Mural, SmartDraw, PowerPoint, Google Draw, and many others have templates that can be modified to create useful timelines. These are all simple tools that can be manipulated easily so you’re able to build them as you go.

If you are looking to develop more sophisticated models, we suggest employing a visual communicator or graphic designer to take advantage of the many ways you can represent temporal data.

The result is something that is engaging and can easily be discussed or presented to diverse stakeholders involved in a project who might be able to validate, contribute to, or constructively challenge the arrangements. We find this to be a powerful way to organize our findings, refresh our memories, and recognize all of the activities that go into a project.

Documenting Innovation Development

Lastly, if you are developing an innovation where there is no clear ‘end’ known at the beginning, timelines are useful in telling the story of the project and documenting the different pivots, changes, adaptations, and their consequences. A timeline can be a powerful asset to Developmental Evaluation and a complement to the Living History Method that we often employ in those kinds of evaluations.

A timeline can honour all the work you put into coming up with your final product and can be an engaging way to get people involved in celebrating, documenting, and tracking what you do and create.

We use these all the time and can help you track and evaluate your project. Contact us and let’s talk about timelines, innovation and impact.

Evaluating Learning for Innovation

by

Learning is at the heart of innovation. Our definition of innovation is contingent upon it:

Learning transformed into value, by design

Traditional approaches to learning tend to focus on two things: recall and performance. Thus, we look at knowledge-based tests (consider most of what we took in grade school and college or university) or performance assessments (reviewed accomplishment on a specific task or problem set).

What is often absent from both of these is a consideration of the context and the learner themselves. It’s one thing to be exposed to information or demonstrations of how to do something, yet it’s entirely another thing to actually learn it.

Assessment of Learning: Questions to Ask

Our assessment of learning is inspired by this approach and informs the questions we ask about learning:

  • Exposure. What level of exposure did we have to the material or experience? How did this exposure treat our sense of understanding of the problem and the context? What salient information did we attend to during this exposure? How (or were) we attentive to what was presented to us and what was the context in which this was presented?
  • Connection. How is what we are exposed to related to what we’ve already experienced? In what ways does this new material fit with what we have previously learned? Where does this material or experience fit in shaping my goals, intentions, or general direction for myself or my organization?
  • Reinforcement. What activities allow me to apply what I’ve been exposed to in new ways and in practical ways repeatedly (including fitting with what I already know, whether a theory or practice-focused material)? What systems are in place to allow me to integrate what I’ve been exposed to into my current understanding of the situation? What activities have been set out to enable recall and re-visiting materials in the near and longer-term?
  • Application. What opportunities do I have to apply what I’ve learned into shaping a new understanding of a problem or steps toward addressing it? What opportunities are present to reflect and integrate this application of knowledge or skill into my existing repertoire of practice or understanding?

Without these, there is a decent chance we will undergo some form of performative learning — doing activities that look like learning but aren’t really effective. Taking workshops on topics that are not relevant to your work or set up too distant from the problems you’re seeking to tackle is one way. Filling your days with reading articles, watching webinars, taking courses, listening to podcasts, and viewing videos on some material without a means to organize and integrate that into your experience.

You will retain some, but probably not enough to warrant your time and energy. Furthermore, this kind of ‘filling’ of your attention actually serves to decrease the likelihood that you’re able to use this because of the sapping of energy from your brain. The more we expose ourselves to, the more energy is required and eventually we’ll be depleted enough that things won’t stick.

Ask yourself these questions above next time you’re looking to really, truly learn as an individual, team, or organization.

If you’re looking to learn more, do more with what you have, please contact us and we’d be happy to discuss ways we can help you be a better learner and innovator.

Better learning comes from better systems, by design. we can help you build them.

Activity Analysis

by

This simple technique is among the most powerful at eliciting a lot of information. When we look at an existing service, it may be easy to describe what people do to deliver, manage, and receive the service in simple terms. For example, an exchange between a bank teller and a client might be described as simply as a person walking up to a desk, asking for money, inserting their bank card, receiving money from the teller, and leaving.

An Activity Analysis would break this down even further. It would involve tracking the experience of the client. It would denote what the client did from the moment she entered the bank, what she saw, what she smelled or experienced, her feelings or thoughts, and the steps she took toward the desk.

You might ask how long she took, whether she stopped en route to the desk, knew where it was (did she ask for directions?) or did she wait in line and for how long.

We can also track what the teller was doing up to and including the moment of engagement with the client. What tasks was she doing? Where was her focus? What is she thinking or feeling?

This is a micro-method version of A Day in the Life, which is another method that helps us understand what our service clients do and use.

How to do it

Activity Analysis can be done as a group, facilitated by a leader to help organize and manage the activity. It’s a great way to get people talking about all that is going on with the actors, the environment, and the tasks. By opening up the discussion and walking through each step in the journey through the service with each actor, everything that shapes the environmental conditions, and the tasks that are performed, you’ll reveal an enormous amount of data about what actually transpires with even the simplest transaction.

This can be used to seed further questions like:

  • What infrastructure is needed to support the interaction?
  • What would be ideal?
  • How might this interaction look different?
  • What other variables could affect the journey and the outcome?
  • What could be done or introduced to make this better?

Activity analysis is something that can be done in small groups over the course of 20 to 60 minutes, depending on the complexity of the task and the amount of knowledge the participants have of the task or activity.

This simple analysis can reveal information about flows, resources, outcomes, and processes that are in place to support your service and help you see what’s not only in place, but what is possible, too.

This can be a great way to bring people together as well as lead your service design and evaluation efforts. If you want to implement this approach in your organization and need help, reach out to us. We’d welcome hearing from you.

Narration Interrogation

by

Police (and some parents) know the secret to spotting a lie in a story: ask someone to repeat that story backwards. As it turns out, it’s a lot easier to concoct a false story going forward than it is backward because of the way we logically connect events in our heads.

This same technique can be used to help spot gaps in logic. Even if we’re not lying to one other (or ourselves) we may find some parts of the story that don’t quite make sense. This gap in logic is not uncommon because as humans we often will fill in the story because of how we are wired for narrative coherence as a species.

Narrative interrogation is a way that we can walk through the story of our program or service to help us identify the key elements that are present in most good stories and how or whether we have them organized (or have them at all). Unlike real interrogation, this is not aggressive or adversarial — rather a way to explore stories through inquiry.

Story Elements

Some of the key elements in a good story are:

  1. Actors. These are your protagonists (the leads), the supports, and the chorus — those in the background. Ask yourself who the main actors are in each scene of the story (e.g., who has the problem that needs solving? What are they looking for? What is their motivation?). This is where using personas can be helpful to fill in the details about these characters.
  2. Relationships. How are the actors related to each other? Are they working collaboratively or competitively and do they need each other? Are there roles that individuals fill? Are there special qualities to their relationship (e.g., power, partnership, etc.).
  3. Setting and Structures. Where are things taking place? Do people need a particular service or product in a specific setting or context? Articulating these will also help you to frame the way in which system structures shape the interactions between the actors and help contribute to or facilitate the problem (or solutions).
  4. Time. Determining when things are to happen and how that temporal aspect shapes everything is important. Does timing matter? Does the amount of time matter? is the problem and solution one that is highly dependent on when something happens or not?
  5. Arc. The last piece is creating some form of coherent story arc between them all. Tying them together helps us understand who is involved, what they are interested in or seeking, why they have the challenges they do, how they are going about things now (and how we could change that with an intervention of a product or service) and the ways in which that will be affected.

Together, this starts to generate a theory of change and helps us connect what we’re seeking to do through our innovation (service, product, policy) and what is needed by those we are aiming to serve.

Using the Method

Stories are told by people, not objects, so this is one method where speaking with individuals is key. Involve those for whom the story matters in the telling of that story. This might be customers or clients, service operators, managers, or founders; it depends on what story you are looking to hear. The aim is usually not to capture everything, rather keep it focused on a specific aspect of your innovation. It might be in use (customers or clients), the development (product team) and marketing, or in understanding the purpose relative to the organization (e.g. senior management).

Using an open-ended approach — free-form — ask people to speak about the topic using a story lens:

  1. Start with the beginning: what is the first thing someone needs to know. This might be the choice to start the project, the moment the ‘problem’ appeared that required a solution, or even the backstory. This is something that the storyteller determines on their own.
  2. Focus. Encourage the person to speak in a manner that focuses on the purpose, however, ask points of clarification when it is unclear what the connection is at different parts. Good stories often involve non-sequiturs and so do poor ones; it’s important to know which one it is.
  3. Reflect back. Once the story is told, re-cap the logic of the story from front to back and
  4. Go backwards. This is the ‘interrogation’ part of sorts. Ask people to retell the story backward from the end. For example, ask what happened right before the conclusion of the story and then what happened before that and before that. It’s similar to the reverse of A Day in the Life method.

What you might find is that the story has different descriptors, relationships, or emphasis when told backward. These allow us to see different configurations of the issues that are associated with the story. It’s not that the person is necessarily lying or keeping anything from you, it’s about the limitations of narrative in that it only works with one set of issues connected logically at a time. Going backward allows us to see things differently, expanding our view.

The interviews and conversations with those involved should be informal and relaxed and can go into as much depth as you want. Generally, this is an approach that makes for a good ‘coffee conversation’ of about 30 minutes. It also can be done remotely, if necessary. It can be done internally by staff associated with the project or externally by an outsider. If the story involves highly sensitive subject matter or material, it is best to use an outsider to the project.

Learn more from your program, your people, and your work with this simple, powerful method for design exploration and research.

We help with storytelling through data. Contact us if you want to implement this with your organization.

Perspective Taking: The Power of Ten

by

Great innovators often see problems or solutions that others miss. This is as much about perception as it is anything else.

To illustrate the power of perception, consider the famous perceptual illusion below which profiles a young girl and an old woman (or “wife” and “mother in law”). The image, which dates back to 1888, shows how the same image can produce two very different stories about the subject matter.

There’s a way to create the same effect by looking at a situation through the lens of time. The Power of Ten is a perceptual forecasting and innovative technique that can help you can perspective on a situation, a product, or service by looking at the effects in layers, each offering a new possibility.

How to do it

The Power of Ten technique is simple. Take the current situation, topic, product, or service and forecast what might happen in ten minutes from now, ten hours, ten days, ten weeks, ten months, and ten years.

In some cases, you’ll find little effect or difference between the two and in others the differences are dramatic.

Consider waiting times for a service call. In that case, ten minutes might be a long time and ten hours is insufferable. If you are on a waitlist for an elective surgery, ten days might be incredibly fast, ten weeks reasonable, and ten months is anxiety producing.

What about a particular situation? Consider the dynamic situation that unfolded with the COVID-19 pandemic and policies that affected how and where we work. Time perception changed, value changed (e.g., Internet access), and certain things like parks, groceries, restaurants and bars, and video conference tools all changed their value in a matter of days, weeks, and months in different ways.

The Power of Ten activity is designed for you to forecast and spend some time thinking about what will something look like, feel like, interact with, and impact the world at each of these different scales.

This simple exercise will allow you to see constraints, opportunities, effects, and interactions that are either not present or imperceptible at one scale at other scales. This allows you to see connections between things that were not perceived before.

This is best done as a group and can be performed in a short time as a facilitated activity or at a distance.

If you want to see possible futures using this approach and want help, contact us. We can help you multiply your perspective by a power of ten.

Note: This exercise draws inspiration for a video first produced in the 1970s by the legendary design partnership of Charles and Rey Eames for IBM.