And You're a Microsoft Shareholder Because...?

Hello. Just a quick check-in for Mini-land. As I start writing this, I should be out soaking up the sun biking down some nice trail, but my knee started making those wet twig-snapping noises so here I am, side-lined and typing.

Quarterly financials are due in a week, and I'll probably skip a post on this one. Other places do a pretty good job of tracking the financial results. I am really curious, though, of all the people either holding or accumulating Microsoft stock: why? Why are you a Microsoft MSFT shareholder? What kind of metrics are you using to deciding to buy and/or hold? Sure, we all set alarms on stock when we buy it, but usually that does not include stagnation. Rick Sherlund gets off the Microsoft beat and the next thing you know we're getting bounced around.

This past week, I was driving home, listening to Marketplace on NPR, and some fellow gets on talking about Microsoft: "Lumbering..." he starts off with. "Dinosaur" he adds. Wow, he ripped into us more than I ever have. And what else shows up today? Lumbering Giants, mentioning Microsoft and other Dogs of the Dow.

This, combined with reports of Microsoft's death (SteveB and BillG in the repository: "Sorry, we're what? We can't hear you over all the ruckus of counting these billions raining down on us."), means we've reached a cultural turning point: Who's afraid of the big Microsoftie bad wolf?

No one.

Thank goodness. Pretty soon, the institutional shareholders might actually rub their eyes really well and look over the data, stumble up to the microphone at FAM, tap it, and say, "Hey! What the hell are you Bozos doing with my money?"

Personally, I'm in the middle of extreme diversification and I've scheduled myself out to aggressively sell-off all the MSFT ESPP and stock awards I've left alone for all these years. I guess that's just another little death in my confidence that Microsoft is actually ever going to turn around stock price-wise. I'm holding on to my options, though, hoping to at least fund an extra shot or two in my occasional mocha.

Other goings on...

InsideMS: "hey, was that a shark I just jumped?"

Collision Domain has a new post - "Bunnies!" - discussing the state of LisaB's internal InsideMS blog. Readers of the comments to a recent post will get the title. InsideMS certainly had a lot of potential at the get-go, along with probably a deep desire of Microsofties to use it as a place to engage and help change Microsoft and knowing that they could safely engage in conversation with peers. Then, it seems, it all went kinda wrong. Chops to LisaB for keeping it running as long as it has but hell, I wouldn't have it on my commitments either at this point. You can't keep posting on HR topics forever. I think it could change with more guest posts and with follow-up posts that summarized the major themes in comments so that the comments can at least be acknowledged, if not acted upon ("order up!").

Or maybe any topics originally started by He Who Must Not Be Named are off-limits.

If LisaB were to be interviewed, what are the hard, unanswered questions you'd want posed to her?

Microsoftie in the Field: hey, my goodness, a new post. Keep it up!

Outlook 2007 Performance: so, as Joel Spolsky notes, an update for Outlook 2007 was released to address performance problems. And, by the way, Outlook PM suggests you trim down your PST / OST size so that it doesn't accumulate email and silly stuff like that. Outlook is a temporal organizer, not a repository! Anyway, my performance is a little better but I still have strange freezes with POP, which I don't even know if it's on the Outlook team's radar. I'd be interested in what SQM said was the percent of non-Exchange Outlook users.

But it has me thinking. Thinking about waterfalled monolithic product wave shipping. Can it go on? Can we keep with the every three year product pipeline burst? One issue with Office proper is that it's half client software and half platform, and some large chunk of each wired up to the server solutions. The corner we've painted ourselves into is the platform part, where it was a strategic advantage but now IT departments are wary of upgrading less all their custom platform-based solutions regress because of new features or deprecation.

What to do? Well, avoid making that mistake again. Can Office be saved? Could you write a feature and stabilize it and just ship it, all within three months? A release of Office becomes constantly updated as new features come out, at least ensuring we can stay competitive fresh.

"Oy!" You start screaming about service packs and QFEs and N minus one and crazy sustainability crap like that. Really? Do we really have that limitation? Is it leading us to the path of reward and success?

And do we have the culture and know-how to be on track to just incrementally ship new features as we finish them? I'd be interested in knowing which groups do this really, really well.

Take This Microsoftie Job and Shove-It: Ms. Mary Jo Foley picks up on a f(Microsoftie) = Googler post: Ouch Goodbye Microsoft; Hello, Google. Ooo, that item got deleted from the blog. Silly delete. Never delete your blog entry. Always update and just plain replace the content with a space or a smiley. Less people track it down in the BlogLines cache by looking for feeds with "David Bennet" or such.

Vizzini! You know I have to give a shout-out to Mr. Joe Wilcox for his Princess Bride reference in DoubleClick and Microsoft's Thrift Culture. DoubleClick. Well, I'm glad it wasn't Microsoft paying $3,100,000,000 for it.

