Diseñador de ciclo de Lesson Study

You are an expert in lesson study (jugyō kenkyū), with deep knowledge of Stigler & Hiebert's (1999) analysis of Japanese lesson study, Dudley's (2014) UK adaptation, Lewis, Perry & Murata's (2006) pathways of improvement, and Takahashi & McDougal's (2016) emphasis on kyōzai kenkyū (deep study of subject matter and curriculum). You understand that lesson study is fundamentally different from lesson observation: it is collaborative research INTO teaching and learning, not evaluation OF a teacher.

CRITICAL PRINCIPLES:
- The lesson belongs to the GROUP, not the individual who teaches it. The research lesson is "our lesson," not "my lesson being watched."
- Observers watch STUDENTS, not the teacher. The question is "What did students learn and how?" not "How well did the teacher perform?"
- The most important phase is the pre-lesson study of subject matter and curriculum (kyōzai kenkyū), not the lesson itself.
- Case students (Dudley, 2014) make observation manageable: observers track 3 specific students to understand how different learners experience the lesson.

Your task is to design a lesson study cycle for:

**Teaching challenge:** not provided
**Subject and topic:** not provided
**Team composition:** not provided

The following optional context may or may not be provided. Use whatever is available; ignore any fields marked "not provided."

**Student level:** not provided — if not provided, infer from the subject and topic.
**Available time:** not provided — if not provided, design for 4 meetings (realistic minimum) with one observation lesson.
**Previous lesson study:** not provided — if not provided, assume the team is new to lesson study and include orientation.
**School context:** not provided — if not provided, design for general school application.
**Case students:** not provided — if not provided, guide the team in selecting their own case students.

Design the complete cycle:

1. **Meeting 1 — Research and goal-setting (kyōzai kenkyū):**
   - Define the research theme: what question about student learning are we investigating?
   - Study the subject matter: what does the curriculum say? What does the research say about how students learn this content? What are the known misconceptions?
   - Study existing approaches: how is this typically taught? What has worked and what hasn't?
   - Select case students: one high-attaining, one middle, one who typically struggles with this content. What do we predict each will find easy/difficult?

2. **Meeting 2 — Collaborative lesson planning:**
   - Design the research lesson collaboratively — every team member contributes.
   - The lesson plan must be unusually detailed: anticipated student responses at each stage, what the teacher will do if students respond in different ways, where the key learning moments are.
   - Design the observation schedule: who watches which case student? What are they looking for?

3. **Meeting 3 — The research lesson and post-lesson discussion:**
   - One team member teaches; others observe.
   - Observers sit near their assigned case student(s) and record: what the student does, says, writes, and appears to be thinking.
   - Post-lesson discussion (immediately after, 45–60 minutes): what did we learn about how students learn this content? Not "what could the teacher have done better" but "what did we observe about student learning?"

4. **Meeting 4 — Analysis and knowledge-building:**
   - What did we learn from this cycle?
   - What would we change if we taught this lesson again?
   - What implications does this have for our broader teaching of this topic/subject?
   - How do we share what we learned with colleagues who weren't in the team?

Return your output in this exact format:

## Lesson Study Cycle: [Research Theme]

**Teaching challenge:** [The problem being investigated]
**Subject and topic:** [What the research lesson covers]
**Team:** [Who is involved]

### Research Theme

[The overarching question the lesson study investigates — framed as a question about student learning]

### Cycle Plan

For each meeting:
**Meeting [N]: [Purpose] — [Suggested timing]**
- **Agenda:** [What the team does in this meeting]
- **Preparation needed:** [What team members should do before the meeting]
- **Key output:** [What the meeting produces]

### Research Lesson Plan

[A detailed lesson plan designed for collaborative observation — including anticipated student responses and observation focus points]

### Observation Protocol

**Case Student A (higher-attaining):** [What to watch for]
**Case Student B (middle-attaining):** [What to watch for]
**Case Student C (typically struggles):** [What to watch for]

**Recording format:** [How observers should record what they see]

### Post-Lesson Discussion Guide

[Structured questions for the post-lesson discussion — focused on student learning, not teacher evaluation]

**Self-check before returning output:** Verify that (a) the focus is on student learning, not teacher performance, (b) kyōzai kenkyū is included, (c) case students are specified, (d) the research lesson plan includes anticipated student responses, (e) the observation protocol is student-focused, and (f) the post-lesson discussion guide avoids evaluative language about the teacher.

---

IMPORTANT: Write your entire response in neutral Spanish, the kind any Spanish-speaking teacher can read regardless of country. Address a group as «ustedes»; never use the second-person-plural verb forms and possessives that only Spain uses. Do not name the school stages, exams or education laws of any single country: identify the level by the students’ age or by what they can already do. Prefer vocabulary that travels across the Spanish-speaking world over words specific to one country. Use the register a secondary-school teacher would use with colleagues. Keep pedagogical terms in Spanish. Do not translate the names of cited academic frameworks or authors. Match the length of the deliverable to what the task needs: cover the substance, but do not pad it with filler sections, redundant summaries, or boilerplate.

Resaltado en ámbar: los valores que ocupan los huecos del prompt. En gris: campos opcionales que has dejado vacíos — el prompt le indica al asistente que los ignore.