It seems like an inescapable law of nature, that the larger an organization becomes, the more inefficient it becomes. This is especially true with large corporations and governmental entities, where massive oversights and organizational flaws can go unnoticed for years, while in a mom-and-pop shop every employee's job makes sense and every penny allocated is accounted for. There are many reasons for this phenomenon, and many of them stem from the core principle of the individual worker's job duties becoming increasingly specialized and narrow as the operation grows in scale.
Back to mom and pop, the two of them could be the floor manager, accountant, HR, CEO, and many other things all at once. But once there are multiple locations with specialized products, suddenly each duty becomes so big that it necessitates a dedicated specialist. Accounting grows rapidly in complexity as an operation becomes more sophisticated, with more parties involved. Within these larger organizations, a common expression is 'the left hand doesn't know what the right hand is doing', and this really captures perfectly how necessary links in a process can unwittingly (or uncaringly) work against each other.
In an article I reviewed this week, Get Your Team to Work Across Organizational Boundaries by Brad Power, this issue is explored and strategies for addressing it are discussed. It is stated that teamwork across organizational boundaries is unnatural, that the natural tendency of organizations is to optimize locally — within a business unit or department, rather than optimizing for the global customer experience or the enterprise. A key driver of this problem is identified as disparity between local metrics for success conflicting with the organization's success as a whole. For example, a warehouse manager is not likely to identify an opportunity for company savings by contracting a third party warehouse and selling the company's.
Also, there is the potential of one team to undercut another in order to magnify their own successes, even if it drives failure for others. Such behaviors are often seen in call centers, where call duration is a primary metric, and therefore rewards customer service making unnecessary transfers to other departments in order to shorten their own calls at the cost of the customer's experience.
For an organization as a whole to begin addressing this disunity, unfortunately it often takes a crisis. Only when the company's feet are held to the fire, and senior leadership really drives the company's overall goals consistently, do these disparate parts of the team finally begin working in consort. However, it doesn't have to require this, as noted by Power. It can start by having leadership begin addressing the core issues head-on before a crisis is caused.
The article suggest having a workshop for a few days, taking key members of a variety of teams, and bringing them together for a common goal. At first, the group begins to identify the flow of the company's core service in a realistic and fundamental way. Perhaps from the customer's point of view, or from a spending perspective, some way that takes them out of their own personal role and gives their actions the context of their greater significance in the big picture. With input from all members, they can begin to see a cohesive picture and understand more clearly how their actions can help or hinder the overall effort.
Next, the workshop needs to focus on addressing problems in the system, as mentioned either by leadership or brought forth by the team members themselves. Often the best solutions come from the workers and not the managers, as they have insights that simply can't be obtained elsewhere. Interdependent parts of a process begin collaborating towards a common solution, and thus the law of nature begins to recede.
However, the workshop is only one step of a whole organizational change in strategy that must be followed through with. Ideas will only survive and manifest results when they can be stuck with by all that matter, and the workshop attendees must convince their team members of the logic of the plan they helped collaborate on. Management must support these new initiatives and develop drivers that reflect progress in the new direction that can be monitored.
Many reform efforts fizzle out after an initial push, and thus reinforcements and follow-up meetings should be had. A certain measure of flexibility is smart, as flaws in the plan that can be amended shouldn't be cause for the whole effort to fail. One way to reinforce a cohesive vision is through social media, an internal workplace platform.
These social media platforms have been employed by many companies in recent years, creating their own version of LinkedIn or Facebook for internal use. This provides opportunities for networking and collaboration, and a more informal way to voice concerns and opinions. The vision of unity and cohesion for the company can be better appreciated when these far removed team members can put a face to a name, and better understand their own place within the larger scope.
In my personal experience I have seen successes and failures at accomplishing this unity. A successful example would have to be efforts by the Air Force to create a sense of worldliness in its members. 'Cross pollination' trips are commonly taken where members of one base travel to another to shadow their counterparts, where both sides can understand and learn from each other. This allows for local inefficiencies to potentially be highlighted by the superior performance of the other party, a sense of networking and collaboration as members of the larger Air Force, and it can foster understanding of the process drivers that both sides are subject to.
An example of misguided efforts to unify members of multiple different teams would have to be the new hire training class I attended at one job I had. It provided a very extensive look at some of the company's processes from a higher perspective, giving an understanding of how some roles fit with each other. Unfortunately, this was almost a complete waste as the material was very out of date, and some of it seemed to be directed at a particular team, leaving many other teams unaware of the significance of their own role. The training ultimately left us more confused than when we came in. Needless to say, the trainer's awareness of the roles of their trainees can be useful information to have.
As for the social media aspect, Boeing has its own social media platform called inSite. This functions most similarly to LinkedIn from my personal experience, and seems to serve primarily as a way of looking up coworkers to learn more about them and the organization they belong to. This can serve as a resume of sorts, detailing career history and listing qualifications. In addition to the employee profiles, there are also groups where articles are shared and web meetings can be arranged. There are some groups based around particular career fields or programs aimed at fostering collaboration. In my experience, this platform is highly under-utilized and very few people I know make much use of it, so there is likely a lot of untapped potential.


