You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Scenario-Focused Engineering is how we are approaching designing the next version of Office. The goal is to make the experience of using Office revolve around what you, our customers, do with the applications; to do our best to design through your eyes. This extends right down to writing Help. We plan to deliver scenario-based Help in the next version of Office.
In thinking about this, I wondered what kind of scenario writing most appeals to people using Publisher and Office generally. In the past we've tended to use scenarios in writing fairly technical IT deployment Help, such as these business intelligence scenarios, or these SharePoint 2003 scenarios, or roadmap articles like this one for SharePoint 2007 that wraps a set of articles into a coherent organization. For the Information Worker audience, we've produced some scenario-based videos, such as the Office Intervention series. And I've put together a roadmap style article on manipulating images in Publisher 2010, but we haven't had a consistent philosophy about scenarios and Help.
So, my question to you is, what do you want from scenario-based Help?
Please sign in and leave your thoughts in the comments section. No, really, please do help me get a better handle on how to effectively write scenario-based Help.
"Help me, help you." Jerry McGuire.
-- Bob deLaubenfels