Microsoft’s Penultimate #BeTheNext Episode: We’re On A Boat!

The search for the next Microsoft Employee continued with the fourth episode this week. So far we have had three different winners the first three weeks of the series. I found myself pulling for Alex this week to make it a perfect four winners in four episodes.

The contestants were put on a ferry boat that runs from Seattle to Bainbridge island, a trip that takes about 30 minutes (and I am thinking I may take myself while at the PASS Summit later this year). While heading out they were given their next assignment. They were to troubleshoot a scenario by collaborating with one another to arrive at a solution. Oh, they also had to finish and present their solution by the time the ferry returned to Seattle.

One of the first things I noticed in this episode was the absence of coffee. How could Buck Woody (blog | @buckwoody) be without coffee for so long? How could I possibly trust his judgement without a triple-quad double pump extra whip eggnog latte? My friend Dandy Weyn (blog | @ilikesql) was the guest judge this week, and I know he loves coffee as well because I saw him install an instance of SQL Server in less time than it takes to make a cup of coffee while onstage with me TechEd this year. So, where’s the coffee? If they had some, they didn’t show any in this episode.

It was interesting to watch the four of them work through the problem. They were being judged on their collaboration skills as well as their technical skills. It is becoming quite clear that Microsoft wasn’t just looking for the sharpest knife in the drawer; they want someone who can compose an idea, present it to others, and defend their idea when others ask questions. That’s what this challenege was meant to show. I think it worked rather well, too.

After the 30 minutes was up the group had no solution to present. Stacy tried her best to present a partial solution but the group was quite divided on the final answer. Clearly 30 minutes wasn’t enough but I’m not sure how much time would have been enough. Frankly, what topic could a group of DBAs ever agree upon within 30 minutes? I’ve been with a group of DBAs that can’t even decide on dinner.

Back at the house Buck, Tim, and Dandy gave their judgement. They explained two very important things. First, when you have an idea that you believe is right, you need to voice that opinion. Second, it is OK to pick apart an idea, but it is never OK to pick apart a person. Alex was closest to having a solution but didn’t convince the others that his idea was sound.

And there’s the rub: how do you know when to push and when to stand back? I think that is a skill that comes with experience. As we saw here, just knowing the correct technical answer isn’t enough, you have to be able to explain why your answer works and is the best answer out of all possible choices.

The judges (with shades on, apparently they chose the only sunny day in Seattle, or they couldn’t wait ten minutes for Sol to go back behind some clouds, or Buck needed them because he hadn’t had any coffee that day) did not declare a winner, but they did award the prize package to Alex. The prize was an MSDN subscription, one of the perks I enjoy as a SQL Server MVP. I’m sure Alex is going to enjoy it! All contestants were then given Windows phones, in an effort to help them communicate better. If any wireless provider is able to come up with a “successful collaboration” calling plan, they will make millions.

As the group was relaxing for dinner Buck walked in uninvited (boy, do I know that feeling) and handed down the next challenge, which involves having all four contestants staying up all night to design a solution. I can’t wait to watch next week!