Promoting Interdepartmental Teamwork for More Efficient Problem-Solving

Solving Problems in Silos

Successful companies aim to build autonomous teams that are self-sufficient and take ownership of their problems. But is there such a thing as too much autonomy? Are excessively autonomous teams missing out on the benefits of inter-team collaboration?

"Are excessively autonomous teams missing out on the benefits of inter-team collaboration?"

While having teams solve their own problems is the desired behavior, a lack of communication can lead to them missing out on valuable external input. Sometimes these inputs can lead to faster, better solutions.

Cultivating Teamwork in Problem-Solving

Complex problems should be communicated within the department. Trying to solve a challenge entirely within a team—when there are other qualified people available for help—can be unnecessarily time-consuming.

Here’s our system for fostering interdepartmental collaboration for problem-solving:

Step 1: Publishing a problem statement. When a team believes that additional help would be useful, they share a problem statement with the entire department. This consists of a short description of the problem and the requirements for the solution. Teams can present these in our regular IT workshops that are open to all our engineers. We ask, who wants to contribute? Who has relevant knowledge and experience in such problems?

Step 2: Collaborating via confluence papers. We create a confluence page for the problem, where anyone can contribute their thoughts and ideas on potential solutions. People can also upvote an existing solution. Anyone who writes or votes is added as a contributor.

Step 3: Sifting through the proposals. We hold a kickoff meeting where we invite all the contributors, discuss the proposals, and agree on a maximum number of three solutions.

Step 4: Deciding on the best solution. We form a work group for each proposal. The groups evaluate the different tools that we have at our disposal and examine ways to execute the given solution. Afterward, they present their findings and we collectively decide on a solution.

Step 5: Executing the solution. Lastly, one of our product development teams will take ownership of implementing a proof of concept for the chosen solution– with the help of the former workgroup– into our product. At that stage, the process returns to our regular workflow.

It Helps to Share Your Problems

• Bringing up problems to the wider team is a great opportunity to extract insight from a large number of people. People often overlook the breadth of knowledge within their department. Individuals with seemingly irrelevant titles can unexpectedly come up with the best solutions. Perhaps they had past experience in that area, or they have a personal interest that is unknown to you.
• Collectively trying to solve a problem is a great way to intrinsically motivate people; ultimately, it always brings good results.