This is the Message Centre for Menthol Penguin - Currently revising/editing my book

Papercuts

Post 1

Not the monkey - Skreeeeeeeeeeeee

Yes...looks useful.

*But*...what I'd like to see is some sort of usability process standard for Linux end user packages based on ISO 13407 (User-Centred Design). Getting it right from the outset is better than fixing it afterwards.


Papercuts

Post 2

Menthol Penguin - Currently revising/editing my book

I've not seen the ISO 13407 thing before, looks interesting and useful. Hopefully it'll get used, although I wonder how many users and developers will take the time to get involved with it.

I find this usability stuff interesting as I found Linux easy to use right from the start. Some stuff was different but I either knew what it meant/found out/pushed the button anyway. I can't see that many places where people find it difficult to use, I'm not sure whether thats because I know a bit about computers or well i dunno I'm not sure really.

It would be interesting to know if some of the stuff isn't user friendly because it was originally used by/designed by geeks and they didn't realise exactly how much needed changing or whether it was because of the nature of Linux, that the developers believe in choice and having as many options as possible, that caused it.

What I also find interesting is that people say that h2g2 is difficult to use, and I have a couple of gripes, but on the most part I find it easy to use. Unlike my windows live email account where I still can't find how to change the damn password!

I'm going to have to find out why some people find Linux difficult to use. To google!


Papercuts

Post 3

Not the monkey - Skreeeeeeeeeeeee

Well 13407 *should* be ised. a) It's been around for years, b) it's (practically) part of EU law.

The big problem with Usability can be summariesed thus: 'Developers Aren't Users'. The tasks developers design their software to do aren't necessarily the Real Life things people will want to do. Problem is...how do users kmow in advance? Hence 13407's emphasis on iterative prototyping.

One *very* interesting thing I've noticed recently on the 'buntu wikis ois talk of 'Use Cases' - scenarios describing the expected interaction. This allows the prototyping to begin before any code is even cut.

Happy to keep talking Usability - it's my job. I tend to get involved more in big, engineering-y thing such as ships - but I started out in software, and it's still where my heart is (and I get to do a User Interface once in a while).

For more 13407 stuff - check out my Guide Entry on Ergonomics.


Papercuts

Post 4

Not the monkey - Skreeeeeeeeeeeee

A3213127


Papercuts

Post 5

IctoanAWEWawi

"Use Cases"

Arrggghhh!
Sorry, I'm sure when properly used they are very useful.
But I've seen too many IT projects where these have been used insteead of a specification.
They're great for process flow and so forth but they don't help at all with system design.

But as said, interface design and usability is very important.
There is a real disconnect between the technical implementation of a system and the daily use of a system. One thing I have found (as a designer/developer/analyst/whatnot) is that actually taking the time to educate the user about the technicalities behind the system helps a heck of a lot.

Too often the focus is all about getting the techie to understand the user process. And this has its place. But when the user doesn't understand the first thing about the design of the system it is not surprising that they have problems with using it.

They will develop their own mental model (even if not consciously) of the data shape and design 'behind the scene' and then will try and use the system according to this design. Many misunderstandings and issues I have come across have had an element of this. 'Oh but I thought this would change that' when there is no such link, and so forth.

Also educating them as to what can and can;t be done helps as well.


Papercuts

Post 6

Menthol Penguin - Currently revising/editing my book

Most of the complaints with linux appear to be with package management rather than anything else. And the mintInstall program is the best I've seen for installing packages.

However what I do think is needed is for people to have better knowledge of computers in general for making computer easier to use. On Linux a pop-up window that explains all of the differences between windows and linux when you use it would also help. I think that would go a long way to helping solve problems that people come across. Not areas where its difficult to use but where its different.

<>

I wonder if some people find Linux difficult to use cos they still have the windows mindset and expect everything to be in the same place/work the same.


Papercuts

Post 7

Not the monkey - Skreeeeeeeeeeeee

>>Too often the focus is all about getting the techie to understand the user process. And this has its place. But when the user doesn't understand the first thing about the design of the system it is not surprising that they have problems with using it.

smiley - ok Hence...it's an iterative process. Use case. Prototype. Test...and so on. And it doesn't end with release, hence Papercuts.

As for 'the user doesn't understand the first thing about the design of the system'...well...that's where Design comes in: making the workings explicit. Or failing that...User-Centred Help to explain the system in user terms.


Papercuts

Post 8

Menthol Penguin - Currently revising/editing my book

I just wonder how much of this difficult to use stuff is left over from when it was geeks only that could uselinux.

I kinda think Linux development and use will go in two stages.

The Geek stage
the whole thing was built and made to work, but only geeks could really use it.

and

the User Stage
Were the usability problems got fixed and everyone could use it and the base system was kept.

I think were somewhere in the middle of those two, so there's the base system and then we need the final bits being done to polish it off. So there are things like the Papercuts scheme and people are realising that some places need work to get them to be usable.

I think a lot of the applications work on their own but when you put them together they need a bit of work to work with each other well.

And with more people using it hopefully it'll get easier to sue. Mind you I find windows difficult to sue now. No middle click paste is slowly killing me! And I miss Compiz-Fusion!smiley - sadface

I do like the phrase that they have where they say that when their grandmother can use anyone will be able to use it. smiley - smiley

smiley - offtopic
And Linux isn't working too well atm cos the ATI drivers where giving me grief but they're working ok as longs as I don't do some thing eg log in manually, automatic login is fine. But thats an ATI problem I think not a Linux one.
smiley - offtopic


Papercuts

Post 9

Not the monkey - Skreeeeeeeeeeeee

Another thing to think about with Linux is its tweakability. An Apple is untweakable. The user has a set of icons and uses them.

Hell...my washing machine would become unuseable if I were allowed to tweak it.


Papercuts

Post 10

Menthol Penguin - Currently revising/editing my book



Just sticking that there so that I remember to reply! Damn revision, stopping me from talking to interesting people!


Papercuts

Post 11

Menthol Penguin - Currently revising/editing my book

Most of the tweaks and stuff I know off/about require either to download a program or to edit a text file. Not something your average user will be able to/want to do. however the basic usability sort of tweaks are normally available in the programs options.

I also think that some of the tweaks in Linux while they may not be easy to do do make life a lot easier than in windows or mac. I find it very useful to be able to have two taskbars on Linux and on windows i miss that. However t set up my mouse to work properly in Linux I'll have to edit a file, but I don't mind poking around in various bits of the filesystem.smiley - smiley


Key: Complain about this post