As promised, here’s the latest from my experiences with Velocity Micro.  When last we left my poor sick PC, it was on the operating table at Velocity Micro’s labs in Richmond, VA.  After a two-week illness here at home, when a house call did not do the trick, it went back to its birthplace for major surgery.  

After my comment on the Velocity Micro blog, and my long entry here, Velocity CEO Randy Copeland intervened and said it was time to build me a new replacement PC.  The Velocity team sprang into action, built me a replacement, and tried to bring it to life as a near-replica of my original system, so I would not lose too much data or time.  And here our saga enters a new chapter.

Anyone who has attempted to migrate from an old PC to a new PC knows this does not work as well as it should.  Yes, there are tools, some from Microsoft and some not, and a quick Google will tell you of the mixed experience users have with these tools.  Even the migration from HEALTHY old PC to new PC is uncertain; the migration from SICK old PC to new PC is fraught with peril. 

Guy Five at Velocity Micro was put in charge of the operation, and things began well enough.  As previously reported, Velocity places a high priority on customer communication (even BEFORE the CEO intervenes), and Guy Five was no excecption.  So I learned relatively early in the process that Windows was badly currupted on my old machine, and that transferring applications and settings would be essentially impossible (although they thought probably they could at least move my email settings, which would be a start).

So — build and test a new machine, copy my files onto it, ship it, and it’s up to me to restore the applications and settings.  OK.  Not what I was hoping for, but at least this shouldn’t take long, right?

Ten days.  Randy’s CEO intervention came on 2/11/2007, and my new machine arrived 2/21/2007, with my data and without my applications, accounts, or settings.  Every step of the way I got daily emails and occassional phone calls documenting progress and setbacks. 

• Everything looks good. 
• Uh oh, the D drive has bad sectors and is causing crashes — better replace it. 
• Everything looks good, if all goes well you’ll have it by Saturday (2/17). 
• Yup, still looks good, it will go out Friday, you’ll have it Saturday. 
• Hmmm, ran into some trouble with the TV tuner software, caused some crashes, we want this thing stable, better keep it running stress tests over the weekend. 
• Oh, yah, kind of a long weekend, but you’ll have it Tuesday. 
• Oh, didn’t actually go out until Tuesday, you’ll have it Wednesday.

And indeed, it did arrive on Wednesday, and it worked right out of the box (no, the email settings weren’t restored, but I can do that along with the rest). 

So from time of first crash to the time I got a working system back under my desk — thirty-four days.  And it will be longer yet before it’s back to the personalized state that makes it “my” PC — I still have a few applications to install, settings to tinker with, and so on.

But it seems stable, it’s fast as can be, and it works, and it’s backed by a company that clearly is trying to serve its customers. 

So would I buy another Velocity Micro machine?  Frankly, I’m glad I don’t have to decide that today.  On the plus side,

• Their PCs are fast and appear to be intelligently designed
• Their staff is professional, courteous, and intelligent
• When things go wrong, they tell you, and admit their mistakes
• Their CEO is willing to engage openly with customers (although frankly I’m disappointed that my comment on Randy’s post on Velocity’s blog was not published)

On the minus side

• I had hardware trouble after just two months
• They could not fix it with a house call
• Their shipping department whiffed on promises at least twice, resulting in frustrating and needless delays
• Getting a replacement system took longer than expected, even after raising a fuss
• Based on my experience, I have to question their QA — I believe that their team eventually identified problems with the graphics card, TV tuner card, original motherboard, RAM sticks, and D drive (not to mention Windows getting corrupted).  But all that stuff shipped to me after “burn in” of my original system.  Was it working when it left their shop the first time?  Possibly.  Did it all die at once at my house?  Who knows?

So it depends what happens now.  If I have a long and happy relationship with my computer from here out, yes, I’d probably still go back.  Even after more than a month of trouble, these guys have managed to stay mostly on my “good side.”  Why?  Because in more than a dozen interactions with their staff, I was never once treated like an idiot.  I know this shouldn’t differentiate them from other vendors, but sadly, it does.  If you’ve ever had trouble with a Dell (and I have, and we have at work as well), you’ll know what I’m talking about.  Nobody asked me to try rebooting, nor tried to walk me through a fifty-step process unrelated to my problem.  Everyone was clearly trying to identify and solve my problem, in a way that would work for me.  That matters. 

So hats off to Randy and his crew for screaming hardware and smart, supportive staff.  Iron out a few processes that I would attribute to growing pains, and you’ll have a happy customer and a winning company.

Tags: Growth, QA, randy-copeland, support, velocity-micro