# Explanatory Style Martin Seligman identified a consistent pattern in how people explain setbacks to themselves — a pattern stable enough across time and situations to be considered a cognitive style, and consequential enough to predict health, performance, and persistence. He called it explanatory style. The insight for practitioners: *the explanation a team gives for its situation is often more diagnostic than the situation itself.* The same objective circumstances — a difficult quarter, a failed initiative, a team that lost a key person — produce radically different trajectories depending on how those circumstances get explained. And the explanation is observable, and workable. ## The three dimensions Explanatory style operates on three axes. For setbacks (the dimensions reverse for successes — pessimists attribute wins to luck or circumstance; optimists attribute them to enduring causes): **Permanence: Permanent vs Temporary** *Permanent:* "This is just how things are here." / "Nothing ever changes." / "We've always had this problem." / "Leadership will never get it." *Temporary:* "That quarter was brutal." / "This project was a mess." / "We lost the thread for a while." Permanent explanations lock the situation into the future. Temporary explanations leave it in the past. A team that explains its difficulties as permanent has already decided that what happened is what will keep happening. A team that explains them as temporary is still in a position to act. **Pervasiveness: Pervasive vs Specific** *Pervasive:* "Everything here is broken." / "The whole culture is the problem." / "Nobody in this organisation gets it." *Specific:* "The handoff between those two teams doesn't work." / "That meeting design produces this outcome." / "This process, not the people." Pervasive explanations spread. When one thing is the problem, everything becomes the problem. Specific explanations contain. They preserve the rest of the system as functional, which means the rest of the system is still available as a resource. **Personalisation: Personal vs External** *Personal:* "I should have seen this coming." / "We just don't have the right people." / "I'm not a strong enough leader to fix this." *External:* "The incentive structure makes this rational for everyone involved." / "The process doesn't surface the right information." / "We inherited this." Personalisation is not always distortion. Sometimes the honest assessment is that a decision was wrong, or a skill is missing. The problem is when personalisation is the default — when the system explanation is not even considered. This is the mechanism that produces blame cultures from the inside: teams that automatically locate the cause of difficulty in people rather than conditions. Seligman's claim: pessimistic explanatory style — permanent, pervasive, personal — predicts depression in individuals and learned helplessness in both individuals and systems. Optimistic explanatory style — temporary, specific, external (for setbacks) — predicts resilience and persistence. ## Why this matters for organizational work The explanatory style a team uses is audible in how it talks about its situation, and it is one of the first things to listen for in any diagnostic conversation. A team that says "we've always had communication problems, it's just how this place works" (permanent, pervasive) is in a fundamentally different situation from a team that says "the last six months were unusually fractured, we think because of the restructure" (temporary, specific) — even if the communication patterns being described are identical. The first team has incorporated the problem into its identity. The second team still has a relationship with it as an event. Three uses for practitioners: **1. Diagnosis before intervention.** Before designing an intervention, listen to how the team explains its situation. Permanent and pervasive explanatory frames are signals that any point-in-time intervention is likely to be absorbed as "another thing that didn't work" — which will further confirm the permanent/pervasive frame. The frame itself needs addressing before the content does. This connects directly to [[Learned Helplessness as Organizational Pattern|learned helplessness]]: the permanent/pervasive explanatory style is often how helplessness maintains itself cognitively. The team has learned that things don't change (permanent) and generalises that to everything (pervasive). **2. Reframing as a precision move.** Reframing is only useful if the frame being offered is more accurate, not just more comfortable. Explanatory style gives the reframe a specific target: you are not simply offering a "more positive" view, you are offering a more calibrated attribution. "That project was difficult" rather than "we always struggle with this." "The process doesn't surface this information" rather than "the team doesn't communicate." The reframe is a hypothesis about a more accurate location of the cause — specific rather than pervasive, external rather than personal. It can be tested. **3. Exception finding entry point.** Teams with strong permanent/pervasive explanatory styles struggle with [[Exception Finding|exception finding]] because the frame filters the exceptions out. "When was this not a problem?" is difficult to answer if your working model is "this is always a problem." The exception work and the explanatory style work interact: finding one exception creates evidence against the permanent frame; loosening the permanent frame makes exceptions more accessible. Often the most useful sequence is to address the explanatory frame first — not by arguing against it, but by asking for a specific instance that contradicts it — then to build from the exception. ## Listening for it Explanatory style is audible in the grammar of how teams and leaders describe their situation: | Signal | Dimension | What it sounds like | |--------|-----------|---------------------| | "Always", "never", "just how it is" | Permanent | "We never get clear briefs from leadership" | | "Everything", "nothing", "the whole" | Pervasive | "The whole culture needs to change" | | "We're not good at", "I should have" | Personal | "We're just not a data-driven team" | | "This time", "that project", "recently" | Temporary | "Last quarter was genuinely hard" | | "This process", "this team", "that meeting" | Specific | "The design review doesn't work" | | "The structure", "the incentives", "the system" | External | "The way we're set up makes this rational" | The most useful diagnostic signals are the ones that appear without prompting — the explanatory style that comes out in how people describe their situation before any intervention has been proposed. That unprompted frame is the working model, and it is what any intervention will have to contend with. ## The team-level dimension Seligman developed explanatory style as an individual construct. At the organizational level, teams develop shared explanatory styles — a collective narrative about why things happen the way they do. This narrative is often more stable than the situation it describes. New information gets processed through the existing frame: a win gets explained as luck (if the frame is pessimistic) or as confirmation of capability (if the frame is optimistic). Shared pessimistic explanatory frames are self-maintaining. They produce lower effort (why try if it's permanent?), which produces worse outcomes, which confirms the frame. This is the cognitive mechanism behind [[Learned Helplessness as Organizational Pattern|organizational learned helplessness]]: the pattern runs, the frame explains it as permanent and pervasive, and both the pattern and the frame reinforce each other. Changing the shared frame is harder than changing an individual one, because it is embedded in the team's collective story — the account they give themselves and others of who they are and how things work here. This is also why [[Signals over Stories - Why It Happens|the stories teams tell about their situation]] matter as much as the signals the situation is producing. ## The limit: when the permanent/pervasive assessment is accurate Explanatory style is not always distortion. Sometimes a pattern really is permanent in a given system. Sometimes the problem really is pervasive. Sometimes the right attribution really is personal — someone made a bad decision, and naming that is honest and necessary. The risk in applying this framework is pathologising accurate perception. A team in a genuinely dysfunctional organisation that uses permanent/pervasive language to describe its situation may be describing reality correctly. Reframing this toward "temporary/specific" would be a kindness that undermines clarity. The test: is the explanatory frame more negative than the evidence warrants, or is it calibrated to the evidence? A team that has raised the same issue twelve times over four years with no response is not distorting when it says "nothing changes here." It is being accurate. The intervention in that case is not reframing — it is either changing the system that has ignored twelve reports, or being honest that the system is unlikely to change. Explanatory style is most useful as a diagnostic lens when the frame and the evidence have diverged — when the team's account of its situation is more negative than what the evidence supports, or when it has frozen a past accurate assessment into a present that has actually shifted. ## See Also - [[Learned Helplessness as Organizational Pattern]] — the behavioural companion; permanent/pervasive explanatory style is the cognitive structure that maintains learned helplessness; the two reinforce each other and are addressed together - [[Exception Finding]] — the practical intervention for pessimistic explanatory frames; finding one exception creates evidence against the permanent attribution and opens the frame - [[Signals over Stories - Why It Happens]] — the broader Owlery frame for how teams filter signals through narratives; explanatory style is one layer of the story structure - [[Ladder of Inference - Why It Happens]] — explanatory style operates near the top of the ladder: it is the assumption layer that determines which data gets selected and how it gets interpreted - [[Common Cause vs Special Cause]] — the pervasive explanatory style often treats common cause variation as evidence of a permanent pattern; the Deming frame is the analytical corrective to this specific distortion - [[Mess vs Problem]] — pervasive explanatory frames often reflect a real mess that cannot be solved at the level of its components; sometimes the "everything is broken" assessment is accurate and requires dissolving, not reframing - [[Grief as Organizational Force]] — a grieving system often develops permanent/pervasive explanatory style as part of its protective logic: "nothing will work without Michael" is both an explanatory frame and a loyalty statement - [[Westrum Culture Typology]] — pathological cultures produce pessimistic explanatory styles because the system genuinely does suppress information and punish messengers; the frame and the reality align - [[Fear Is the Enemy of Learning]] — personal explanatory style for failure (I'm not capable, I'm not good enough) is the individual-level mechanism fear produces; changing the cost of being wrong shifts the attribution - [[Host as Conditions Designer]] — if the explanatory frame is reasonably calibrated, the conditions need to change before the frame will; you cannot argue a team out of an accurate assessment - [[Optimism as Avoidance]] — the failure mode of the optimistic explanatory style; when the permanent/external/general orientation becomes a routing mechanism that keeps attention outward rather than a genuine cognitive orientation; the defence that wears optimism's face