As a second plausible post, I’ll simply link to this explanation on the slowness of the TypePad service and make a general statement about the unsung heroes of this kind of work. Its a place I have played a few times and after a few rather big moves at this clothing company I worked at, I learned a few valuable lessons. First thing is that nothing or NOTHING ever goes completely the way planned and when a thing is going to break, it will pick the worst time of all possible times to do that. It will basically make life hell and its like it knows. Once moving almost 50 desktops and printers, conduits of communication were not laid down correctly and we faced a floor with no electrical power to speak of in the various rows and rows of desks. Luckily, the versatile and able WBE showed up and within time measured by our own beating hearts, rendered the floor usable for networking and power. Meanwhile all those systems, printers, scanners, and other doodads just sat in cubicles idly anticipating their new work.
But the main thing is not the computers. No. Its all the other stuff that enable the computers to do things. Switches, UPS, AC plugs, all the stuff that gets packed up and mysteriously lost. I worked and managed a move once for a rather large OEM’s technical service group and we labeled down to individual plugs with a scripted tag that had location, name, etc on it. This was planned down to the individual senior engineer cubicle that each had 4 workstations in it. Still we had issues in the new place. Its the territory and its the place and its what happens when a thing is moved. Distributed systems are particularly notorious as one person quoted to me in the recent past. A thing basically can happen to a system that you never knew you relied on and it will break everything else. A weakness in the chain and fabric of the space-time continuum? No. Just human intervention and the human way. Never blame a person for a thing like this unless you live in the blame factor world . There, in that world, its easier to just place the blame for heat, air conditioning, plugs, switches. Instead study what happened and you will see the fixes for the next thing. But when you implement the fixes next time around, remember there are new skids on your work that will suddenly announce themselves. Back at that same clothing company, one time I moved 110 desktops from San Bruno to SF. Somehow, a few got “jostled” and would not power up. Amazingly, all the systems running OS/2 Warp just started while the others running this legacy Windows OS had a variety of problems. Its all in the possibility game of a thing happening and then watching as another thing does.
I’ve enjoyed the IT world because all of those things challenge project managers with scenarios to plan against. But even the best project manager will find herself beset by real and imaginary dragons. As my drill sergeant used to say in Army Basic Training, “keep up the fire”.




