COMMUNITY-BASED, HUMAN-CENTERED DESIGN

(Don Norman & Eli Spencer)

We propose a radical change in design from experts designing for people to people designing for themselves. In the traditional approach, experts study, design, and implement solutions for the people of the world. Instead, we propose that we leverage the creativity within the communities of the world to solve their own problems: This is community-driven design, taking full advantage of the fact that it is the people in communities who best understand their problems and the impediments and affordances that impede and support change. Experts become facilitators, by mentoring and providing tools, toolkits, workshops, and support.

The principles of human-centered design have proven to be effective and productive. However, its approach is generally used in situations where professionals determine the needs of the target populations and then develop products and procedures to address the needs. This is Top-Down design: starting with higher-level conceptualizations and then refining the ideas and concepts to specific instances of products or services. This works well for mass produced items which only allows limited specialization for individual needs and requirements.

Although traditional methods are effective for traditional mass-produced items, they are unable to take account of the local needs, cultures, and history of individual people and communities. The literature on the world-wide aid community is filled with examples of well-intentioned “solutions” failing to work when introduced into developing nations (see (Easterly, 2013; Ramalingam, 2013). And if they do work at first, they are often so difficult to maintain and service, that they soon fall into disuse. Finally, in some cases the unintended negative consequences outweigh any good that has resulted. We believe that the people best equipped to address these issues are the people who live there: This article shows one approach.

In this brief note, we quickly review the four principles of human-centered design, the difficulties faced by the traditional top-down approach, and the proposed bottom-up, community-based approach. There are already multiple examples of the power of bottom-up design. We build on this work, especially on the proposal by Jeffrey Myerson that he calls “Scaling Down.” The fact that there are many instances of community-driven, down-scaled approaches validates these ideas. Among other activities, it would be valuable to bring together the many different approaches and communities so they can all share and learn from one another, yielding a powerful set of tools that can be freely adopted and used by people around the world.

The Four Principles of Human-Centered Design

1.   Understand and Address the Core Problems. Solve the fundamental, underlying issues, not the symptoms.

2.   People-Centered. People-centered as opposed to technology-centered, ensuring that the outcome is appropriate for the history, culture, and environment

3.   Use an Activity-Centered Systems Approach. Design must focus upon the entire activity under consideration, not just isolated components. Moreover, activities do not exist in isolation: They are components of complex sociotechnical systems.

4.   Rapid Iterations of Prototyping and Testing. Start with simple prototypes, perhaps simply drawings illustrating the idea, and then after testing, refine and enhance the capabilities through successive iterations.

Myerson’s “Scaling Down” approach

Jeremy Meyerson, from London’s Royal College of Art has proposed a closely related approach (Myerson, 2016): “Scaling Down.” Here is his description:

The growth model of the 20th century required that designers and companies achieve economies of scale. Scaling up involved abstraction to make large-scale production possible for the global industrial economy. In the 21st century, social challenges are increasingly disrupting world markets. This changes the focus of the design process. Designers once needed to learn just a little about large groups of people to serve mass markets. Today, they must learn a great deal about relatively small numbers of people. They must shift from concentrating on what makes groups of people similar to what makes them different.

Myerson proposed five principles of scaling down. They complement the approach in this paper by being very similar in spirt, but from a slightly different perspective, introducing slightly different concepts. 

The Limitations of Community-Based Design

Community-based design has several major weaknesses: local knowledge about a complex topic can be incomplete or even erroneous. Moreover, even if an excellent solution to the local problem, the solutions tend to be for the symptoms, not the underlying causes and are, moreover, local, and therefore only one small part of what is invariably a larger, much more complex system. This results in two difficulties. First, solving the symptoms does not get at the underlying causes, so problems will continue to arise. Second, even if the local issues are completely solved, local optimization does not always lead to global optimization. Here is where expert advice, mentoring, and facilitation is needed. The community-based design should still be the driving force, but informed and aided by a deeper understanding of the overall system.

Combining Expert Knowledge with Local, Community-Driven Design

Designs must confront several major complexities when applied to the large, complex, needs of the world. These complexities are of special importance to the application of Human-Centered Design. Three areas are of special note:

A.   Large complex, sociotechnical systems. When major political, economic, social and cultural variables interact, it is best to proceed slowly, with incremental, opportunistic steps (See Norman & Stappers, 2016).

B.   The need for understanding. Modern automated technology can provide powerful answers, but its operations is often impenetrable (opaque) to both experts and affected citizens. This reduces faith and trust in the results. We need systems that provide understandable explanations.

C.   Cultural sensitivity. The results must be sensitive to history, culture, and belief structures. This means that technologists and domain specialists are not enough: the local communities have to be involved in determining the outcomes.

Myerson discusses another way expert knowledge can be used to enhance the ideas derived from community-based approaches:

“for many design projects—mass-market healthcare innovations or software introductions, for example—scaling up is a perfectly desirable course of action. On the other hand, some community-focused projects merit a reversal of tradition. They have a complexity that defies standard, off-the-shelf solutions. And once designers scale these kinds of projects down to create and test a specific proposal, they can then see what works and explore ways to take the key ingredients and “scale back up” to help other communities and individuals.”

The drive toward community-based design methods does not imply that experts are not needed. Rather, it points out the need to change the way that designing for the major social, economic, and educational, and health needs of the world’s population is carried out. These are all difficult issues which require the combination of approaches to solve. Experts provide the tools for analysis and for understanding. It will be experts that modify the opaque automation to make it a better fit to human understanding. These are top-down, conceptually-driven approaches. But then, it will be individual people and communities who understand their own cultures and environments who can best apply the knowledge of experts. This is a bottom-up, data-driven component. Both are needed. Each supplements and complements the other.

At the University of California, San Diego’s Design Lab we are working to build upon the creativity and abilities of the people themselves. In fact, most of the principles of Human-Centered Design are practices by those who do things for themselves. They understand their needs – the do not need experts to come in and tell them. They are solving the problems that they themselves face, as well as that of their families, relatives, neighbors and communities: they are obviously people-centered, for they are aimed at the needs and capabilities of themselves and their community. They understand the interactions of each thing they do with the local community and services: they are system based. And finally, they tinker, trying this approach and that, until they get something that works: rapid prototyping and iteration.

Authors:

Don Norman is the Director of the Design lab at UC San Diego and the author of the Design of Everyday Things, amongst many other books. Eli Spencer is a professor of medicine, builds things for global health, and directs the Center for Health at the Design Lab. Both like pizza and are worried about the state of the planet.

Acknowledgements

We have been influenced by the works of many colleagues. In particular, through multiple, lengthy conversations with Eliah-Aronoff Spencer, a UCSD Medical School (and Design Lab) faculty member with considerable experience in the developing world. This work was informed by and with Eric von Hippel of MIT, including his month-long visit to the UC San Diego Design lab. We also owe much to continual discussions with Design Lab members Steven Dow and Eric Hekler. And then through the writings of Ezio Manzini, Jeremy Myerson and, although we never met him, Victor Papanek (Manzini, 2015; Myerson, 2016; Papanek, 1971, 1984; von Hippel, 2005, 2017).

References

Easterly, W. (2013). The tyranny of experts : economists, dictators, and the forgotten rights of the poor. New York: Basic Books, a member of the Perseus Book Group.

Manzini, E. (2015). Design, when everybody designs: an introduction to design for social innovation. Cambridge, MA: The MIT Press.

Myerson, J. (2016). Scaling Down: Why Designers Need to Reverse Their Thinking. She Ji: The Journal of Design, Economics, and Innovation, 2(4), 288-299. doi:10.1016/j.sheji.2017.06.001

Norman, D., & Stappers, P. J. (2016). DesignX: Complex Sociotechnical Systems. She Ji: The Journal of Design, Economics, and Innovation, 1, 83-106.    

Papanek, V. J. (1971, 1984). Design for the real world: human ecology and social change (First edition, 1971: This is the 2nd, completely rev. ed.). New York: Van Nostrand Reinhold Co.    

Ramalingam, B. (2013). Aid on the edge of chaos : rethinking international cooperation in a complex world (1st ed.). Oxford: Oxford University Press.

von Hippel, E. (2005). Democratizing innovation. Cambridge, Mass.: MIT Press.

von Hippel, E. (2017). Free innovation. Cambridge, MA: The MIT Press.


We wish to help create a world-wide community, sharing procedures and results through powerful communication and learning tools, using whatever media are appropriate. This is the power of the mixed approach, building upon proven techniques in both the top-down and the bottom-up approaches. Experts provide the building materials, and build the communication structures. Local communities build upon these resources. A powerful combination.

Shashwata Agnihotri

UX, UI and Communication Design | Ex-PwC

4y

Rightly said sir, practices like participatory design and de-colonizing design are the need of the hour to achieve the right results when it comes to solving problems for more diverse and every changing paradigm of the society...with the advent of individualistic behaviours within society, the needs of specific groups are becoming more and more significant over the needs of larger more generic target groups...coming from India...I believe what we have here is a perfect situation for community based interventions...the sheer diversity and intricacy of the populace here makes it imperative to approach design practices from a more down scaled perspective...adding on to this...i think the need for agile and inclusive frameworks when it comes to problem solving should be the right way to go...design processes should be provided the flexibility and freedom to effectively encompass individual to community based problems.

Larry Marine

Veteran UX Researcher and Author of Disruptive Research

4y

Don Norman accurately captures the issue of the difficulty users have in understanding their problem. I believe a better way to characterize this is that users typically don't actually understand their problem, they just recognize that there is a problem and describe it by its symptoms. I'm not sure that we will grow beyond this in the foreseeable future, but that's not the only major hurdle to community-based HCD. Another hurdle that isn't mentioned here is that people are not that good at the analytical thinking of a problem to arrive at a real solution. I've made a career out of solving the problems not just the symptoms, often with extraordinary results. I've researched with 100's of designers and interviewed 1,000's of users, most all who were not very innovative when it came to describing or designing solutions. More often their approaches were just iterations on the current solutions. For instance, I've seen a number of enterprise designs that were simply an automated copy of a spreadsheet created years ago and never evolved. All they did was automate current frustrations. People all have unique capabilities, including some with a proclivity for innovative thinking that accurately solves a problem. Relying on a community of users (outside of the UCSD Design Lab) to all have that unique critical thinking ability is unrealistic. This is where the design expert plays an important role and will probably never be replaced by community-based design. A really good designer can look beyond the existing solutions and identify a new strategy that leapfrogs the current thinking and transcends the iterative nature of most solution approaches. The average person, not so much.

Marcos Teodoro 🏳️🌈

Product Manager | PM3 Ambassador

4y

I love your article! I just started study Service Design and UX and in all course the teachers said to focus on people. Thank you for sharing.

Like
Reply

Perhaps this could be called user-up vs designer-down?

Jung-Soo Choi

Design and Innovation

4y

great article Don! we are working with a great partner to address these sociotechincal system designs...

Like
Reply

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics