The 12 Habits Of Highly Collaborative Organizations

When it comes to the future of work and collaboration I’ve worked with and researched hundreds of companies. Collaboration is indeed a top priority for many business leaders but knowing what makes organizations successful can be a tricky thing.  

After all no two companies are like and their strategies and technologies can be quite different. In addition collaboration initiatives come from different departments with different budgets, they have different uses cases and corporate cultures, and different approaches, goals, and measures of success.  

So if there is so much variety here then how do we know what makes organizations successful?  The answer lies in chess.

The Secrets of Great Teamwork

Collaboration has become more complex, but success still depends on the fundamentals.

Today’s teams are different from the teams of the past: They’re far more diverse, dispersed, digital, and dynamic (with frequent changes in membership). But while teams face new hurdles, their success still hinges on a core set of fundamentals for group collaboration.

Making collaboration across functions a reality

Fast-changing global markets put a premium on simplifying processes radically and breaking through silos.

Companies have long struggled to break down silos and boost cross-functional collaboration—but the challenge is getting more acute. The speed of market change requires a more rapid adaptation of products and services, while customers increasingly expect an organization to present them with a single face.

Even well-established multinationals routinely fail to manage operations end to end. The result: interactions with customers are sluggish; complex, customized products are hard to create on time and on budget; and blocked lines of communication make new sales and distribution channels difficult to navigate.

The basic principles for improving performance—imposing stretch targets from the center, empowering cross-functional teams, standardizing processes, tightening up execution—are mostly familiar. But making these things happen is a different matter. In many companies, ownership of processes and information is fragmented and zealously guarded, roles are designed around parochial requirements, and the resulting internal complexity hinders sorely needed cross-business collaboration.

What’s more, in our experience, companies that apply traditional solutions (such as lean and business-process reengineering) either exhaust their managers with efforts to rework every process across business units or, by contrast, focus too narrowly within functions.

Our observations of 25 companies in a wide range of industries in Europe, Asia, and North America have led us to conclude that perspiration is as important as inspiration in addressing these challenges.

Here’s the story of how two companies launched new approaches successfully. One needed to focus narrowly to fix a critical process that compromised its core business. The other, swamped by the complexity of its processes, required a broad-based transformation.

The importance of teamwork

Healthy teams enjoy benefits that go far beyond the company’s bottom line.

Anyone who thought the rise of remote and hybrid work would would be the downfall of teamwork has probably changed their tune by now. The truth is, teamwork is more important than ever. 

“The use of teams and collaboration expectations have been consistently rising,” says Dr. Scott Tannenbaum, a researcher and president of the Group for Organizational Effectiveness. “And when I say teams, I’m talking about all types of teams, whether it’s stable work teams [or] whether it’s teams that now, in the current environment, are operating virtually.”

Information Management – Holschuld

Wikipedia – Information management uses the legal terms Holschuld (obligation to collect) and Bringschuld (obligation to deliver) for the information behavior of persons or personnel who have to collect information, messages or knowledge from the owner of the information in a timely and complete manner and in a suitable form or to forward it to another person.

According to the sender-receiver model, work instructions, service instructions or a manager must clarify in advance which information is required to be retrieved (pull) and for which information is required to be delivered (push) and who is responsible for the transmission of information. There is an obligation to deliver if the sender is the initiator of the information forwarding. In the case of an obligation to collect, the recipient is the initiator and must make an effort to obtain information from a source.

As a rule, information and messages are the responsibility of the person who received this information. He must decide to which addressees it is to be passed on. In hierarchical organizations, the reporting obligation (obligation to provide) is imposed on the respective lower level, which has to report to the higher level. Management must then inform the board accordingly. Since the supervisory board should obtain all relevant information in a better and more detailed manner, it has to actively demand the executive board’s obligation to provide it and to meet its obligation to collect it to a greater extent.

Information in the project – Holschuld or Bringschuld?

Holschuld from holen, to get and Schuld, obligation. You are obligated to get or ask for the information. Bringschuld from bringen, to bring, provide, give and Schuld, obligation. You are obligated to bring, provide, give the information.

“I didn’t know that!” – “But that’s on the intranet. You should have known that! After all, information is a debt to be collected!”

This or something similar is a dialogue that is heard again and again between project employees and project managers. Whereby instead of “Intranet” there can also be “Project drive”, “SharePoint” or another medium.

Is that really true? Is information in the project really the responsibility of the project staff?

I think the project manager (or the project office) makes things too easy here. I can’t throw all the information out at the employees’ door and then expect them to pick out the ones that are relevant to them. So that we understand each other correctly: the project manager can expect his employees to read meeting minutes or other periodicals regularly if they know where to find the latest issue.

But they won’t, and shouldn’t, bother to sift out “out of line” information that affects them from the jumble of information. That’s not their job. You should work on the project, any other approach would slow down the project.

One sentence. Twelve German dialects.

German is a difficult language to learn as it is, but there are more than 12 German dialects spoken within the country. Some don‘t sound like German at all. If you‘re studying German, think twice!

YouTube comments:

“Fun fact: Plattdeutsch is so far from Hochdeutsch that it is considered as a language of its own. Also, there are many variants of Plattdeutsch itself – some of which I cannot understand, although I grew up with Plattdeutsch. Often, it takes less than 50 kilometers to find a place where you hardly understand the dialect.”

“As an American who learned hochdeutsch fluently. It took me forever to understand what people were saying in Bayern.”

“As someone who can speak the dying Lorraine dialect, I appreciate the inclusion of Letzeburgisch. It is not exactly the same, but closer then any other dialect.”

“Fun fact. In Baden we alone have dozens of dialects, sometimes significantly varying from village to village.”

Holschuld. Bringschuld. German law.

Holschuld: get obligation. Bringschuld: deliver obligation.

What is the difference between a debt to collect, a debt to bring and a debt to send?
In the case of a debt to be collected, the place of performance is with the debtor – the owed item must be picked up there by the creditor.

In the case of an obligation to deliver, the place of performance or fulfillment is with the creditor. The debtor must therefore pay at the domicile of the creditor. If there is a debt to be sent, the debtor must also send it.

The distinction is particularly important when it comes to the question of transport or shipment costs and the question of the transfer of the risk of the loss of the goods (e.g. if a package is lost in the post).

Kleinstaaterei

Klein means small. Staaterei means states or statehood.

Kleinstaaterei is a generally pejorative German-language catchphrase for what is perceived as a particularly pronounced federal structure, particularly in relation to territorialization and federalism in Germany. As early as the beginning of the 18th century, early Enlightenment literature criticized German small-stateism and publicly expressed the wish for a nation state.

Thirty Years War

This episode of Ten Minute History (like a documentary, only shorter) covers the outbreak of the Bohemian Revolt which was what would eventually spiral out of control into the Thirty Years’ War.

The revolt was crushed fairly quickly but sparked intervention by Denmark, who didn’t do too well, and later Sweden who did very well. Both of these were aided by France who decided to get directly involved in 1635.

By 1648 the Holy Roman Empire lay in ruins, with Austria and Spain struggling to pay for the war and rebuild the Habsburg Empire. This war saw the rise of Sweden and France but most importantly saw the foundations of modern diplomacy built.

understand-culture
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.