One Problem Is Never Just One Problem

One Problem Is Never Just One Problem
Why what looks like one organizational issue may be part of something much larger
The main issue is timing, since we only become aware of organizational problems when they have become difficult to ignore. The second problem is more difficult to detect: even after we do notice it, we usually look at it as an isolated issue. A resignation is dealt with as a resignation. A complaint is given its own file. A drop in output is turned into a discussion about productivity rather than being seen as part of a bigger picture. We treat individual symptoms as if each one has its own separate story, whereas the reality is generally not so neat.
Most organizations are designed to divide reality according to departments. A staffing shortage is then treated as a scheduling issue. An increase in absenteeism is dealt with as an HR matter. Low morale is referred to as a wellness issue. Turnover has its own dashboard, usually being looked at in a separate meeting from the one where burnout is discussed. Each problem is assigned to its own responsible person, gets its own explanation, and is sometimes given its own consultant. Yet the organization as a whole does not go through all of these issues in separate departments. The same root cause that is behind the staffing shortage is often also the cause of the turnover, the absenteeism, and the gradual decline in morale. The organization’s structure just doesn't state this.
Music provides a good example. If you play a single note by itself it doesn't tell you much; it's only when several notes are heard while a melody and its meaning become clear. Similarly, organizational information often functions in the same way. A single data point may be interesting on its own, but meaning seldom exists in any one piece of information by itself; rather, it is found in the relationships between the pieces, in the changes that occur when you stop reading them one at a time and begin to listen to what they say when taken together.
The way things are viewed causes leaders to ask different questions. The first and most frequently asked question in an organization is What happened? Although this is a reasonable starting point, it is seldom the most helpful one. The next better question comes shortly after: What else is happening? And the most important question of all is the one that is almost never asked: Could these things be connected? Most organizations content themselves with the first question. Very few go on to ask the third.
There is no need to give up the way most organizations are currently arranged since departments have valid reasons for existing and specialization does in fact have value. All that is required is a habit which most leaders never develop, that of laying the information side by side with each other before deciding what it means. The error we should avoid is not failing to spot a problem; the greater mistake is to notice the problem, understand it by itself, and then stop there.






Join the discussion
Members can read and add comments on every article.