Overcoming Communication Barriers in Nearshore/Offshore Software Development with Andy Hilliard at Techstrong Con 2024

Hi everyone. I'm Andy Hilliard, CEO of Accelerants. Welcome to today's session, focusing on conquering communication challenges in nearshore and offshore software development teams.

Effective communication is crucial for any project success, especially when working across geographic distances. So, a little bit my about myself first. Um, early in my career, I fostered a passion for building globally distributed development teams from volunteering in rural Costa Rica with the Peace Corps to leading large scale clients.

At Cognizant, I witnessed the vast untapped potential of talent outside of the United States, which, by the way, only 16% of software development talent resides in the us, meaning 84% reside outside. This ignited a vision in me, empowering small and mid-size companies to access and leverage the global talent pool. Just like Fortune 1000, fortune 500 companies could do that.

Through the likes of Accenture and Cognizant and Infosys, I wanted to bring that down to a mid-cap and, and a scaling small cap, uh, marketplace, so that they too could take advantages of the global talent pool and use it effectively for competitive reasons. I translated this vision into reality by forming my own company, Isma Costa Rica, in 2003. It's a nearshore software development company that's scaled to about 300 software engineers in only four years, this success and demand fueled the building of what is accelerants.

Today, a network of pre-vetted, uh, high quality specialized development partners across Asia, Latin America, and Europe that can roughly be described as large enough to scale and small enough to care. Today, accelerants boasts over 200 certified partners in three, two countries. We send teams around the world constantly vetting and assessing software development organizations out of the massive worldwide pool of 30,000 development shops.

And we not only help clients connect with the ideal aligned software development partner, but we also help guide them in a building effective distributed development environments. So, one last thing is last month in March, I just published my third book called Synergy, A blueprint for building effective globally distributed teams in the new era of software development. A lot has changed, as you know, pre covid, post covid, co-location of teams, distributed teams all over the world.

There's a lot of new insights, and I've brought together 10 thought and practice leaders to help me in crafting a new blueprint for how to leverage software development resources. So let's get into understanding the challenges, uh, of communication hurdles that we often face with globally distributed teams. Uh, first is obviously language barriers.

They live in a different countries typically speak different first language, um, most often, if not always, uh, for at least the leaders of teams. Uh, their course secondary language is, is English, but you know, even with English as a common ground, misunderstandings can arise due to accents, idioms, technical jargon. Uh, and, uh, Americans tend to use a lot of, uh, a lot of anecdotes and a lot of, uh, uh, ways to say things.

In fact, this morning I was saying, uh, he's full of p**s and vinegar, which may even be an American regional thing, but no one outside of the US will probably understand that. So it's important, uh, that to understand that language barriers in many different ways can, can create a barrier. Also, cultural differences, uh, communication styles, decision making processes and humor, like I just mentioned before, often significantly vary, uh, across different cultures.

Time zone disparities, uh, whether you are follow the sun, which essentially means the other side of the world where you'll work during the daytime and it's nighttime with your partner, or even like in Latin America, where, uh, most of it is the same time zone. But, uh, on the West coast and Argentina, there's, uh, four hours difference. So, you know, time zone discrepancies and the ability to coordinate in real time and to hand off things effectively and to, and to communicate can often, you know, create a challenge.

And, and the last thing that is typically overlooked is an us versus them mentality. And, and that is rooted in the fact that Americans in general are very transactional and litigious as it comes to outsourcing. And that comes back in the day when outsourcing was more the production of, of hard goods.

I always use the term like a, a wicker chair. If you were to build a wicker chair in China, you send over specifications and then you get iterations and, and you reject them. And it's very transactional and, and, and very binary.

And, and if the product continues to, to fail, you know, quality, uh, concerns, then it may even turn into a litig litigious. But software development, product development is a much more, um, integrative, collaborative, team oriented art and science. So, uh, this is not traditional outsourcing and, and just taking this arm's length, uh, binary, uh, approach to partnering and team dynamics is a very destructive, uh, approach to software development.

So let's move on to some core elements that actually support effective communication. So first and foremost is you need to build the right partnership with the right foundation. So first, you know, you need to do, uh, adequate vetting with proven technical application, and sometimes even vertical expertise and focus.

