[TYPO3-hci] Usability testing in lab?

Matthew Manderson matthew at manderson.co.uk
Mon Sep 11 17:45:39 CEST 2006


Kasper,

Thanks for your considered reply.

I just found that section I had lost, it was on the no brainers page.

...
Usability involves identifying WHAT is usable and considering if there are
problems to be fixed. This page seems to miss out the valuable research
stage. 

Ideas: 1) Identify through a logging extension? top paths through TYPO3 BE
of the installations already out in the wild. This is likely to highlight
unused areas of TYPO3 BE and overused areas of TYPO3 BE. 2) Critically
follow paths and consider if they make sense. 3) Add a feedback extension
to TYPO3 BE allowing people to contexturally submit 'in the wild' reports
back to TYPO3 for logging and analysis. Anyone already have this experience
with corporate software etc? (matthew)
...

Just picking up on the no brainers section. I see that it is picking up some
good ideas, to be tested of course, but we need to understand the basis for
prioritising. On what basis should one idea be chosen over another?

>  From all the information we have on the wiki, would you like to help
> working on the roadmap which should basically spell out what the
> priorities for version 4.1, 4.2, 4.3 etc of TYPO3 will be?

On timing, for the next 5 weeks I am under a lot of pressure to complete
current projects. I am moving from full time freelance to just part-time
while I take on a part-time role in a company. In this time however I
expect to finish a new TYPO3 v4 document which is coming along very well.

So after this time I expect to be able to help contribute more on HCI.

I read this list so yes I'll be available with the road map to help as help
is asked for.

An idea to help avoid the discussions that arose over the TYPO3 logo process
will be to make sure that the TYPO3 community generally is asked to help
prioritise the road map as it is drafted.

Any changes to TYPO3 is always met with a mixed response given the
attachment many users have with it!

The TYPO3 Ready! idea if approved could be incorporated into those
discussions although as an idea I think it merits it's own topic.

Best regards,
Matthew





More information about the TYPO3-team-hci mailing list