It never ceases to amaze me how organizations kick themselves in the ass by making teamwork almost impossible.
John from Sales, Edna from Product Marketing and Paco from Customer Service are at one another’s’ throats. They were summoned into the big boss’ room and told to “get their act together and act like a team”. John has been promoting products that do not exist; Edna has been accused of ignoring customers’ unique needs (especially in low cost markets and the Japanese market) in her product road map and Paco keeps telling his customers that he will ask a design engineer from R&D to fix bugs, because his own department lacks the needed documentation and some of the features are “immature”. Customers have complained to the big boss that “no one in your organization gives the same answer”.
Thus the boss stressed the need for team work; however, he ain’t gonna get what he asked for.
The standard definition of a team is a group of people with shared common goals, mutual dependencies and a feeling of partnership. However, this definition is very misleading. Indeed mutual dependencies may exist, but these dependencies may not be acknowledged due to the very way that an organization is designed. As a result of poor design and the wrong assumptions, infighting, finger pointing, endless email threads and inter-departmental warfare predominate-not team work.
Back to the gang of 3. John, Edna and Paco are not a team. Indeed they may have a common goal, mutual dependencies and a feeling of partnership as expressed by some nebulous commitment to the company’s vision, but when the rubber hits the road, not only are their goals not aligned, but their mutual dependencies are unacknowledged. John needs to sell, Edna needs to produce a coherent product road map, and Paco needs to fix what does not work, or cool off the customer until a new fix is available. And above all, Paco, John and Edna need to make their respective bosses (not one another) look good.
The integration of organizational system for which John, Edna and Paco work is not to be downloaded to these three players; it is a matter of organizational design, prevention of sub system maximization, and allowing integration and trade-offs to be made at the lowest possible level. Example: John will sell only from the product road map, Edna will make this road map more flexible and Paco will ensure that his service agents have more product knowledge.
But this won’t happen, because the organization does not want it to happen. The basic assumption guiding the present dysfunction is that if John, Edna and Paco do their very best and over-perform in their specific areas, the organization will succeed. Nothing is farther from the truth.
1,678 total views