Thursday, November 20, 2008

Personal Experiences with Live Mesh

This post is not going to be about Dynamics AX. It will be about a software product I was thrilled by so much I would like to share it with all of you.

I won't post a detailed description of the product here. You can read that yourself at www.mesh.com. But here is a brief introduction, just to give you a basic idea of what the software can bring into your life.

WHAT IS LIVE MESH?

With Live Mesh, you can synchronize files with all of your PCs (and soon your WM6 phone and Mac as well), so you always have the latest versions handy. Access your files from any device or from the web, easily share them with others, and get notified whenever someone changes a file. Working on one computer, but need a program from another? No problem. Use Live Mesh to connect to your other computer and access its desktop as if you were sitting right in front of it.

Here is a screenshot of the web interface for managing your devices in the mesh:


What I would like to share with you is the personal experiences I had using this software for a month now. In 1 word - fantastic. Live Mesh is still in Beta, but already I can tell you - simplicity is the word. You set it up (takes 5 minutes and is very simple, all you need is a LiveID, which I hope all of you already have). And that's it, you are done. And from then on - it just works. Great!

And here are 2 screenshots of how I use Live Mesh in my everyday life.
Obviously, I have all of my computers meshed, available to me when I need them (they need to be turned on, and have access to internet, of course).



And so far I have 4 folders in the mesh, and I would like to discuss each of them separately:


Personal - I store a backup of my personal data in this folder, which is synced across all my PCs, so that I have it at hand in case I need it. Plus, I have my Personal OneNote workbook in there, with all info I need.
Favorites - Favorites are not synced accross all my PCs, providing the same list on all of them in IE. This is great. This was a feature most of the browsers tried to implement throughout multiple releases. And here it is, as easy as it gets. Any time I bookmark a page, all my other browsers get this page bookmarked as well.
Incoming - this is the folder for file transfer between PCs. Now I don't have to send it to my e-mail every time I need a document scan or something. And, I invite other people as members of this folder, sharing pictures and other documents with them. That easy. And, they get updates every time I add a file, without me having to notify them.
Work - This is my work folder, which I don't sync to my home PC (you can see it is a ghost folder on the screenshot). Any file I work on is automatically synced between my work PCs, so I have an up to date file any time I access it. Extremely efficient.

Well, that's about it. Now, all you have to do is go and try it out yourself.
Have fun!

Saturday, November 15, 2008

Achieving Senior Level 63 at Microsoft

I want to share some of my thoughts about succeeding at Microsoft and reaching Level 63, the Senior contributor level at Microsoft. Given that quite a few Microsofties are going to find themselves locked into their current group for a while, the ability to succeed by swinging on the vines to a new group is going to be rare. Within the comments, I hope to elicit advice that follows up on what I start here, and maybe even contradicts it. I'm interested in hearing your stories of success, mentorship, and turning a career that was off-path back on-track. For the folks on the path to L63, I want you to first understand your boss's opinion of you, your opinion of yourself, what it takes to succeed in your team, and then ways you can step up and be on the right path.

Let's Hear it for the Boy! Let's Hear it for the Girl! If you reach L63 during your time at Microsoft, especially if you started at L60 or below, you should celebrate. Here's to you! What an achievement! You have the right stuff to succeed and Microsoft is very happy with you.

L63 is very much an important milestone, and in tough-hiring times like these the following question has never been more important: "Will <<fill in the blank>> reach Level 63 during their career?"

If you're not there yet and your boss was asked that question by your skip-level-boss, what is your boss's answer?

Unless you know for sure that your boss's answer is an immediate "Absolutely!" you need to hit the pause button for one big time-out regarding where you are, where you're going, and what needs to change. And I'm going to tell you right now, I'm 99.9% sure what needs to change is you. Because, except on the rare occasion, Microsoft and your team isn't going to change.

Up until L63, you can pretty continue to be promoted based on raw talent to get things done smartly and efficiently. Things get thrown your way and you knock each and everyone of the challenges out of the park. Then perhaps you're stuck at L62. What got you here ain't gonna get you there. What now?

