This document is work in progress.
A CaT is a tool to help facilitate the practice of Inclusive Design. It’s goal is to engage a “full diversity of potential users”, a key principle [Insights] in the practice of Inclusive Design, in the design process. In essence, a CaT is a diverse community of co-designers (or co-creators) brought together to contribute to the collective design of a system, product or service. Inclusive Design practices include: accessibility integration from the start, open work, a focus on functional needs and preferences, frequent testing, inclusive facilitation, design for adaptability and flexibility and design for uncertainty.
A CaT may also be considered as collective creativity or participatory design (Wikipedia page on Participatory Design), all of which are fundamentally a process that includes both the expertise of system/product/service designers/researchers and the situated expertise of users (those impacted by change to or creation of new systems, products and services). (Sanders and Stappers).
A CaT aims to create an environment that encourages input from diverse perspectives. “In keeping with the edict 'nothing about us without us', this principle is about including a diversity of people with a broad range of needs, preferences, interests and skills into the design process, and in so doing, weakening [blurring] the distinction [line] between user and designer.” source: https://guide.inclusivedesign.ca/insights/DiverseParticipationAndPerspectives.html
A CaT should encourage active involvement from users or potential users of the system, product or service being iterated upon—the key is to have involvement of a diversity of users, users whose needs aren’t met, users whose needs are constantly in flux; users whose insights are not available elsewhere because they do not fit into a construct of “average”.
CaTs can be applied at as many points as possible in the design process. To practice inclusive design there should be several touch points throughout a design process, and not simply at the beginning. To design inclusively it is important to review progress with and have input from a CaT community at multiple stages.
A CaT intends to:
Collecting, sorting and applying information generated at a CaT aims to maintain all individual contributions as important as the other. They are a collection of perspectives that contribute to robust and agile solutions rather than reductive practices of data analysis that contribute to a concept of an “average”.
Collecting and applying participant stories generated at a CaT should aim to maintain all individual contributions to be as important as the other. Participant stories are a collection of perspectives that can contribute to robust and agile design solutions. The structure of the CaT should be designed to facilitate individual story gathering and the preservation of individual stories by providing multiple opportunities to create, critique, reflect, and iterate. It is important to avoid reductive practices of information analysis; avoid distilling stories to a collection of averages and eliminating individual differences in favour of sameness.
Individual stories can help counter-balance personas.
Personas (behavioural models of potential stakeholders) are created by "considering the needs, interests and daily tasks of non-obvious or untraditional users helps a design team to think broadly and stay open to unpredicted uses of the systems they are creating". However, personas as sole user-representation can lead to stereotyping or the fictionalization of an non-traditional user. A CaT aims to counter-balance representations (like personas) with the the understanding that individual stories don't represent the voice of the user, they are the voice of the user. Therefore, participant stories are fundamental to the practices of co-design and inclusive design.
CaTs are “short term collaborations between small groups”, similar to a Hackathon (also refer to https://handbook.floeproject.org/InclusiveMakingAndHacking.html). A Hackathon commonly appeals to the "technical" end of the spectrum either by focusing on digitally-based design solutions or engineering physical artifacts. A CaT aims to be broader than a traditional Hackathon in that it encompasses all forms of design mediums (industrial, interior, graphic and digital) and seeks to generate ideas and stories that inform the shape of a solution rather than attempting to create a solution or an artifact.
When to consider using a CaT:
Goal: Use a CaT to help gather ideas, stories, perspectives that give you possible directions for further exploration.
Step 1: Define a broad problem space
Starting with an end goal in mind, create a broad problem space which encompasses your goal. We start with a broad problem space as it encourages creative thinking which may generate more robust solutions and new possibilities (serendipitous discovery and virtuous cycles). A more general problem space would also appeal to a broader audience which can give deeper insights into established demographics, or new insights into under served members.
For example, if you define your goal as to "increase museum gift shop receipts by 10%" and solicit solutions based on that scope, you may find solutions related to changing prices, or improving inventory. Also the study may attract only people retail experience. If the problem were defined more broadly as "discover why guests do not visit the museum gift shop", the ideas you get may be more interesting and useful for broader applications (i.e. "Strollers can not fit between the retail shelves" may lead to better accessibility throughout the facility). Also the broader problem space makes room for a larger demographic to participate.
The Energy Skate Park sim is a challenging sim because:
PhET Energy Skate Park Simulation
Sanders, Elizabeth B.-N, and Pieter Jan Stappers. Convivial Design Toolbox. Amsterdam: BIS, 2014. Print.!DIgeneral1234
Guide.inclusivedesign.ca. (2017). Welcome to The Inclusive Design Guide | Inclusive Design Guides. [online] Available at: https://guide.inclusivedesign.ca/index.html [Accessed 26 Sep. 2017].