How To Build a Startup With an Outsourced Team
Tips from the Mad Devs technical team manager about creating a startup. Benefits and risks of hiring outsourcing teams.
Join the DZone community and get the full member experience.Join For Free
Building a startup is all about risks, uncertainty, and rush. You’ve got an idea, even raised funding, or took a loan, and here is the toughest stage comes — the implementation of the idea itself. At this point, you start looking for an outsourced or co-located team. The first option is in most cases is cheaper, especially if we are talking about the South and Central Asia. The outsourced teams are becoming more and more popular now. According to the Deloitte Global Outsourcing Survey, in 2018 the outsourcing market amounted to $85.6 billion. However, hiring an outsourced team sometimes still undermines challenges starting with the usual change of the deadlines or scope of work and ending with a lack of transparency and the absence of trust.
42% of startups fail because there is no market need. (CBInsights)
Before the implementation, go back to your idea and think it over again:
- What problem do you address?
- What will potential users save time using your product?
- Have you experienced this problem personally or have you imagined it?
- What is the potential market share you plan to cover at the launch?
- Who are the competitors in the market and how your product is different?
The nice idea is to conduct market research first and make sure your idea has an audience and you understand the target users. In addition to that, it will help you to analyze the experience of your competitors who may operate in the market and build the product for years: which features are working and generating revenue and which are not. Taking into account the costliness of the development, try to test your hypothesis before the development. For example, create a survey or run the test adds.
When you are sure about the idea, go further and think of the MVP scope of work.
Forming the Scope of Work
The aim of the MVP is, first of all, to verify the hypothesis. Therefore, the scope of work formation should start with the key functionality dedicated to solve users’ problems and save their time. Imagine, you are learning a foreign language. Would you just go to the country you’ve never been and where you understand no-one or would you learn it word by word, one grammar rule by another? In the case of the startup, the second option is more preferable: building it piece by piece and collecting the users’ feedback as soon as possible after the development start.
The narrow MVP scope of work resolves several issues at the same time:
- Accelerates the first product launch that is especially important when the market is new and the competitors come on the heels.
- Reduces the risk of the missed deadline due to inaccurate estimation since it allows us to spend more time on planning and detailed research.
- Gives more freedom to pivot the development based on the real users’ needs instead of the blind intuition. It brings the ability to justify each following feature with the data.
Don’t be afraid to eliminate features that make sense to have in the future, but are not critical now. For example, it is nice to have video calls in the forum app, but it is not a necessity at all.
Please also note, that it is fine to launch the product for free, but you need to think of its further monetization to be able to continue development after the launch and turn the startup into the growing business. Ensure that users are ready to pay for the service and identify how much? In addition to that, think of the KPIs by which you’ll measure the product's success at the end.
Choosing a Team
23% of startups fail because they didn’t have a right team. (CBInsights)
If it is your first time working with an outsourced team, I would advise paying attention to how the team works and ask for the references. You should find out how your chosen team positions itself in its community. If they are a development team, are their portfolios available, such as GitHub repositories? Do they have real reviews on rating platforms such as Clutch? It also makes sense to have a trusted person on your side — CTO or Product Owner who will closely interact with the technical team. It is especially important if you have never worked with the technical teams before. Another option is to attract a third-party company to audit the working processes, code, documentation, etc.
Look for the experts, not just blind performers. Such a team will always challenge you and share their experience that at the end of the day will significantly improve the product. Even though it is important for the whole team to be professionals, pay special attention to the UI /UX expert at the MVP stage. Good, but not necessarily complicated design, with the well-thought-out user flow, can increase your chances of product success and save time on further readjustments. One of the ways to save time on future development is to conduct proper UX testing of the prototype.
In addition to that, give preference to teams that work in accordance with the Agile, and that allows you to directly communicate with any team member. In this case, you’ll see the results gradually and will be able to pivot the development if necessary. The second will ensure transparency and a single product vision.
Working With the Team
Transparency of Working Processes
Working with remote teams can be stressful sometimes since you are cut off from the daily information. Therefore, you may require a team to provide you with a certain level of transparency. It should be at least:
- Daily standups (either in a Slack channel or at the call)
- Clear tasks in the issue tracker
- Regular demo meetings and iterative approach of implementation
- Time tracking and detailed description of the work done (especially if you work on an hourly basis)
- Regular reports and retrospectives.
In addition to that, the team should be open to communication.
Unlike the co-located teams, one of the issues working with an outsourced team is the low involvement of the team in the project idea. The good news is there is a solution for that — regular communication. It is extremely important to be one the same page. Therefore, calls should be conducted several times per week and there should be a meeting summary approved by all the team members.
As we discussed before, in the case of the startup iterative approach is much preferable since it allows us to get the results faster and ensure the chosen track is the right one. In addition to that, you will know exactly what the product meets the expectations or identify the risks of failing the deadline earlier.
There is no way to have a project about the problems. It is all about telling them at the right time. The trustful atmosphere will encourage the team to speak out their ideas about product improvement, suggest alternative solutions for the tasks, and rise the potential issues. Working with the team for a long time will allow you just to share the problem you want to solve with the team and they will come up with a solution on their own.
It is a rare case when people are motivated with strict deadlines and penalties. Moreover, it often demoralizes the team and leads to poorer results. There is no way a good idea to force the team overtime all the time thinking they’ll work faster. Constant extra work decreases productivity and consequently, the product quality will fall and not allow you to demonstrate the product to users.
The best means to cheer up the team and encourage to perform better are:
Your attitude to the project — you should be extremely involved and passionate. Sharing the product vision and business value to let a team see that it writes code, not for the sake of code, but to solve a real problem. Users’ feedback is another inspiration tool. For example, when the project will be already in production, you may arrange a retrospectives meetings and present the business metrics for the team to show how the project is growing.
Hiring an outsourced team is risky. Yet the risks may be eliminated with the proper working processes and regular communication. You just need to find a good team.
Published at DZone with permission of Tamara Mun. See the original article here.
Opinions expressed by DZone contributors are their own.