More than the Progect Method
Reggio-inspired practice beyond “doing projects”
If you’ve explored Reggio Emilia, you’ve likely met a string of powerful “images”—the image of the child (competent, curious), the teacher (researcher), the family (partner), and the environment (third teacher). Many of us study pedagogical documentation and then ask, “What comes next?” The answer is progettazione—often translated as projected curriculum. And it’s more than a calendar of activities. It’s a way of thinking-while-teaching: a living plan that stays in dialogue with children’s learning processes.
Below is a practical guide to what progettazione is (and isn’t), how it connects to the project tradition, and how to make it work in your classroom tomorrow morning.
First, what progettazione is not
- Not “project method” redux. Dewey and Kilpatrick’s project method and Katz & Chard’s Project Approach gave us student-centered investigations. Progettazione respects that lineage but adds a stronger stance of teacher inquiry and documentation-led iteration.
- Not a fixed unit plan. Backward planning has its place, but Reggio’s projected curriculum is intentional and provisional—held lightly so children’s ideas can bend it.
- Not “let the children do whatever.” Progettazione is structured: teachers formulate hypotheses, set conditions, and design constraints that generate thinking.
What progettazione is
A disciplined cycle of listening, interpreting, and designing next steps. Teachers collect traces of learning (photos, quotes, sketches, artifacts), study them together, form hypotheses about children’s thinking, and project the next moves—materials, groupings, provocations—that will test and extend those ideas. The plan breathes because it is regenerated by evidence.
Think of it as three interlocking practices:
- Listening to the “hundred languages” (gesture, drawing, building, talk, play).
- Documenting learning to make it visible to children, families, and colleagues.
- Designing environments and experiences (the progettazione proper) that respond to what the documentation reveals.
A mini-vignette: “Where does a shadow go?”
Context. First graders notice their shadows “run away” at recess. A small group debates whether the sun “pulls” the shadow or the child “pushes” it.
Documentation. Teachers gather short video clips, children’s drawings, and quotes (“My shadow hides under me when the sun is on top.”).
Interpretation meeting (30 minutes). Team identifies emergent ideas: directionality, occlusion, and time of day. They draft two hypotheses:
- If children can manipulate a single light source, they’ll reason about angle and length.
- If they can record changes, they’ll begin to coordinate time with observation.
Projected next steps.
- Set up a “shadow lab” with clamp lamps, translucent screens, blocks, and measuring tapes.
- Introduce a simple time-lapse station (tablet + fixed stand).
- Add vocabulary cards (“angle,” “occlude,” “long/short”) born from children’s language.
Re-launch. Children test ideas; teachers capture new traces. The curriculum evolves from about shadows to children theorizing with light. Standards are met (measurement, evidence, explanatory language), but the learning path is co-authored.
The engine: pedagogical documentation
Documentation isn’t a scrapbook; it’s your research dataset and your design brief.
- Collect: short audio/video (10–30 seconds), photos of intermediate work (not just “final products”), verbatim quotes, and teacher field notes.
- Curate: weekly 20–30 minute team review; sort traces under What do we notice? What might they be trying to figure out? What could we test next?
- Return: make panels or table-top sequences children can read to revisit their thinking. Ask, What should we try now?
Rule of thumb: If a next step isn’t traceable to evidence in your documentation, it’s probably an activity—not progettazione.
A simple cadence you can keep
- Daily – Capture at least three traces; jot one “teacher hypothesis” sentence.
- 48 hours – Post a mini-panel (4–6 images + quotes) for children to revisit.
- Weekly – Team interpretation (30 minutes): choose 1–2 projected moves; identify what evidence would confirm or challenge your hypothesis.
- Monthly – Share a short case with families: child voices first, teacher analysis second, next moves last.
The teacher stance (and a few talk moves)
In progettazione, teachers are designers and researchers.
- Pose generative questions: “What do you think the water wants to do here?”
- Press for evidence: “What makes you say that?” / “Show me with your drawing.”
- Open multiple languages: “Could you build your idea too?”
- Name strategies: “You compared two shadows—scientists call that a fair test.”
Designing environments that think with you
- Materials as variables: Offer contrasts (rigid/flexible, opaque/translucent).
- Surfaces for revisiting: Whiteboards, transparent trays, and clipboards that live with the materials, not in a closet.
- Visible purposes: A small “Question Wall” and “We’re trying…” card at each station ties work to the living plan.
Assessment that fits the work
Progettazione pairs children’s problems with teacher intentions.
- Double-voiced goals: “Children will compare the length of shadows” (teacher) alongside “We’re figuring out where shadows go at noon” (children).
- Lightweight rubrics for talk moves (e.g., paraphrase, build, respectfully challenge), representation (clarity, correspondence), and inquiry habits (persistence, risk-taking).
- Standards mapping: One monthly grid showing how emergent work aligns to your state standards—no need to pre-determine every move.
Equity is a design choice
- Honor home languages in captions and conversations; accept drawings, gestures, and constructions as full-status contributions.
- Rotate who gets the microphone: small-group formats and artifacts that speak reduce the dominance of fast talkers.
- Document with consent and care: share processes, not just portraits; invite families to co-interpret panels in their own words.
Common pitfalls (and quick fixes)
- Theme traps (“It’s our ‘ocean unit’ no matter what.”) → Shift to phenomena children actually encounter (flow, balance, growth).
- Showcase bias (only “cute” displays) → Publish messy middles and revisions.
- Activity creep (busy, not deep) → Return to evidence: What question are we pursuing, and what will count as progress?
A one-page Progettazione Canvas (use tomorrow)
- Generative focus/phenomenon: __________________________
- Evidence we’re hearing/seeing: _________________________
- Our hypothesis about children’s thinking: _______________
- Projected next steps (materials, groupings, invitations):
- What evidence will confirm or challenge our hypothesis?
- How we’ll make thinking visible (to children/families):
Why progettazione matters now
Project work taught us to follow curiosity; progettazione teaches us to design with curiosity. It respects standards without letting them script the day. It centers children’s theories, honors teachers as researchers, and invites families into the meaning-making. Most of all, it keeps teaching in conversation with learning—where it belongs.
