IOP 460 Week 4 Learning Organizations Example

The Recalled Peanut Butter That Went Out Anyway: Building a Learning Organization at a Food Bank

[Student Name]

University of Phoenix

IOP/460: Organizational Cultures

Week 4 Assignment

[Instructor Name]

[Date]

The food bank, its staff and the incident are composites written for a model paper; research and theory come from the sources listed.

Organizations make mistakes. What distinguishes learning organizations is not avoiding every error but learning from errors in ways that change the conditions that produced them. This paper examines a food safety near miss at the food bank followed since Week 1.

The Incident

On a Tuesday, a national manufacturer recalled several lots of peanut butter for possible salmonella contamination. The recall notice arrived by email at the food bank's general information inbox, which a part-time receptionist checks when time allows. The notice was not opened until Friday. By then, the east-side warehouse had distributed two hundred jars from the recalled lots. Staff pulled the remaining stock, called the families they could reach using sign-in sheets and posted notices in English and Spanish at the pantries. No illnesses were reported. The operations coordinator reminded the receptionist to check the inbox daily.

Single-Loop and Double-Loop Learning

Argyris (1977) distinguished two kinds of organizational learning. In single-loop learning, people detect and correct errors without questioning the underlying policies, goals and assumptions, like a thermostat that turns on the heat when the room is cold. In double-loop learning, they question and change those underlying policies and assumptions. Argyris argued that organizations often fail at double-loop learning because of defensive routines: people avoid embarrassment and threat by not raising difficult issues, and the avoidance itself becomes undiscussable.

The food bank's response was single-loop. Pulling stock, calling families and reminding the receptionist corrected the immediate error. It did not ask why safety alerts went to an inbox no one watched daily, why no one was responsible for food safety across the three warehouses after the merger, or why the east-side warehouse had no way to check lot numbers before distribution.

The Learning Organization

Senge (2006) described a learning organization as one in which people continually expand their capacity to create the results they want, in which new patterns of thinking are nurtured and in which people are continually learning how to learn together. Senge proposed five disciplines: personal mastery, mental models, shared vision, team learning and systems thinking, the fifth discipline that integrates the others. Systems thinking means seeing interrelationships and patterns of change rather than isolated events and linear causes.

A systems view of the recall reveals a pattern: since the merger, responsibilities that used to sit with one experienced person have been split or lost. Food safety, recall monitoring and lot tracking all fell between roles. The near miss was not a receptionist's failure but a system without an owner for food safety.

Why Frontline Workers Work Around Problems

Tucker and Edmondson (2003) observed hospital nurses and found that when they encountered problems, such as missing supplies or information, they usually solved them on their own in the moment, first-order problem solving, without communicating the problem so that its causes could be addressed, second-order problem solving. Workarounds kept patients cared for but allowed the same problems to recur. Factors that discouraged second-order problem solving included heavy workloads, an emphasis on individual vigilance and managers who were not present to hear about problems.

The food bank shows the same pattern. Warehouse staff had noticed before that donated products sometimes arrived near or past their dates and had quietly sorted them out by hand. No one reported the pattern, so no one designed a system to check products, including recalled lots, at intake.

Every warehouse worker had a private way of spotting bad cans; none of those ways was written down, and none of them caught a recall.

Mental Models in the Way

Senge's discipline of mental models helps explain the response. Leaders held an unspoken belief that food safety was a warehouse task handled by experienced hands, a belief formed when one veteran manager ran a single site and personally checked every pallet. After the merger, that manager left and the belief stayed. Surfacing and testing such assumptions is part of double-loop learning. At the first review meeting, a site lead said aloud, "We all thought someone else was watching the recalls," and the room went quiet: the shared assumption had finally become visible.

Barriers at the Food Bank

Several barriers keep Valley Harvest from double-loop learning. Workloads are high, especially during the holiday season. The culture, built on heroic effort, praises staff who fix things themselves. After the merger, staff from different sites rarely meet. And the receptionist, though not at fault, felt blamed, which teaches others to stay quiet about future mistakes.

Recommendations

Assign ownership. Name a food safety lead with authority across all three warehouses, responsible for monitoring recall alerts through a dedicated address and subscription to official recall notices.

Change the system. Record lot numbers at intake for high-risk products and check them against recall lists before distribution.

Hold after-action reviews. After any incident or near miss, gather the people involved from all sites to ask four questions: what was expected, what happened, why and what will change. Focus on systems, not blame.

Encourage reporting. Create a simple way for staff and volunteers to report problems and near misses, and share at monthly meetings what was changed as a result, so reporting feels worthwhile.

Protect time. Set aside thirty minutes each month at each site for team learning, even in busy seasons.

Measuring Learning

The food bank will track the number of near misses reported, the time between recall alerts and action and the changes made in response to reports. Rising reports, at first, would be a good sign, showing that problems are surfacing rather than being hidden, and leaders should say so publicly so staff do not read a jump in reports as failure.

Conclusion

The food bank's response to the recall corrected the error but did not question the conditions that produced it. Research on double-loop learning, the learning organization and frontline workarounds explains why and points to practices that change those conditions: clear ownership, system checks, blame-free reviews and protected time for learning.

References

Argyris, C. (1977). Double loop learning in organizations. Harvard Business Review, 55(5), 115-125.

Senge, P. M. (2006). The fifth discipline: The art and practice of the learning organization (Rev. ed.). Doubleday.

Tucker, A. L., & Edmondson, A. C. (2003). Why hospitals don't learn from failures: Organizational and psychological dynamics that inhibit system change. California Management Review, 45(2), 55-72. https://doi.org/10.2307/41166165