After a peer city suffers a crane collapse, a public-works director dismisses the lessons as “not us.” What continuous-improvement response is more appropriate?
Select an answer to reveal the explanation.
Short Explanation
“Not us” is how someone else’s accident becomes yours next year. Peer failures are free case studies—pull the lessons, check your cranes, and tighten controls before gravity writes the same headline. Learn outward, then look inward.
Full Explanation
Learning from external events is a recognized continuous-improvement method. When a peer city suffers a crane collapse and a public-works director dismisses lessons as “not us,” the better response is to use external incidents to trigger internal control reviews where similar exposures exist. Civic agencies share equipment classes and contractor patterns even when vendor logos differ.
Treating external incidents as irrelevant unless the same vendor logo appears locally invents an overly narrow applicability test. Waiting until an identical collapse happens locally before reviewing crane controls accepts preventable local harm as the learning trigger. Discussing peer-city events only in press releases, not risk meetings, separates public relations from operational improvement.
Exam caveat: external incident reviews are valid improvement inputs. Logo matching is not required for applicability screening.
Operational check: after notable peer incidents, screen for similar equipment, contractors, or procedures; open a targeted control review; document findings and actions; share lessons with relevant municipal shops. Maintain a short external-incident screening checklist for public-works leadership so peer events routinely generate a go/no-go local review decision. Document why an event was judged not applicable when skipped.