When Frontline Knowledge Never Reaches the Decision

A public service can collect concerns, publish guidance and hold review meetings without becoming better at learning. The missing connection is often between what a worker notices and what an institution is able to decide.

A repeated problem may remain in a supervisor’s notebook while the next budget, procedure or staffing decision is made elsewhere. When that happens, the institution possesses information without necessarily having a usable memory.

For organisations concerned with policy implementation, this creates a practical question: how can everyday delivery knowledge enter decisions without requiring workers to become researchers or adding another reporting burden?

My perspective comes from adult social care management in England. The suggestions here are practitioner proposals, not findings from research in Pakistan, and should be examined with local practitioners before application.

Learning needs a route into authority

The Alliance for Health Policy and Systems Research’s 2021 report on learning health systems treats learning across individuals, teams and organisations as important to strengthening health systems. Its relevance here is a broad principle: learning needs organisational support.

My argument is that a concern becomes institutionally useful when it can reach someone authorised to examine it. That does not mean every observation should trigger a policy change. It means the organisation should be able to distinguish a local question from an issue requiring a different level of authority.

Consider a hypothetical public-facing service. Several workers report that citizens repeatedly return because the instructions they receive are difficult to follow. One supervisor rewrites a sentence. Another spends extra time explaining the same form. Both responses may help, but neither necessarily reaches the person responsible for the form itself.

The underlying decision is then left untouched. The service treats each encounter as a separate difficulty rather than asking whether the shared instruction needs review.

Preserve the question, not the personal details

A useful record does not need to reproduce a citizen’s private story. It might identify the recurring point of confusion, which part of the procedure is affected, what remains uncertain and who can investigate.

This distinction matters. Organisations should not collect sensitive information simply because it could be interesting. Existing confidentiality, safeguarding and complaints routes must remain available, and urgent concerns should use the appropriate escalation process immediately.

For ordinary improvement questions, the record should be proportionate. If staff need twenty minutes to report a five-minute obstacle, the learning process may itself become an obstacle.

The minimum useful record is a proposal for local testing, not a universal template. A small service and a national programme will require different arrangements.

Distinguish an explanation from a solution

A decision-maker may discover that an apparent communication problem reflects something harder: a missing resource, an unclear eligibility rule or a requirement set by another institution.

Listening cannot create resources that do not exist. Nor should a manager promise to resolve a matter beyond their authority.

A useful response can nevertheless explain what has been understood, what action is possible, what must be referred elsewhere and what cannot currently change. The record then preserves both the issue and the reason for the decision.

That explanation is particularly valuable when staff change roles. Without it, the next team may repeat an unsuccessful adjustment or ask citizens to explain the same difficulty again.

Make implementation a subject of learning

WHO’s 2024 Implementation Playbook is intended to help health-system leaders and programme managers strengthen implementation capacity and connect daily work with impact. It supports attention to implementation as work in its own right. It does not validate the specific approach proposed in this article.

An organisation could examine one recurring, non-urgent service difficulty over an agreed review period. Before beginning, it would identify the decision involved, the responsible person and the information needed to judge whether an adjustment helped.

The review should consider more than whether staff completed a new step. Did users understand the next action? Did the adjustment shift work to another team? Did it exclude people who could not use the preferred communication channel? What additional effort did it require?

These are questions to investigate, rather than outcomes to assume. Any example involving real people would need appropriate permissions, protection of information and, where applicable, ethics review.

A conversation for Pakistan, not a prescription

For a Pakistan-focused institution, the value of comparative experience lies in the questions it makes available. Local contributors would need to establish which service, administrative level, language requirements and decision structures make an inquiry meaningful.

A productive starting point would be one jointly selected problem, grounded in local evidence. Comparative practice could inform the discussion while local expertise determines what transfers, what requires adaptation and what should be rejected.

The ambition need not be another elaborate system. It can begin with an institutional habit: when a recurring difficulty reaches a decision, keep a clear account of what was considered and what happened.

Public services cannot learn from knowledge that disappears with the person who held it. Preserving a proportionate, usable connection between experience and authority is one way to make learning part of ordinary administration.

Opinion pieces reflect the views of their authors, not necessarily an institutional position of PIVRA.