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

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

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...