Sign In
Try. Experience. Discuss.
Home  |   Blogs  |   Jobs  |  About
Microsoft Office Labs demo during the CEO Summit Keynote

Wow… exciting day here at Office Labs.  This morning, Bill Gates, chairman of Microsoft Corp., delivered his final CEO Summit keynote address titled “The Next Wave of Business Productivity and the Challenge of Continual Innovation” to more than 115 CEOs from around the world. Quick background: The Microsoft CEO Summit is a premier forum that unites the world’s business leaders to discuss and debate the most pressing economic, political, social and technological trends shaping the global business landscape.

 

You might wonder what this has to do with Office Labs?  If you had a chance to see Bill’s keynote, you probably remember the TouchWall / Plex demo.  This work is an example of some of the research we are doing as a part of our envisioning effort.  We are exploring new technology before people even know they need it, helping to paint a picture of what the future could look like.  We are evolving software solutions for people to work better and smarter. It was a thrilling opportunity to share some of our envisioning explorations with the CEO Summit audience here in Redmond and via the web cast with viewers like you from around the world!

 

So a bit more detail… what are TouchWall and Plex? TouchWall is a research project, developed in conjunction with our friends in Microsoft Research.  It is large format display prototype, built to more deeply explore collaborative multi-touch interaction scenarios. Plex is a research prototype from Microsoft Office Labs.  It explores an alternative experience for organizing, exploring and presenting content. Like a vertical representation of Microsoft’s Surface technology, it lets the presenter give an infinite tour of materials in a more dynamic format.  TechCrunch and CNet have already reported on the TouchWall and Plex in their blog posts.

 

Over time, you’ll likely see more envisioning explorations on officelabs.com. We know that some of you came across our future health vision video on popular video sharing sites. This video showcases real emerging technology concepts from Microsoft Research and partners. It provides a glimpse of what we believe is a possible scenario in envisioning technologies’ impact on the future of health. Office Labs’ work is based on comprehensive research of global social, economic and industry trends in light of emerging technology shifts and transformations. With close input from customers, partners and subject matter experts from around the world, our team is constantly evolving future productivity explorations. We hope to share more of those explorations with you on officelabs.com. Stay tuned.

Why did we build Search Commands?
I’m Aravind, the Lead Developer of Search Commands, and I’d like to tell you about our motivation and vision for Search Commands.
 
When we started this project, our goal was to advance the state of user interface technology to make it more natural. Initially, we thought that a “natural user interface” was mostly about speaking to the computer, but as we looked into user problems by looking through help query logs, newsgroups, books, etc., we came to realize that the real challenge was to make it easy for the computer to better understand the user, and for the user to better understand the application. A conceptual misunderstanding on the user’s part, of how the application works (not EVER the user’s fault by the way) means that neither written nor spoken words can represent the whole picture of the user’s goal. For example, if a user wanted to change the background image on all slides of a PowerPoint presentation and she wasn't aware of the Master Slide feature, she might express her intent as "change background" instead of "setup a master slide". For her to understand that there is a better option, there needs to be some way for the application to have a conversation with her to figure out what she wants.
 
For example, let’s take a real life example of ordering food in a restaurant. When you are given the menu, you read through it and while some items are clear, for some you might need additional information. When the waiter comes to take your order, you can:

i.  Point to a dish you want.
ii. Say the number next to the dish.  (e.g.  V32 for Mongolian Tofu).
iii. Ask the waiter to tell you which dishes fit particular criteria (e.g., the “vegetarian” options or the dishes that don’t have much spice).
iv. Have a conversation with the waiter where you learn more about the different dishes and the waiter gets a better idea of what you want. For example, listen to the specials, find out what ingredients they have, and pick the one you want.
 
Depending on your familiarity with the cuisine and the restaurant, you might pick different ways of ordering. In Starbucks I always get a 2% extra hot tall latte, but in an unfamiliar restaurant I would have to talk to the waiter to better understand the different options.
 
Imagine now that restaurants banned the use of language and so waiters can only take your order if you point to a dish you want or say its number on the menu. You are not allowed to ask any clarifying questions, and so you are limited to just reading the one line descriptions of each item, and pointing to the one you want to order.
 