Think Locally: remember three years back when we talked about the book Corporate Confidential? It's a good time to flip back through that. One of the key lessons is to know who is the gate keeper for your career. Pop quiz: who is it? Think about it. Ready? Let's compare answers... answer is: your boss. Your lead. The person who puts you up for promotion and has promotion conversations with your skip level. It's a question your boss gets asked so it's not a surprise to them. Your boss should already have about a year-long plan about who on the team is getting promoted when - it's essential for team promotion budget planning. And when the time comes, putting you up for a promotion to L63 is the first time your boss will be challenged by your skip-level and by your Aunt and Uncles (your boss's peers) about one of your promotions. It's hard for L63. Harder for L64. And a knife-fight for L65 (some other day). They will have thought this out.

If you're saying "Ah, dude, my boss is in the way of my promotion" then all I have to say is "Duuuude, your boss is the way to your promotion." Perhaps someone can explain to me how you get successfully promoted without your boss's support.

So honestly, what is your boss's answer about if you'll reach L63? If it is "Absolutely!" then the follow-up is: after what accomplishments and around when?

Your Recently Promoted L63 Peers: let's say you have at least one peer that in the past year or so has been promoted to L63. Why? Do you know why? Specifically, what did they accomplish, and what contributions do you see them doing to justify their promotion? Write it down in a team-culture career section you keep in OneNote (start that section now if you don't have it).

Now read over your answer. If you're going into that comfort zone of complaining about politics and butt-kissing and favorites, do me this favor: hold your right palm up, nice and flat like you're about to be sworn in to testify in a trial, and now extend your right arm out nice and wide, and then quickly swing your right arm around the front of you in a nice arc that ends with the flat of your right hand quickly connecting to the left side of your face for a hard, resounding slap. Repeat. Alternate to your left hand appropriately when tired. Continue to do so until you've slapped yourself silly to the point that you're not complaining about how other folks must just be connected or political or adept at the finer art of buttock tongue massage. Excuses and griping and bemoaning aren't the stuff that L63 contributors are made of. So either keep slapping yourself or choose to wake up. Until you can be honest with yourself (and it's not fun, trust me) you will be stuck doing what you're doing and your complaining will be the glue keeping you there.

Turn (it) Around, Bright Eyes: every now and then I get a little bit thrilled when someone joins the team straight out of school (or with a little industry experience) and after a few months it's obvious that Microsoft is the best company for them. They just plain resonate. They are 100% star material. Will they reach L63? Absolutely. And on one total-eclipse-rare occasion, I've been able to be answer the follow-up question: will they reach L65 and say with confidence: Absolutely. Well, what about everyone else? Sometimes the answer is, "well, we'll see..." and other times the answer is, "if they'd only stop doing X and start doing Y on a sustained basis, I could see it..."

If you're not an Absolutely! then do you know what more you need to do? And in your answer, there's a kicker follow-up: not only what you need to do to justify being promoted to L63, but to succeed in comparison to your L63 + L64 peers. For some teams - especially those like Office with few departures release-to-release resulting in level compression - that's a rough bunch.

I have seen people turn it around. If you're off-path, you can turn it around. You first have to be truthful with what direction you're going in and where you actually are trying to head. Get yourself a formal or informal mentor who is already doing what you want to be doing. Successful people looooove to expound upon the secret to their success. Some can even challenge you and give you the tough love and direction you need. Buy a Principal a coffee. There is no better investment at Microsoft for tuning your career. When someone gives you the hard advice to succeed, it's quite the gift. Don't waste it. It's a lot better than folks being ambivalent about your success or failure, right?

Your Team: you have to be able to understand why the L63s and L64s are where they are. You might have the Microsoft Senior Career Stage Profile in front of you all marked up and broken into more sections in OneNote, but which ones matter most to your team? And to your boss. And to your skip level. If your boss is saying "Yes, ready for promo now" and your skip is saying "No, not now" well, why?

