Skip to main content

Microsoft Office 12.0 : Say Goodbye to the standard user interface

Wow - for years, the familiar File, Edit, View menu approach has become synonymous with the "Windows" and "Office" experience (even though it was pioneered by Apple, PARC, etc) and now in one swoop, MS has decided to do away with it (at least once version 12 comes out)

The slide show is linked about half-way down. Update: Direct Link

While I'm a big fan of "task-groups", I'm not sure how this user interface will fly. Why?

1. While every application is different, having a standard interface does make it easier to learn and train new users on. Menus are "complexity browsers" and while Office continues to try and make it easier to use, having spent the last 10 years convincing people that menus are good - to come around and say they are no longer there, may not be quite the best default option.

2. By grouping items into categories, it certainly helps improve the interface but if you look at the last slide (the "less-intimidating" Access), you'll see that there's a real danger when you continue to have lots of options available.

3. I do like the idea of when you click on Write in Word, it shows "galleries" of areas where you can make changes like fonts in one section, paragraphs in another. It almost reminds me of the "toolbars" that appear in "other" operating systems and applications.

Now, I'm sure MS has done their user research on this so I'm excited to see what it will look like in the end but don't forget - MS User research also suggested that people would like "MS Bob" and Clippy. And some people do.

What does this mean for the FoxPro developer? It will be interesting to see - because while FoxPro has kept up to speed on the "Windows XP" compatibility (Theme support, etc), it has always lagged behind with the Office user interface compatibility. With the new Office 12, the UI will most certainly be affected.

I'm looking forward to what Ken has said regarding Sedna's compatibility with Office 12- it's likely more to do with the new XML file formats.

But I think developers will face another round of "why doesn't my application look like...." - sounds like a job for Arg Software Design!!

Comments

Andrew MacNeill said…
Direct link:

http://reviews.cnet.com/4520-9696_7-6322533-2.html?tag=ss
Andrew MacNeill said…
Watching the "Julie" video and it does look

It was really interesting listening to how they did their usability tests.

There WAS a reason for that Office usability option in the program after all!

The real test - will more people be able to figure out Pivot tables in Excel?

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 .

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...

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