The importance of knowledge alignment in outsourcing development models

by yaniskes

Dear readers, business and IT specialists, I’d like to share with you a few insights on the importance of knowledge and information that indirectly impact product quality and performance in software development outsourcing models.

I’m not sure how it will sound, but I advocate that all team members from CTO to an intern should engage in transitions of any information. Everyone in the remote team should be aware of the CEO’s vision, company goals, initiatives, and the grounds of their discoveries. As basic as it sounds, I’d still ask: why is it so important to pass around indirect information in a company with an outsourced development team?

Engineers, product, and marketing departments that reside in the same space have much more communication. And it’s not only about information passing verbally or electronically within the same environment, but it is also important to note that the responses between different management or engineering tiers are faster, which allows the teams to make quick and appropriate decisions.

How missing information affects product

Software engineer in outsourced team

Now let’s take a deep dive into an outsourced model and see how information gets missed, distorted, and how it affects decisions and the product itself. No matter how perfect and detailed the requirements are, there will always be some questions flowing in all directions. It is typical behavior in any organizational structure, but it is the most critical in outsourcing models. An important fact to remember: the more extended responses – the fewer clarifications will be asked. When engineers get blocked, they try to solve the problems faster with the team lead, project manager, or on their own, if the owner of the spec is not available, let’s say because of some time difference. Some team members won’t even realize that there might be another underlined meaning and will proceed with their assumptions. Some engineers may slightly debate a low priority change and still move with the best of their knowledge to progress. As a result, the work may deviate from expectations. In this case, the tech debt is unavoidable, which is not just an extra cost for the company, but also it shakes the technical base and may require refactoring in the future.

Why is this happening

To fix communication between the teams, we first have to understand the source of miscommunication. And this is, of course, the lack of information and non-real-time connection. To have a feature built properly, we need to ensure that the solution links to the problem, the problem links to the goal, the goal links to the vision. If one of these links is missing the solution, spec, and its implementation have a great chance of being misunderstood. So, I would outline two types of new information between teams:

  1. Provided information
  2. Based on assumptions

Team communication in outsourcing

Team members receive the first type of information at meetings, in the documentation, BTS, verbally, written, or visual. The more details – the better understanding and less damage for the company and the product, of course. And of course, it minimizes the chances of assumptions made by remote folks (btw, I suggest making it a solid rule for every requirement to contain the goal, problem, and expectations). With the second type of information, we are dealing more often with outsourced teams in comparison to a standard development model. Assumptions made by the remote team are unavoidable. No matter how detailed the spec is, if there is a single chance to misunderstand it, it will be misunderstood; per my experience, all details matter. Many factors contribute to this misunderstanding factor, for example, a language barrier, missing link with previous work, no presence at the meeting, etc. All we can do is try to prevent the wrong assumptions. How do we do that?

The answer lies in human nature. We tend to think that we are the owners of our decisions, but we are wrong, and it’s been scientifically proven. Our brain uses our experience and related information to come up with solutions and even opinions and thoughts. Scientists in the neuromarketing field made this discovery a while ago. However, the first discovery was made by supermarket workers. They noticed that when they played German songs in the store, German wine sales were twice as high compared to French wine sales. They saw the same pattern when they played French songs, French wine outsold German wine on those days. Take a look at another experiment: researchers from Yale identified that impression of a person was directly related to the warmth of the interviewees’ coffee. Our brain operates on our instincts and knowledge to create a picture and understanding of any receiving information. In other words, you are reading this article because you know the English language. If you didn’t know the language well, you could have great chances to assume some other meaning. But because you have all the essential knowledge, you can more precisely understand what I’m trying to outline here, and assumptions you make would be more in alignment with the information I’m trying to deliver. If you don’t believe me or don’t just understand this concept, try this test: don’t read this word: MILK. Lol. Now imagine any animal. Was it a cow? Try this experiment with your friends, write down “milk” and ask them to imagine any animal. I’m sure that more than 90% will imagine a cow.

What to do

The same concept works when we make assumptions. Our knowledge influences our thoughts and decisions. The more knowledge and experience executives pass to engineers – the less their assumptions deviate and the more aligned decisions the development team can make when building the product. Therefore it’s essential to deliver to the remote team as much information as possible. It can be company news, company direction, cause of the goal, how executives came up with the initiative, what information helped the discovery, why it is important, the expectations from users, and how it will benefit the company, etc.

Knowledge transfer in remote teams

Consider newsletters, meetings (formal and informal), requirements, group chats, envelope in the mail, or knocking the door at their home. Lol… The point is to make the remote team experience and understand the transformation of information and decisions from how the idea was born to why you selected this design for the target group. And this will play a useful role in building new features. Overall, having such detailed knowledge alignment between the teams and their members will result in better product quality. When everyone plugged into this kind of “knowledge pool,” you will also notice growing motivation resulting in higher performance and better feedback from the outsourced development team members.

Related Posts

Leave a Comment