Aspects of an L63 Contributor: some random aspects that come to my mind beyond our CSPs:

  • They can own a room: they aren't warming a seat but rather can take charge of a conversation and represent such a deep level of knowledge that they gain respect for what they say and earn a good reputation. Their focus stays on accountable results and this person can bring resolution and closure together.
  • Expert: They are sought after to be in meetings, for instance, so that good decisions can be made.
  • Results-focused: they are focused on getting great results and don't entwine their ego to particular solutions. They don't get defensive if their ideas are revealed to have flaws but rather delight in being able to move to a better solution.
  • Leadership: pro-active leadership that convinces team members of the future direction and even helps to implement it. This is a big difference between those who can complain about the way things should be and those you can actually bring it about.
  • Solutions, not problems: following up on the above, they aren't complaining about problems on the team but rather implementing and driving solutions.
  • Makes other great: the team benefits and grows from the person's contributions. Answers questions from the team, from support, from customers. Knows what the team delivers backwards and forwards. They are a good mentor.
  • Influence when they can, scare when they must: they have fundamental skills in influencing people, but if they need to flip into junk-yard dog mode, they can. They don't give up and walk away but rather fight when they need to fight, escalating only when needed and with lots of justification.
  • Makes the boss great: if the team and your boss are succeeding because of you, of course you'll be succeeding too.
  • Not doing it for the promotion: if you're out for a promotion, don't do work specifically chose to get the promotion. This is like meeting the Buddha on the road. If you come up with a pretty plan to justify your promotion, you've already lost it. Such plotting is obvious and actually detrimental to your career. If, however, you've determined what it takes to have a successful career in your group at Microsoft and have started what you need to start and stopped what you need to stop, then you're on the right path.

When I write all of this, I think back to an older piece by Joel Spolsky talking about Rosh Gadol contributors. Be the Rosh Gadol Microsoftie.

Also, go mine some of Dr. Brechner's Hard Code columns.

No, never: now, going back to that <<fill in the blank>> question above: if your boss is answering "No, never" then this is a red-alert moment for you. Flip on the klaxons! Why? Because when it comes time to roll people out of the team (as teams do from time to time) this "No, never" a marker that is used to help figure out who - at I and II CSP levels - is either on-track or out. If the answer for you is "No" and you don't like that, well, what are you going to do? I suggest understanding why it is "No" first, truthfully accepting the point-of-view as pissed off as it may make you, and then having a self-directed action-plan to get on track.

Discussion: First off, I'm going to be hard-core about comments here. I want them productive and about career success at Microsoft, especially your thoughts about achieving L63. What advice do you have to pass on? What advice do you need? What worked well and what really horked things up for you? If you're a manager, what's your L63 promotion philosophy? I'm not looking for any off-topic comments let alone woe-be-me comments - remember that slap thing?

If you have an itching to talk about something else, please go here: But Mini, I Want To Talk About...


But Mini, I Want To Talk About...

Don't want to talk about reaching L63 at Microsoft and bummed that I've locked down the comment stream on that post to be my way or the cutting-room-floor?

Tell you what I'll do: I'll put this post up to have a post to riff within, but still stay within my commenting guidelines.

What's on your mind?

  • Who's still hiring at Microsoft? How teams are locking down and freaked out about the risk of losing positions if people try to leave? Ideas to move groups?
  • Wondering if the mobile team can be possibly slapped enough to compete against the iPhone and Android momentum?
  • What's up with Arik Hesseldahl calling Microsoft big and bloated? Is that passé now?
  • I still love my Media Center PC, even though lately it's started hating all of us... is this how SkyNet starts?
  • Azure. (shakes head) It makes me want to sing to the Talking Heads about how this is not my beautiful house. It's a solution. It will solve problems. Are they really the right problems, and therefore, is it really the right solution?
  • Kudos for a great PDC / Win7 debut. I'm drawing hearts around my sketch of SteveSi... and littles x's and o's... ahem.
  • On that theme: since the Company Meeting 2008, I've felt that we've turned a corner. A good corner. Do you agree, and if not, what do you believe has to happen for Microsoft to have turned the corner onto the freeway of success?
  • What topics would you like to see discussed in future posts? Ooo, I knows! Something about the new Microsoft Store on the internets!

Wednesday, October 22, 2008

Microsoft FY09Q1 Results

FY09Q1: wow, I wonder what's going to be on everyone's mind during this quarter's webcast with the analysts?

  • "How has the global economic crisis affected Microsoft?"
  • "What product groups are the most affected? The least?"
  • "How has your forward looking assessment changed for FY09?"
  • "What kind of efficiency measures are you putting into place?"
  • "According to reliable sources (ahem) the Microsoft hiring freeze through major parts of the corporation is real. How does this hamper Microsoft's ability to hire the best talent and to retain the best talent?"
  • "Are you going to buy Yahoo! since it's so much cheaper?" (Please keep Mr. Ballmer away from any recording device during this question.)

etc. etc. Any big questions you're looking to be answered?

