1-Pager
Back to Plan
Knowledge/Skill Building

📊 Message Frames and Prototype Tests

Gather and organize original data Analyze and interpret data Build models, prototypes, or action plans Identify an issue or design challenge Develop as a multilingual Engage in discussion Plan an investigation or test a design individually and c... Design, evaluate, and/or refine a solution to a complex r... Humanity faces major global challenges today, such as the... Evaluate competing design solutions to a real-world probl... 6.3.12.GeoGI.1 Compare and evaluate competing arguments or design soluti... Product Core Content Community Partners Essential Question Critique and Revision Submission Required

Students receive just-in-time modeling on turning outbreak data into persuasive visuals and converting user needs into testable prototype features. Teams build one campaign or policy mockup with a graph, rate, or trend line and one low-fidelity device prototype using paper, cardboard, tape, labels, or digital wireframe tools. They also write a short test plan that identifies variables, predicted user response, and what evidence will count as success.

Plan day
Day 14
Duration
80 min
Grouping
Small Group
Steps
6 steps

Lesson plan

6 steps · 80 min
# What teachers do
1 Launch the work session by naming the deliverables for today: one campaign or policy message mockup with a graph, rate, or trend line; one low-fidelity infection-prevention prototype; and one short test plan. Model 2-3 examples of strong message frames that turn outbreak data into a clear claim for a target audience, and model how to turn a user need into a testable prototype feature with a variable and success measure. (12 min)
2 Have teams revisit yesterday’s concept sprint notes and quickly decide which audience, problem, and design challenge they will focus on today. Ask them to list criteria and constraints for both products, including clarity, accessibility, cost, usability, trust, and language access, and to note one lesson from the Black Death comparison that should shape their decisions. (10 min)
3 Guide teams to draft their message frame. They select one data display, write a headline or claim, add one evidence statement using outbreak data, and include bilingual or multilingual wording, labels, or icons where appropriate for the intended audience. Circulate to push teams to justify why their graph type best matches the message they want users to understand. (16 min)
4 Move teams into rapid prototype building. They create one low-fidelity device prototype using paper, cardboard, tape, labels, or a digital wireframe tool, making visible at least 2-3 features that respond to infection-control needs and user constraints. Prompt teams to label features and note tradeoffs such as protection versus comfort or effectiveness versus cost. (18 min)
5 Facilitate a structured prototype and message test planning block. Teams write a short test plan that names what they are testing, the variable they may change, the predicted user response, the evidence they will collect, how they will keep the test fair, and what will count as success. Have them include at least one question they want a nurse, epidemiologist, or infection-control specialist to answer later. (12 min)
6 Run a quick peer test cycle in pairs of teams. One team presents its message mockup and prototype while the other acts as target users and leaves brief response-card feedback focused on clarity, trust, accessibility, and practicality. Teams capture observations, organize feedback, and identify one revision they will make before the next gallery walk. (12 min)
Preparation (10 items)
  • Prepare a visible agenda with the three required outputs for the day and the step timings.
  • Gather low-fidelity prototyping materials such as paper, cardboard, index cards, tape, scissors, markers, sticky notes, labels, rulers, and optional devices for digital wireframes.
  • Prepare a short modeling set with 2-3 sample message frames that include a headline, graph or trend line, evidence statement, and audience-specific call to action.
  • Prepare a short modeling example of a prototype feature translated into a test plan with variable, predicted response, evidence to collect, and success criteria.
  • Print or post team planning tools for criteria and constraints, including clarity, accessibility, cost, usability, ethics, trust, and language access.
  • Provide teams with access to their outbreak datasets, Black Death comparison notes, prior concept sprint materials, and any clinic/community concern notes from earlier in the project.
  • Create response cards for the peer test cycle with prompts such as 'What was immediately clear?', 'What data evidence was convincing?', 'What might confuse or exclude a user?', and 'What feature seems most useful or least practical?'.
  • Prepare a concise test-plan template with fields for test question, variable, control considerations, predicted user response, evidence to collect, and success indicators.
  • Set up tables or stations so teams can build, test, and display drafts efficiently without losing transition time.
  • Pre-identify sentence stems and vocabulary supports for multilingual messaging, feedback, and discussion, including optional Spanish terms or bilingual labels connected to public health and prevention.
Student-facing instructions
Today you will turn your team’s idea into something visible and testable. Your task is to create three things: 1) a campaign or policy mockup that uses at least one graph, rate, or trend line to communicate a prevention message, 2) a low-fidelity prototype of a product that could reduce infection spread, and 3) a short test plan for one of your drafts. You will use your outbreak research, your Black Death comparison, and your notes about community needs to make design choices. Start by agreeing on your audience, the specific problem you are trying to solve, and your criteria and constraints. Then build your message frame with a clear headline, one key data display, and language or visuals that make the message accessible to your intended users. Next, build your device prototype using the provided materials or a digital wireframe tool, and label the features so another person can understand how it works. After that, write a test plan that identifies what you are testing, which variable you might change, what response you predict from users, what evidence you will collect, and what will count as success. During the peer test, you will present your drafts, gather response-card feedback, and record at least one revision you will make before the next gallery walk.