1.3. Key Concepts (In-depth)

● Problem Scoping & Boundaries: Scoping defines what’s in/out of focus. Students will write a "Scope Statement" of no more than 100 words delineating the project’s limits.

Problem scoping is about clearly defining what a project will cover and what it will not. Students are tasked with writing a Scope Statement, which is a brief description (100 words maximum) that outlines the boundaries of their design project. This means they need to clarify which aspects of the project are included and which are excluded. For example, if a project involves creating an app for event sign-ups, the scope might focus only on the app's functionality and not on the marketing strategy. This clarity helps to avoid confusion and keeps the project focused.

Think of problem scoping like planning a road trip. Before setting out, you decide your starting point and destination. You may choose to avoid certain cities along the way because you want to save time or stick to a specific budget. In the same way, defining your project scope helps you know what parts of the task will be included and what parts you're choosing to leave out.

● Research Continuum: Plot methods along axes of depth vs. breadth. For instance, ethnographic fieldwork offers deep context but limited breadth; online polls offer breadth but less nuance.

The Research Continuum concept helps students understand different research methods in terms of depth and breadth of information. Depth refers to how detailed the information is. Ethnographic fieldwork, which involves observing and interacting with users in their environment, provides rich and detailed insights about behaviors and contexts. However, it might involve fewer participants, limiting the generalizability of findings (less breadth). On the other hand, online polls can reach a larger number of people quickly, offering a wide range of responses (more breadth) but typically lack the deep insights that qualitative methods provide. Students will learn to choose the right research method based on the type of information they need.

Consider a detective solving a case. If the detective interviews a suspect and observes their behavior in various scenarios, they gather deep insights but focus only on that one person (depth). Alternatively, if the detective sends out a survey to hundreds of people asking for observations about a location, they gather lots of data quickly but might miss nuanced details about specific individuals’ experiences (breadth). Both methods are valuable, but serve different purposes.

● Stakeholder Ecosystem: Map relationships among Clients (commissioners), End Users (primary users), Secondary Users (e.g., administrators), and Influencers (e.g., regulators, teachers). Identify at least two priorities per group.

Understanding the Stakeholder Ecosystem is crucial for successful design and implementation. This chunk teaches students to map out the various groups involved in or affected by their project. Clients are the ones paying for the project and have specific goals. End Users are the people who will use the product, while Secondary Users might be different groups that have a stake but are not the primary users, like administrators. Influencers can include people or organizations that impact the project, such as regulatory bodies or educators. Students should also list at least two priorities for each stakeholder group to ensure that their design considers all perspectives.

Think of a school production where different groups are involved: the principal (Client) who wants the play to be successful, the students (End Users) who will act, the teachers (Secondary Users) who will help with logistics, and parents (Influencers) who want to see their children succeed. Each of these groups has different priorities, like budget constraints for the principal, performance quality for students, and support resources for teachers. Mapping these relationships helps create a successful production that meets everyone's needs.

--