Module #1 draws from Competency 1:
The AI literacy paper defines competency #1 as a disambiguation task:
The paper points to the importance of providing definitions of AI to accomplish this competency:
Of course, the paper acknowledges the wide and often conflicting definitions of AI. Therefore, the designers should pick a definition that suits the format and context of the learning environment (which is what we have done). The module opens with a warm-up that allows the group to define AI. The goal of this ice-breaker is two-fold:
One key part of enabling people to recognizing AI highlighted in the paper is the importance of understanding intelligence:
The definition of intelligence depends on the approach and context:
Thus, much like with defining AI, how intelligence should be articulated will depend on the learning context and goals. The paper suggests the following approach explaining intelligence:
The current implementation follows this suggestion in several ways. First, the video contrasts human intelligence (e.g., baking) and artificial intelligence (e.g., Roomba; IBM Deep Blue). The video then pivots to critically and cautiously question the level of artificial intelligence necessary for more complex situations like hiring.
The activity builds upon the contrast of intelligence set-up in the video by framing algorithms as recipes and inviting participants to “cook up” an algorithm for soup. The activity employs a constructivist approach in how it leverages a familiar experience (cooking) as a scaffold towards engaging an unfamiliar experience (algorithm development) through social interactions (sharing and discussing the steps). By putting people in control of designing an algorithm and revealing the subjectivity of the design process, this activity is intended to provide the foundation for agency and a sense of closeness to AI. Specifically by simplifying the complexity algorithms as a form of “everyday intelligence” via cooking. Learners need to understand two points from this activity: they are performing a pseudo coding process that models the computational thinking of computer scientists; their “code” (like all code) is subjective, context and goal dependent.