Differentiate conversation starters for first versus repeat viewings¶
Strategy · All strategies
Evidence · no claims cited
Description¶
A strategy in which conversation starters are designed as two series: one for a first viewing to contextualize the science content through the episode narrative, and another for repeat viewings to focus more heavily on science ideas and invite science discourse. The team created "one series of prompts was created for the first viewing and another set for subsequent (repeat) viewings" so that prompts over time reinforced more complex core ideas and practices.
Design Implications¶
Context¶
Requirements¶
- Knowledge of which viewing scenario a family is in
- Prompts for before, during, and after viewing
Constraints¶
- Families did not always use the starters in the way they were initially designed
- Before prompts were hard to use because families lacked episode context, and were ultimately removed
Target Learners¶
- Parents and caregivers co-viewing science media with young children
Target Learning Goals¶
- Deepening science discourse across repeated viewings
Related Strategies¶
Examples¶
-
Key Sources¶
- Digital Promise, The Jim Henson Company, Concord Evaluation Group, & Curious Media. (2021). Designing an app to support families' joint engagement with media: Design principles and lessons from research. [White Paper]. Digital Promise. https://doi.org/10.51388/20.500.12265/121
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
differentiate-starters-first-repeat-viewings |
title |
Differentiate conversation starters for first versus repeat viewings |
description |
A strategy in which conversation starters are designed as two series: one for a first viewing to contextualize the science content through the episode narrative, and another for repeat viewings to focus more heavily o... |
status |
review |
generated |
by process:wiki-ingest on 2026-10-09 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — digital-promise-2021 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.