In such a world, because of the limitations of how you can express your intent, the design of the menu becomes very important, and restaurants will have to think carefully about their dishes in terms of the ease of ordering rather than the merits of the dish itself. You might take the trouble of reading a book on how to order food in your favorite restaurant. That way when you go there, you will be able to point quickly to the dish you want. Experts might even offer courses in “how to order food.”
 
After several years of only pointing to menu items in restaurants, restaurants will work on making user-friendly menu systems. They will add picture menus, icons for spice levels, etc. People will debate the merits of different menu designs:
 
• Some people would wonder why restaurants offer so many choices. Twenty years ago, the beverage menu had only three choices – coffee, tea, and hot chocolate. Now you can order 2% grande mochas with whipped cream. Does anyone really need so many choices?  After all, no one orders more than ten different items from the menu. Shouldn’t the menu have these ten choices only and nothing else?  Then we can just learn the numbers of the dishes we want, and they will be easy to order.
• Some people would have become experts in a particular menu. If the menu changes, there will feel frustrated – where did number 56 (Mongolian chicken with fried rice) go?
• Some restaurants will advertise their ease of ordering as the differentiating factor. Their simple, clean menus with a small number of items will appeal to people who don’t want to spend a lot of time reading the menu and looking for stuff to point to.
•  After years of training, when asked if they would prefer to just tell their order to a waiter, some experts in the old system might think it is ridiculous to talk to the waiter. After all, ordering food is about pointing and choosing – if you need to talk, the restaurant menu is badly designed, and you should just go to another place to eat.
 
These examples sound silly as we can’t relate to the idea of restaurant menu’s being difficult to use or that the design of their menu’s as being important. That’s because the menu is only a starting point, and we can use language to find out more about different dishes and to place our order. There is no need for us to learn the positions of different dishes on the menu.
 
However, with computer software we are limited in our ability to express our intent, and are forced to spend a lot of time learning the menu design of applications, when we really only care about doing our work. Ideally, the menu should be the starting point, and you should be able to have a conversation with the application.
 
Even the best designed menu will still need you to learn some concepts about the application. For example, I came to the U.S. as a grad student, and on my first day I went to a McDonalds. As I’m a vegetarian, I read the menu in order to find something to eat that wouldn’t have meat in it, and I picked the cheeseburger!
 
Changing the interface of software applications to allow for language input and the ability to have a conversation is a very old and ambitious goal. The challenge for us was to how to take a baby step and still solve a real problem. Search Commands is what we came up with. Given that building true language understanding is very hard, we decided to treat it as a search and UI problem. We would just create a list of keywords and map each keyword to different commands. We would use the frequency of command use to rank the results and use feedback to improve the system. That way if someone types in a word we don’t have in our word list, we can add it later and the system keeps getting better. The second part is about dialog. For selected queries that are ambiguous and require the user to understand a concept, we built lightweight wizards or guided helps (An example is the change background wizard in PowerPoint). In my next blog post, I’ll talk about some of our designs, our findings, and ideas for the future.

 
Search Commands: additional FAQs
Hey everyone – thank you for all the great feedback and suggestions so far on Search Commands!  Please keep it coming…
 
Along with feedback we have gotten a lot of questions most of which are in the Search Commands FAQ.  Below is a recap of the most frequently asked questions and a couple of new ones.
 
Is there a hotkey for Search Commands?
Yes -- Windows key + Y, if you have other add-ins installed it will require a number as well e.g., Windows key +Y1. When you press the Alt key it will show you what the hotkey is.
 
How can I view where a command is on the Ribbon?
After you do a search hover over the command you are interested in. The location on the Ribbon will be displayed. A few users have noticed that in some cases the location isn’t the most direct.
 
Search Commands is not working, how can I fix it?
There are a few common problems people run into. Search Commands does not work with a minimized Ribbon. In Excel you must press enter to execute the search. Sometimes add-ins become disabled and need to be enabled, enable instructions are here.  Check out more information on the known issues here.
 
I have done all that and it still is not working, how can I uninstall it?
In Vista: Control Panel -> Programs -> Uninstall a program -> Search Commands from Microsoft Office Labs -> Uninstall
In XP: Start -> Control Panel -> Add or Remove Programs -> Search Commands from Microsoft Office Labs -> Remove
 
note: it has been reported (but not verified) that uninstalling and reinstalling has fixed problems people have run into
 
