Five Ways Design Firms Fail at Innovation

I know HBR is about the success story, so we are all awkward when it comes to writign about failure, the focus of the special online issue. I wrote a book about organizational and product failure, in 2008, and was told by designers even in that golden year of failures that “fail doesn’t sell.”  But if we do not tell the truth, we anticipate and attend to the wrong issues that lead to failures.

I admire the work of design powerhouse Ziba. But I find Vossoughi’s recent HBR blog article leaves out half the story of the failure of clients to innovate. In Five Ways to Fail at Design, designers blame the client for not following our wisdom and messing up their chances at innovation.

It’s common to hear of companies hiring a creative consultancy, applying its recommendations, and yet at the end of the contract, seeing little or no return on investment. The majority of engagements that end this way have resulted in solutions that were never implemented, or were not implemented to their full potential. The design failed, in other words.

Yes, the client company must do the innovation, but still our expectation is that the design firm can successfully plan and design the innovation. If competitive innovation was achievable by hiring design firms, then innovation would no longer be a distinctive competency of a firm.  So yes, some firms fail because they are not inspired innovators.  But more fail because they are poor strategists, poor executors, or they fail to listen to their users and the evolving markets that users co-create.

And a case can be made that corporate-level design projects fail because of the design firms. And innovation – defined simply as bringing significantly novel products or services successfully to a crowded market – fails for reasons that design firms can often do nothing about. Maybe we should separate failure processes we can recognize and deal with from those organizational problems we cannot mitigate.

Vossoughi suggests five big reasons for the failure of design, which are all client-centered problems  (I have summarized and bolded the two I see as prevalent):

  1. Refuse to change any other part of your business.
  2. Design outside of your innovation space. Designers don’t implement solutions, companies do. For that reason, the most innovative solution on earth won’t work if it’s pursued by a company that can’t properly execute it. At Ziba we call this capability the client’s “innovation space” — the arena in which they’ve already proven themselves willing and able to lead the pack. Some companies are technology innovators, others are product innovators or experience innovators. Learning which you are in order to direct later efforts is a crucial first step that most companies skip.
  3. Try to design for everybody. Design works as a differentiator because it responds to human needs, both functional and emotional.
  4. Insist on replicating another company’s success.
  5. Compartmentalize design into isolated tasks. It’s tempting to treat design as a menu of services, applying it here and there on bits of a project that need sprucing up. To a skeptical client this can feel economical and controlled, but it cripples the design effort by fragmentation

Now let’s consider how design firms fail. Those 5 assumptions show an astonishing lack of reflection on the part of designers, which often fail at planning and appropriately delivering what a client really needs. Let’s have some empathy for the businesses we consult for. As a small firm designer/researcher I work closely with client projects, and see the results of Big Firm Big Ideas that cannot be realized in reality. Here are my 5, OK 6 ways:

  1. The big firms drive up a large project to justify their reputation and send an oversized team in early to scope out a large chunk of “innovation space.”  What’s often needed is an early phase of research that helps the client understand the opportunity first to do a better job of planning.
  2. The big firms know they get one shot, and may not get to return for some time. So generative design if often done too early, to produce concepts to win over the client. Weak design research is done to prove the concepts. A better process is where a good opportunity is discovered early, and the right concept gets validated later with a stronger, contextual concept design.
  3. The big firms are not known for their social sciences and user research. You get to see these reports after a while, and the quality is highly variable. They don’t know the client’s business well enough to recruit good users, and they focus on Big Ideas and not the user’s work practices, which lead to understanding what products and services might break through the market noise.Most projects are not disruptive innovation, but every product manager likes to imagine his or her product will be the one. Its fun to design “as if” the product will be disruptive, but how often does a company really get that opportunity?
  4. Ziba is right about compartmentalized tasks. But to “design big” beyond the brief, a firm needs to be a real business partner with the client, and to care about the project for a year or so to integrate the design into the systems and processes. This is way beyond product design, it means prototyping, building and field testing multiple versions, a boring and high-cost process for big firms.
  5. Big Design Firms never send you their A Team. Its like a rule. They send a guru in to present and win the project, then staff the project with whoever needs the coverage. Or maybe those are just the projects I’ve seen …
  6. But the bottom line is few big firms really have specialized knowledge about the business and users and do not have the time or mandate to learn on the job. They use intuition and design experience to aim high and reach for a great concept, and hope they capture the client’s imagination. But if big generalist design firms do not have depth in your business or the real work of your users, they may design poorly for the context.

Admittedly, it is a difficult balance. A good design team can push the client outside of their groupthink and conceive of much better products than possible with their own team. We can create the prototypes and architectures that establish a new system or product foundation.

