The business owner who shuttles between the shop floor and the office, the manager who covers for whoever is missing and the professional who reconstructs the client's request every time are all living the same script: the problem comes back, and only the person caught up in it changes.
\nAn organizational problem is a recurring problem that happens because the way the work is designed makes it likely, no matter who does it.
\nIn Italy, 78.9% of companies with at least 3 employees have between 3 and 9 [1]: at that size, and often beyond it, every problem has a first and last name, and calling it \"personality\" is the shortest way out.
\n\n\nAn organizational problem is recognized not by how serious it is but by how often it repeats: if the same problem keeps coming back with different people, the cause is not in the people but in how the work is organized.
\n
This article shows examples by area, the signals that come before the cost, the points where information gets lost and when to move from recognizing the problem to applying a method.
\nThe same delay, with two different people in the same position: is it a problem with the people or with the position?
\nIn Italy, 83.3% of micro-enterprises are controlled by one person or one family [1]: where the owner is also the one who decides, the problem with the position lands on the table with a person's name on it.
\nA company that has no name for organizational problems calls them three things: personality (\"that's just how he is\"), timing (\"we're going through a busy period\"), bad luck (\"it just happened\").
\nThe three labels have the same effect: they close the discussion without opening any action.
\nThis section defines the organizational problem starting from what the three labels hide and proposes a one-question test you can repeat on any problem: what happens if someone else is in that person's place?
\nIt closes by drawing the lines against the terms most often confused with it: competence problem, unexpected event, critical issue, communication problem.
\nThe ISTAT figure, from Italy's national statistics institute, concerns companies with 3 to 9 employees in 2022 [1]; the link with concentrated decision-making is an editorial interpretation.
\nThe three labels cover the same thing: a hand-off that lacks a piece of information, a criterion or an owner.
\nIf the problem comes back with another person, the problem belongs to the position; if it disappears, it is a matter of that person's competence.
\nAn unexpected event is the episode; an organizational problem is the rule that generates it.
\nA critical issue is the same thing in management language; a communication problem is a subset of it: the information exists but does not reach where it is needed.
\nThe model that holds roles and hand-offs together is on the page about business organization: here the only task is recognizing the problem.
\nOnce you have established that it belongs to the position, what remains is to see what shape it takes in each area.
\nA late order on the shop floor and a stalled quote in the office: are they two different problems or the same problem in two rooms?
\nMore often than it seems, it is the same one: a piece of information stuck at a hand-off that has no owner. Eight examples, one criterion — if the problem changes person and stays, it belongs to the organization.
\n\n\nThe criterion does not change from one area to another: a problem that keeps coming back with different people is not a people problem, it is a problem with how the work is organized.
\n
In a 15-person family-owned contract machining company, the long-standing customer's rush order jumps the production sequence every other week.
\nThe business owner calls it \"that customer is just like that,\" the shop floor manager calls it \"sales overpromises,\" and the salesperson calls it \"production is slow.\"
\nThree names for the same missing hand-off: there is no shared criterion for deciding what goes first.
\nThe table below collects eight cases of this kind, two per area, with the signal that makes them visible and the wrong name they get today.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n| Area | Signal (how it shows up) | Misreading (the name it gets today) |
|---|---|---|
| Production | the rush order jumps the sequence every other week | \"that customer is just like that\" |
| Production | a part is remade because the specification was given verbally | \"carelessness\" |
| Office | a quote is stuck for three days waiting for a piece of data | \"he's busy, he's on vacation\" |
| Office | two versions of the same file in circulation | \"confusion\" |
| Sales | the delivery date promised over the phone without checking | \"overoptimistic salesperson\" |
| Sales | the customer calls the business owner directly | \"habit\" |
| People | after three months the new hire still asks \"who do I ask?\" | \"he's slow\" |
| People | the long-time team member is the only one who knows how to do a job | \"irreplaceable\" |
scroll the table →
\nIn production, besides a priority criterion, there is no format for the hand-off from office to shop floor: the outcome does not change with the operator.
\nIn the office, the information has a single holder and there is no shared reference: the quote stalls whenever anyone is absent.
\nIn sales, there is no check with production before the promise, and the customer's point of contact is not defined.
\nOn the people side, onboarding is not designed and knowledge is not documented: the new hire and the irreplaceable team member are the same missing hand-off.
\nAs the company grows, hand-offs multiply, and with them the points where work stops: this is the Symptom growth increases confusion.
\nAn isolated incident has a date; an organizational problem has a frequency.
\nDoes a critical issue show up first in the income statement or in the calendar?
\nIn the calendar, months ahead: the margin records the critical issue once it has finished costing. The Treccani dictionary also gives the Italian word for \"critical issue\" (criticità) the meaning of \"a single problem, a single critical situation\" [2]: it is the word management language uses for the same thing described in the previous section, without the person's name.
\nA critical issue shows up in three places before it reaches the numbers: in timing (what systematically takes longer than planned), in questions (\"who do I ask?\", \"where is it?\") and in exceptions (what has been handled \"just this once\" for three quarters).
\nThis section turns the three places into a diagnostic grid by area: for each of the four areas, an observable signal, a check question with a countable answer and a first action.
\nThe grid does not ask for opinions, it asks for counts, and that is why it works even where the business owner and team members disagree about the causes.
\nIt is filled in every quarter; a signal goes in if it has occurred at least twice.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n| Area | Signal | Check question | First action |
|---|---|---|---|
| Production | an order jumps the sequence | how many times in the quarter, decided by whom | count the jumps for one month |
| Office | a quote stuck waiting for a piece of data | where it stops, who notices, after how many days | give the hand-off an owner |
| Sales | a date promised without checking | how many deliveries rescheduled after the promise, in the quarter | check the date with production before giving it |
| People | a job only one person knows how to do | how many activities stop if that person is away for a week | write down the sequence of the job |
scroll the table →
\nFor the office, the completed line says: nine quotes stuck in the quarter, eight waiting for a supplier's cost, six discovered when the customer called back.
\nThe first action is not a method: an owner for the request to the supplier, a two-day deadline, the count repeated the following quarter.
\nA critical issue that has been counted is already a recognized problem; what remains is to understand at which hand-off the information was lost.
\nIs information lost more often because it is missing, or because it exists but does not reach where it is needed?
\nThe second case is the most frequent and the least visible: Morrison and Milliken (Academy of Management Review, 2000) describe \"organizational silence\" — the widespread withholding of information about potential problems by the people who do the work — as a collective phenomenon, produced by the context, not as a choice made by individuals [3].
\nA communication problem in a company is rarely a problem of quantity: there are meetings, and there are chats too.
\nIt is a problem of hand-offs: five points where information changes hands and, in changing hands, loses a part.
\nFrom the customer to whoever takes the request; from the office to the shop floor; between one person and the one who takes over; from the shop floor to whoever decides; from the decision made to whoever has to carry it out.
\nThis section describes, for each point, what usually gets lost, how to recognize it and the question to ask to find out whether the hand-off has a format or is left to memory.
\nHow to act on each hand-off is the subject of internal business communication.
\nWhen there are many hand-offs without a format, the lost information comes back as an emergency.
\nIs a company with many emergencies a company that works hard or a company that is badly organized?
\nThe two get confused because the second produces the first: Repenning and Sterman (California Management Review, 2001) show that the time spent fighting fires is taken away from what would prevent the next one, and they call the cycle in which working harder generates more emergencies the \"capability trap\" [4].
\nThe business owner who spends the morning on the shop floor unblocking the machine, the delivery and the supplier, and the afternoon in the office catching up on what the morning pushed back, does not have a full day: he has an organization that produces emergencies at a steady pace.
\nA single emergency is an unexpected event; an emergency that keeps coming back in the same form is an organizational problem that has found a way to be treated as an unexpected event.
\nThis section gives the signals for telling the two cases apart and points to two further readings: the difference between unexpected and unpredictable, and problem triage, the filter that decides which emergencies deserve an analysis.
\nThere are four signals.
\nIt has a schedule: it comes back on Monday morning, at the end of the month, at the close of every job.
\nIt has a name: the same customer, the same machine, the same supplier.
\nIt has only one person who can unblock it: the business owner, and when the business owner is in the office, the machine waits.
\nIt has a reward: whoever puts out the fire gets noticed, whoever prevents it does not [4], and the cycle feeds itself.
\nIn Italy, in 2024, hours worked in the market sectors grew by 2.3% and value added by 0.4%, with labor productivity down 1.9% [5]: this is not proof that companies are fighting fires, it is the context in which the extra hour does not pay off.
\nThe difference between unexpected and unpredictable is covered in the dedicated Symptom, how to reduce unexpected events.
\nProblem triage — recurrence, impact, spread, cost of not acting — selects the emergencies to bring into analysis.
\nDoes every recognized problem deserve a structured analysis, or only some?
\nOnly some, and choosing them is already part of the method: treating every anomaly as a case to analyze paralyzes the company as much as ignoring them all.
\nRecognizing an organizational problem does not yet tell you what to do about it.
\nThere are three paths, in order of cost: a direct correction when the missing hand-off is obvious and the problem is isolated; a cause analysis when the problem repeats and there is more than one plausible cause; an intervention on the organizational model when the recognized problems are many and similar.
\nThis section stops at choosing the path: the methods have their own pages, and so does the organizational model.
\nA direct correction is the first action from the grid carried through to completion: owner, format, verification date.
\nRoot cause analysis is a family of methods: with more than one plausible cause, you start from the Ishikawa diagram, and the guide to business problem solving compares them.
\nAn intervention on the model makes hand-offs independent of people: it is the subject of business systemization and business organization.
\nThe criterion is in the grid: obvious cause and low count, correction; high count and conflicting causes, analysis; the same line filled in across three areas, model.
\nOnce the path is chosen, what remains is to avoid the mistakes of recognition.
\nDoes hiring one more person fix an organizational problem or hide it?
\nOften it hides it, at the highest available price: in 2024, 47.8% of the hires planned by Italian companies were considered hard to fill, compared with 26.4% in 2019 [6].
\nFive mistakes recur among people who are starting to recognize organizational problems, and four of them come from the rush to close.
\nLooking for the culprit instead of the hand-off; calling \"a busy period\" something that has lasted three quarters; covering with a new hire work that stops for lack of a criterion; cataloging everything without deciding anything; buying a tool for a hand-off problem.
\nThis section describes how each one shows up and the move that avoids it, with particular attention to the family business, where the easiest culprit to find is also the hardest to name.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n| Mistake | How it shows up | Correction (the move that avoids it) |
|---|---|---|
| Looking for the culprit instead of the hand-off | \"he's the one making mistakes,\" said under one's breath if he's a family member | the different-people test before judging |
| Calling \"a busy period\" something that has lasted three quarters | \"we're going through a busy period,\" at every closing | count: three quarters have a schedule |
| Covering a missing hand-off with a new hire | the new person inherits the same hand-off with no format | first the hand-off, then the person |
| Cataloging everything without deciding anything | forty critical issues on a list, not one decision | the grid is a filter: move on to triage |
| Buying a tool for a hand-off problem | a new management software and the same stuck quote | an owner for the hand-off, then the software |
The first mistake has a basis in the numbers: among small Italian companies with 10 to 49 employees, 74.5% are under personal or family control [1], as is the majority of Italian companies.
\nThe third is the most costly: in Italian manufacturing, 53.7% of the hires planned for 2024 were hard to fill, and for 33.6% of the sector's total planned hires the reason was a lack of candidates [6], so the person arrives late and at a high cost.
\nThe different-people test is a criterion for interpretation, not a measurement: in a micro-enterprise where the position has only one possible person, it applies hypothetically (\"if there were someone else\"), with less force.
\nMorrison and Milliken's organizational silence [3] is a general model, and Repenning and Sterman's cycle comes from industrial and product development cases [4]: applying them to a 15-person family business is an editorial proposal, not a finding from the literature.
\nThe ISTAT productivity figure is an aggregate of Italy's market sectors [5]: it describes the context, not individual companies.
\nThe examples by area and the completed line of the grid are typical cases constructed by the editorial team, not survey data: they serve to recognize the pattern, not to estimate its frequency.
\nThe grid counts signals, it does not weigh their cost: choosing what to analyze remains a matter for triage and for the methods in the problem-solving guide.
\nThe ones that keep coming back with different people at the same hand-off: rush orders that jump the sequence, quotes stuck waiting for a piece of data, dates promised without checking, jobs that only one person knows how to do.
\nThe table by area in this article collects eight of them, two for each of the areas production, office, sales and people.
\nA communication problem is a subset of an organizational problem: the information exists but does not reach where it is needed, because one of the five hand-offs between customer, office, shop floor, decision and execution has no format.
\nWith the different-people test: if someone else were in that person's place, with the same instructions and the same time, would the problem come back?
\nIf yes, the problem belongs to the position; if not, it is a matter of the person's competence, and the way forward is on-the-job coaching.
\nChoose the path based on the count and the causes: a direct correction if the missing hand-off is obvious, a cause analysis if the problem repeats with more than one plausible cause, an intervention on the model if the problems are many and similar.
\nThe methods are compared in the guide to business problem solving.
\nA problem is organizational if it keeps coming back with different people in the same position: that is the test to run before any judgment.
\nThe four areas to look in are production, office, sales and people, with two examples per area and the wrong name they get today.
\nBefore the numbers, a critical issue shows up in three places — timing, questions and exceptions — and the diagnostic grid turns them into counts by area.
\nInformation gets lost at five hand-offs, from the customer to whoever carries out the decision, and for each one the question is whether the hand-off has a format or is left to memory.
\nAn emergency that has a schedule, a name, only one person who can unblock it and a reward for whoever puts it out is a symptom, not a workload.
\nThere are three paths after recognition, in order of cost: direct correction, cause analysis, intervention on the model.
\nAn organizational problem is not a serious problem: it is a problem that comes back.
\nRecognizing it means you stop asking who made the mistake and start asking at which hand-off the work stops, whoever happens to be in that position.
\nThe examples by area, the diagnostic grid and the five points where information gets lost serve this purpose: seeing the problem while it is still in the calendar and not yet in the margin.
\nThe next step depends on what you found.
\nTo choose the analysis method, the guide to business problem solving compares the tools, from PDCA to root cause analysis.
\nTo act on the model, business systemization describes how to make hand-offs independent of people.
\nA company that recognizes its own organizational problems changes its character: emergencies tend to decrease in number even before they decrease in severity, the business owner goes back to deciding instead of unblocking, and the long-time team member can be away for a week without the work stopping.
\nIt is not a company without problems: it is a company that calls them by their name.
\n\n[1] ISTAT, \"Censimento permanente delle imprese 2023: primi risultati\", press release, November 14, 2023 (reference year 2022; about 280,000 responding companies, representative of 1,021,618 companies with at least 3 employees). Available at: https://www.istat.it/comunicato-stampa/censimento-permanente-delle-imprese-2023-primi-risultati/ — PDF: https://www.istat.it/it/files/2023/11/REPORTCensimprese.pdf
\n[2] Treccani, \"criticità\", Vocabolario on line, Istituto della Enciclopedia Italiana. Available at: https://www.treccani.it/vocabolario/criticita/
\n[3] Morrison, E. W., Milliken, F. J., \"Organizational Silence: A Barrier to Change and Development in a Pluralistic World\", Academy of Management Review, vol. 25, no. 4, 2000, pp. 706-725. Available at: https://doi.org/10.5465/amr.2000.3707697
\n[4] Repenning, N. P., Sterman, J. D., \"Nobody Ever Gets Credit for Fixing Problems That Never Happened: Creating and Sustaining Process Improvement\", California Management Review, vol. 43, no. 4, 2001, pp. 64-88. Available at: https://doi.org/10.2307/41166101 — Open-access PDF (MIT): https://web.mit.edu/nelsonr/www/Repenning=Sterman_CMR_su01_.pdf
\n[5] ISTAT, \"Misure di produttività – Anni 1995-2024\", press release, December 12, 2025. Available at: https://www.istat.it/comunicato-stampa/misure-di-produttivita-anni-1995-2024/
\n[6] Unioncamere – Ministero del Lavoro e delle Politiche Sociali, Sistema Informativo Excelsior, \"La domanda di professioni e di formazione delle imprese italiane nel 2024\", 2025. Available at: https://excelsior.unioncamere.net/pubblicazioni/2024/domanda-di-professioni-e-di-formazione-delle-imprese-italiane-nel-2024 — PDF: https://excelsior.unioncamere.net/sites/default/files/pubblicazioni/2024/Domanda_professioni_formazione_imprese.pdf
","headings":[{"level":2,"text":"When a problem is organizational and when it is not: the different-people test","id":"when-a-problem-is-organizational-and-when-it-is-not-the-different-people-test"},{"level":2,"text":"8 examples of organizational problems by area: how to tell them apart from an isolated incident","id":"8-examples-of-organizational-problems-by-area-how-to-tell-them-apart-from-an-isolated-incident"},{"level":2,"text":"How to spot critical business issues before they show up in the numbers","id":"how-to-spot-critical-business-issues-before-they-show-up-in-the-numbers"},{"level":2,"text":"Where information gets lost: the 5 hand-offs behind communication problems in a company","id":"where-information-gets-lost-the-5-hand-offs-behind-communication-problems-in-a-company"},{"level":2,"text":"The company that keeps fighting fires: when constant emergencies are a symptom","id":"the-company-that-keeps-fighting-fires-when-constant-emergencies-are-a-symptom"},{"level":2,"text":"From symptom to method: when a correction is enough and when you need a cause analysis","id":"from-symptom-to-method-when-a-correction-is-enough-and-when-you-need-a-cause-analysis"},{"level":2,"text":"The most common mistakes in recognizing organizational problems, and how to avoid them","id":"the-most-common-mistakes-in-recognizing-organizational-problems-and-how-to-avoid-them"},{"level":2,"text":"Limitations and conditions of applicability","id":"limitations-and-conditions-of-applicability"},{"level":2,"text":"FAQ","id":"faq"},{"level":3,"text":"What are the most common organizational problems in a company?","id":"what-are-the-most-common-organizational-problems-in-a-company"},{"level":3,"text":"What is the difference between an organizational problem and a communication problem?","id":"what-is-the-difference-between-an-organizational-problem-and-a-communication-problem"},{"level":3,"text":"How can you tell whether a problem lies with the people or with the organization?","id":"how-can-you-tell-whether-a-problem-lies-with-the-people-or-with-the-organization"},{"level":3,"text":"What should you do after identifying an organizational problem?","id":"what-should-you-do-after-identifying-an-organizational-problem"},{"level":2,"text":"Operational summary","id":"operational-summary"},{"level":2,"text":"Conclusion","id":"conclusion"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"A team member who makes the same mistake at the same step for the second time: is that an attention problem, or is it the company that has an organizational problem?","tldrItems":null}