[IxDA Discuss] What do you think of Microsoft Surface
Chris Bernard
Chris.Bernard at microsoft.com
Thu May 31 14:43:24 PDT 2007
The MVP process certainly has its place but as you've also illustrated Will it has its shortcomings too. The roots of the process you've described are the squeaky wheel getting the oil. The MVP process is what helped Microsoft in its race to feature bloat with products like Office 2003 and numerous others and was simply Microsoft extending its heritage in designing with the loudest voice in mind.
See here and here for some context on what Office 2003 became (although I suspect we are all familiar with this story)
Here's a Webcast that talks about the feature bloat of Office 2007
http://download.microsoft.com/download/1/f/f/1fff960f-51a2-44b1-b033-bf25a3c7c7ab/BRE001.wmv
Here's a blog from Jensen Harris, Product Manager of Office 2007 team.
http://blogs.msdn.com/jensenh/
I'll be contrarian here and suggest that if you really did these two following things you may have often done a disservice to the products and services your group worked on.
"1) Never contradict the MVP. Make sure you know precisely what he's
complaining about, and what he thinks would be a good solution. If he
missed some important point, find out why. We are here to learn. The
MVPs are the teachers."
MVPs are also a political animal and have agendas that can conflict with the needs of the business and users.
"2) Every _individual_ MVP complaint, concern or suggestion WILL be
written up as a detailed entry in the bug database BY END OF DAY.
Every MVP bug will receive the same attention and regard as a bug
written by the chief design PM, and will live or die on its own
merits. Each MVP will be kept appraised of the progress of 'their'
bugs and will be given chances for further comment."
Some 'bugs' were simply feature requests because a tool or product didn't do what an individual wanted. Taking this stuff at face value without other context or validation is simply a poor way to design.
Now leveraging the MVP process in conjunction with good IxD principals and other sensing programs certainly has merit but I quite frankly can't think of a worse idea than opening ideas like the iPhone or Surface to this board. If that had been done I doubt either would have ever gotten off the ground.
What I see on this board quite often is a rush to turn assumptions based on incomplete information into facts with which we summarily judge our peers competence with. That's not a dialog or a discourse and who would want to be on the receiving end of it. I suspect folks will simply find other more constructive forums to have those conversations.
Chris Bernard
Microsoft
User Experience Evangelist
chris.bernard at microsoft.com
312.925.4095
Blog: www.designthinkingdigest.com
Design: www.microsoft.com/design
Tools: www.microsoft.com/expression
"The future is already here. It's just not evenly distributed." William Gibson
-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com [mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Will Parker
Sent: Thursday, May 31, 2007 3:25 PM
To: pauric
Cc: discuss at lists.interactiondesigners.com
Subject: Re: [IxDA Discuss] What do you think of Microsoft Surface
On May 31, 2007, at 12:12 PM, pauric wrote:
> "we're supposed to be the poster-children of abductive thinking"
>
> With all due respect, we're supposed to apply a little real world
> context to marketing hyperbole and engineering out design.
<snip>
> When are people supposed to ask questions about re-purposing a table,
> security? Whats the business case for a device thats only going to be
> found the executive lounge of the airport/hotel?
>
> There's nothing wrong with getting excited about this but there are
> valid questions about context of use and it's exactly our job to ask
> them.
Back when I worked at Microsoft, we had a practice of flying in MVPs
('Most Valuable Partners') moderately late in the development process
to give them full access to the upcoming product and the PMs, devs
and other people bringing the product to life. The MVPs were
individuals who were acknowledged masters of the product, well-
respected in the user community.
We would show them the product, let them beat on it with whatever
sticks they wanted to use, and complain as loudly and profanely as
they liked about what we left out or failed to fix.
We had two hard and fast rules from our Group Manager about MVP days,
and since he was a former tank commander, you'd better believe he
expected us to follow them religiously.
-----------------------
1) Never contradict the MVP. Make sure you know precisely what he's
complaining about, and what he thinks would be a good solution. If he
missed some important point, find out why. We are here to learn. The
MVPs are the teachers.
2) Every _individual_ MVP complaint, concern or suggestion WILL be
written up as a detailed entry in the bug database BY END OF DAY.
Every MVP bug will receive the same attention and regard as a bug
written by the chief design PM, and will live or die on its own
merits. Each MVP will be kept appraised of the progress of 'their'
bugs and will be given chances for further comment.
-----------------------
Microsoft Surface looks like a very promising version 1.0 product,
but judging _just_ from the marketing demos (as we must at the
moment), there are some moderately serious gaps, relative to _real-
world_ usage, in the use cases presented. And yet, the defining
product for an entirely new platform is slated to ship within the
next 6 months.
I submit that it is time (and possibly well past time) for Microsoft
to start gathering MVP opinion, following the two rules cited above.
Given the challenges and opportunities of a new multi-touch platform,
I further submit that we here on this list constitute one well-
qualified group of MVPs.
Merely applauding the impending launch may provide (well-deserved)
gratification for the Surface team, but doing so provides little
usable information. Telling critics to ignore current shortcomings is
one way to further reduce the flow of potentially useful information.
This risks stunting the product. Applause is nice, but bad reviews --
if honestly given -- help you learn.
As an aside, I work for a large advertising company. It is obvious
that Microsoft Surface devices will play a large role in kiosk
advertising at the very least, so despite my misgivings about what
I've seen (or rather, not seen) in the current demos, I have already
recommended that we get a Surface machine ASAP.
- Will
Will Parker
wparker at ChannelingDesign.com
"I wish developing great products was as easy as writing a check. If
that were the case, then Microsoft would have great products." -
Steve Jobs
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://listguide.ixda.org/
List Help .................. http://listhelp.ixda.org/
(Un)Subscription Options ... http://subscription-options.ixda.org/
Announcements List ......... http://subscribe-announce.ixda.org/
Questions .................. lists at ixda.org
Home ....................... http://ixda.org/
Resource Library ........... http://resources.ixda.org
More information about the discuss
mailing list