Keep the design provisional. A fictional interview note can support a classroom exercise, but it cannot become evidence that real visitors need the proposed solution.
Three original wayfinding notes
Fictional exercise inputs, not actual interviews or usability results:
| Note ID | Supplied note | What it supports |
|---|---|---|
| N1 | Visitors confuse Room A and Room B labels. | Investigate how the two labels are distinguished. |
| N2 | One visitor wants the letter readable at door height. | Consider letter visibility at the supplied placement. |
| N3 | The maintainer requires a removable paper-only prototype. | Preserve that material/removability constraint. |
An original need statement is “Help a visitor distinguish A from B at the door using a removable paper prototype.” Link it to N1-N3. Keep unanswered questions visible: Which label causes confusion? What does “readable” mean for the intended trial? What placement is approved for the prototype?
The TCEA design-thinking article emphasizes understanding users, questioning assumptions and reframing problems. This lesson uses original notes and materials; it does not reproduce its linked lesson-plan template or claim a real user study.
Compare two prototype options
Option 1: A removable paper label with one large room letter and the supplied room name underneath. It addresses N2 through letter prominence; its usefulness remains untested.
Option 2: A removable paper label with a large letter inside a distinct outlined shape, plus the same room name. The extra shape is a hypothesis about distinguishing labels, not a requirement established by N1.
Both must keep N3's paper/removability constraint. A permanently mounted sign would change the brief. Ask the group to name the note supporting each choice and label any unsupported addition assumption to test. Do not select Option 2 merely because it has more decoration.
A proposed 45-minute lesson
- Read notes, 6 minutes: Separate the three supplied inputs from assumptions.
- Frame need, 7 minutes: Write a bounded need with note IDs and unresolved questions.
- Ideate, 8 minutes: Sketch two original options and compare their evidence links.
- Prototype, 10 minutes: Prepare the teacher-authorized removable paper version.
- Trial plan and revision, 9 minutes: Write the user task and observation fields; discuss a proposed revision from labeled hypothetical feedback or actual evidence if available.
- Reflect, 5 minutes: Explain the need/design link and what still needs testing.
The total is 45 minutes. Actual trial records remain blank unless a trial occurs under the teacher's supplied arrangements.
Choose a trial that can change the design
An original task is “Using these prototypes at their approved locations, identify Room A and Room B.” Do not tell the participant which letter to read or describe the feature you hope will help before observing the task.
Use blank fields for prototype version, approved placement, task instruction, participant action observed, confusing point, and proposed change. Keep personal details out of the classroom example.
Hypothetical feedback: “Found A but missed B.” This supports investigating or revising B's clarity. It does not establish why B was missed or prove all visitors can find A. A specific proposed revision might make B's letter more prominent while keeping removable paper; record that as a hypothesis and say what another trial would check.
Copy a note-linked design lesson brief
Create one complete, self-contained US-English HTML companion for “Wayfinding · Note-to-Prototype Lesson”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Select option 1; Select option 2; Reveal evidence links; Check links & constraints; Proposed; Hypothetical; Actual notes; Restore 45-minute timing; Select plan text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Draft an original design-thinking lesson in US English.
Class context and duration: [enter or TO CONFIRM]
Approved real observations or explicitly fictional note set with IDs: [paste]
User task, constraints and approved trial arrangements: [paste]
Two prototype descriptions: [paste or request original proposals]
Actual feedback: [paste or NOT SUPPLIED]
Trace a bounded need and each design choice to note IDs, labeling added
assumptions. Compare at least two options. Preserve constraints in selection. Plan a specific user task and blank observation record. Separate actual from
hypothetical feedback; a partial success is not universal success. Link a
proposed revision to the exact evidence and state the unanswered question. Times must sum to the lesson length. Do not invent interviews, trial results,
accessibility certification, approvals or learning gains.
Return lesson, note/need/design links, sketches' descriptions, trial fields
and revision proposal. If requested, offer an HTML colleague-review copy
showing those links. No automatic trial completion or user-response collection.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Design Thinking Lesson Plan Template: Trace the Prototype Back to a User Note
A group sketches a bright room label, but nobody can say which user observation it addresses. Give the lesson a note-to-need-to-design chain before asking learners to choose a prototype. Then plan a trial whose observations can support a specific revision.
Keep the design provisional. A fictional interview note can support a classroom exercise, but it cannot become evidence that real visitors need the proposed solution.
## Three original wayfinding notes
**Fictional exercise inputs, not actual interviews or usability results:**
| Note ID | Supplied note | What it supports |
| --- | --- | --- |
| N1 | Visitors confuse Room A and Room B labels. | Investigate how the two labels are distinguished. |
| N2 | One visitor wants the letter readable at door height. | Consider letter visibility at the supplied placement. |
| N3 | The maintainer requires a removable paper-only prototype. | Preserve that material/removability constraint. |
An original need statement is **“Help a visitor distinguish A from B at the door using a removable paper prototype.”** Link it to N1-N3. Keep unanswered questions visible: Which label causes confusion? What does “readable” mean for the intended trial? What placement is approved for the prototype?
The [TCEA design-thinking article](https://blog.tcea.org/design-thinking-learning/) emphasizes understanding users, questioning assumptions and reframing problems. This lesson uses original notes and materials; it does not reproduce its linked lesson-plan template or claim a real user study.
## Compare two prototype options
**Option 1:** A removable paper label with one large room letter and the supplied room name underneath. It addresses N2 through letter prominence; its usefulness remains untested.
**Option 2:** A removable paper label with a large letter inside a distinct outlined shape, plus the same room name. The extra shape is a hypothesis about distinguishing labels, not a requirement established by N1.
Both must keep N3's paper/removability constraint. A permanently mounted sign would change the brief. Ask the group to name the note supporting each choice and label any unsupported addition **assumption to test**. Do not select Option 2 merely because it has more decoration.
## A proposed 45-minute lesson
- **Read notes, 6 minutes:** Separate the three supplied inputs from assumptions.
- **Frame need, 7 minutes:** Write a bounded need with note IDs and unresolved questions.
- **Ideate, 8 minutes:** Sketch two original options and compare their evidence links.
- **Prototype, 10 minutes:** Prepare the teacher-authorized removable paper version.
- **Trial plan and revision, 9 minutes:** Write the user task and observation fields; discuss a proposed revision from labeled hypothetical feedback or actual evidence if available.
- **Reflect, 5 minutes:** Explain the need/design link and what still needs testing.
The total is 45 minutes. Actual trial records remain blank unless a trial occurs under the teacher's supplied arrangements.
## Choose a trial that can change the design
An original task is **“Using these prototypes at their approved locations, identify Room A and Room B.”** Do not tell the participant which letter to read or describe the feature you hope will help before observing the task.
Use blank fields for prototype version, approved placement, task instruction, participant action observed, confusing point, and proposed change. Keep personal details out of the classroom example.
**Hypothetical feedback:** “Found A but missed B.” This supports investigating or revising B's clarity. It does not establish why B was missed or prove all visitors can find A. A specific proposed revision might make B's letter more prominent while keeping removable paper; record that as a hypothesis and say what another trial would check.
## Copy a note-linked design lesson brief
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Read the selected label back against N1-N3 with a teaching colleague. Keep the actual trial fields blank until used, then revise only as far as the observed feedback supports.