Skip to main content

R.I.P. WYSIWYG - Results-Oriented UI Coming (Jakob Nielsen's Alertbox)

Saw this on ProFox (thanks AGAIN , Malcolm)

It's interesting that Neilsen jumps over the new "results-oriented user interface", as noted by Office 12's interface. His big statement: "We know from user testing that users often demand that other user interfaces work like Office"

It will be interesting to see how this plays out - but keep the key poitns in mind from the new Office 12 interface - it's still all about the document-centric vision.

What do I mean by that? The O/S used to be application-centric - that is you choose the application to do the job you need done. Windows (and the web for that matter) has always tried to be more
document-centric - you work in a document and choose the right tools to do the job.

This new results-centric approach says you choose the tools based on the results you want and it's the job of the interface to make it easier to show what the results are - in short, you don't have to deduce or figure out what the tools mean, the interface should make it plainly obvious to you.

MS has been doing this for a few years now -still it's very telling that Jakob Neilsen is noting the big change in Office 12 as the telling signpost for the next generation user interface.

His comment: "But Microsoft Word 2003 has 1,500 commands, and users typically have no clue where to find most of them." Well the question really should be - do you NEED 1500 commands? (ask that to any Fox developer who knows all about dBloat) - maybe the real solution is the 37signals approach of less is more.

Most people who are starting with word processing (and there are a lot of them) don't get the difference between spaces and tabs or tables or columns so having 20 different commands for each of them essentially creates the UI conundrum.

It's a good article to read though - whether or not you agree or disagree with his conclusion that the Office 12 interface is going to be the defacto standard.

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...