![\"\"](\"http:\/\/www.danielpjohnston.com\/graphic-language\/wp-content\/uploads\/2011\/08\/ms_word_2003_reference.jpg\" "\\"ms_word_2003_reference\\"")
\n<\/p>\n
\n<\/p>\n
Is all this really necessary? For everyone? All the time? Microsoft Word 2003 window, new document; shown approx. 50% actual size<\/p>\n
<\/p>\n
For something with such a simple purpose, and an even simpler name, Microsoft Word<\/i> sure does seem complicated. From the moment a user opens a new document until they finish\u00e2\u20ac\u201da three-word note or a three-thousand page novel\u00e2\u20ac\u201dthey are surrounded by an acerbic cadre of mismatched toolbars, icons and menu options. The vast majority of these are never used. Many of these never should be used. Most people using Word<\/i> don’t need to do complex math equations or manage mail-merge settings, they don’t need hundreds of oddly-colored warped lettering options and they don’t need to create a web page; they need to write a paper.<\/p>\n
\nAs part of a cooperative workshop one of the Visual Communication Design professors at the University of Washington set up with one of Microsoft’s design leaders, the few of us who chose to participate were asked, “What should Word<\/i> be like?” DPJ Word<\/i> interface mockup, new document; 1024 x 768px + \/ 2004<\/p>\n \nWriting often requires intense focus. The primary goal of my prototype was to provide the least distracting, most intuitive and flexible interface for paper writing, editing and reading, while integrating simpler navigation of documents large and small… DPJ Word<\/i> interface mockup, page 1 of 2 in document, focus screen set to reveal one line of type in the middle of the page; 1024 x 768px + \/ 2004<\/p>\n DPJ Word<\/i> interface mockup, multiple-page document, focus screen set to reveal one line of type in the middle of the page; 1024 x 768px + \/ 2004<\/p>\n \nNow, just because there are very few options at the top of the page, that doesn’t mean the added functionality of Word<\/i> would be eliminated. In fact, there could be more\u00e2\u20ac\u201dor at least more useful\u00e2\u20ac\u201dtools available. These more advanced functions have just been moved into vertical tool “drawers” to the right of the screen to maximize vertical real estate for the page. These drawers could be pulled out independently to view the full list of related capability. DPJ Word<\/i> interface mockup, multiple-page document, focus screen set to reveal one line of type in the middle of the page, “Library” tool drawer pulled out; 1024 x 768px + \/ 2004<\/p>\n \nOne or more tool sets could be clicked open to be viewable at all times, or drawers could be pulled out completely and positioned organically in the work area. DPJ Word<\/i> interface mockup, multiple-page document, focus screen set to reveal one line of type in the middle of the page, “Library” tool drawer detached and placed in work area; 1024 x 768px + \/ 2004<\/p>\n \nIf a user wanted to reference another source of content for their document, they could click on the option from the “Library” tool set and the page and menus would slide off and the background screen would dissolve, so the source could be searched for in the actual desktop environment, instead of by an abstracted dialogue menu (if desired\u00e2\u20ac\u201dthe standard menu placement interface could also be used). DPJ Word<\/i> interface mockup, desktop Library search mode; 1024 x 768px + \/ 2004<\/p>\n \nAs a user went through a larger document, they would be able to tag words, passages or pages with notes to themself, their editor, vice-verse, and so on, so they could call attention to a particular point, further research a topic or at least avoid repeating themselves. DPJ Word<\/i> interface mockup, page 30 of 100, note flags visible with one clicked open Though much of my efforts were trained on removing unnecessary tools, I did make one very notable addition: the magnification slider. At the top of the screen is a track with a positioner that aligns to the right edge of the page. Sliding the positioner right or left\u00e2\u20ac\u201deither manually or by keying in the desired percentage\u00e2\u20ac\u201dwould increase or decrease the magnification of the document, making the interface is equally ideal for writing, editing or reading a one-page report… DPJ Word<\/i> interface mockup, one page document, focus screen set to reveal one line of type in the middle of the page, magnification positioner slid all the way to the right for maximum magnification; 1024 x 768px + \/ 2004<\/p>\n \n… or a 500 page novel. Sliding the left would allow quick jumps between pages or even chapters. Tapping a page would bring that up to the default magnification for writing or editing. DPJ Word<\/i> interface mockup, multi-page document, focus screen set to reveal all lines of type below the middle of the page, magnification positioner slid all the way to the left to view long document in “chapter” sets for quick navigation across hundreds of pages; 1024 x 768px + \/ 2004<\/p>\n \nSide note:<\/i> Microsoft Word<\/i> 2011:mac interface, multi-page document, magnification positioner slid out to “84%” \/ 2011<\/p>\n \n Microsoft Word<\/i> 2011:mac interface, multi-page document, magnification positioner slid in to “10%” \/ 2011<\/p>\n \nHowever, since Microsoft’s slider’s correlation to the page display is so abstracted (it’s a short track in a separate toolbar, not aligned to the page in any way), its use is clumsy and unintuitive. And, without clear labeling or grouping of pages, or the ability to zoom back in on a page in the zoomed out view by just clicking on it, the potential for faster broad-jump navigation is all-but-lost. DPJ Word<\/i> interface mockup, new document, cherry wood desktop \/ metal work area setup; 1024 x 768px + \/ 2004<\/p>\n \nOriginally, I envisioned the most intuitive interface known for writing or editing a paper: actual paper, on a desk. A cherry wood desk would be nice. I imagine that this sort of background could be one in a library of preferences. DPJ Word<\/i> interface mockup, new document, colored interface tool work area setup; 1024 x 768px + \/ 2004<\/p>\n
\n
\n
\n![](\"http:\/\/www.danielpjohnston.com\/graphic-language\/wp-content\/uploads\/2011\/08\/dpj_word_a_lg.jpg\")
<\/a>
\n<\/p>\n
\n
\nIn this prototype, every element has been made to recede from the page. There are is no complex application background. Rather, the page, itself, rests on the user’s desktop, which has been unfocused behind a dark screen. From the top menu, The user can select type style and size and page margins and tabs from the top menu when they start their draft, and that’s pretty much it.
\n
\nOne obnoxious aspect of typing in Word<\/i> (or virtually any other computer program) is its awkward page scrolling in response to adding content: You have to follow your type all the way to the bottom of the page, then the page jumps to reveal the very last line at the bottom of the page from there on out. To further enhance the writer’s focus in this prototype, a translucent screen could be set to the height at which the line being written or read is always positioned and the pages would scroll smoothly behind this line as one types (similar to how one would interact with a typewriter). As one types well into their first page, it scrolls up and over the top font and type size menu (since that is probably no longer needed) and the next page comes up below it.
\n
\n
\n<\/a>
\n<\/p>\n
\nAs multiple pages of content are written, they would be added behind the focus page in virtual space, so the user would always have a general idea of how long their work is.
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n; 1024 x 768px + \/ 2004<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n
\n
\nIt is interesting to see that MS Word<\/i> (and PowerPoint<\/i>) now feature magnification sliders that will allow you to see multiple pages in your document when you zoom out (this feature did not exist in 2004 when I designed my prototype):
\n
\n
\n<\/p>\n
\n<\/p>\n
\n
\nNow, back to my story…<\/i>
\n
\nThe essential idea of a much more simple interface drove my design from the beginning. But there were a few variations on the theme I explored along the way that would make for an experience more familiar in the context of physical reality or further abstracted and function-focused.
\n
\n
\n<\/a>
\n<\/p>\n
\n
\n
\n<\/a>
\n<\/p>\n