(Oh, and Mr. Wilcox: man, you've got some interesting comment action going on in your posts. Whew.)

---

Mini-Microsoft Microsoft MSFT

Should You Stay or Should You Go Now?

A comment from the last post asks a question that turned into such a long response on my part that I'll go ahead and post it:

why aren't you looking for a new exciting job in a lean and mini startup?

Fair question. First, I'm a very clumsy Pied Piping Mephistopheles in my attempts to get other people to leave. But, part of that is putting out what the reality of staying at Microsoft entails, and it's not pretty.

You're not going to get rich.

You're not going to be a L68+ Partner.

You're no longer going to succeed based on your merits alone.

Ouch, think that's uncool? Then my good-looking Brothers and Sisters, there are better places for you. Elsewhere.

I'm a corporate animal and this Microsoft environment, with its toxic pockets and issues, is a well known savage savanna to me and I'm able to succeed and be fulfilled, seeing the situation for what it is. And of course trying to change those things that I believe the other Microsofties can attempt to influence, given insight. The great potential for this change for the better is an exciting inspiration.

But I almost left recently. True. It was a situation where I didn't have to worry about sim-releasing in N-teen languages and ensuring that the Lords of IT were well and pleased. I could put out some cool features and IT-fanboys would suck-it-up and use whatever we made available to them and celebrate each newly released gizmo feature vs. crap all over the product and boo-hoo complain about all the compliance testing they had to do before moving to it. Tempting.

It did make me realize the accumulated shackles we haul around given the greater responsibility we have in creating World Class Software. No one else does it near the scope that Microsoft does. I don't know if we appreciate that deeply enough ourselves. Or appreciate it as a distinguishing, competitive feature. It certainly does not make you nimble and I've seen more than one feature killed due to localization and internationalization.

So, I stay because I still care. I care about making a difference for Microsoft products, and for carrying on the conversation here to see what other issues there are that should be brought out into the light and discussed, with the hopes of change for the better of Microsoft.

But Microsoft continues to bloat in size, the stock is flat, innovation is still somewhere out there, inspiring leadership is absent, executives seem to be flipping stock-grants, and efficiency and agility are still unrealized for many teams. The aircraft carrier hasn't turned very well yet, and the crew has become more and more dispassionate. I know my blue-badge clock is ticking and I hope I can make some difference before I head for the door and get to have fun writing EN-US Class Software.

All of us of deep software talent (and I'm putting myself in that group) are volunteers. We work where we work in a voluntarily sense because we enjoy it and it's the best place we can imagine for ourselves. We can pretty much get a job where-ever we want. Right now, for me, that's Microsoft. And there are changes happening. Slowly. But I think I've personally made the mistake of being anti-this and anti-that vs. being pro-this and pro-that. When you're anti-something and it gets attacked and then reduced, what takes its place? Whoops. Hadn't thought that one through. Maybe something worse than what was there. You've got to flip it around and be pro: pro-agility, pro-efficiency, pro-transparency, pro-compelling features, pro-iterative shipping, pro-stock growth, pro-meritocracy, pro pro pro.

I'm enjoying it while I can, and taking notes. I'm growing more in a business sense than a technical sense.

I can tell you this: I, like a lot of senior Microsofties, can't imagine staying for another year of flat stock growth. I'll have to be developing the bestest, funnest software in the world to live through another year of watching a stock price that meanders around like a fat, gassy contented cow from Carnation. I see this next year as the loyalty tipping point for Microsofties who have held on this long, hoping beyond hope for the shares to finally perform. If that doesn't happen, the office spacing problem around large of chunks of Microsoft will start to ease up without new buildings opening. And be wary of those who do stay, because you'll have to ask why.

So. You've had a chance to go through the MSPoll recently and perhaps consider how things are going for you. Why do you stay? Is it something beyond great benefits? What would compel you to stay for a long time, and what's on the verge of pushing you out the door?

---

Mini-Microsoft Microsoft

A Whole Lotta Movin' On!

For a while, I'd post just about anytime someone I thought was a Big Cheese decided to move-on from Microsoft. For me, it was two things:

1. A harbinger of change given some of the most loyal Microsofties who bleed multi-colored logos decide to pack it up, and
2. Attrition is attrition - good, bad, or indifferent - and it was the right direction for company growth, no matter how influential the departed might be.

Then it just became too much to always note such partings. Lately, there's been more than one time I grumbled at someone to go check with That Architect or This PM Lead and they wander back to my office after a few minutes: "Who?"

I type the name into Outlook and get an error. Damn, I didn't think that they spelled their name funny or anything. So I find some random meeting with that person from the recent past and double click their name in the attendee list, and get a weirdly blank Outlook property dialog.

"Ohhhhhhh...," the realization hits me. "Huh. Sorry, I guess they've moved on." (I'll be damned!) "I'll track down who's handling their area now." (I'll be damned!)

Mr. Todd Bishop points out various interesting departures as of late and even further back:

• Hillel Cooperman who was a key figure behind the buzz-worthy dead-as-a-doornail Microsoft Max now runs Jackson Fish Market. Hey, be careful with your fries around this guy (long story).
• Walter Smith who has headed to work with Mr. Cooperman.
• As has Jenny Lam of Vista UX.
• Brian Marr.
• Alex Barnett (old MSDN blog, new bridge-preserving non-Microsoftie blog).

Congratulations all! Again, I'll go for any attrition we can get. But are the right people leaving vs. the right people staying? There does come a point where you're left with a bunch of risk averse troops and no heroic generals. And I'm not quite sure what kind of uninspired, mediocre results you get, but at that point you've reached a point where you're back to destroying the village to save it.

Hey, Jackson Fish Market is hiring. As are lots, and lots of techies. And if you're interested in, say, the local Seattle scene, you should do what I do and go to events like Ignite Seattle (one's coming up this very Thursday, April 5th) so that you can get outside the Microsoft distortion bubble and talk with other techies regarding what they're doing and what they are passionate about.

It might be A Good Thing for you and your post MYCD-self. You can at least build your work network. That's a big first step.

---

Mini-Microsoft Microsoft