Posted: May 18, 2012 | Author: Cameron D. Norman | Filed under: behaviour change, eHealth, health promotion, innovation, public health, Social media, systems thinking | Tags: complexity, creativity, design thinking, developmental design, developmental evaluation, eHealth, evaluation, Facebook, health, health promotion, healthcare, innovation, medicine, organizational change, organizational design, public health, Social media, systems thinking |

Social media is finally catching on with healthcare, public health, and health promotion. With a few recent articles published in the academic literature to rest on, academic health sciences has finally (and I might argue, begrudgingly) conceded that 900+ million users and $100B valuations (Facebook), and thousands of messages exchanged every milisecond (microblogs like Twitter and Sina Wiebo) might have some value for the public beyond entertainment.
If you note how long it took the health sector to start using the telephone as a serious means of engaging their patients or the public, this is lightning-quick adoption. Still, the barriers to adoption are high and the approach to using the technology is scattered. Indeed, just like the start of Internet-delivered telehealth (or cybermedicine (PDF), which has now evolved into eHealth), there is a mad rush to get liked, followed or some other metrics that most health professionals barely understand.
And that is part of the problem.
Meaningful Social Media Metrics
What is a meaningful metric for social media and health? A recently published article in Health Promotion Practice suggested four metrics that are taken from social marketing and applied to social media. These Key Performance Indicators (KPI’s) are:
- Insights (consumer feedback)
- Exposure (media impressions, visits, views, etc..)
- Reach (# people who connect to the social media application)
- Engagement (level of interaction with the content)
These are reasonable, but to to the uninitiated I would suggest a few words of caution and commentary to this list.
Firstly, the insights suggested by Neiger and colleagues “can be derived from practices such as sentiment analysis or data mining that uses algorithms to extract consumer attitudes and other perspectives on a particular topic” (p.162). While not incorrect, this makes the job sound relatively simple and it is not. Qualitative analysis + quantitative metrics such as those derived from data mining are key. Context counts immeasurably in social media use. It’s only in situations where social media is used as a broadcasting tool that gross measures of likes and sentiment analysis work with little qualification.
Even that is problematic. Counts of ‘likes’, ‘visits’, ‘follows’ and such are highly problematic and can be easily gamed. I am ‘followed’ on Twitter by people who have tens of thousands of followers, yet virtually no presence online. Most often they are from marketing fields where the standard practice is to always follow back those who follow you. Do this enough and pretty quickly you, too can have 23,000 followers and follow 20,000 more. This is meaningless from the perspective of developing relationships.
Engagement is the most meaningful of these metrics and the hardest to fully apply. This category gets us to consider the difference between “OMG! AWESOME!” and “That last post made me think of this situation [described here] and I suggest you read [reference] here for more” as comments. Without understanding the context in which these are made within the post, between posts (temporally and sequentially), and in relation to a larger social and informational context, simple text analysis won’t do.
Social Media Evidence: Problems and More Problems
One of the objections to the use of social media by some is that it is not evidence-based. To that extent I would largely agree that this is the case, but then we’ve been jumping out of airplanes with parachutes despite any randomized controlled trial to prove their worth.
Another article in Health Promotion Practice in 2011 highlights potential applications for social media and behaviour change without drawing on specific examples from the literature, but rather on theoretical and rhetorical arguments. An article published in the latest issue of Perspectives on Psychological Science highlights the current state of research on Facebook, which is timely given that its IPO is set for today. That review by Wilson and colleagues illustrates the largely descriptive nature of the field and offers some insight on to the motivation of Facebook users and their online activities, but rather little in what Facebook does to promote active change in individuals and communities when they leave the platform.
The answer to whether social media like platforms such as Facebook ‘work’ as methods of promoting change is simply: we don’t know.
Does social media provide support to people? Yes. Does it inform them? Yes to that too. Does that information produce something other than passive activity on the topic? We don’t know.
In order to answer these questions, health sciences professionals, evaluators, and tech developers need to consider not just followership, but leadership. In this respect, it means creating changes to the way we gather evidence, the tools and methods we use to analyse data, and the organizational structures necessary to support the kind of real-time, rapid cycle evaluation and developmental design work necessary to make programs and evidence relevant to a changing context.
As Facebook launches into its new role as a public company it is almost assured to be introducing new innovations at a rapid pace to ensure that investor expectations (which are enormous) are met. This means that today’s Facebook will not be next month’s. Having funding mechanisms, review and approval mechanisms, a staff trained and oriented to rapid response research, and an overall organizational support system for innovation is the key.
Right now, we are a long way from that. Hospitals are very large, risk averse organizations; public health units are not much different. They both operate in a command-and-control environment suited for complicated, not complex informational and social environments. Social media is largely within the latter.
Systems thinking, design thinking, developmental evaluation, creativity, networks and innovation: these are the keywords for health in the coming years. They are as author Eric Topol calls the dawning of the creative destruction of medicine.
The public is already using social media for health and now the time has come for health (care, promotion and protection) systems to get on board and make the changes necessary to join them.
Like this:
One blogger likes this post.
Posted: February 13, 2012 | Author: Cameron D. Norman | Filed under: behaviour change, complexity, design thinking, innovation, Systems science, systems thinking | Tags: AC4D, complexity, design, Jon Kolko, planning, strategy, systems thinking, wicked problems |

All Knotted Up...Like a Wicked Problem
Wicked problems are receiving a lot of attention these days giving much excitement to systems thinkers and designers alike. Yet what these problems mean for planning and understanding social programs and policies is not clear and may be even more wicked that it first appears.
I was excited to learn that Jon Kolko and his creative band of learners at the Austin Center for Design (AC4D) are coming out with a book on wicked problems. As one who studies and helps others to intervene in addressing such problems, this was like being a Star Trek fan learning that Leonard Nimoy was coming to speak at the Trekkie convention in my hometown. It is refreshing to see that the concept of the wicked problem is gaining traction beyond the small band of scholars and practitioners working at the intersection of complexity, systems and design thinking (which, admittedly is where many AC4D folk inhabit, but hopefully their audience will not).
But it’s not just one book. We are seeing transformations in education and science — with calls for a ‘new breed of scientist’ being created at places like Massey University in New Zealand — or spread through the news or business stories in various forms.
The concept of the wicked problem was originally posed by management science scholar and systems thinker C. West Churchman with planners Horst Rittel and Melvin Webber. The Wikipedia entry on wicked problems provides some examples of what these things are:
Classic examples of wicked problems include economic, environmental, and political issues. A problem whose solution requires a great number of people to change their mindsets and behavior is likely to be a wicked problem. Therefore, many standard examples of wicked problems come from the areas of public planning and policy. These include global climate change[4], natural hazards, healthcare, the AIDS epidemic, pandemic influenza, international drug trafficking, homeland security, nuclear weapons, and nuclear energy and waste.
In recent years, problems in many areas have been identified as exhibiting elements of wickedness – examples range from aspects of design decision making and knowledge management[5] to business strategy.[6]
As our social lives become more interconnected through the Internet, globalization, and mass migration, the complexity of the situations we find ourselves in grows. More of anything in diverse forms interacting together is likely to create complexity as new properties emerge and those properties change the trajectory of actions and reactions of the parts dynamically.
As one who is interested in wicked problems and works with people to address them, I should be thrilled to see the term used so widely. I am, but cautiously so. There is a risk that in the enthusiasm to embrace the lexicon of complexity that the meaning gets lost, which is what one gets from the hype cycle (See below).

The Hype Cycle: Coming to a Wicked Problem Near You?
The hype cycle is described as phenomonena initiated by a technology (or idea) and, once caught on, spikes the expectations beyond reason leading to discouragement, mass abandonment of the idea, and then — hopefully — a return to a level of reasonable return.
While the “cycle” (it is not a cycle) has limitations, the analogy here is well suited to fads of various types and the rapid ascension of the concept “wicked problem” in past years is indicative of a trend. Below are two representations of the amount of citations of the work “wicked problem” and “wicked problems” from Google’s Ngram service:

Wicked Problem Citations: 1950-2008

Wicked Problem(s) Citations: 1973-2008
It appears that wicked problems (plural) are increasing and reference to a single problem is staying the same.
Regardless, an upward trend is evident. What it means is another matter…
If wicked problems are becoming talked about more often and by more people, it is appropriate to ask what kind of impact that this new thinking will have on not only the way the problems are posed, but how people seek to address them.
To that end, it is worth envisioning the future with caution. One of the reasons for this is that wicked problems are often not wholly wicked in their composition or the strategy required to address the problem — which ironically makes these types of problems even more wicked.
This has to do with the interconnected, multidimensional, and embedded nature of the problems themselves which contain within them many interconnected non-wicked problems. I’ve started to see difficulties with organizations developing strategy that fails to consider this. It is, as I’ve discussed before, an artefact of either-or thinking. Tackling the kind of wicked problems like poverty, chronic disease, and global finance require a meta-level strategy that recognizes, shapes and adapts to complexity, while accounting for micro-level issues that are indeed, very linear and simple.
Finding, training and retaining the right talent to work with diverse communities on problems that are poorly supported or funded from many sources is wicked. The human resource needs for payroll, supply management, and field support might be much less so. Yet, both are joined-up and require strategies that can extend beyond traditional management and strategy, but also embrace some of the very ‘best practices’ that seem at the outset to be antithetical to complexity.
Just as I shake my head in frustration at seeing complexity dealt with using amplified linear strategies that ‘do the wrong things righter‘, I have surprised myself by how much I’ve been twitching at hearing recent converts to systems thinking rail against the traditional ways of planning as if anything other than seeing problems as complex would be wrong.
At issue is that wicked problems are made more so by having both complex and non-complex elements working together, requiring a level of strategy development that is far more sophisticated than many first thought. Even a review of the better management texts using complexity give short shrift to the relationship between the complex, the simple and the complicated working simultaneously in environments and how we plan for that. The Cynefin Framework provides a start, but just a start.
Until we recognize this complexity — no pun intended — in the way we plan, there is great risk of replicating the hype cycle when our sole use complexity-based models yield poor results of a different nature than the poor results we are seeing from traditional linear, reductionist thinking models applied to many of the problems we deem as wicked today.
Picture credits: A Close Up on Knotted Rope by Sundariel used under Creative Commons License from DeviantArt
Graph: Gartner Hype Cycle by Jeremy Kemp used under licence from Wikipedia.
Like this:
Be the first to like this post.
Posted: January 29, 2012 | Author: Cameron D. Norman | Filed under: complexity, design thinking, evaluation | Tags: complexity, design, design thinking, evaluation, George Miller, language, psychology, public relations, social change |

I (heart) PR
Complex concepts like evaluation, design and even complexity itself provide insight, strategies and applications that provide usable solutions to real-world problems, but also suffer from widespread misunderstandings, confusion and even derision. If they are to take hold beyond their initial communities of interest, they need to address their PR problem head on.
This past week was Design Week in Toronto. As one works extensively with design concepts and even has a health promotion-focused design studio, one couldn’t be faulted for thinking that this would be a big week for someone like me who lives and works in the city. Well, it came and went and I didn’t attend a single thing. The reason was partly due to timing and my schedule, but largely because the focus of the week was not really on design writ large, but rather interior design. Sure, there were a few events that focused on social issues (what I am interested in) like the Design With Dialogue session on Designing a Future for our Future, but mostly it was focused on one area of a large field.
And thus, interior design was left to represent all of design.
So why does this matter? It matters a lot because when people hear the term design, most of what was presented this week fits with that perception. The problem is that design is so much more than that. It is about making things, creative thinking and problem tackling (design thinking), social innovation, and responsive planning for complex situations. Architects, business leaders, military strategists, social service agencies and health promoters all engage in design. Indeed, Herbert Simon‘s oft-quoted and often contested definition fits nicely here:
Everyone designs who devises courses of action aimed at changing existing situations into preferred ones
If one accepts that we are all designers and all of what we create and use for change is design, than a week devoted to the topic should offer much more than innovative concepts in furniture or flooring. Yet, this high-concept style showcase is what most people think about when they first hear design. Give people a choice between a Philippe Stark Juicy Salif citrus juicer and creating a trades-based, social change curriculum for low-income kids such as the work by Emily Pilloton as the example of design and they will probably guess think Stark over Pilloton, when both are equally valid examples.
Evaluation (another area I focus my work on) is equally fraught with perception problems. If you want to raise someone’s blood pressure or heart rate, tell them that either they or their work will be the focus of an evaluation. Evaluation may be the longest four-letter word in the English language. Yet, tell someone that you have a strategy that can enable people to learn about what they do, its impact, and provide intelligence on ways to improve, adapt and outperform their competitors and you’ll find an inspired audience for evaluation services.
Lastly, complexity presents the same challenge. It’s very name — complexity — can make people shy away from it. As humans, we crave the simple in most things as it is easier to understand, manage and control. Complexity offers none of these things and, if anything, reveals how little control we have. Entire fields of inquiry have been established around complexity science and its related theories and practices. Complexity can help us make sense of why things don’t work as we think they ought to and allow us to better navigate through unpredictable terrain with greater resilience than if we tried to tackle such problems as if they were linear in their cause and consequence.
In all of these cases — design, evaluation and complexity — there exists a PR problem. The advantages that they pose are tremendous, yet these concepts are frequently misunderstood, dismissed, or inappropriately used . When this happens, it creates even greater distance between the potential benefits these concepts offer and their real-world application.
This distance is partly an artefact of poorly articulated definitions and examples, but also by design (no pun intended). There are those who relish having these concepts appear opaque to those outside of their social cluster. Thus, we have the ‘superstar designer’ who seeks to create products and personas that are built upon their rarity, rather than accessibility. There are evaluators who exploit the fear that people have of evaluation and lack the understanding of the methods and practices of evaluation (vs concepts like research or innovation consulting) to gain contracts and social influence within their field. Complexity, with its foundations in physics and systems biology, can appear to the layperson as otherworldly, making its practitioners and scientists seem all the more powerful and smart. These tactics benefit a small ‘elite’(?) number of professionals, while robbing a far larger audience of the potential benefits.
In 1969, then president of the American Psychological Association, George Miller, implored members to “give psychology away“. His message was that psychology was too important to be left just to the professional, graduate-trained practitioners to use. If psychology was to confer social benefits, it was necessary to ensure that everyone had access to it — it’s theories, methods, models and treatments. It is perhaps no surprise that psychology remains one of the most popular undergraduate degree programs in the arts and social sciences and the focus of television shows, magazines and and an array of services. Miller was commenting on the need to change a field that he perceived was becoming elitist and not serving the needs of society.
The same might be true of design, evaluation and complexity if we let it. It’s not a surprise that these three concepts are intimately tied together, as those training to apply design thinking and strategic foresight learn. Perhaps its time to start giving these ideas away, but to do so we first need to rehab their image and apply some design thinking and brand development strategy to all three ideas. As practitioners in any or all of these fields, giving away what we do by educating, reinforcing, and ensuring that the work we do is of the highest quality is a way to lead by example. None of us is likely to change things by ourselves, but together we can do wonders.
For those interested in evaluation, I suggest catching up on the AEA365 blog sponsored by the American Evaluation Association, where evaluation bloggers and practitioners share ideas about how to practice evaluation, but also how to communicate it to others. For those interested in design, I would encourage you to look at places like the Design Thinkers LinkedIn group, where practitioners from around the world discuss innovations and way to promote and apply design thinking. A similar group, and opportunity, exists with the Systems Thinking LinkedIn group or by joining the Plexus Institute, which does considerable work to promote complexity and systems thinking in North America.
Photo: I (Heart) PR by The Silfwer used under Creative Commons Licence from Flickr.
Like this:
Be the first to like this post.
Posted: January 23, 2012 | Author: Cameron D. Norman | Filed under: complexity, social systems | Tags: common sense, complexity, decision making, developmental design, Duncan Watts, evaluation, leadership, social networks, strategy, systems thinking |

Bye, Bye Common Sense
Great leaders are often ascribed traits that include ample common sense. But what passes for common sense is often a grab bag of miscellaneous, inconsistent ideas that are context dependent and less useful in the complex environments where leadership is called for most.
common sense |ˌkɑmən ˈsɛns|
noun
good sense and sound judgment in practical matters: use your common sense | [ as modifier ] : a common-sense approach.
Today Research in Motion announced that its founder Mike Lazaridis and his co-CEO Jim Balsillie would be relinquishing their roles with the company. In their place, a ‘pragmatic, operational-type guy ‘was installed. Presumably, Thorsten Heins has the common sense to lead RIM after the founders lost theirs. Yet, the pragmatic, common sense that RIM is looking for might not be what they need given the complexity of the environment they are leading in.
Common sense is a false lure in complex systems. In his recent book, Everything is Obvious *Once You Know the Answer, social network researcher and Yahoo! Research scientist Duncan Watts eloquently critiques the concept of common sense, illustrating dozens of times over how “common sense” doesn’t fare so well in decisions that go beyond the routine and into the complex. Indeed. the very definition of the term implies that the problems that common sense works towards addressing are relatively simple and pragmatic.
Certainly, navigating daily social conventions might lend itself well to what we might call common sense. Watts refers to sociologist Harry Collins’ term ‘collective tacit knowledge‘ that is encoded in social norms, customs and practices of a particular world to describe common sense. However, what becomes common is a byproduct of many small decisions, dynamic and flexible changes to perspective, an accumulation of knowledge gained from small experiments over time, and the application of all of this knowledge to particular, context-dependent, situations. This constellation of factors and its interdependent, contextual overlap is why artificial intelligence systems have such a difficult time mimicking human thought and action. It is this attention to context that is most worth noting for it is this context that keeps common sense from being anything but common:
Common sense…is not so much a worldview as a grab bag of logically inconsistent, often contradictory beliefs, each of which seems right at the time but carries no guarantee of being right any other time.
Watts goes on to argue:
Commonsense reasoning, therefore, does not suffer from a single overriding limitation but rather from a combination of limitations, all of which reinforce and even disguise one another. The net result is that common sense is wonderful at making sense of the world, but not necessarily at understanding it.
Thus, we often concoct a narrative about the way something happens that sounds plausible, rational and be completely wrong. Throughout the book, Watts shows how often mistakes are made based on this common sense approach to solving problems.
When it comes to RIM, some have pointed to the late Steve Jobs’ assertion that they would have difficulty catching up to firms like Apple given that the consumer market is not their strength, the enterprise market is. Yet, Steve Jobs didn’t let the fact that Apple was a computer company stop him from making music players (the iPod), mobile phones (the iPhone) or becoming book, music and movie vendors (iTunes). A read of Steve Jobs’ biography by Walter Isaacson reveals a man who was able to lead and be successful through what appeared to be common sense, yet was decidedly uncommon among media and technology leaders. That is why Apple is where it is and why so many other technology companies lag behind them or simply disappeared.
The reason is that common sense in leadership looks as simple in hindsight only, not in foresight or even in the present moment. This is one of the big points that Watts makes. He uses the example of Sony’s MiniDisc system that, when introduced, had all of the hallmark features of the innovations that Apple introduced (novel, high quality, portable, smaller, visible advantages over the alternatives), yet it was a spectacular failure. Canadian management consultant Michael Raynor has called this the strategy paradox. When qualities such as vision, bold leadership, and focused execution — all the commonsensical aspects of great leaders — are applied to organizations it can lead to great success (Steve Jobs and Apple) or resounding failures (RIM?).
Strategic flexibility, making small adjustments consistently, and imaging scenarios for the future in an ongoing manner are some of the potential ways to limit the damage from common sense (or use its advantages more fully). This requires feedback mechanisms and close monitoring of program activities, developmental evaluation, and a willingness to tweak programs and design on the go (what I call: developmental design) . It’s not a surprise that this incremental approach to development is consistent with the way change is best produced in a complex adaptive system.
By recognizing that common sense is less than common and is certainly not consistent, program designers, developers, evaluators and other professionals will be better positioned to provide true leadership that addresses challenges and complexity rather than adds to the complexity and creates more problems.
Photo: Goodbye to Common Sense Space by Amulet Dream from Deviant Art
Like this:
Be the first to like this post.
Posted: January 7, 2012 | Author: Cameron D. Norman | Filed under: complexity, design thinking, evaluation, Systems science, systems thinking | Tags: complexity, design, developmental design, developmental evaluation, evaluation, health, human services, Social media, systems thinking |

The Architecture of Complex Plans
Planning works well for linear systems, but often runs into difficulty when we encounter complexity. How do we make use of plans without putting too much faith in their anticipated outcome and still design for change and can developmental design and developmental evaluation be a solution?
It’s that time of year when most people are starting to feel the first pushback to their New Year’s Resolutions. That strict budget, the workout plan, the make-time-for-old-friends commitments are most likely encountering their first test. Part of the reasons is that most of us plan for linear activities, yet in reality most of these activities are complex and non-linear.
A couple interesting quotes about planning for complex environments:
No battle plan survives contact with the enemy – Colin Powell
In preparing for battle I have always found that plans are useless, but planning is indispensable – Dwight D. Eisenhower
Combat might be the quintessential complex system and both Gens Powell and Eisenhower knew about how to plan for it and what kind of limits planning had, yet it didn’t dissuade them from planning, acting and reacting. In war, the end result is what matters not whether the plan for battle went as outlined (although the costs and actions taken are not without scrutiny or concern). In human services, there is a disproportionate amount of concern about ‘getting it right’ and holding ourselves to account for how we got to our destination relative what happens at the destination itself.
Planning presents myriad challenges for those dealing with complex environments. Most of us, when we plan, expect things to go according to what we’ve set up. We develop programs to fit with this plan, set up evaluation models to assess the impact of this plan, and envisage entire strategies to support the delivery and full realization of this plan into action. For those working in social innovation, what is often realized falls short of what was outlined, which inevitably causes problems with funders and sponsors who expect a certain outcome.
Part of the problem is the mindset that shapes the planning process in the first place. Planning is designed largely around the cognitive rational approach to decision making (PDF), which is based on reductionist science and philosophy. Like the image above, a plan is often seen as a blueprint for laying out how a program or service is to unfold over time. Such models of outlining a strategy is quite suitable for building a physical structure like an office where everything from the materials to the machines used to put them together can be counted, measured and bound. This is much less relevant for services that involve interactions between autonomous agents who’s actions have influence on the outcome of that service and that result might vary from context to context as a consequence.
For evaluators, this is problematic because it reduces the control (and increases variance and ‘noise’) into models that are designed to reveal specific outcomes using particular tools. For program implementers, it is troublesome because rigid planning can drive actions away from where people are and for them into activities that might not be contextually appropriate due to some change in the system.
For this reason the twin concepts of developmental evaluation and developmental design require some attention. Developmental evaluation is a complexity-oriented approach to feedback generation and strategic learning that is intended for programs where there is a high degree of novelty and innovation. Programs where the evidence is low or non-existent, the context is shifting, and there are numerable strong and diverse influences are those where developmental evaluations are not only appropriate, but perhaps one of the only viable models of data collection and monitoring available.
Developmental design is a concept I’ve been working on as a reference to the need to incorporate ongoing design and re-design into programs even after they have been initially launched. Thus, a program evolves over time drawing in information from feedback gained through processes like evaluation to tweak its components to meet changing circumstances and needs. Rather than have a static program, a developmental design is one that systematically incorporates design thinking into the evolutionary fabric of the activities and decision making involved.
Both developmental design and evaluation work together to provide data required to allow program planners to constantly adapt their offerings to meet changing conditions, thus avoiding the problem of having outcomes becoming decoupled from program activities and working with complexity rather than against it. For example, developmental evaluation can determine what are the key attractors shaping program activities while developmental design can work with those attractors to amplify them or dampen them depending on the level of beneficial coherence they offer a program. In two joined processes we can acknowledge complexity while creating more realistic and responsive plans.
Such approaches to design and evaluation are not without contention to traditional practitioners, leaving questions about the integrity of the finished product (for design) and the robustness of the evaluation methods, but without alternative models that take complexity into account, we are simply left with bad planning instead of making it like Eisenhower wanted it to be: indispensable .
Like this:
Be the first to like this post.
Posted: December 5, 2011 | Author: Cameron D. Norman | Filed under: social systems, systems thinking | Tags: Annie Lennox, Aretha Franklin, complexity, design, design thinking, leadership, Rosie the Riveter, social innovation, wicked problems, women |

We Can Do It by J. Howard Miller
“The Sisters Are Doin’ It For Themselves” – Aretha Franklin & The Eurythmics
The old cliches of where a woman’s place ought to be have changed to mean: anywhere she wants to be. Women are poised to drive change in the age of complexity leading us all to consider why this might be the case and what we can learn from it.
There was a time when women repeated the line in graphic artist J. Howard Miller‘s famous piece: We Can Do It! Now, as Aretha and Annie sing, they are doing it for themselves…and in spades. The ‘it’ is leading and innovating in times of great complexity and change and not necessarily by role, but by action. When the challenges of ‘wicked problems‘ become great and pervasive, it is women not men who are stepping up to lead and that might have a lot to do with design. How?
Design and design thinking is fundamentally about strategies used to create, shape and influence. There are many definitions of the concept, but generally speaking it is about finding / clarifying problems at their root, framing them within a larger context, and addressing them using empathic methods. Quite often this involves intense engagement with the issue and those whom the issue most affects and these are areas where women are doing well.
Drawing on the growing literature base on design thinking and a series of ongoing interviews I have done as part of the Design Thinking Foundations project, there are three areas that sit at the core of this way of approaching problems. As it turns out, women are pretty good at all of them:
- Empathy. Getting to learn more about the person / people who are designing for / with by stepping into their shoes is a powerful vehicle for gaining insight into the nature of the problem at hand, its frames, and possible ways forward. Research looking at males and females consistently shows women expressing higher levels of emotional empathy than men (e.g, ). More recent work has begun to explore the ways in which women relate empathically to others, whereas men are more prone to what can be called Machevellian tendencies;
- Literacy. By this I refer to a constellation of skills that sit at the intersection of craft and knowledge to address a particular problem. A designer’s literacy most often includes creativity and the ability to analyze problems. These skills can fall within artistic realms, but also scientific and mathematical realms. Here in Canada, a recent report on the state of education finds that boys are lagging in literacy scores and, for the first time, science scores. They are tied with girls in math. The report (PDF-summary) adds greater weight to the shifting nature of boys and girls.
- Engagement. Designers — whether they are introverts or extroverts — need to be able to engage in diverse social situations in order to create useful products and services. Early work on online social networks is suggestive of this, building on a body of work looking at the strength of associations between gender, emotion and socialization (see 2010 chapter of the same name)
It used to be that women would express these three areas in social roles that were of lower status than men and generally following male leads (e.g., homemaker, assistant). However, the balance is starting to shift and women are no longer waiting for men to give things up, they are taking things for themselves. Indeed, women are becoming the new leaders and are designing themselves lives that will keep them in this position for the foreseeable future if indeed design is the new competitive advantage as has been suggested by Roger Martin at the Rotman School of Business in Toronto.
Lest we think this is isolated to Canada or the United States, the rise of women and girls is being seen globally. Earlier this year, the Economist explored how Asian women are marrying less and marrying later. One of the reasons is that they are no longer tied to men in the same way and are less willing to fill a role that sees them often as less than in their marriages. Indeed, Asian women are eschewing the practice altogether in rates never before seen and may be on the cusp of instilling deep and profound social change.
A lot of Asians are not marrying later. They are not marrying at all. Almost a third of Japanese women in their early 30s are unmarried; probably half of those will always be. Over one-fifth of Taiwanese women in their late 30s are single; most will never marry. In some places, rates of non-marriage are especially striking: in Bangkok, 20% of 40-44-year old women are not married; in Tokyo, 21%; among university graduates of that age in Singapore, 27%.(Economist, August 20, 2011)
One of the reasons is that women are more often placed in roles of great social complexity in the family/social sphere, yet without the power to make key decisions. This might mean child raising (often held as the ideal example of complexity), negotiating and planning social engagements, and doing much of the emotional maintenance in relationships. While these are not universal and suggestive of stereotype, there are libraries full of research that have found these roles tend to be persistent and consistent across most Western countries. Until now. These are also the kinds of skills that are needed in complex systems and to create means to navigate through them.
Women are no longer satisfied (nor should they be) with the roles assigned to them by men, but are shaping and crafting new ones for themselves and reclaiming and challenging outdated, sexist ones. A terrific example of this is the SlutWalk movement that started in Toronto in reaction to public statements by a police officer aimed at helping prevent rape that placed blame on victims, suggesting that women “stop dressing like sluts”. Here, women just took action and men followed.
As societies, we will (and do) need leaders and innovators who know how to manage complexity well and design solutions and women may be the first place to look because they are doing it already.
Like this:
One blogger likes this post.
Posted: November 19, 2011 | Author: Cameron D. Norman | Filed under: complexity, evaluation, innovation, systems thinking | Tags: complexity, developmental evaluation, emergence, Michael Quinn Patton, program evaluation, road trip, strategic learning, systems thinking |

Developmental evaluation (DE) is a problematic concept because it deals with a complex set of conditions and potential outcomes that differ from and challenge the orthodoxy in much of mainstream research and evaluation and makes it difficult to communicate. At a recent gathering of DE practitioners in Toronto, we were charged with coming up with an elevator pitch to describe DE to someone who wasn’t familiar with it; this is what I came up with.
Developmental evaluation is an approach to understanding the activities of a program operating in dynamic, novel environments with complex interactions. It focuses on innovation and strategic learning rather than standard outcomes and is as much a way of thinking about programs-in-context and the feedback they produce. The concept is an extension of Michael Quinn Patton’s original concept of Utilization Focused Evaluation with concepts gleaned from complexity science to account for the dynamism and novelty. While Utilization Focused Evaluation has a series of steps to follow (PDF), Developmental Evaluation is less prescriptive, which is both its strength and its challenge for describing it to people (things I’ve discussed in earlier posts).
So with that in mind, our group was charged with coming up with a way to explain DE to someone who is not familiar with it using anything we’d like — song, poetry, dance, slides, stories and beyond. While my colleague Dan chose to lead us all in song, I opted to go with a simple analogy by comparing DE to a hybrid of Trip Advisor and the classic Road Trip (due to lack of good vocalizing skills).

Trip Advisor has emerged as one of the most popular tools for travellers seeking advice on everything from hotel rooms to airlines to resorts and all the destinations along the way. Trip Advisor is averaging more than 13 million unique visitors per month and, unlike its competitors, focuses on user-generated content to support its service. Thus, your fellow travellers are the source of the recommendations not some professional travel agent or journalist. At its heart are stories of varies tones, detail and quality. People upload various accounts of their stay, chronicling even the most minute detail through photos, links to their blogs, video, and narrative. If you want to get the inside details on what a hotel is really like, check Trip Advisor and you’ll likely find it.
However, like any self-organizing set of ideas, the quality of the content will vary along with the level of reportage and the conclusions will be different depending on the context and experience of the person doing the reporting. For example, if you are a North American who is used to having even the most basic hotel chain offer a room with full-service linens, a bathroom, closet, desk and separate shower, you’ll have a hard time adjusting to something like EasyHotel in Europe.
The Road Trip part (capitalization intended here to denote something different than a regular trip by road), denotes the experience that comes from a journey with a desired destination, but not a pre-determined route and only a generalized timeline. A Road Trip is something that is more than just traveling from Point A to Point B, which is usually accomplished by taking the shortest route, the fastest route or a combination of the two; rather it is a journey. Movies like National Lampoon’s Vacation (and, European Vacation), Thelma and Louise, Harold & Kumar Go to White Castle, and (surprise!) Road Trip all capture this spirit to some effect. I suppose one might even find a more grim example of a Road Trip in the Lord of the Rings Trilogy or The Road.
Road Trips have a long history and are not just a North American phenomenon as this article from the Indian Newspaper, The Hindu reports in some detail:
“Road trips are fun when they are not planned point-to-point. As long as you have accommodation booked, that is enough. Its better not to have agendas; get as spontaneous and adventurous as you can. My friends and I went on a road trip to Goa last year. It was loads of fun as it was the first time we took off on our own without parents. To me, it was more than just a trip with friends. It showed that I could take care of myself and that I was now a grown-up, free to do what I wanted,” says Siddharth, who is doing his engineering.
The idea of spontaneity and adventure are part of the process, not an unexpected problem to be solved like in a traditional evaluation. Indeed, some of these unplanned and unusual departures are not only part of the learning, but essential to it. It is akin to what
Thor Muller describes as
planned serendipity; you might not know what is going to come, but it is possible to set the conditions up to increase the likelihood of and preparedness for moments of discovery and learning. This is like setting out on a journey with a
mindset of developmental and strategic learning to fit with what Louis Pasteur stated about discovery:
Chance favours the prepared mind
Thus, as Developmental Evaluators and program implementation leaders we are creating conditions to learn en route to a general destination, but without a clear path and an open mind towards what might unfold. This attention to the
emergence of new patterns and then the sensemaking to understand what these new patterns mean in the context to which they emerged and the goals, directions and resources that surround the discovery is a important facet of what separates Developmental Evaluation from other forms of evaluation and research.
So in describing DE to others, I proposed combining these two ideas of Trip Advisor and the Road Trip to create: Road Trip Advisor.

Road Trip Advisor for Developmental Evaluation
Road Trip Advisor would involve going on a journey that has a general destination, but with no single path to it. Along the way, the Developmental Evaluator would work with those taking the journey with him — likely the program staff, stakeholders and others interested in strategic learning and feedback — and systematically capture the decision points to take a particular path, the process that unfolded in making decisions, the outcomes or events connected to those decisions inasmuch as one can draw such linkages, and then continually dialogue with the program team about what she or he or they are seeing, sensing and experiencing. This includes what innovations are being produced.
Returning to the article on road tripping from The Hindu:
“Road-tripping is a great way to bond with the people you are travelling with and I would strongly recommend it to people. It not only makes you appreciate yourself as an individual but is an amazing experience as you get to meet new people, know different cultures and sample different cuisines. I can never forget biking on sleet, riding though torrential rains, gobbling hot rotis at dhabas, the beautiful snow-capped mountains and guy talk with friends on the trip,” says Dheeraj, who recently went to Ladakh.
Here the focus is on relationships, learning new things and taking that learning onward. That is what DE is all about. My colleague Remi illustrated this in our meeting by having us all spread out throughout the room and go through a pantomime-type skit where he collected information from each participant about where the wisdom was and then bringing this person along for the journey. So as he started out alone as the Developmental Evaluator, he wound up at the destination of wisdom with everyone.
Road Trip Advisor requires documenting the journey along the way, sharing what you learn with others, and continuing learning and revisiting your notes — while checking out what notes others have (including use of evidence from other projects and academic research) — and integrating that together on an ongoing basis.
But as my other colleagues pointed out in their presentations, the journey isn’t always about feeling good. Sometimes there are challenges as the Hindu article adds:
all is not hunky dory during these trips. You have to be way about accidents and mishaps. And, realise that freedom comes with responsibility. Says Arjun: “I had borrowed my friend’s bike for the trip, and though it looked good, it gave problems on the foothills of Kodaikanal and we couldn’t do the climb. Being a weekend, there were no mechanics. It helps to know your machine. A passion for road-tripping is not enough. You need to be equipped to take care of yourself also.”
Here, the story parallel is about being prepared. Know evaluation methods, know how to build and sustain relationships and to deal with conflict. A high tolerance for ambiguity and the flexibility to adapt is also important. Knowing a little about systems thinking and complexity doesn’t hurt either. Developmental evaluation is not healthy for those who need a high degree of predictability, are not flexible in their approach, and adhere to rigid timelines. Complex systems collapse under rigid boundary conditions and do evaluators working with such restrictions in developmental contexts.
So why do people do it? “Well, my memories of my favourite road trip were an injured leg, chocolates, beautiful photographs and a great sense of fulfilment,” recalls Arjun.
It is youngsters like these who have transformed road-tripping from just a hobby to an art.
After all, friendship and travel is a potent combination that you can’t say no to.
In DE, the “youngsters” are everyone. But as we (my DE colleagues) all pointed out: DE is fun. It is fun because we learn and grow and challenge ourselves and the programs that we are working with. It’s collaborative, instructive, and promotes a level of connection between people, programs and ideas that other methods of evaluation and learning are less effective at. DE is not for everyone or every program and Micheal Quinn Patton has pointed this out repeatedly. But for those programs where innovation, strategic learning and collaboration count, it is pretty good way to journey from where you are to where you want to go.
Like this:
Be the first to like this post.
Posted: September 10, 2011 | Author: Cameron D. Norman | Filed under: complexity, design thinking, Systems science, systems thinking | Tags: Andrea Yip, complexity, creativity, definition, design, design thinking, innovation, OCADU, Richard Buchanan, Roger Martin, strategic foresight, university |

Design Thinking?
Design thinking is a concept that has gained much purchase in the creative industries and beyond, but what does it mean and does it matter? Determining an answer to this question might mean the difference between advancing it further or ending the concept’s use altogether.
The Latin form of the question of “what is design thinking?”, quid nunc cogitat?, asks about what is design thinking now? It implies a sense that design thinking is a moveable, dynamic concept and might better illustrate its true nature than trying to develop a singular definition.
I’ve been struck by the concept of design thinking for some time and this week I began a two-year journey towards a Masters degree in design at OCAD University in Toronto where the concept will be placed at the centre of the curriculum. Perhaps not surprisingly, the first course of the program is Business and Design Thinking. This was the first week of classes and after spending a few days with my classmates it might be expected that this group of mid-career professionals interested in design thinking might have a clear idea of what it is that sits at the centre of their studies, but that hasn’t been the case.
Nor was it the case a few weeks ago at the Design Thinking unconference that I posted on earlier where people from across North America (and beyond) gathered to spend two days discussing the subject. It seems that no matter where I look, whatever books I read, the answer to the question of what is design thinking seems elusive. All these design thinkers and no definition to unite them.
The simplest answer to the question of what it is might be : it is what designers think about when they work.
And a designer might be: anyone who creates something with a conscious intent.
While these might suffice for cocktail parties, they are unsatisfying to those of us who seek to explore the concept of design thinking further than the hors d’oeuvre tray.
Among the best examples of what design thinking is about are conveyed through metaphors, like the Periodic Table of Design (twice!) or the design enzyme, both by social designer Andrea Yip. Roger Martin and others have considered design thinking to be a form of abductive reasoning around complex problem solving. Richard Buchanan suggests that this is the kind of thinking that is applied to wicked problems.
These examples either illustrate the concepts in specific terms or generalized ways of thinking, but do not in themselves provide a definition of design thinking. It seems we are very good at delineating the key elements of design thinking (Andrea Yip), the ways of approaching design problems (Roger Martin) or defining the types of problems that design thinking works best at addressing (see Richard Buchanan), but we are less good at saying what it is.
Perhaps we are left with the paradoxical answer and question posed by Faith No More
What is it? It’s it.
Sudhir Desai has argued that we need terms that have little or no prior meaning to define what design thinking is, lest we risk creating more confusion resulting from pre-conceptions like the words “design” (design what?) and “thinking” (isn’t it about ‘doing’ things too?). Taken further, this argument suggests that we will not find a suitable definition using the existing terms.
I am not so sure. There is another road to take. Consider DT’s close peer, systems thinking. Although not uncontested, many systems thinkers and scientists agree that systems thinking refers to a class of theories, methods and tools that address systems-level issues in a coherent manner. Complexity science, system dynamics, soft-systems methodologies, and cybernetics are among the fields that fall under the broader systems thinking rubric. This organization is best articulated in Michael Jackson’s 2003 book on Systems Thinking, cited in the Censemaking library.
Another good example (also in the library) is the work by evaluators Bob Williams and Richard Hummelbrunner on systems concepts in action. In this concise and articulate work, the authors illustrate the various concepts that fall within the larger realm of systems thinking in a manner that allows people to appreciate the breadth and depth of the concept and its multiple ways of understanding systems.
Design thinking may be ready to make the leap to this style of conceptualization. Rather than seek to kill the term and replace it with something else, as some have argued, perhaps its time to expand it while putting the effort forward towards articulating its components and the relations between them rather than seeking to come up with a gold-standard definition that suits everyone. The latter idea is one that has already suggested its doomed to fail.
Using this example, design thinking might be ripe to be re-defined as an umbrella term to support concepts like human factors design, plan-do-study-act approaches to change, and strategic foresight. Rather than design thinking be conceived of as a specific thing, it might be better off described as a set of things of which design and thinking are two of the central, unifying features.
Leaving my first full day of school, I walked a classmate to the subway and we discussed this fuzziness with the term and, prior to us parting said “it really is making things with some intent behind it, isn’t it?” to which the response was “yeah, pretty much “. Behind what seemed like a pat answer on both of our parts is a sense that we know design thinking is real and offers something of value that other concepts do not. That is the reason why the search for a definition is important and why this is not just an academic exercise in semantics, but a larger journey for understanding the role creativity plays in finding and addressing problematic issues and how we can better tackle them all.
So perhaps the new definition for design thinking now is: it is what creative people seek to find a definition for.
Like this:
2 bloggers like this post.
Posted: August 28, 2011 | Author: Cameron D. Norman | Filed under: complexity, design thinking | Tags: Andrea Yip, chemistry, complexity, design, developmental design, learning, science |

The Chemistry of Creation
There is a certain way in which things come together to create a successful design (or relationship) that is often chalked up to “chemistry”. But design chemistry could mean something both literal and evolving just like biological organisms if we take the concept to its fullest.
Metaphors are commonly used in tackling complex problems. The uniqueness of the situation, the level of detail of the manner by which the influencing factors coalesce, and the multidisciplinary ways of seeing the problem in the first place all present a problem of language, thus using oblique comparators can often fill the gap.
Science and mathematics have the advantage of being closer to ‘universal’ languages than many of the other forms of communication we share as a species (Leibniz’s ideas notwithstanding). They are less (not completely) influenced by cultural variations and local differences and can be shared globally. It is for this reason that the the prospect for a means of communicating concepts like design through science has appeal. As Andrea Yip has pointed out, design itself can be transformed into chemistry using the periodic table as a guide to serve as a more universal metaphor for understanding the way design thinking is experienced and practiced.
Chemistry is the study and creation of the bonds of the universe. More specifically, it is:
the science of matter, especially its properties, structure, composition, behavior, reactions, interactions and the changes it undergoes.
As a metaphor for design thinking it works beautifully. Through the Periodic Table of Design Thinking we see an attempt to lay out the properties of design thinking, map out the structure and explain their composition. Through practice and reflection we will see how these compounds play out in the design process.
Another scientific metaphor that takes up the charge from where chemistry leaves off is from developmental biology:
the study of the process by which organisms grow and develop
In the case of this metaphor, design thinking is the organism. Just as an organism, made of chemical compounds interacting over time, evolves, so too does the design process and the thinking that comes with it. In this case, metaphors like those proposed by Ms Yip and the concept of developmental design fit harmoniously.
Designing for and with complexity requires attention to a dynamism that can be lost if one takes the approach that product development happens at only stage of its life cycle. For many products this might be appropriate, but it falls short when we describe social design issues such as creating policies or social programs such as those found in health and education. I’ve referred to this concept as developmental design. Developmental design, like developmental evaluation, implies an evolved, dynamic approach to generating knowledge or outcomes and while I only loosely conceived of it in a way that matched developmental biology, it may be time to revisit that more intently. Designing developmentally means working through the design process on an ongoing basis, like perpetual beta in the software industry. It means evolving strategies for adaptation rather than solving problems because true solutions to wicked problems are often more dream than reality.
Taking the chemistry metaphor, it means that the ingredients, dosage and combinatorial mixes change over time in the production of a new compound or design. They may require catalysts — such as the inclusion of new perspectives or a particular discipline — to provoke certain reactions and move ideas into new space. It may also involve the same type of intervention from the designer to bring these chemicals to life. The chemist is not removed from her creation.
All of these are metaphors, yet they provide us with a means of taking the messiness of the language, something discussed in previous posts, to a new place until we can find the language that is most appropriate. Until that time, science might offer one of the better means of conveying design, complexity and the creativity that comes when we apply them both to generating products and services.
Photo Chemistry! by matfred used under Creative Commons Licence from Flickr.
Like this:
Be the first to like this post.
Posted: August 21, 2011 | Author: Cameron D. Norman | Filed under: design thinking | Tags: complexity, design thinking, innovation, language, unconference, Vancouver, wicked problems |

Reflections on the Language and Process of Design Thinking
From August 19-20th, dozens of design-oriented people from different backgrounds came together in Vancouver to meet and discuss the concept of design thinking: its meaning, its application, and its future. These are some reflections on what I took away from the two day event.
Design thinking is becoming a hot topic — or term — and while there are those who argue that it has jumped the shark (i.e., outshone its utility and over-reached — see Bruce Nussbaum’s thoughts on this) the past two days showed how clearly this is not the case.
A cluster of passionate people from various worlds of design, architecture, education, business consulting and even public health came together to listen to examples of how design thinking is being applied and conceived of (day 1) and work through the issues in small discussion through an unconference (day 2).
Throughout the two days a few patterns emerged from the Design Thinking Unconference 2011, which I will summarize here.
1. The language of design thinking is ripe for evolution. Bruce Nussbaum aside, there has been much written on the concern with the term “design thinking”, most notably that it focuses on thought and cognition and not action, which is what design is also about. Rather than re-ignite this discussion, a more interesting turn was initiated by Sudhir Desai, an innovation strategist based in Cambridge, MA, who noted the problem of using terms that were intended for something else to mean what we mean with design thinking. Quoting the work of Management scholar and pracititioner Dave Snowden (of Cognitive Edge):
We cannot use the same words to describe our solution with those used to define the problem
Through his brief presentation on Friday and the unconference session he convened Saturday, Sudhir succeeded in inspiring dialogue on whether we need a new term altogether — something that might not even be one that we know of at present. Terms like ‘innovation’ and ‘creativity’ were thrown out, but they met with criticisms and a sense of dissatisfaction. No viable term was proposed, but the seeds for a contemplative discussion on what that should be, whether we need one, and what the challenges of language are for design thinkers was made clear.
2. Design thinking and design tools are not the same thing. Another strong theme was a railing against the popular held notion that design thinking is all about what it does. This is another twist on the argument about design + thinking, but one that instead focuses on the way of approaching problems, not just the tools to solve them. Although there was much interest in tools and strategies, there was also agreement that design thinking is about practice, a way of approaching problems, and manners by which tools and strategies bring them together as a whole, not as a series of parts.
Which brings me to the next point…
3. Design thinking is (very often) systems thinking. This is something I noted even if it wasn’t made as prominently explicit among the discussions. Design thinkers might be one of the best groups I’ve been associated with at systems thinking; that is part of what they do. Whether it was something about this group or something about the discussions that took place, there was a real, palpable sense of looking to the past, the present and future of any design project and exploring the wider system of where design takes place. On Friday, Trevor Boddy, a Vancouver urbanist and author (PDF), took a group out on a walking tour of the city to show how the landscape was changed and transformed over time through a series of successive steps and interconnected actors and policies. This way of seeing Vancouver permeated through the ways in which the attendees saw their issues as part of systems, not just isolated activities.
4. Context is everything/designers have to be excellent listeners. The resistance to the idea that there is a recipe — something that many attendees voiced wanting to get at the start of the two-day event — for design thinking was made visible and loud. Context counts more than almost anything else and designers cannot succeed with cookbook strategies to generate solutions to design problems. Context, context, context was plastered all over the place during the summary session yesterday after the unconference.
At the same time, there was a quieter, but equally powerful push for designers to be good — indeed great — listeners.
The need for design thinkers to engage in deep, contemplative listening was something that permeated a lot of the sessions at the unconference that I was a part of (and not necessarily because I brought it up). The challenges and ironies associated with deeper listening were also noted as many noted that there is such a push, particularly for those working in corporate environments, to do more and do it faster instead of slow down and think. To this end, I am reminded of the work of Ezio Manzini and his push towards a culture of slow in support of sustainable social innovation and the work of the Centre for Contemplative Mind in Society who work to promote mindfulness in academia and education.
As we wish to speed innovation, sometimes slowing down is the way to go faster.
5. Design thinking is best done visually. Visual communication — sketching, digital rendering, mock-ups, art in various forms — was presented repeatedly as a means of conveying the complexity of the information that is often generated from tackling the problems design is called on to address (see below). Thankfully, a room filled with creatives generated a lot of visual media to support ideation and synthesis. Sketching on notepads and craft paper, model building (literally, with fruit and food sometimes!), and graphical presentations featured prominently in the conference; not by design, but by necessity. Building on the points raised earlier, it was evident how challenging our current language is in describing design problems and situations. I’ve elaborated on this in previous posts, but these two days only served to strengthen my conviction that we need more creative means of expression introduced into our work and people who can render ideas in visual forms on our teams.
6. Design thinking is wicked. The conference began with a discussion of the wicked problems that designers are frequently employed to tackle and over two days it was obvious that not only are the problems wicked, so too are the design thinkers involved in those problems. By wicked the reference is to a set of conditions that are unstable, non-directional, dynamic, context-sensitive, and in need of diverse, coordinated, flexible responses. This is design thinking to a tee.
To paraphrase the great Winston Churchill:
This is not the beginning of the end, but the end of the beginning.
Much more will come in the months ahead and the networks forged and extended because of this event, for which I am grateful for the opportunity to attend, will advance and so too will the ideas for what is design thinking. For readers interested in engaging in this discussion and learning more, check out the Design Thinking LinkedIn group that is the hub and the source for this entire two-day event.
Like this:
Be the first to like this post.