A continuing weakness across the industry is the design and management of research appropriate to the innovation problem. Conducting interviews at a user’s desk is not “ethnography.”  Different stages of innovation each require a different toolkit.  Often both client and design firm are weak in user research or what passes for ethnography in most commercial studies. But without this crucial capability, design firms deliver what they only think they know, and clients don’t know what they don’t know.  Research overly constrained by client confirmation biases can study the wrong thing. But under-informed design teams that do not understand a user’s work domain can miss the weak signals that a trained observer would detect and correctly interpret. The designers can always claim they “did the research,” and clients rarely have the qualitative research expertise on staff to guide research effectively. If I had to pick one shared weakness of both design firms and clients that accounts for project failure, it would be lack of depth in research methods and interpretation.

What have you found to be the case?

Avoiding Informatics Overload

Mark Hurst posts on Good Experience the argument that information overload suppresses comprehension and creates an absence of understanding and retention: To solve info overload, make friends with The Nothing

In my experience this is true, and is moreover a testable proposition.  Mark says:

Because the only way to really make information disappear, these days, is to surround it by a sufficient amount of competing information.

Case in point is Side Effects? These Drugs Have a Few. Here the NYT references a Harvard study showing that there are, on average, 70 side effects listed on drug labels. Some labels contain over 500 side effects.

What would be the possible benefit of a drug maker listing over 500 side effects? Easy: it gives coverage in a liability lawsuit.

What’s clear is that the patient experience is harmed by these labels. Patients now know less about side effects than they did before. Sure, a drug might hypothetically bring about any of 500 side effects, but what are the few most common ones to look out for?

The drug label story teaches us that we have to change our perspective in the digital world. In a world full of information, the villain isn’t The Nothing – it’s actually The Everything.
Put another way, too many competing inputs are the same as not using the inputs at all:

In the digital world, information will find us. It’s inescapable, and if we’re not careful, The Everything will arrive and paralyze us. So the challenge is to find The Nothing, and make friends with it, to solve overload permanently. Let the bits go.

Electronic Medical Records (EMR) systems present too much information with too little context, overwhelming the attention and time of clinicians. Clinical Decision Support systems (for the most part) have poorly designed search and information navigation, requiring extensive parsing and disambiguation of similar topics and references. Online scientific research, too many papers, too little context.

My guess is that a power law function guides this relationship – similar to short term memory (7 +/2) there is a small number of objects that can be invariably retained as important, and each additional object adds load linearly, until the entire set of objects becomes useless.  Designers often limit the number of search hits to 10 per page in hopes that their relevance is sufficient to deliver a satisficing result in that priority view. I disagree with that practice, because good content and indexing is all. Since people naturally chunk information objects, we can repair context by effective clustering and visual support. But yes, as discrete information objects grow beyond (5-7), individual attention significantly degrades until the information set is truncated (cutting off everything after the first 5) or discarded (using a new resource). (These are presented as testable propositions, but are supported by my observations in UX and field research and enduring cognitive science studies).

Designing for Whole Systems & Services in Healthcare

We’re at CHI 2011 Vancouver, Tuesday May 10 for this Special Interest Group. Please join us if you’re at CHI!

Abstract

This CHI 2011 SIG provides a workshop for collective problem finding and community identification. The goal is to initiate a working group to coordinate systemic design research issues across practitioner communities. This SIG addresses the insufficiency of user-centered design and informatics research to design for system and service-level innovations in healthcare. The SIG seeks to coordinate communications and participation across design practice, research disciplines, and areas of health practice for service system innovation.

About:  The SIG addresses the problem of coordinating and advancing systems design and design research for service-level and systemic innovations in healthcare.

Healthcare is a domain characterized by multiple stakeholders (from consumers and patients to clinical staff, from administrators to insurers), multiple services (from primary care to academic institutional networks), and multiple sectors of services (from clinical practice to insurance and government). There are no definitive “users” in these complex systems of practice, few common workflows, and with highly dispersed informatics, no integration. The ability to design at the service and systems level is seriously mitigated by these inherent and ongoing issues.

The methodologies and analytical regimes associated with user-centered, experience, and service design practices are valuable in many contexts, but limit design options when employed for complex systems.  With a wide variety of stakeholders and differing clinical and economic problem owners, healthcare has no common voice and fewer “whole system” solutions. In practice, design and implementation decisions are fraught with competing interests, often imposing near-term decisionmaking on IT and practice changes. Design/research professionals are often isolated in narrow bands of problem scope, with the inability to design to root cause issues or to scale their successes across institutions or across practices.  Policy advocates and key advisors in the field are widely separated by problem scope (disease management, education, insurance reform)  and problem-solving modality (policy, practice innovation, patient-centered medicine, information systems).