Pre-announcement portion: my suggested post-analysis sites for quarterly results:


Interesting angle Microsoft has come with during the global economic crisis: when money is tight, drop those custom solutions and go with Microsoft to save money and be more cost effective. Nice. Post-analysis postings of note (to me):

Mr. Joe Wilcox:

Mr. Todd Bishop:

Mr. Joe Tartakoff:

Mr. Brier Dudley:

It will be interesting to see the $500,000,000USD savings in action. There was some probing by the analysts on that but just a broad answer in response.


Sunday, October 19, 2008

Is Microsoft Recession Proof?

Is Microsoft recession proof? No, of course not. While it can be buffeted back in forth in a mild recession and get through without group parties here and there, it's pretty unclear what kind of Microsoft will emerge at the other end of a deep global recession. Just a quick post about the immediate staffing impact as we head towards quarterly results.

First: thank whatever deity you hold dear that we didn't go forward with that Yahoo! acquisition. How crazy would that look now?

At this point, organizations are being told to eliminate inefficiencies. For different organizations this means some pretty radically different action items. For some parts of Microsoft, this means hiring freezes. While hiring freezes aren't any fun (more below) you probably prefer them to full-blown Reduction in workForce (RIFs... though I guess that would be called RIWs or RIWFs).

What we need, though, is one big RIF.

There is an unfortunate consequence to hiring freezes for Microsofties: those ready to move on to a new position are stuck because there is no where to go and, even worse, those who have already gone through an interview loop are having their offers frozen out. Also, any attrition is not going to be backfilled and the org loses that headcount. Let's talk about this.

Now first of all, I'm all for reducing Microsoft's headcount. I was for that, what, 40,000 hires ago? Microsoft's key asset and key overhead are the Microsoft employees. You reduce that right, you save a bunch of money. And it is not just a one time saving.

