SubjectNest resource library

Development draft · local review needed

Day 89 · Who designs a familiar handoff?Foundation Design Tech · T2 W17–18 · Day 89 lesson

Prepare this lesson

Foundation / Design And Technologies / Term 2 / Weeks 17 18

Part of the full two-week lesson sequence. Check the pack guide and taught point before teaching.

Open for this lesson: Pack guide · Sources and materials · Worked swaps · Fresh learner checks · Aids and text routes.

Download full sequence

Teacher copy: This page may include teaching prompts or answer keys. Answer keys in this public library can be viewed by anyone. Give learners a clean prompt, use checks as formative evidence, and change a case locally when prior access matters.

Learner choices

Target/codes: Identify a person-designed familiar product/service feature when genuinely observed, and its user purpose; AC9TDEFK01 and AC9TDEFP01, local-source conditional.

  1. Welcome · 3 min. Some classrooms use a real folder, message book or request system. None is supplied as a real example in this pack.
  2. Notice source · 4 min. Show blank local source slot. Fill it only with a school-approved actual item and provenance; otherwise stay with the fictional paired cards.
  3. Model · 5 min. “A person designed this feature to help a user pass/find a message.” If no real item, frame that sentence as a possible purpose, not an observation. A folder never substitutes for an authorised school reply.
  4. Child design talk · 7 min. Child identifies a feature and who might use it, compares it with their chosen folder idea, and asks one question they would need to check. If a genuine item is observed, record date, location/permission and exact child-seen feature privately.
  5. Check/respond · 4 min. Record source type, feature, intended user and unknown. If fictional practice becomes a claim about actual school procedure, ask who provided the real source.
  6. Exit · 2 min. “A person may design ___ to help ; I know/need to check .”