4 ms·
I've had some bad experience with consultants. So much so that I'm hesitant to use them now. They'll have a plane to catch to fly to the next client's site. And
by 16s 15y ago
I've had some bad experience with consultants. So much so that I'm hesitant to use them now. They'll have a plane to catch to fly to the next client's site. And they'll rush to catch that plane and make mistakes on your project, etc. They have the mentality that this is "not their baby".
If you do hire one, make sure you have a maintenance agreement with them so they can't just set it and forget it leaving you with a big bill and problems.
Just my experience.
Edit: I've never used an Oracle consultant. My comment is meant at technical consultants in general.
- mgkimsal 15y agoAnd I've had bad experiences with clients who want to treat an external consultant as just another body they don't have to treat any differently with respect to communication. There's pitfalls on both sides, but I've had people not give me information for 3 weeks, fiddling with other projects, then get upset, after our initial agreed on engagement timeframe is done, when they can't just have me stay involved for another month. I've said before, and I'll say it again - almost all projects I've been involved with that failed or were extremely bad projects (consultant or employee or whatever) failed because of communication issues, not technical issues. Even when tech issues arise, there needs to be competent communication about the impact. Good communication - from all parties - is key. It's just that with full time employees I think many managers prefer to let things slide around longer.