SubjectNest resource library

Development draft · local review needed

Day 92 · Together or one step at a time?Foundation Design Tech · T2 W19–20 · Day 92 lesson

Prepare this lesson

Foundation / Design And Technologies / Term 2 / Weeks 19 20

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: Compare two human-designed prompt sequences for a named listener; AC9TDEFK01 and AC9TDEFP01, proposal only.

  1. Welcome · 3 min. A new listener wants to report a completed attempt without accidentally counting the interrupted one.
  2. Notice source · 4 min. Show ALL AT ONCE and ASK · CHECK · TELL. Both are untried service ideas; neither is automatically best for every user.
  3. Model · 5 min. ALL AT ONCE could let a confident reader scan everything; the sequence could help another reader pause at status. These are hypotheses about use, not measured outcomes.
  4. Child design talk · 7 min. Child gives one possible help and difficulty for each route, chooses one provisionally for a particular listener, and says what a real willing listener would need to do to check it.
  5. Check/respond · 4 min. Record both route features and user-linked reason. If “everyone needs the steps” appears, ask which listener and what exact feedback is missing. If the child equates completion with a farther mark, distinguish status from location.
  6. Exit · 2 min. “I would try ___ with ___ because ___.”