I sent in an awesome suggestion for Search Commands, when will Search Commands be updated with it?
We do appreciate your suggestions, however there are no planned updates for Search Commands.
 
Can you please provide Search Commands in Chinese, Dutch, French, German, Italian, Korean, Russian, etc?
抱歉, Droevig, Désolé, Traurig, Spiacente, 유감스러운, Огорченно, QoS, Sorry….  No, Office Labs will not be providing different language versions of Search Commands. We are running the concept test in English only. For more information check out this explanation of Office Labs concept tests.
 
Can you please provide Search Commands for Access and other Office applications?
Sorry….  No. Search Commands is only being tested in Office 2007 - Excel, PowerPoint, and Word. For more information check out this explanation of Office Labs concept tests.
Tips and Tricks on Making Good Videos

Hi, folks! It’s been a week since we launched Community Clips, and we’re starting to see lots of community-generated videos coming in. We’ve already had 32 community-submitted videos (some of them are tests) –  and that’s exciting! I thought now would be a good time to share a few quick tips and tricks on making good videos. Feel free to share your own thoughts in comments.

 

·      Keep it short. Viewers will want to rewind and replay your video, to make sure they fully understand how to do the task at hand. The shorter the video, the easier it is to digest, and the easier it is to find the part you want to watch again. We recommend 2-4 minute videos.

·      Close other apps. Any app that might pop up in the middle of a recording (ex: mail clients, IM clients, etc) could make you have to restart your recording. Not to mention, the Community Clips recorder can eat up a lot of your CPU (it’s a prototype), so you’ll have better performance if you close everything other than the apps you want to record.

·      Change your screen resolution. Your videos will look best if you set your screen resolution to 1024x768 before starting your recording.

·      Minimize background noise. It’s a good idea to silence your phone, and shut the door (if possible). The less ambient noise, the clearer your audio stream will be.

·      Give your videos descriptive names (and tags). Most viewers find videos by searching for them. The more descriptive your name, description, and tags, the more likely it is that viewers will be able to find your videos. It’s good practice to think of key words – either official names of features (ex: AutoText) or friendly names that you think viewers will think of during search – and add them as tags.

·      Speaking of tags…add your own! Did you know that you can add tags to other people’s videos? It’s true. Let’s say you search for a video on a particular topic, don’t find it, and then you browse collections by clicking the Video tab. If you stumble upon the video that you were searching for but couldn’t find, why not leave a tag with the search term you tried? Just sign in, and add tags in the left column under the Tags header.

 

 

Thanks for all of the feedback so far. We’re trying to respond quickly as issues get reported to us, so please keep the feedback coming! Be sure to visit our discussion forum to connect with other Community Clips users.

Welcome to Microsoft Office Labs
"Welcome to Microsoft Office Labs." It's great to be able to say that. For quite some time the Office Labs team has been exploring ideas internally at Microsoft. Now we'd like to show you some of our ideas and ask you to give them a whirl.
 
We're a group of designers and developers that collect ideas from all over Microsoft (but mostly from Office and other products related to 'getting stuff done' - what we call 'productivity'). We build working prototypes of the most promising of these ideas to see if they work as well as we hope they might.
 
Concept testing is what this site is all about.  The projects you find here are not products or beta versions. They don't even pretend to be complete product ideas. They are the equivalent of 'concept cars' for software. Automotive companies sometimes produce near and far-future test vehicles to test design concepts or features to see how effective they are. In most cases there is no intent to productize the vehicles as shown. They simply work for the purposes of getting feedback. We do the same for software. The difference is that you to get to test drive the concepts. Because of that, all these experiences are strictly 'use at your own risk', and we can't promise to fix every bug that is reported but we'll try to nip the worst ones.
 
We are often asked if any of the things seen here will become products or features of products in the future. It's possible that some of them will appear in some form. But what we are really after is feedback and information from you. We want to know how often people use these tools. What parts of them are used most? What are the patterns of usage? Do they work for you? You may see some of the concepts updated over time to improve them based on the feedback. Even with all that, most of these ideas just won't make the cut for a product. Even when something is pretty useful, there are usually many other things even more useful to more people that are selected for inclusion in our products.
 
You might be wondering why this site isn't located on microsoft.com. One reason is simple: we didn't want to give anyone the impression that these projects are full blown Microsoft products. This site itself is also a concept test. Over time we'll be modifying it to experiment with ways to engage with you, our community.
 
