馃攳
An interview with Tom Horvei | Outsourcing | Future Processing - YouTube
Channel: unknown
[14]
First time,
[15]
it was because we needed really peculiar skills and special competence in a project.
[22]
It was nowhere to be found within the borders,
[26]
so then we just had to go abroad to find that very special competence.
[31]
That was the very first time that we not only outsourced, but also offshored.
[36]
The second time,
[37]
it was merely a matter of having bigger needs in a shorter period,
[45]
so that we would be better off getting an external team to do our things.
[56]
I would say three Cs.
[59]
So - Capacity, Competence and Culture.
[64]
Make sure that they have the capacity to actually dedicate time to your project,
[69]
not have a team doing it parallel to another one.
[73]
And then, the competence that you want.
[76]
You basically want those people to be labeled to exactly what you need
[81]
and they should have a culture that fits with the culture within your company.
[87]
I would say, an open culture that lets you, as a customer, in.
[96]
I would say that, whether it鈥檚 overseas,
[101]
or whether it鈥檚 just down the street for you,
[104]
it鈥檚 all about getting somebody that鈥檚 really fitting.
[111]
You have to keep in mind that the contact should be close,
[116]
that it鈥檚 still your project, you cannot outsource a problem,
[120]
the problem is still there for you to solve it.
[123]
You鈥檙e just using somebody else parallel to you.
[126]
So, keep in mind that the communication needs to be good all the way.
[132]
In addition to the criteria you go for when you鈥檙e selecting the consulting house down the street,
[141]
you especially think about culture as a national culture,
[147]
to get the good gut feeling and then think about the practical things
[153]
can you get there often? Is it in a time zone that you can live with?
[158]
That sort of thing.
[166]
Yes, it is.
[167]
It is important to understand that with the small software department in house,
[179]
you will never be able to maintain the people,
[182]
to inspire them, the way a bigger environment of developers can do.
[187]
To build competence in house is so difficult and,
[192]
in most cases for most companies, it鈥檚 off their core.
[196]
Even though you have a software department, even though you develop your own software,
[200]
you鈥檒l always find the tasks that go a little bit on the outside of everything that takes away inspiration,
[208]
that takes away time that you need,
[210]
and then outsourcing is a wonderful business model, if you do it in a right way.
[221]
I would say getting close to the project,
[225]
to still remember that it鈥檚 your project.
[228]
It鈥檚 not somebody else鈥檚 problem,
[231]
though you鈥檝e signed a contract with an outsourcing partner.
[235]
You have to keep in mind that all way along you need to influence the processes,
[242]
you need to influence the development,
[245]
and you need to see that this is becoming what you鈥檝e dreamt of.
[249]
We all know, since we鈥檙e in the business,
[252]
that a way from the spec, no matter how much you worked with it,
[257]
to an end product is a long one and things are not quite how you envisioned them from the beginning.
[266]
And therefore you just have to be close to it.
[275]
For us, outsourcing meant that we didn鈥檛 have to recruit people in a difficult market,
[282]
we didn鈥檛 have to put a small team together,
[285]
without the capacity to actually give them the knowledge that they needed to solve our specific problems.
[294]
For that reason, outsourcing was a huge success,
[297]
because in a short time we got a dedicated team,
[300]
caring only about our problems and we got an end product that we are now really proud of.
[312]
Well, I was skeptical to offshoring, for sure.
[315]
I thought that especially in the late 90鈥檚, when the capacity was scarce in all of Europe.
[325]
You couldn鈥檛 get developers and lots of projects went to Indian markets
[333]
and we saw the bad things happening.
[337]
There were problems with culture, problems with time zones,
[342]
problems with communication, all way long.
[347]
The trip there was so massively long,
[351]
we didn鈥檛 want to go there every second week, every month to that matter.
[356]
And then you just ended up ordering bananas and you got apples back,
[361]
and then you complained, and then they sent you pears,
[365]
and you ended up with a melon.
[368]
But that was still a problem,
[370]
lots of money went out the window,
[373]
actually more money than if you have gotten a closer outsourcing partner to begin with.
[384]
What changed my mind was that at some point we had to offshore,
[388]
because we needed competence that wasn鈥檛 within the country
[392]
and we were just really conscious about not making those mistakes
[397]
that we all have been part of making
[399]
and we鈥檝e seen others make.
[401]
Therefore we just decided to be closer to the project
[406]
and we were opened with our offshoring partner at the time,
[412]
with our skepticism and our worries,
[416]
and they were opened back,
[418]
and together we鈥檝e found a key, a way of doing it.
[422]
That worked, and that has worked ever since.
[431]
Of course, you will always find extremely strong personality,
[438]
with strong opinions around your product.
[440]
As long as you're engaged, as long as you鈥檙e aware of cultural differences,
[445]
as long as you keep in mind what鈥檚 your vision with the product,
[451]
then you will end up with a very good end result
[455]
and losing control well, it hasn鈥檛 been a problem.
[462]
Obviously, when you鈥檙e looking for an outsourcing partner, and you鈥檙e looking offshore,
[469]
then money is part of it.
[472]
You should also see it the other way,
[477]
since it鈥檚 a way of getting a bigger, more dedicated team,
[482]
to fit your budget.
[483]
But for a while you should forget the budget bit
[487]
and you should look at them like you would look at any outsourcing partner.
[494]
Then you have to look at how they鈥檙e organized, how they would fit your way of working,
[502]
whether they understand your business, whether they have experience in your field.
[509]
And when you鈥檝e done that, and you have gotten some rapport with the company,
[514]
you established your first contact and all that,
[517]
then you should, at an early stage sit down and call the references.
[522]
Talk to them,
[524]
because this is so important and a lot is separating the good ones and the bad ones,
[530]
but sometimes it鈥檚 not easy to see,
[532]
certainly not by just looking for a few minutes at a web page.
[537]
And when you鈥檝e done that, just find a way of working together,
[541]
where you can actually share your worries and your thoughts all the way long,
[546]
and make sure that you culturally fit with them.
[550]
This would be good to do in a pre-project.
[553]
Once you feel that this is running smoothly
[556]
and you actually have good communication,
[559]
then you can go on and say:
[561]
Ok, this will be our partner for the rest of this project.
Most Recent Videos:
You can go back to the homepage right here: Homepage





