{"meta":{"slug":"fundamental-attribution-error","area":"strategia","data":"2026-10-03","autore":"Redazione Prodability","meta_title":"Fundamental Attribution Error: People or Processes?","meta_description":"The fundamental attribution error explains why companies blame the person instead of the system. How to diagnose the context before judging character at work.","keyword_principale":"fundamental attribution error","keywords_secondarie":"fundamental attribution error in the workplace, blaming people instead of the system, process problem or people problem, Lee Ross attribution error, Deming 94 percent system","tags":["Business processes","Leadership","Company culture","Org chart and roles"],"title":"Attribution error: why we blame people instead of processes","lunghezza":"12 min read","featuredVisual":{"kind":"image","src":"/article-assets/errore-attribuzione-crescita-azienda/en/fundamental-attribution-error.jpg","alt":"Attribution error: why we blame people instead of processes"}},"content":"# Attribution error: why we blame people instead of processes\n\nWhen a delivery falls through, is the problem the person who was handling it or the system that person was working in?\n\nThe immediate answer, almost always, is about the person: they're disorganized, they're not motivated, they don't have enough experience.\n\nSocial psychology has a name for this immediate answer. The fundamental attribution error is the tendency to explain someone's behavior by their character, underestimating how much the situation in which that behavior occurred weighs [1].\n\nIt is a mechanism that affects anyone who evaluates someone else's work: the professional with two team members, the business owner with twelve employees, the director who coordinates ninety.\n\nThe following sections reconstruct how this error works, how much it costs when it enters business decisions, and which questions take you from judging the person to diagnosing the system.\n\n## Recognize the attribution error before judging a person\n\nIn 1977 the social psychologist Lee Ross published an essay that would become a reference in the field: it describes the ordinary observer as an \"intuitive psychologist\" who diagnoses others with the same tools as a researcher, but without the researcher's controls [1].\n\nThe main flaw of this intuitive psychologist is systematic: when observing a behavior, they attribute it to a stable characteristic of the person who performs it and overlook the conditions in which it happened.\n\nSomeone who is late is unreliable, not a person stuck in a process that depends on others. Someone who delivers imprecise work is careless, not someone who was never shown the expected standard.\n\nIt is worth distinguishing this error from a term it is often confused with. Confirmation bias concerns the information you look for: you notice the data that support an opinion you have already formed. The attribution error, by contrast, concerns the explanation you give for an observed behavior: it doesn't filter the evidence, it chooses the cause. The two mechanisms add up — first you attribute to character, then you collect the episodes that confirm that judgment.\n\nAn important clarification: recognizing the weight of the situation does not mean taking responsibility away from people. It means placing responsibility in the right spot, which is sometimes the person and other times the way the work was organized.\n\nOne question remains: how strong is this distortion really? The best-known answer comes from an experiment designed specifically to measure it.\n\n## The quiz experiment: when role is mistaken for talent\n\nIn that same year, 1977, Ross, together with Teresa Amabile and Julia Steinmetz, ran two experiments with 120 university students [2].\n\nThe setup is simple. Participants are randomly assigned to two roles: one asks general knowledge questions and the other tries to answer them. The questioner can pick questions from their own area of expertise; the answerer faces ground they don't know in advance.\n\nThe outcome is what anyone looking at the study design would expect: the questioners seem more knowledgeable. The relevant outcome is another one. Even outside observers, though they knew the roles had been assigned at random, judge the \"questioners\" more competent than the \"answerers\" [2].\n\nThe advantage was entirely in the role. The judgment landed on the person.\n\nIt should be stated precisely where this finding comes from: it is a laboratory experiment with university students, not a survey of companies. Its value for a business context is not statistical, it is illustrative: it shows that the distortion persists even when the role advantage is plain to see.\n\nA later review of the literature reconstructed the mechanisms that produce this effect: failing to perceive the situation, unrealistic expectations about how a normal person \"should\" behave, and incomplete corrections of the initial judgment [3]. This last point is the most useful in a business: correction requires attention and time, and under pressure attention is in short supply.\n\nThe key point: whoever holds a favorable position looks more capable, whoever holds an unfavorable one looks less capable, and in both cases the credit or the blame is assigned to the person.\n\nIn an organization, roles are not assigned at random as in the experiment. But they are still situations: some let you work well, others don't.\n\n## The cost of the attribution error: you replace the person and the problem comes back with the replacement\n\nThis is where the error stops being a matter of psychology and becomes a cost item.\n\nWhen something isn't working and the diagnosis stops at the person, the solution that follows is consistent: replace the person. You change the logistics manager, you hand the warehouse to someone else, you hire a new salesperson.\n\nThen comes the thing that makes the error visible: after a few months the replacement produces the same delays, the same inaccuracies, the same oversights as their predecessor.\n\nThe replacement has inherited the same situation: an unwritten process, a verbal handover, a tool inadequate for the volumes, a boundary of responsibility that nobody has defined. The behavior repeats because what repeats is the context that produces it.\n\nThe bill is twofold: the cost of the replacement — recruiting, onboarding, shadowing time, knowledge that leaves the company — and the cost of the original problem, which in the meantime has not been touched.\n\nAnd this is where the attribution error slows growth. A company that grows fast is a company that solves problems once. A company that attributes system problems to people solves them at every staff change, and starts from scratch every time.\n\n## Analyze the context before the person: four questions to ask\n\nThe correction does not require sophisticated tools. It requires reversing the order of the questions: first the situation, then the person.\n\nWhen a result is missed, four questions shift the analysis from character to context.\n\n- **Who got this same negative result before now?** If the problem has already come up with at least one other person in the same position, the likelihood that it depends on the individual's character drops sharply. It is the cheapest signal to collect and the one most often ignored.\n- **Did the person know what was expected, to what standard and by what deadline?** An expectation that was never stated is not an expectation: it is an assumption in the head of whoever coordinates the work.\n- **Did the person have the information, the tools and the authority to do it?** Many tasks fail because whoever carries them out has to ask permission from someone who isn't available, or use a tool designed for the volumes of three years ago.\n- **Who did the start of the work depend on?** A delay downstream is often the reflection of a delay upstream that nobody measured.\n\nA practical way to make this reversal systematic is to keep track of it. For every recurring problem, note the position where it occurred instead of the name of the person who experienced it: after a few months, the positions that generate problems regardless of who holds them become apparent.\n\nAnswering these questions almost always leads to the same place: does a process exist or not?\n\n## Check whether the process exists, is written down and can be carried out\n\nW. Edwards Deming, one of the founders of quality thinking, made an estimate that became famous: in his experience, about 94% of problems belong to the system, which is management's responsibility, and 6% to special causes [4].\n\nIt is important to read it for what it is: an assessment based on direct observation of many industrial organizations, not a statistical measurement. The exact proportion does not transfer to a small service business. The direction of the indication, however, does — and it coincides with that of the attribution error.\n\nChecking whether a problem belongs to the system means checking three levels, in order.\n\n**Does the process exist?** In many companies a task has been carried out for years without anyone ever establishing which steps it consists of. It is not a process: it is a habit, which lives in the head of the person who carries it out.\n\n**Is the process written down?** A process that isn't documented can't be taught, checked or improved. It can only be imitated, with the variations every imitation introduces. This is why bringing in a new person calls into question results that seemed secure. For how to put a task in writing so that others can carry it out, see the [guide to standard operating procedures](https://blog.prodability.com/procedure-operative-standard-sop/).\n\n**Can the process be carried out with the available resources?** A procedure that takes eight hours from someone who has five is not a procedure: it is a statement of intent. Michael Gerber, in his work on small businesses, describes exactly this situation as the recurring trait of a company that depends on people instead of on the system [5].\n\nThe key point: if even one of the three levels is missing, the problem belongs to the system, and replacing staff is unlikely to solve it.\n\nThere is, however, an opposite risk, just as costly.\n\n## Distinguish a system problem from a role or competence problem\n\nThe attribution error has a flip side: attributing to the system what really depends on the person. In that case you rewrite procedures that were already clear, while the situation stays the same.\n\nThree criteria help separate the two cases.\n\n- **Repetition across different people.** If the problem appears with whoever holds that position, it belongs to the system. If it appears with only one person, while others in the same position get different results, the hypothesis shifts to the person.\n- **A defined boundary of responsibility.** Many problems that look like competence problems are scope problems: two people each think the same task belongs to the other. Before evaluating a person, it is worth checking that their role is defined. On this, see the [guide to defining the responsibilities of a role](https://blog.prodability.com/definire-responsabilita-ruolo/).\n- **The gap between expected and actual results under normal conditions.** A result missed in an exceptional week says little. The same result missed under ordinary conditions, with a written process and available resources, points to a competence or role problem — which is addressed with training, shadowing or reassignment, not with a new procedure.\n\nWhen the diagnosis concludes that the problem lies with the person, the conclusion is legitimate. The difference is that at that point it is a conclusion, not a starting point.\n\n## The most common mistakes in diagnosing an organizational problem\n\nEven people who know the mechanism tend to fall back into three patterns.\n\n**Diagnosing under pressure.** Correcting the initial judgment requires attention, and attention is the first resource to run short when a customer is waiting for an answer [3]. Postponing the diagnosis by twenty-four hours, when the urgency allows it, often changes the conclusion.\n\n**Applying the analysis only to others.** The attribution error concerns the way you observe others; for your own missed results, the situational explanation comes naturally. A useful check is to ask yourself which explanation you would adopt if the same mistake had been made by the person doing the judging.\n\n**Confusing diagnosis with justification.** Analyzing the context is not a way to avoid difficult decisions. It is a way to make them on the right data: a person replaced after a complete system diagnosis is a well-founded decision, a person replaced on first impressions is a gamble.\n\n## Move from judging people to diagnosing the system\n\nThere is only one idea to take away: when a result is missed, the first question is about the situation, not the character. Judging the person remains possible, but it comes later — and only if the context has passed its checks.\n\nIt is a reversal of a few lines that changes the way an organization learns. Every problem attributed to the system and solved there produces an improvement that stays even when people change; every problem attributed to the person disappears with that person and comes back with the next one.\n\nThis reversal is also the first step in a broader effort: turning company habits into repeatable processes. For the overall picture, see the [guide to systemizing your business](https://blog.prodability.com/sistematizzazione-azienda/); for building the structure of positions, the [guide to the organizational chart](https://blog.prodability.com/organigramma-pmi/).\n\nA company that diagnoses the system before the people accumulates solutions instead of repeating them. It grows faster not because it works more, but because it stops solving the same problems twice — and the people who work in it feel they are evaluated for what they do, not for the position they happen to be in.\n\n## FAQ\n\n**What is the fundamental attribution error?**\n\nIt is the tendency to explain a person's behavior by their character, underestimating the weight of the situation in which that behavior occurred. The concept was formalized by the social psychologist Lee Ross in 1977, in the essay in which he describes the ordinary observer as an \"intuitive psychologist\" who diagnoses others without a researcher's controls [1].\n\n**How can you tell whether a business problem is about the process or the person?**\n\nThe cheapest criterion is repetition: if the same problem has come up with at least one other person in the same position, the most likely hypothesis is the system. Then three levels need to be checked: whether the process exists, whether it is written down and whether it can be carried out with the available resources. If any of the three is missing, the problem is organizational.\n\n**Does analyzing the context mean taking responsibility away from people?**\n\nNo. It means placing responsibility where it really lies. A diagnosis that concludes there is a competence or role problem remains a legitimate conclusion: the difference is that it comes after the context has been checked, not before. Difficult decisions are not avoided, they are made on more solid data.\n\n**What is the relationship between the attribution error and the speed of growth?**\n\nA company that attributes system problems to people solves them once for every person who holds that position. Improvements don't accumulate, they repeat. Fixing the system, by contrast, produces results that stay even when people change: it is this ability to accumulate that makes it possible to grow without redoing the same work every time.\n\n**Are confirmation bias and the attribution error the same thing?**\n\nNo. Confirmation bias concerns the information you look for: you mostly notice the data that support an opinion you have already formed. The attribution error concerns the cause you assign to an observed behavior. The two mechanisms tend to reinforce each other, though: first you attribute the problem to character, then you collect the episodes that confirm that judgment.\n\n## Sources and references\n\n1. Ross, L. (1977). The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process. In L. Berkowitz (Ed.), *Advances in Experimental Social Psychology*, 10, 173–220. Academic Press. https://doi.org/10.1016/S0065-2601(08)60357-3 — foundational reference.\n2. Ross, L. D., Amabile, T. M., & Steinmetz, J. L. (1977). Social roles, social control, and biases in social-perception processes. *Journal of Personality and Social Psychology*, 35(7), 485–494. https://doi.org/10.1037/0022-3514.35.7.485 — foundational reference.\n3. Gilbert, D. T., & Malone, P. S. (1995). The Correspondence Bias. *Psychological Bulletin*, 117(1), 21–38. https://doi.org/10.1037/0033-2909.117.1.21 — foundational reference.\n4. Deming, W. E. (1986). *Out of the Crisis*. MIT Center for Advanced Engineering Study, p. 315. — foundational reference. The 94%/6% split is presented by the author as an estimate based on his own experience, not as a statistical measurement.\n5. Gerber, M. E. (1995). *The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It*. HarperBusiness. — foundational reference.","path":"content/articles/art-0025/en.md","routePath":"fundamental-attribution-error","wordCount":2585,"imageMeta":{"/article-assets/errore-attribuzione-crescita-azienda/errore-attribuzione-crescita-azienda.jpg":{"w":1200,"h":825},"/article-assets/errore-attribuzione-crescita-azienda/en/fundamental-attribution-error.jpg":{"w":1200,"h":825}},"html":"<p>The immediate answer, almost always, is about the person: they're disorganized, they're not motivated, they don't have enough experience.</p>\n<p>Social psychology has a name for this immediate answer. The fundamental attribution error is the tendency to explain someone's behavior by their character, underestimating how much the situation in which that behavior occurred weighs <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>It is a mechanism that affects anyone who evaluates someone else's work: the professional with two team members, the business owner with twelve employees, the director who coordinates ninety.</p>\n<p>The following sections reconstruct how this error works, how much it costs when it enters business decisions, and which questions take you from judging the person to diagnosing the system.</p>\n<h2 id=\"recognize-the-attribution-error-before-judging-a-person\" class=\"article-h2-retrowave\"><span>Recognize the attribution error before judging a person</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"recognize-the-attribution-error-before-judging-a-person\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>In 1977 the social psychologist Lee Ross published an essay that would become a reference in the field: it describes the ordinary observer as an \"intuitive psychologist\" who diagnoses others with the same tools as a researcher, but without the researcher's controls <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>The main flaw of this intuitive psychologist is systematic: when observing a behavior, they attribute it to a stable characteristic of the person who performs it and overlook the conditions in which it happened.</p>\n<p>Someone who is late is unreliable, not a person stuck in a process that depends on others. Someone who delivers imprecise work is careless, not someone who was never shown the expected standard.</p>\n<p>It is worth distinguishing this error from a term it is often confused with. Confirmation bias concerns the information you look for: you notice the data that support an opinion you have already formed. The attribution error, by contrast, concerns the explanation you give for an observed behavior: it doesn't filter the evidence, it chooses the cause. The two mechanisms add up — first you attribute to character, then you collect the episodes that confirm that judgment.</p>\n<p>An important clarification: recognizing the weight of the situation does not mean taking responsibility away from people. It means placing responsibility in the right spot, which is sometimes the person and other times the way the work was organized.</p>\n<p>One question remains: how strong is this distortion really? The best-known answer comes from an experiment designed specifically to measure it.</p>\n<h2 id=\"the-quiz-experiment-when-role-is-mistaken-for-talent\" class=\"article-h2-retrowave\"><span>The quiz experiment: when role is mistaken for talent</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-quiz-experiment-when-role-is-mistaken-for-talent\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>In that same year, 1977, Ross, together with Teresa Amabile and Julia Steinmetz, ran two experiments with 120 university students <a class=\"article-citation\" href=\"#rif-2\">[2]</a>.</p>\n<p>The setup is simple. Participants are randomly assigned to two roles: one asks general knowledge questions and the other tries to answer them. The questioner can pick questions from their own area of expertise; the answerer faces ground they don't know in advance.</p>\n<p>The outcome is what anyone looking at the study design would expect: the questioners seem more knowledgeable. The relevant outcome is another one. Even outside observers, though they knew the roles had been assigned at random, judge the \"questioners\" more competent than the \"answerers\" <a class=\"article-citation\" href=\"#rif-2\">[2]</a>.</p>\n<p>The advantage was entirely in the role. The judgment landed on the person.</p>\n<p>It should be stated precisely where this finding comes from: it is a laboratory experiment with university students, not a survey of companies. Its value for a business context is not statistical, it is illustrative: it shows that the distortion persists even when the role advantage is plain to see.</p>\n<p>A later review of the literature reconstructed the mechanisms that produce this effect: failing to perceive the situation, unrealistic expectations about how a normal person \"should\" behave, and incomplete corrections of the initial judgment <a class=\"article-citation\" href=\"#rif-3\">[3]</a>. This last point is the most useful in a business: correction requires attention and time, and under pressure attention is in short supply.</p>\n<p>The key point: whoever holds a favorable position looks more capable, whoever holds an unfavorable one looks less capable, and in both cases the credit or the blame is assigned to the person.</p>\n<p>In an organization, roles are not assigned at random as in the experiment. But they are still situations: some let you work well, others don't.</p>\n<h2 id=\"the-cost-of-the-attribution-error-you-replace-the-person-and-the-problem-comes-back-with-the-replacement\" class=\"article-h2-retrowave\"><span>The cost of the attribution error: you replace the person and the problem comes back with the replacement</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-cost-of-the-attribution-error-you-replace-the-person-and-the-problem-comes-back-with-the-replacement\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>This is where the error stops being a matter of psychology and becomes a cost item.</p>\n<p>When something isn't working and the diagnosis stops at the person, the solution that follows is consistent: replace the person. You change the logistics manager, you hand the warehouse to someone else, you hire a new salesperson.</p>\n<p>Then comes the thing that makes the error visible: after a few months the replacement produces the same delays, the same inaccuracies, the same oversights as their predecessor.</p>\n<p>The replacement has inherited the same situation: an unwritten process, a verbal handover, a tool inadequate for the volumes, a boundary of responsibility that nobody has defined. The behavior repeats because what repeats is the context that produces it.</p>\n<p>The bill is twofold: the cost of the replacement — recruiting, onboarding, shadowing time, knowledge that leaves the company — and the cost of the original problem, which in the meantime has not been touched.</p>\n<p>And this is where the attribution error slows growth. A company that grows fast is a company that solves problems once. A company that attributes system problems to people solves them at every staff change, and starts from scratch every time.</p>\n<h2 id=\"analyze-the-context-before-the-person-four-questions-to-ask\" class=\"article-h2-retrowave\"><span>Analyze the context before the person: four questions to ask</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"analyze-the-context-before-the-person-four-questions-to-ask\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The correction does not require sophisticated tools. It requires reversing the order of the questions: first the situation, then the person.</p>\n<p>When a result is missed, four questions shift the analysis from character to context.</p>\n<ul class=\"article-check-list\">\n<li><strong>Who got this same negative result before now?</strong> If the problem has already come up with at least one other person in the same position, the likelihood that it depends on the individual's character drops sharply. It is the cheapest signal to collect and the one most often ignored.</li>\n<li><strong>Did the person know what was expected, to what standard and by what deadline?</strong> An expectation that was never stated is not an expectation: it is an assumption in the head of whoever coordinates the work.</li>\n<li><strong>Did the person have the information, the tools and the authority to do it?</strong> Many tasks fail because whoever carries them out has to ask permission from someone who isn't available, or use a tool designed for the volumes of three years ago.</li>\n<li><strong>Who did the start of the work depend on?</strong> A delay downstream is often the reflection of a delay upstream that nobody measured.</li>\n</ul>\n<p>A practical way to make this reversal systematic is to keep track of it. For every recurring problem, note the position where it occurred instead of the name of the person who experienced it: after a few months, the positions that generate problems regardless of who holds them become apparent.</p>\n<p>Answering these questions almost always leads to the same place: does a process exist or not?</p>\n<h2 id=\"check-whether-the-process-exists-is-written-down-and-can-be-carried-out\" class=\"article-h2-retrowave\"><span>Check whether the process exists, is written down and can be carried out</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"check-whether-the-process-exists-is-written-down-and-can-be-carried-out\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>W. Edwards Deming, one of the founders of quality thinking, made an estimate that became famous: in his experience, about 94% of problems belong to the system, which is management's responsibility, and 6% to special causes <a class=\"article-citation\" href=\"#rif-4\">[4]</a>.</p>\n<p>It is important to read it for what it is: an assessment based on direct observation of many industrial organizations, not a statistical measurement. The exact proportion does not transfer to a small service business. The direction of the indication, however, does — and it coincides with that of the attribution error.</p>\n<p>Checking whether a problem belongs to the system means checking three levels, in order.</p>\n<p><strong>Does the process exist?</strong> In many companies a task has been carried out for years without anyone ever establishing which steps it consists of. It is not a process: it is a habit, which lives in the head of the person who carries it out.</p>\n<p><strong>Is the process written down?</strong> A process that isn't documented can't be taught, checked or improved. It can only be imitated, with the variations every imitation introduces. This is why bringing in a new person calls into question results that seemed secure. For how to put a task in writing so that others can carry it out, see the <a href=\"https://blog.prodability.com/en/standard-operating-procedures/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">guide to standard operating procedures</a>.</p>\n<p><strong>Can the process be carried out with the available resources?</strong> A procedure that takes eight hours from someone who has five is not a procedure: it is a statement of intent. Michael Gerber, in his work on small businesses, describes exactly this situation as the recurring trait of a company that depends on people instead of on the system <a class=\"article-citation\" href=\"#rif-5\">[5]</a>.</p>\n<p>The key point: if even one of the three levels is missing, the problem belongs to the system, and replacing staff is unlikely to solve it.</p>\n<p>There is, however, an opposite risk, just as costly.</p>\n<h2 id=\"distinguish-a-system-problem-from-a-role-or-competence-problem\" class=\"article-h2-retrowave\"><span>Distinguish a system problem from a role or competence problem</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"distinguish-a-system-problem-from-a-role-or-competence-problem\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The attribution error has a flip side: attributing to the system what really depends on the person. In that case you rewrite procedures that were already clear, while the situation stays the same.</p>\n<p>Three criteria help separate the two cases.</p>\n<ul class=\"article-check-list\">\n<li><strong>Repetition across different people.</strong> If the problem appears with whoever holds that position, it belongs to the system. If it appears with only one person, while others in the same position get different results, the hypothesis shifts to the person.</li>\n<li><strong>A defined boundary of responsibility.</strong> Many problems that look like competence problems are scope problems: two people each think the same task belongs to the other. Before evaluating a person, it is worth checking that their role is defined. On this, see the <a href=\"https://blog.prodability.com/en/define-roles-and-responsibilities/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">guide to defining the responsibilities of a role</a>.</li>\n<li><strong>The gap between expected and actual results under normal conditions.</strong> A result missed in an exceptional week says little. The same result missed under ordinary conditions, with a written process and available resources, points to a competence or role problem — which is addressed with training, shadowing or reassignment, not with a new procedure.</li>\n</ul>\n<p>When the diagnosis concludes that the problem lies with the person, the conclusion is legitimate. The difference is that at that point it is a conclusion, not a starting point.</p>\n<h2 id=\"the-most-common-mistakes-in-diagnosing-an-organizational-problem\" class=\"article-h2-retrowave\"><span>The most common mistakes in diagnosing an organizational problem</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"the-most-common-mistakes-in-diagnosing-an-organizational-problem\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Even people who know the mechanism tend to fall back into three patterns.</p>\n<p><strong>Diagnosing under pressure.</strong> Correcting the initial judgment requires attention, and attention is the first resource to run short when a customer is waiting for an answer <a class=\"article-citation\" href=\"#rif-3\">[3]</a>. Postponing the diagnosis by twenty-four hours, when the urgency allows it, often changes the conclusion.</p>\n<p><strong>Applying the analysis only to others.</strong> The attribution error concerns the way you observe others; for your own missed results, the situational explanation comes naturally. A useful check is to ask yourself which explanation you would adopt if the same mistake had been made by the person doing the judging.</p>\n<p><strong>Confusing diagnosis with justification.</strong> Analyzing the context is not a way to avoid difficult decisions. It is a way to make them on the right data: a person replaced after a complete system diagnosis is a well-founded decision, a person replaced on first impressions is a gamble.</p>\n<h2 id=\"move-from-judging-people-to-diagnosing-the-system\" class=\"article-h2-retrowave\"><span>Move from judging people to diagnosing the system</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"move-from-judging-people-to-diagnosing-the-system\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>There is only one idea to take away: when a result is missed, the first question is about the situation, not the character. Judging the person remains possible, but it comes later — and only if the context has passed its checks.</p>\n<p>It is a reversal of a few lines that changes the way an organization learns. Every problem attributed to the system and solved there produces an improvement that stays even when people change; every problem attributed to the person disappears with that person and comes back with the next one.</p>\n<p>This reversal is also the first step in a broader effort: turning company habits into repeatable processes. For the overall picture, see the <a href=\"https://blog.prodability.com/en/how-to-systemize-your-business/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">guide to systemizing your business</a>; for building the structure of positions, the <a href=\"https://blog.prodability.com/en/organizational-chart/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">guide to the organizational chart</a>.</p>\n<p>A company that diagnoses the system before the people accumulates solutions instead of repeating them. It grows faster not because it works more, but because it stops solving the same problems twice — and the people who work in it feel they are evaluated for what they do, not for the position they happen to be in.</p>\n<h2 id=\"faq\" class=\"article-h2-retrowave\"><span>FAQ</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"faq\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p><strong>What is the fundamental attribution error?</strong></p>\n<p>It is the tendency to explain a person's behavior by their character, underestimating the weight of the situation in which that behavior occurred. The concept was formalized by the social psychologist Lee Ross in 1977, in the essay in which he describes the ordinary observer as an \"intuitive psychologist\" who diagnoses others without a researcher's controls <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p><strong>How can you tell whether a business problem is about the process or the person?</strong></p>\n<p>The cheapest criterion is repetition: if the same problem has come up with at least one other person in the same position, the most likely hypothesis is the system. Then three levels need to be checked: whether the process exists, whether it is written down and whether it can be carried out with the available resources. If any of the three is missing, the problem is organizational.</p>\n<p><strong>Does analyzing the context mean taking responsibility away from people?</strong></p>\n<p>No. It means placing responsibility where it really lies. A diagnosis that concludes there is a competence or role problem remains a legitimate conclusion: the difference is that it comes after the context has been checked, not before. Difficult decisions are not avoided, they are made on more solid data.</p>\n<p><strong>What is the relationship between the attribution error and the speed of growth?</strong></p>\n<p>A company that attributes system problems to people solves them once for every person who holds that position. Improvements don't accumulate, they repeat. Fixing the system, by contrast, produces results that stay even when people change: it is this ability to accumulate that makes it possible to grow without redoing the same work every time.</p>\n<p><strong>Are confirmation bias and the attribution error the same thing?</strong></p>\n<p>No. Confirmation bias concerns the information you look for: you mostly notice the data that support an opinion you have already formed. The attribution error concerns the cause you assign to an observed behavior. The two mechanisms tend to reinforce each other, though: first you attribute the problem to character, then you collect the episodes that confirm that judgment.</p>\n<h2 id=\"sources-and-references\" class=\"article-h2-retrowave\"><span>Sources and references</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"sources-and-references\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<ol class=\"article-process-list\">\n<li>Ross, L. (1977). The Intuitive Psychologist and His Shortcomings: Distortions in the Attribution Process. In L. Berkowitz (Ed.), <em>Advances in Experimental Social Psychology</em>, 10, 173–220. Academic Press. <a href=\"https://doi.org/10.1016/S0065-2601(08)60357-3\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">https://doi.org/10.1016/S0065-2601(08)60357-3</a> — foundational reference.</li>\n<li>Ross, L. D., Amabile, T. M., &amp; Steinmetz, J. L. (1977). Social roles, social control, and biases in social-perception processes. <em>Journal of Personality and Social Psychology</em>, 35(7), 485–494. <a href=\"https://doi.org/10.1037/0022-3514.35.7.485\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">https://doi.org/10.1037/0022-3514.35.7.485</a> — foundational reference.</li>\n<li>Gilbert, D. T., &amp; Malone, P. S. (1995). The Correspondence Bias. <em>Psychological Bulletin</em>, 117(1), 21–38. <a href=\"https://doi.org/10.1037/0033-2909.117.1.21\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">https://doi.org/10.1037/0033-2909.117.1.21</a> — foundational reference.</li>\n<li>Deming, W. E. (1986). <em>Out of the Crisis</em>. MIT Center for Advanced Engineering Study, p. 315. — foundational reference. The 94%/6% split is presented by the author as an estimate based on his own experience, not as a statistical measurement.</li>\n<li>Gerber, M. E. (1995). <em>The E-Myth Revisited: Why Most Small Businesses Don't Work and What to Do About It</em>. HarperBusiness. — foundational reference.</li>\n</ol>","headings":[{"level":2,"text":"Recognize the attribution error before judging a person","id":"recognize-the-attribution-error-before-judging-a-person"},{"level":2,"text":"The quiz experiment: when role is mistaken for talent","id":"the-quiz-experiment-when-role-is-mistaken-for-talent"},{"level":2,"text":"The cost of the attribution error: you replace the person and the problem comes back with the replacement","id":"the-cost-of-the-attribution-error-you-replace-the-person-and-the-problem-comes-back-with-the-replacement"},{"level":2,"text":"Analyze the context before the person: four questions to ask","id":"analyze-the-context-before-the-person-four-questions-to-ask"},{"level":2,"text":"Check whether the process exists, is written down and can be carried out","id":"check-whether-the-process-exists-is-written-down-and-can-be-carried-out"},{"level":2,"text":"Distinguish a system problem from a role or competence problem","id":"distinguish-a-system-problem-from-a-role-or-competence-problem"},{"level":2,"text":"The most common mistakes in diagnosing an organizational problem","id":"the-most-common-mistakes-in-diagnosing-an-organizational-problem"},{"level":2,"text":"Move from judging people to diagnosing the system","id":"move-from-judging-people-to-diagnosing-the-system"},{"level":2,"text":"FAQ","id":"faq"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"When a delivery falls through, is the problem the person who was handling it or the system that person was working in?","tldrItems":null}