You may have read the team blogs for various groups in Office, such as Word, Excel, SharePoint, and so forth. This is the Office Labs team blog. Check this space for updates from us on our work and behind the scenes stories about the various projects that show up here. And please, join in the discussion - we want to hear from you.
Welcome to Community Clips

We set out to build Community Clips as an experiment, or “proof of concept,” around communities and help.  Months ago, we were talking with some teams at Microsoft that run help and support sites, about making these sites even more useful for customers. We started thinking…what if, instead of just providing help for people, we actually encouraged them to help each other? Let’s face it: any person who doesn’t work for Microsoft, who tells you that he really struggled with something until he figured out a particular tip or trick, earns a lot more street credibility than we do. People know what issues they struggle with, and maybe they’ll be likely to share their successes with their peers.

 

But we had a lot of questions. Sure, sites like YouTube and Soapbox have huge communities of users, who actively view, rate, upload, and discuss videos, but the videos are about all sorts of subject matter.  If we were to narrow the focus to help and how-to videos, would we get a similarly active (though smaller) community, or would the traffic patterns be dramatically different? Are people willing to share their knowledge of Microsoft products, specifically Office? There might be a lot of people who want to view videos, but what would motivate people to create videos? We can use all sorts of market research and formulas to predict the answers to these questions, but in Office Labs we took a different approach. We built it. We want to see for ourselves what would happen!

 

Working at Microsoft, it’s really easy to become an expert on Office.  Whenever we don’t know how to do a particular task, we poke our head out of our office and shout down the hall something like, “Anyone know how to summarize a pivot table by sum instead of count?” Someone is bound to know the answer. We walk over to that person’s office, watch over their shoulder, and successfully – and proudly – pull it off.  Well, most people aren’t so lucky to have an immediate network of experts who are happy to share their proficiency. Office Online has loads of help content, Microsoft Help and Support has loads of KB articles, and MVPs do a great job of spreading the world and solving real users’ questions. But the reality is, most people just don’t know about these opportunities, or don’t utilize them! That’s why we created Community Clips. Let’s create a place where people can meet each other, share tips and tricks, and connect over a desire to become better Office users.

 

There are 3 people working on Community Clips – me (a program manager) and two developers.  Since Community Clips is a proof-of-concept, you’ll see a lot of iteration in the next few weeks and maybe even months. We’re going to pay close attention to what motivates people to do the things they do, and then we’ll start introducing new features and will measure their impact. We really want to hear from you. What do you think of the project so far? What else do you want to see? What do you want to see done differently? A lot of the iteration we do will be based on the feedback you give us. So please, check out Community Clips, and let us know what you think!  

 

And don’t forget: ANYONE can create a video! Don’t be bashful! You don’t have to be an expert (but if you are, that’s great too)! To create a video, just download our lightweight recorder to get started.

Why Search Commands?
Before answering why Search Commands, thank you for downloading it if you already have. If not, we hope you do soon.  
 
So, why Search Commands? Searching for commands in applications follows the trend of searching for information on the Internet and on your own computer. When Web surfing first became a mainstream activity, people relied on directories like Yahoo!’s to find specific Web pages, much in the same way they relied on folder structures to find documents on their computers. But the large number of Web pages made browsing an inefficient way of finding a Web page. Similarly, the number of e-mail messages, MP3 files, photos, and other types of files made browsing the computer a pain. Search interfaces came on the scene as a welcome addition to browsing. The question brewing within the team was what are the advantages and disadvantages of using search as an additional way to access commands in software products.
 
A prototype was created to evaluate the idea. Earlier versions were used by Microsoft employees to test out this concept with Office 2007 – Word, PowerPoint and Excel.  We selected these applications because they are successful, have a lot of commands, and have an extensible UI. The feedback and usage metrics generated by the Microsoft employees greatly helped to improve the early versions of Search Commands.  Now we would like everyone to try out the prototype.
 
Office Labs will be collecting and analyzing feedback and usage metrics from users to understand what are the advantages and disadvantages of using search as an additional way to access commands in software products. Think of it as one big experiment.
 
Interested? Install Search Commands and please let us know what you think
Questions? Check out the Frequently Asked Questions and Answers
Comments? Post away.  Comments should follow these guidelines

 ‭(Hidden)‬ Admin Links