Program management is an interesting discipline at Microsoft – it was when I first joined the company, it remains so now. It is a role that requires good "soft skills" ("I'm a people person"), good prioritization skills, good analysis skills, good presentation skills, and being able to walk that Zen line of "good enough" when shipping product. It's half art, half science, half Buddhist monk, half evangelist (arithmetic skills aren't really a requirement, though). It is a neat role that you don't see at a lot of other places – you'll see the title Program Manager, or Project Manager, but it is rare that you see Microsoft Program Management in action (although, as Rick points out, occasionally the more feature-happy Program Managers need to be put in their place).
I was never a Program Manager at Microsoft, I started as a Technical Evangelist (technical marketing) and then transitioned to a software development role and worked my way from there. I made the jump to general management in April of 1998, but I was still fairly heavily development biased in my thinking. My self-selected career track of leaving Microsoft to start a company really threw me into the realm of Program Management for the first time. Investors, customers, employees – that list of skills I mention up front turns out to be REALLY handy. Over the past 7 1/2 years, I've found that one can Program Manage anything to get the results one wants. I'd been doing it unconsciously for the first 35 years of my life, but once one is doing it consciously, watch out. It helped me navigate everything from raising money during the most hostile environment to startups in a long time to navigating the halls of a media company.
About seven months ago, my (just turned) six year old son was diagnosed with Type 1 Diabetes. We got lucky in that he didn't end up hospitalized – normally, how you find out your pancreas has stopped producing insulin is that you start to lose weight and you get really sick. But he had his six year checkup a week after he had started to wet the bed out of the blue, so we mentioned the bed wetting to the doctor, and bam – one urine test and a trip to the hospital later, we had our diagnosis. His blood glucose levels were north of 450 (60-120 is normal for non-diabetics) and his A1C result was 8.2% (<6% is normal for a non-diabetic, good control for a diabetic is < 7%). Point blood glucose tests tell you how you are doing at any given moment, but they tell you nothing about the hours in between. A1C really is the ultimate metric – it is your body's memory of how your blood sugars have been behaving. So the 8.2% showed us that while his initial blood glucose reading of 450+ was wildly high, it hadn't been wildly high for the past 3 months – just way too high.
Anyway, after the initial shock was over, I set about in a methodical way to understand how his body used carbohydrates and how it consumed the injected insulin, and to put in place a discipline and a methodology to really manage his diabetes. I did a ton of research up front (and continue to this day). An Access database was born, along with a tightly watched and tweaked rhythm for eating and exercising. Far more than the suggested minimum number of daily blood glucose readings became part of the program – after all, the pancreas does it continuously, so the more the information we have to help us substitute for the pancreas, the better. Part of the fun along the way was the evangelism of doctors and nurses to get the extra supplies we need (I am a huge fan of redundancy and long term planning). A lot of questioning and pushing back against medical advice that didn't fit what I was seeing in the patterns of the numbers was a big part of the fun – although we have switched to Children's Hospital in Seattle where the staff seems much more knowledgeable and much more willing to listen to reason, so I'm having to deal with less crap now. Every day is a day that something could go wrong and every day requires careful attention, but we are really in the zone now.
Once every 3 months, we have to take our son to Children's for a checkup. Today was that day. The travel and the appointment take about a half-day all told, and they poke, they prod, they ask questions – oh, and they measure his A1C. Today it was 5.8%
You can Program Manage anything.
Comments
Maybe it's better off that they didn't let you activate the 2nd iPhone. I was "successful" adding the 2nd iPhone to my account. My first AT&T bill for 1 week of service - $805.54...
I took me 6 hours to get that resolved. Love the phone - hate AT&T.
Posted by: Pat Friel | July 29, 2007 6:39 PM
I'm giving you guys over there a lot of wiggle room, don't push it too far! Good move with the delaying MacOffice, let's schedule another delay announcement when they're stock recovers a little more!
Posted by: Steve Ballmer | August 2, 2007 10:02 AM
Or consider my friend's experience http://www.oreillynet.com/etel/blog/2007/06/iphone_first_impressions_what.html
Where AT&T refused to activate his account for the longest time.
Meanwhile, Craig, how's that Office 2008 coming along? We're anxious :)
Posted by: vmarks | August 2, 2007 4:37 PM