{"id":316,"date":"2010-02-23T16:56:35","date_gmt":"2010-02-23T03:56:35","guid":{"rendered":"http:\/\/www.thunderguy.com\/semicolon\/?p=316"},"modified":"2010-02-23T16:56:35","modified_gmt":"2010-02-23T03:56:35","slug":"microsoft-inductive-user-interface-guidelines","status":"publish","type":"post","link":"https:\/\/thunderguy.com\/semicolon\/2010\/02\/23\/microsoft-inductive-user-interface-guidelines\/","title":{"rendered":"Microsoft Inductive User Interface Guidelines"},"content":{"rendered":"<p>When designing Microsoft Money 2000, Microsoft followed a &#8220;new user interface model&#8221;, which they called <em>inductive user interface<\/em> (IUI). The <a href=\" http:\/\/msdn.microsoft.com\/en-us\/library\/ms997506.aspx\">Microsoft Inductive User Interface Guidelines<\/a> are available on <a href=\" http:\/\/msdn.microsoft.com\/\"><abbr title=\"Microsoft Developer Network\">MSDN<\/abbr><\/a>. I came across them a few months ago and thought they give a nice description of how to make simple, focussed applications  screens, whether for a desktop or web application. I&#8217;ve summarised the main points here.<\/p>\n<p><strong>Ensure each page has a clear title.<\/strong> Almost everything else follows from that simple rule.<\/p>\n<p><strong>Focus each page on a single task.<\/strong> A screen is focused on one purpose if the designer can express that purpose with a concise, meaningful, and natural-sounding screen title.<\/p>\n<p><strong>Title each screen with a concise and explicit statement of its primary task.<\/strong> This can be a direct instruction (&#8220;Select the account you want to balance&#8221;) or a question you want the user to answer (&#8220;Which account do you want to balance?&#8221;). To write a page title, designers imagine a friend asking, &#8220;What is this screen for?&#8221; and then come up with a clear, helpful response that completes the sentence &#8220;This is the screen where you&#8230;&#8221; The words that complete the sentence become the screen title.<\/p>\n<p><strong>Optionally include a brief descriptive paragraph at the top of the screen.<\/strong> Even when a title is carefully chosen, the title region may be too small to adequately explain a complex task. To alleviate this problem, you can include a brief descriptive paragraph at the top of the screen&#8217;s content area that elaborates on the task.<\/p>\n<p>If the screen title is clear and simple, designing the screen is usually straightforward.<\/p>\n<p><strong>Provide a clear exit from the page.<\/strong><\/p>\n<p>I remember back when I first saw Microsoft Money 2000, I was struck by how much it looked like a web site &#8212; screens looked like web pages, and UI controls looked like web controls. They had simplified the interface so it felt like a website. At the time I thought this was the way of the future: desktop apps would start to look like web apps. Actually I wasn&#8217;t exactly right: what&#8217;s happened is that desktop apps have been <em>replaced<\/em> by web apps. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>When designing Microsoft Money 2000, Microsoft followed a &#8220;new user interface model&#8221;, which they called inductive user interface (IUI). The Microsoft Inductive User Interface Guidelines are available on MSDN. I came across them a few months ago and thought they give a nice description of how to make simple, focussed applications screens, whether for a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[84],"class_list":["post-316","post","type-post","status-publish","format-standard","hentry","category-general","tag-usability"],"_links":{"self":[{"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/posts\/316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/comments?post=316"}],"version-history":[{"count":1,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/posts\/316\/revisions"}],"predecessor-version":[{"id":317,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/posts\/316\/revisions\/317"}],"wp:attachment":[{"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/media?parent=316"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/categories?post=316"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thunderguy.com\/semicolon\/wp-json\/wp\/v2\/tags?post=316"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}