In our business, providing highly skilled technology teams from Argentina, we have seen a pattern develop over time that clients tend to define a certain “number” of team members they need. We habitually ask where they came up with that – our response usually being…why so many?
Over time we’ve found that, many times, it is a misconception. Why? One reason is that a client may have had an experience with other offshore teams. Time zone, cultural and communications barriers can impact productivity and therefore create the perception that more is better.
So how have we realized that? Our clients tell us!
Allow us to share a story that describes this principle.
Recently, a company (let’s call them Company X), where we already had 1 developer assigned, decided to bring on three developers from a farshore location for a project. The rationale? With more hands on deck, they’d likely get more work done. It sounded like a strategic move, especially given the allure of lower operational costs…their teams were roughly half the cost of our teams on an individual basis
They wanted to carry on with our humble team of one developer, who was highly regarded.
Over time, Company X found themselves wading through numerous issues. Despite having three developers, they frequently encountered bugs, faced integration problems, and struggled with quality and meeting sprint deadlines. Recently, Company X’s CEO mentioned that they were dropping the far shore team after several months for those reasons. The bottom line was that our 1 developer was more productive than the 3 other developers. The lesson was clear: even if the trio was more affordable, they couldn’t match the value and expertise of our single developer.
This is not to say that our teams are superior. There can be several reasons that explain the productivity differences, among them:
- Cultural differences
- Communications issues
- Team integration (or lack of it)
While these may be intangible issues for the most part, they creep into the life of a project in different ways – and there are different dimensions to these problems that may not be perceptible, or they may manifest in a way that can create a blind spot as to what the root cause problem is.
The story of Tangonet Solutions and client Company X isn’t just about the number of developers or the cost factor. It’s about real value measured in terms of quality and productivity. It’s about understanding that sometimes less is more.
Another client had a specific request, stating they would need between 6-10 from our development team. Why? They based it on a 1.7 year backlog and the time estimated to bring that down to a more manageable level. My response was that while a larger team might be able to bring the backlog down faster, there is also a question of reaching a point of diminishing returns regarding productivity. The result was that we never had more than 4 development team members. Why? There was no need. The team showed over time that their level of productivity was more than enough to bring the backlog down to acceptable levels.
Start Slow – build the team gradually: Why It Matters
When it comes to your business, projects are only as good as the people behind them. And, as the saying goes, sometimes less is more. Every choice of resource – particularly when it comes to developers and engineers – becomes a cornerstone for the project’s success. By starting out slowly, building a strong foundation around 1 or 2 key resources, we’ve found that projects can move faster over time and can be likened to building a house on shaky foundations; no matter how impressive the design, it’s bound to face issues down the line. In the long run, the choice of technical teams can influence not just the immediate output, but also maintenance costs, adaptability to changes, and even the overall lifespan of the project.
Beyond that, there is also a question of the right resourcing model. Agile Team or Team Integration models (aka staff augmentation) are much more effective if the external teams can effectively integrate, and become part of, the internal teams. This facilitates communication and a greater sense of team integration and teamwork, allowing projects to move forward faster and more efficiently (more in a future blog post).
This is why, at Tangonet Solutions, we emphasize the union of talent and passion in every individual we onboard and we only work in one region where we have proven, over a number of decades, that cultural affinity, strong communication skills in addition to strong technical background are attributes that, together, creates a strong technical team. We believe in delivering solutions that stand the test of time, adapt to changing needs, and consistently exceed expectations. The next time you embark on a project, consider Tangonet Solutions as your partner. With us, you’re not just investing in a service, but in a legacy of excellence. No project is too small.
If you’re looking to elevate your project’s success with a team that prioritizes quality and productivity, let’s start the conversation. Contact Tangonet Solutions today and experience the advantage of a team where every member’s talent and passion contribute to your enduring success. Reach out to us, and let’s build not just software, but a partnership that lasts. Join us in redefining what it means to have a truly effective tech team.