Uh, that's really critical to start on the same page. And don't forget, uh, the, the comment about, you know, culture, uh, choosing the right partnership most often and, and really should include since you are trying to build this sort of one team, what we call one shore approach is getting on planes, spending time in your host country's, uh, environment breaking bread, you know, uh, measuring the, the fluidity of communication and, uh, being able to, you know, capture each other's thought and, and reflect them back, uh, fairly accurately and, and intuitively and naturally. Uh, these are all elements in, in building the right partnership.

Also, cultural alignment. So during this due diligence phase, you know, playing, paying some close attention to say how eager inquisitive a, a prospective partner is, uh, and, and the natural interaction between you and them. Language proficiency, addressing something on the last slide.

So strong English proficiency, or frankly, whatever language, uh, you happen to work in, is vital for both, you know, written and, and oral communication. The right partner will communicate obviously, in the language of choice, but also don't forget the, uh, the innuendos and the meaning behind the words that you use. Um, time zone overlap.

Some real time, real time collaboration is needed for effective offshore management. Uh, it's, it's not, doesn't have to be total overlap, but enough to ensure complete process alignment. Uh, and the last I'm gonna talk about today is the depth and breadth of business thought and practice leadership.

Uh, it's given the fact that there are 30,000 development shops, uh, around the world today. Uh, many shops, uh, can easily say or sell you on, on, you know, that they're aligned with everything that you need from a requirements to a delivery perspective, when in fact, uh, it's, they are often thin shells of companies that have been created in a relatively short period of time and have very little infrastructure or assets, uh, to their name. Uh, what's really important and, and a and a hack for us, is to make sure that they have a very broad and deep level of business leadership, technical leadership, practice leadership and thought leadership.

Because smart people hire smart people, and smart people attract smart people. And, and that is usually, uh, a, a due diligence and a risk mitigation maneuver that a lot of people, uh, miss. They, they tend to fall in love with, uh, people who are fronting the organization, but there's very little behind it.

We're gonna go a little bit deeper into ways to build a results oriented collaborative culture. Uh, first and foremost is creating a unified team environment. And that means a culture that is a no blame culture, you know, treating remote and local teams equally to foster trust and collaboration.

Documentation is your secret weapon. Detailed instructions and a shared knowledge based are cr crucial for managing offshore software developers. Clear project requirements, version control, and a centralized information hub prevent misunderstandings and assure that everyone is on the same page.

Agile for offshore successes, managing offshore teams is streamlined, uh, with Agile's continuous feedback and adaptability. Regular sprints and transparency ensure that everyone starts on the same page, allowing for quick adjustments to time zone delays or changing requirements. Emphasize radical candor, which basically means to be direct, but care.

The culture of equality and trust enables sharing directly while caring, personally dissolving silos of differences. The promotion of servant leadership that entails empowering the engineers, clearing obstacles and setting clear goals To motivate teams, you want to empower your partner and your people so that they in turn will deliver for you. It's a way that I, I approach it.

It's, it's selfish, but it's the appropriate way to motivate, uh, the best out of people. Multi-channel approach. Email alone won't cut it when you're working with offshore development teams.

Embrace video conferencing, shared workspaces like Slack or teams, and a robust project management tool for efficient communication. And I cannot stress this enough, getting on planes quarterly, semi-annually, spending time building team dynamics, building what I like, like to call the, the four critical areas of, uh, trust, radical candor, commitment and accountability that can only be effectively developed through in-person presence. And, and, uh, time spent is absolutely critical.

Cultural understanding and appreciation training, this ties right into that. Promoting understanding of different cultural norms and communication styles, establishing a rhythm, regular check-ins are key to managing offshore teams. Whether it's a daily standup or a weekly progress meeting.

Find a cadence that works for your relationship. And finally, celebrating wins together, acknowledging milestones, big and small to boost morale and keep your offshore team motivated for your project. So these are some of the more granular ways to build results oriented teams.

I hope you put them into effect. Uh, missing one is missing a lot. So, uh, you know, anyone who is watching this, uh, presentation should make a note on, on how to integrate this effectively into their, uh, relationship building, uh, efforts and roadmap.

So in conclusion, uh, by implementing these strategies and fostering a collaborative culture, you can overcome communication barriers and lock the full potential of your nearshore or offshore development team. Uh, clear communication is the foundation for successful nearshore and offshore software development. com.

I'm here to serve you and I appreciate your, uh, attention during this presentation.