What is a “Collaborative Organization” Anyway?
What is a “Collaborative Organization” Anyway?
DevOps is all about collaboration and breaking down silos, so what does a real collaborative organization look like?
Join the DZone community and get the full member experience.Join For Free
Whatever new awaits you, begin it here. In an entirely reimagined Jira.
Over the last few years, I’ve spent a lot of time writing and talking about the benefits of collaboration and the technology to support collaboration in its many forms. What has become clear during that time, however, is just how nebulous and confusing the term “collaboration” is. But while it’s easy to get caught up in defining what “collaboration” itself actually means (and yes, MWD has its own definition too!), I’ve come to realise that it’s not necessarily the act of collaborating that needs defining, but what this means in the context of an organization that is looking to be more collaborative. So perhaps the question should be – What does a collaborative organization look like?
It is highly unlikely that there is no collaboration taking place in your organization at present people are no doubt talking to each other in the office or on the phone, sitting in meetings to discuss particular activities or events, or working together on particular projects or documents, for example. However, evidence of anecdotal collaboration such as this is not the same as being a collaborative organization; this suggests an underlying culture of collaboration which drives all activity within the organization. In real terms, I think there are three important characteristics that help to define a collaborative organization:
A networked and non-hierarchical organization structure
A culture of openness, honesty and trust
An engaged and valued workforce.
A Networked and Non-hierarchical Organization Structure
A collaborative organization is typically the antithesis of the traditional command-and-control organization where there is a rigid hierarchy of roles and management authority. Instead, the organization structure is much more fluid and flat , with individuals given greater responsibility to make decisions appropriate to their role and the task concerned, without the bottlenecks caused by layers of management approvals and red tape. Teams are defined not by their position within the organization, but by what they are trying to achieve whether this is a specific project or an on-going business process and so tend to be more transient, with teams made up of a collection of different roles required to complete the task or tasks, rather than simply a group of peers of the same role, for example. Similarly, individuals are defined not by their role, their seniority, or even their team, but by the set of skills, knowledge and experience they can contribute to a particular task, discussion or activity.
Rather than layers of management which focus on controlling behaviour and driving activity, there is an emphasis on providing leadership setting targets for individuals and teams, and then providing the appropriate motivation and support to help them achieve those targets. One of the benefits of less-structured, non-hierarchical collaborative working environments is that new ideas can be executed more quickly, enabling the organization to respond rapidly to competitive challenges or market pressures. New projects and teams can get up and running quickly, without the need for major reorganization, creating new dynamics within the business. Communication is also much faster, with central news able to reach individuals directly, rather than being filtered through management, and information able to flow more easily throughout the organization via a peer-to-peer channel.
A Culture of Openness, Honesty and Trust
In a collaborative organization, every individual has a voice, and is encouraged to express their opinion without fear of stepping on the toes of more senior people. This is less about people being given a forum to publicly criticise their peers, managers or leaders, but about creating an environment where openness, sharing and discussion is central to everything that takes place, be that the announcement or definition of a new strategy or direction for the company, a proposed change to a process in a particular part of the business, or simply an event, news item or suggestion at a local level. This does not mean to say that every activity, every decision within a collaborative organization is necessarily always achieved collaboratively, but that there is a common bond of trust between peers, between leaders and employees, so that there is no sense of threat or inconvenience from inviting others to contribute an opinion, or provide feedback, and people are confident and willing to do so when asked.
An Engaged and Valued Workforce
In a collaborative organization, employees are given greater responsibility, and are given the opportunity to voice their opinion, to engage with peers and managers and in so doing have a say in the way things are done and the direction the company is taking. The result is a workforce that is much more interested in the organizations fortunes, that cares whether or not the company achieves its goals, and that feels a collective sense of ownership and involvement in the process of achieving those goals. This empowered workforce has much greater loyalty to the organization as a result, and so is less likely to churn frequently as individuals seek to gain greater levels of responsibility, or find an employer who better values their commitment.
Clearly, while most organizations can show evidence of some collaborative behaviour, the majority have some way to go before they can honestly say they check all three of these boxes. It’s a long, arduous journey in some cases, but those who have done it confirm it is worth the effort in the long run.
Published at DZone with permission of Angela Ashenden , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.