In Italian schools, there is no shortage of experimentation. A teacher alters the structure of a lesson, a department tests a different assessment method, or a small team develops an interdisciplinary path that engages students more than before. These are often grassroots initiatives, underpinned by solid professional skills and the willingness of those who choose to invest time beyond the ordinary.
Their limitation, however, is well known: many fizzle out when staff changes, project funding stops, or the energy of those who launched them fades. An initiative can be successful and yet leave no structural trace in the institution. The difference does not lie in the value of the work done, but in its capacity to embed itself into the school's organizational life.
This is the shift addressed by Bruno Lorenzo Castrovincì in an article published on October 14 in Tuttoscuola: an effective practice does not automatically become a model simply because it met with approval in a classroom or was presented as a success story. To become part of the school community's shared heritage, it must be able to be understood, discussed, modified, and adopted by other professionals, even in settings different from the one in which it originated.
The issue has a concrete impact on school quality. Every year, institutions produce a substantial amount of planning, materials, observations, and operational solutions. If that capital remains tied to individuals, any turnover risks sending the work back to square one. If, instead, it is transformed into shared knowledge, the school can accumulate experience and leverage it to improve with greater continuity.
Before dissemination, an analysis of the results is needed
The first misconception is mistaking a successful outcome for proof that an experience can be replicated anywhere in the exact same way. A methodology may have worked because of the makeup of the class, the number of hours available, the quality of the rapport built by the teacher, or a specific interplay between subject matter, activities, and feedback. Transferring only the materials or the operational sequence is no guarantee of reproducing its effects.
This is why the decisive phase is not the announcement of the practice, but the analysis of what made it effective. It is necessary to reconstruct the initial objectives, the choices made, the working conditions, the evidence collected, and the obstacles encountered. It is not a matter of turning every activity into an academic research project, but rather of distinguishing what is essential from what belongs to specific circumstances.
This distinction makes it possible to avoid two opposite risks. On the one hand, there is the celebration of the exception, whereby the project remains the virtually unrepeatable feat of a particularly gifted teacher. On the other hand, there is mechanical replication: a formula is adopted because it worked elsewhere, without questioning the characteristics of the students, the disciplines involved, and the resources actually available.
A useful model, therefore, is not a rigid script. Rather, it is a set of criteria that enables those who adopt it to recognize the problem being addressed, understand the pedagogical reasoning that guided the solution, and decide what modifications to introduce without distorting its core nature.
Documenting does not mean building an archive of compliance
Documentation is one of the tools that enables this transformation, provided it is not reduced to a collection of forms, slides, or final photographs. In school life, the volume of paperwork is already substantial; adding documents devoid of a learning function does not create organizational memory—if anything, it merely increases the workload.
Truly useful documentation should make the journey legible: what goals were set, what decisions were made, how students were engaged, what outcomes emerged, and where difficulties arose. Mistakes and adjustments matter too. Those who did not take part in the experience must be able to reconstruct not only its outcome, but also the logic with which it was conducted.
From this perspective, documentation does not serve to certify that a project existed, nor to promote a positive image of it. It becomes a working asset for the faculty council, departments, and teams designing subsequent activities. Its value lies in the ability to bridge the gap between a local experience and the institution's collective professional knowledge.
For schools, increasingly called upon to manage funded projects, networks, and initiatives, this is a substantial difference. At the end of a project, it is not enough to simply preserve the resulting outputs: guidelines must be provided so others can understand if, how, and under what conditions that path can be taken again.
Sharing requires time and peer exchange
Circulating best practices does not end with a mention during a meeting or uploading a folder to a digital platform. These steps may be necessary, but they are not enough. Materials without context risk remaining invisible; presenting an experience, if it does not spark discussion, may merely document an already concluded outcome.
Professional sharing, on the other hand, requires opportunities where teachers can ask questions, pinpoint the challenges encountered, compare the proposal against their own classes, and consider necessary adaptations. This is where an experience ceases to belong exclusively to whoever designed it. Not because everyone must apply it, but so everyone can evaluate its principles and use them consciously.
What is at stake is also linguistic and organizational. When a school continuously discusses objectives, feedback, planning, and evaluation criteria, it builds a shared professional vocabulary. This does not eliminate differences between academic tracks, subjects, and teaching styles, but it provides a foundation for collaborating without starting from scratch with definitions every time.
Without dedicated time and space, innovation risks relying on individual goodwill. The paradox is that the most promising experiences can often remain marginal: the people who created them are frequently the ones most occupied with carrying them forward, leaving them with fewer opportunities to make them accessible to colleagues.
Adapting does not mean betraying the model
The pursuit of consistency must not lead to standardization. A practice designed for one group of students may require significant revisions in another classroom; an effective solution in one subject area may take on different forms elsewhere. Demanding an identical implementation risks depriving teachers of the ability to interpret actual needs and, ultimately, compromising what made the experiment worthwhile in the first place.
The most robust school model is therefore one that sets a direction, clarifies key milestones, and preserves room for decision-making. Fidelity does not lie in repeating details, but in maintaining the educational rationale and the conditions that generated value. To verify whether an adaptation remains consistent, what is needed is dialogue and observation, rather than purely formal oversight.
Ultimately, transitioning a best practice from experimentation to institutional culture requires a governance choice. School leadership, specialized support functions, departments, and the faculty board all have distinct roles, yet all influence the ability to give continuity to educational paths. Without recognizing dedicated time for planning and collaboration, the idea of a school that learns from its own experiences remains reliant on individual initiative.
The result is neither a catalog of projects to replicate nor a standardized school. It is an organization capable of retaining what it learns, interrogating its own results, and recirculating practices that have proven useful. In a system marked by turnover, administrative burdens, and project discontinuity, this capability can make the difference between episodic innovation and lasting change.