The organizers call for a network of coordination of communications and participation across design practice and research disciplines, and areas of health practice. Informatics and service designers are natural integrators across fields of knowledge and practice, and are hampered in effective solutions when working in dedicated, narrow sectors of the field.  While it may not be necessary to form a new organization or group, the organizers see the opportunity for a working network that can begin to work across discourse communities, coordinate research and service prototypes, and integrate practice concepts, emerging findings and key stakeholders toward these concerns.

Full abstract online:  Healthcare Design SIG CHI11

Healthcare Experience Design: 4.11.11

The first Healthcare Experience Design conference, a one-day symposium held in Boston April 11, sold out with nearly 300 participants across all sectors and industries.  The program selected leading speakers and designers in four tracks of presentations:

  • Patient-Centric Design
  • Designing for Care: Provider Interfaces and Care Environments
  • Facilitating Engagement
  • New Models for Healthcare Delivery

Keynote speaker was BJ Fogg of Stanford’s Persuasive Technology Lab, with a physically interactive talk on designing for persuasion that required managing latex gloves, floss, and instructions prepared for hundreds of sealed envelopes.

Because things were organized in tracks, I was speaking in “Designing for Care” and missed Matthew Diamanti’s talk on People are the Product in the Patient-Centered Care track. I’m waiting for the videos to become available (soon) so we can see watch those presentations at leisure.

The symposium brought together designers and leaders across a wide range of healthcare sectors.  There is something new and inaugural about this meeting, like attending CHI for the first time in its early years.  This is just the start of something, big, as designers, researchers and institutions are starting to find new ways of creating health value for people and patients.

Healthcare spends millions on clinical and business technology, but health institutions continue to lag most other industries in innovative design and IT.  (However, this is not in itself a service problem – efficiencies in healthcare are not ever gained by IT alone). The need for service, process, and interaction innovation is clear, but now the desire to forge change is apparent at the leading institutions (Mayo, Cleveland Clinic, Kaiser, Sloan Kettering were all in attendance).

Some primary trends I’m seeing and the companies guiding those trends:

See all presentations and speakers

In Experience Design as Creative Care I raised these issues:

  • We (designers) are a new role in health institutions, and have a high credibility hurdle.
  • Earning trust takes time. Designers are still inexperienced in critical domain knowledge.
  • Our skills are tactical & not clinical (and not strategic, even if we think so.)  That will take time to change. We need to develop strong design research portfolios.
  • Our user-centered language is often irrelevant to doctors. (And who’s a “user” in healthcare?)
  • Always think: “How does (my) design help patients?”

What is Design for Care about?

  • Targeting design interventions to whole systems and services, not products and interfaces.
  • If the aim is improving patient experience and performance at the point of care, we need to rethink the service design and care flows for practitioners.
  • Think (IBM) service systems. Not users.
  • Designers need to patiently develop a shared language understood and effective in healthcare.
  • We (UX) need to start sharing design research & practices across sectors, centers, locations

Synergetics: Buckminster Fuller Revival

Southern Illinois University Carbondale recently held the Synergetics conference, a symposium revival of Buckminster Fuller’s work, faculty, and former students at his last major home institution. Invited speakers included former Design students and faculty Bill Lunderman (Colgate) and Larry Busch.

Invited speakers included me, Jennifer Rice (Fruitful Strategy),  and Steelcase’s Melissa DeSota.  Keynote was Thomas Zung, Fuller’s architect collaborator and archivist. This year they are also saving domes and putting a large one up at his former residence, and recovering his legacies. placing our current sustainability thinking in line with his lifelong dream of a world that works for everyone.

A slide in my talk  Collaborating for Complexity credits Fuller as the first philosopher of Thrivability, the reach beyond sustainability that we strive for in socially systemic innovation.

In Critical Path Fuller said:

“The success of all humanity can be accomplished only by a terrestrially comprehensive, technologically competent, design revolution. This revolution must develop artifacts where energy-use efficiency not only occasions the artifacts’ spontaneous adoption by humanity, but also occasions the inadvertent, unregretted abandonment and permanent obsolescence of socially and economically undesirable viewpoints, customs and practices.”

Fuller always pushed the boundaries of the possible and created the models and technology to  prove his points.  He would have been unimpressed with the progress we are collectively (not) making on global sustainability for human habitation, ecology, and economy.  The conference also engaged participants directly in cluster groups to work directly on product development sustainability exercises (rethinking emergency shelter, consumer electronics, and mobility). An exciting diversity of creative thinking was brought to the 2 half-day sessions, and as I left Friday afternoon the conference was still in full gear. The real treasure of a small engaged conference like this was the ability to really meeting and converse with people from so many other design backgrounds than mine.