I'm all for good and bad attrition. But I'm concerned about implementing unhealthy policies vs. just a one big 10% or 20% reduction all-around (we've identified 10%-ers already right - at least 10% Situation I-ers). If you do this big and once and you can still backfill future attrition and let people move around the company into new positions.

It's unhealthy for Microsoft to lock people into their jobs, which might be the reality for the next half-year to a year. I want the most talented Microsofties to - as their current commitments come to a close - look around the company and find new challenges to move to. It makes for stronger careers building our future leaders and creates stronger results. It also makes bad teams fail sooner by loosing key contributors. What's even worse, perhaps for planning, is that people will be locked and not moving on during a natural product cycle rhythm coming up (major product groups, for instance, going into stability), and these same people, once headcount reopens in the future, will be abandoning their commitments mid-way. Uncool. Unsurprising.

As for being told "Hey, we're not going to let you fill your attrition." Well, what group, let alone empire builders, is going to move on bad contributors now? Better to limp along than have reduced capacity. Not even that alluring, "Wouldn't you want to move-on that plateau'd L61 person with a hot college new-hire?" works now.

Some comments on this. First a common hit on most teams:

time to talk about layoffs. Hiring is frozen and teams are being told to reduce head-count through attrition. Sounds like layoffs to me.

What happens when you want to move internally and have already interviewed (oy!):

Any updates on the hiring freeze anyone? I desperately want to get out of my current team but teams I have interviewed with are withholding offers because of this damn freeze...

An excellent manifesto on hiring freeze for talented contributors:

What the Hiring Freeze Means to Me - An Open Letter to HR

I am high performer, a gold star winner, have a relatively high level and I have a problem.

In an all too common scenario, my group was re-orged and I was given a new manager. As is many times the case, this manager is well regarded for his technical skills but is absolutely an abysmal manager. He has little aptitude or interest in actually managing his people and still operates like he's an IC.

Multiple members on the team have gone to the new manager, as well as the skip level manager to discuss the situation.

The skip level manager now has a dilemma - does he support the manager, and help him grow into the role?

If he does, it will clearly take 6+ months, and this is on top of the 3 months it took the team to muster the courage to escalate to the skip level manager to begin with. If the manager stays and doesn't improve, myself and the people on his team will surely take a hit at review time at the end of the year.

In our case, the manager doesn't know what to do. He's thinking about it, and in fairness we recognize he's in a tough spot.

All the while, though, the clock is ticking, and the high performers on the team are looking for the exits. We're demotivated, demoralized, and are placed in a position where we cant realize our potential.

Most people reading this are likely nodding their heads. This happens here. Alot.

Typically when this happens, employees see this as an opportunity to explore another part of the company, and round out our experience.

But not today. There's a hiring freeze, no internal transfers are allowed, and we're stuck.

We've done the appropriate thing, we've talked with our manager and our skip level manager. We're now in a weird limbo.

Of course this comes at a time when we're in a down economy, and in many respects lucky to have our jobs. We're sure as heck not going to rock the boat any more than we already have.

This seems to leave to options. The first is to suffer in silence, the second is to leave the company.

Neither of these options are good for us or for Microsoft.

Our group is not alone.

I'd ask you to consider four things:

(1) New rule - anyone new to people management is on a trial basis for the first year, to be reviewed and renewed quarterly.

(2) New rule - anyone new to people management shouldn't be given a team of more than two people. If they do a good job with two, go to five, and so on.

(3) Make managers of managers responsible for their appointments.

If you put a bad manager in place, and you don't resolve the issue after 1-2 quarters, you take a percentage hit on bonus and stock.

This will result in people spending more time in the decision making process for this.

(4) Allow for internal transfers, atleast for higher level positions. When you take high leveled, high performers and you put them in a position where they can't be high performers due to poor management, they either leave or grow demoralized and become less productive to accomodate a bad manager.

Eventually, this second group also leaves, with the ones that don't downgrading to average performers.

A snippet to re-enforce that:

Internal is frozen, too, for the most part. I see Live and MSN technical openings, and various business-oriented ones. I had just seen a couple positions for which I wanted to do informationals. Before the hiring managers and I met, they both called me and said that they had just been told that couldn't hire anyone for the time being.

It's really my time to leave my team, because the three year timer is ticking and I'm topped out in my org given the kind of work management wants it to do. I'm capable of more, but the level of work isn't there. When I've tried to just go get it, I've caught flack from management - because I was taking on actual business risk that scared them, instead of the safe work our team usually does. I don't like the online services biz, so I hope the powers that be finish evaluating the business climate and open up a few more product heads in profitable divisions sometime soon. My preference is PM or dev in Exchange, as I'd like to contribute to that. But at this point, any core product would be interesting.

I think that this is an opportunity for major change vs. aloof delegated inefficiency hunting, but major change has to come from SteveB. If need be, the global climate gives Microsoft cover to make big revamps. E.g., "...the economy made us do these big cut-backs vs. us doing what we should have been doing all-along." It is too soon to expect this during this week's quarterly results, but within the next quarter, as the impact to reduced global PC sales becomes apparent, we should be ready to announce some major overhead reduction (e.g., not towels but rather less butts for said towels to dry - win-win). And remember: you cut once and you cut deep. Incremental pain is unhealthy and all that you're doing is poisoning your teams and setting up a huge round of bad attrition once things turn around.

I imagine each one of you wants to make your team better and more productive and streamlined, and have ideas for your team and beyond. This is an excellent time for our HR leadership to re-engage Microsofties plus finally join the 21st century and implement team-focused awards. Yes, we would still offer differentiated awards, but team achievements must be recognized with the same level of attention that our super-star hero culture is given. Who doesn't want an excellent team to be rewarded, let alone dysfunctional underperforming teams torn apart?

So, if your team had to get by with 10% less budget, how do you think it would be best addressed?


Friday, October 17, 2008

TableBrowser.NET (a small .NET BC tutorial)

Here is a Visual Studio solution, demonstrating how the Dynamics AX database can be queried through the .NET Business Connector, and how the results of this can be presented to the user in a user-friendly manner.

Here is a screenshot of how it looks:


You can download the solution on axaptapedia.com.

The class to investigate in the solution is the DynamicsAX class. It provides a pretty good interface for reading data out of Dynamics AX.

After opening the solution, make sure to replace the BusinessConnectorNet.dll, pointing it to your AX installation path (if it is not in GAC)

Tuesday, October 7, 2008

The future of programming languages or Anders Hejlsberg/Steve Ballmer Tech-Pep-Talk

Sunday, September 28, more than 350 IT-professionals from the entire country (Denmark) came to MDCC (Microsoft Development Center Copenhagen) to get a 90-minute TechTalk from Anders Hejlsberg and a 15-minute PepTalk from Steve Ballmer.

Click here to see the video.