Government agencies lose institutional memory in two ways. The first is ordinary staff turnover: people leave, retire, transfer, and their knowledge of how things work, what has been tried, why certain decisions were made leaves with them. The second is political turnover: every five years, a change in government brings new leadership at the senior and political levels who were not present for the previous administration's work and have limited visibility into what was done, what worked, what failed, why. In both cases, knowledge that should accumulate over time instead dissipates, and each new cohort of staff or leadership starts with an incomplete picture of what came before.
Programs that were working well get discontinued not because they failed but because new leadership does not know they exist or does not understand their value. Programs that failed get repeated because no one remembers why they were abandoned. Initiatives get launched that duplicate work already underway in another department because no one has a comprehensive view of what the ministry is doing. New staff take months to become effective because there is no structured way to learn what the organization does beyond what their immediate colleagues happen to tell them. Consultants and new hires ask the same questions that were asked and answered years ago, and the answers have to be reconstructed from memory each time. These are the outcomes of organizations that have no systematic way to document and transmit what they know.
Documentation as infrastructure for continuity
Public Policy Lab has been working with the Ministry of Social and Family Development to build the documentation infrastructure that makes institutional memory possible. The core of this effort is a comprehensive publication that documents all policies and programs being carried out across every department of the ministry, including their context, their implementation status, the challenges they face, and their results where available. New staff can use it as an onboarding resource that provides a complete picture of the ministry's work rather than the fragmented view they would otherwise piece together over months. For existing staff, it breaks down the silos that typically keep departments unfamiliar with each other's work, because when everyone has access to a document describing what every department does, heads of department and individual staffers can identify complementary activities, avoid redundant work, coordinate on shared needs like site visits that could serve multiple purposes.
For leadership transitions, this documentation provides something that rarely exists in government: a genuine handover. Incoming leadership can read a single document and understand what programs are underway, what their status is, what challenges they face, what the reasoning was behind key decisions, without having to rely on briefings that may be incomplete or on institutional memory that may have already departed. Programs that were working well are visible and can be continued, programs that were struggling are documented along with the reasons so new leadership can make informed decisions about whether to persist, adjust, discontinue. Future governments remain free to set their own priorities; the documentation exists so they have the information needed to make good decisions rather than reconstruct what came before from scratch.
Breaking silos through shared visibility
Comprehensive documentation also addresses the silo problem that affects most large organizations. Ministries get divided into departments, and departments often have limited visibility into each other's work. One department conducts site visits to islands without knowing that another department needs information from those same islands, so two trips happen when one could have served both purposes. One department develops a data collection system without knowing that another department already built something similar. One department identifies a systemic issue through casework without a clear channel to share that finding with colleagues working on related policy. The fragmentation comes from absent infrastructure that would make collaboration natural. People cannot coordinate on work they do not know exists.
A single publication documenting the work of every department and shared ministry-wide makes these silos harder to maintain. Staff can see what their colleagues in other departments are working on, identify overlaps and opportunities for coordination, flag when their work connects to someone else's. The documentation has to actually be comprehensive and actually be shared, something everyone in the organization knows about and treats as a working reference. The investment in producing and maintaining such documentation pays off not in visible outputs but in the accumulated efficiency gains of an organization that knows what it is doing across all its parts.