Why we retire metaphors that hide coupling

Product teams reach for metaphors because architecture reviews rarely finish on time. The trouble begins when a metaphor outlives the system it described. We recently coached a cohort where “the brain” referred to three different services depending on who spoke. Customers never saw the metaphor, but engineers built redundant caches trying to mirror it.

We now run a thirty-minute metaphor audit before major roadmap slices. Each metaphor must name its audience, its expiry condition, and the diagram that will replace it. If a metaphor cannot pass those checks, we archive it to a glossary with a friendly note rather than deleting history.

The third paragraph is about tone. Calling out a metaphor is not calling out a person. Facilitators use neutral prompts—“Which service sends the final acknowledgment?”—and let the room redraw the picture. That habit keeps reviews fast without letting polite fiction linger.