![\"\"](\"https:\/\/www.rudebaguette.com\/assets\/two-thumbs-up1.jpeg\" "\\"two-thumbs-up\\"")
<\/a>\nSome will tell you that you should not outsource, but this is not what I think. Actually I won\u2019t have enough of one article to tell you all the cases in which you should<\/em> outsource (lack of time, not the required skills in-house, not enough people in the team…).
\nIt doesn\u2019t really matter why<\/em> you want to outsource.\u00a0What matters is that before doing so you ask yourself \u00abAm I outsourcing what defines my company?\u00bb This is especially true for startups that focus around one main product: you do not want to lose control over what makes the core of your business.<\/p>\n
Build up a Team<\/h3>\n
I suppose you don\u2019t want to be forever dependent on contractors, right? Your goal is to build up a team, because in the end this is what makes a startup. A passionated team can build anything if gathered around the right vision, and outsourcing without thinking can hurt that dynamic.
\nWhile a lot of contractors are very able and talented, the problem is that they are only part of the team very temporarily and will not get involved as much as your teammates. They will lack the long term vision and won’t think “if I do X, what will happen in a year when I need to make it evolve into Y”. The problem given to them will be solved, but later evolutions might be harder.
\nRemember that your team members decided to join the adventure for more than a couple of billable months. They will have opinions, ideas and will thrive to build the best product possible if you give them the means to do so.\u00a0You want developers thinking by themselves and ready to go back and improve what they wrote months ago. You want designers that are creative and in phase with the company’s vision.
\nThis is why you need to build what\u2019s important internally and outsource only when you can\u2019t do it in house… and even when you do, do it keeping in mind that you will have to integrate what has been created and that your team will have to maintain it. If done correctly, outside help can be a good thing for everyone, as mixing ideas and processes is always interesting and a good experience.<\/p>\n
Outsourcing Done Right<\/h3>\n
Like I mentioned before, sometimes you need to call someone to help out. In this case you need to be sure you do not hurt your product or your team in the process. The deliverable should be easy to test, easy to maintain and easy to evolve. If those conditions are not fulfilled, you might deal with frustration in your team. If they are, everyone will be happy about a job well done.<\/p>\n
Design<\/h4>\n
If you\u2019re outsourcing your product’s design, ask to be provided with a full style guide, general guidelines, grid templates… anything that can help\u00a0future designers can build on top of what you already have without having to start from scratch. Use a lot of constructive criticism and keep in mind the big picture: your product shouldn’t feel patchy, even if you got a lot of people working on it.<\/p>\n
Development of a New Feature<\/h4>\n
If you’re outsourcing development directly inside your main product – like a new feature, you want to make sure the code that is given to you is good and perennial.\u00a0To achieve that, you should ask from your contractors:<\/p>\n
- \n
- \u00a0The code should be shipped in a modular fashion, avoiding coupling as much as possible. The new features should not interfere too much with the existing codebase.<\/li>\n
- A lot of pertinent automated tests.<\/li>\n
- Documentation, not only on what the features are doing, but also on how they can be maintained and improved.<\/li>\n
- Try collaboration\u00a0with a member of your development team (if you have one), even part time. You want someone able right away to maintain this new feature.<\/li>\n
- Enforce your internal best practices as much as possible if you have some. If you don’t, enforce the ones accepted by your technology’s community.<\/li>\n<\/ul>\n
Always keep in mind that you will have to live with this new code for a while and decide accordingly if outsourcing is the right move or not.<\/p>\n
One Shot<\/h4>\n
The other possibility is to outsource something that is not directly linked to your core product. This could be a marketing campaign or something similar.\u00a0In this case it is easier to get it right, and this is the situation where outsourcing works very well for a startup. You will not need to maintain the new code for long, it will not impact the existing code base… the only thing that matters is that the final result if up to your company’s standards.
\nA perfect example of that is my company’s\u00a0new website<\/a>.
\nWe launched it recently\u00a0and gave design control to a creative agency<\/a>\u00a0during development. We did this\u00a0because we knew that they would create a better design than us. While we care and love about building things that look good, this is not our core business. Delegating this part of the job also gave us the possibility to focus more on our platform for social media applications which is what we do best.
\nDuring the whole process someone kept checking to see if we were agreeing on the choices made. The final phase of integration was made in house because we have great front-end developers that should be able to make the website evolve later on.<\/p>\nKeep Control<\/h3>\n