We don't seem to have very good luck with analysts this year.
A few weeks ago one of our new analysts went completely AWOL after two weeks. Now another new one is insisting that the reason he's taken two weeks (so far) to not complete a simple change is because he has to understand the ENTIRE business process, in every possible permutation, even the areas that will never be affected by the tiny one line change he has to make, before he understands what change he has to make.
I've pointed him to the three things this change will affect, and basically talked him through what needs to change, but still he won't make the change because he need to know EXACTLY what it will affect (to the point of wanting to look at the code itself, which is a big No-no in our company. Analysts should never need to look at the raw code, that's not their job).
I've pointed out that we have daily review meetings to check all changes going out and any change he makes will have to be run through at least three review sessions before it gets near our live servers, but he won't even put it into the first review stage until he "understands the entire system perfectly".
I'm all for knowing what you're doing, but there's a point where you become so paralysed by the need to know EVERYTHING that you can't do anything because of the uncertainty.
The PD bit - He insists that the way he works has worked for him for 16 years, and the problem lies not with him but with the environment that we work in. And since his system works, the environment will have to change to suit his working method.
We're a high pressure, high workload, tight deadline environment and I don't think there's room for that level of perfectionism in our team. We've had one like him before and they got themselves coiled up in so many details they were worse than useless because they couldn't get past the knowledge stockpiling to make a useful contribution, and just ended up running around in circles unable to finish anything.