Stuart here - i'm the new team member, and this is my first blog.
When is it too early to start user testing ? never would be my answer.
Let your users guide and lead the development rather then presenting them with a product and then 'tweaking' it till it's possible for them to use. Retro development of adding features to an already formed system will always prove more difficult than having the right starting place and initial plan before beginning any code or programming.
That is just one of the reasons why i liked the approach to SkillClouds and their aim for user centered design when i arrived.
From the initial stages of user research, stakeholder interviews and group sessions there had been a great deal of information gathered as to needs of the users, institution, jisc and ideas as to how the project should fulfill these.
Interviews gave us proof of concept information
"After thinking about it for a while I realized that I could only come up with about three skills I acquire at University and that is with the physics department always telling us what skills a physics degree gives us. I am therefore convinced that students from other parts of the campus have the same difficulties if not worse."
"students don't really know what their skills are so telling them without them specifically having to look for this information would give them a big boost in motivation."
And plenty of ideas for what was needed from SkillClouds
"when you click or hover over a skill a short paragraph will appear on the same page outlining the general meaning of the skill."
"I wouldn't always want to open a new window and then having to read through a long essay to get a simple and short description of the skill,"
" .. more in-depth on skills. What else was there? Describing the skill, alternate words .."
"see how they’re transferable and maybe have a link to what kind of jobs they do "
"I mean on that web site you’re linking to your marks and everything as well so you could tie them in, right? […] So in “Essay 1 for Toy Design” you used your communication skills, so you click on that and it’ll give you your mark and an outline of what the report was or whatever. Cos then you could have that going through like all of your years and you could use it as a reference to say “Right, I’ve got communication skills from my 1st year in Toy Design” – and you’re in your 3rd year you’ve got to go back to what sort of skill sets you got."
"It could be useful as well to have feedback from your tutors as well, where you could have improved or things like that, that could"
After a series of user experience data-mining sessions based on analysis, transcripts and recordings of the Pilot Stage and Tag Cloud Navigation Strategies two semi-distinct types of user requirement for SkillClouds emerged :
1. Information
2. Presentation
Having constructed a list of users information goal statements we continued the user centered design process in order to define the information needs of the user, give them structure, order and explore how users saw the types of information SkillClouds might offer them.
9 Students were recruited through Facebook and the SkillClouds mailing list to take part in an open card sorting exercise. The results of even such a small sample group gave us a very strong steer for the development of our information architecture, how users saw the information, what information they want/need and how it should be how/why it should be delivered.
A description, some photos and the initial output of the card sorting is now up on the SkillClouds project website here.
We are currently mapping out a user journey based on the card sorting output which will evolve into our user driven design for SkillClouds.
Wednesday, July 16, 2008
Open card sorting
Posted by stuart lamour at 5:00 PM 0 comments
Labels: card sorting, project activity
Tuesday, July 15, 2008
Seven key skills in information literacy - and SkillClouds project
Back in 1999, SCONUL (the Society for College, National and University Libraries) proposed and have subsequently refined a set of seven key skills (described as pillars) in information literacy.
Here at the JISC Innovation Forum 2008 in the theme on How to Meet the Changing Student Experience there was a discussion today on the "Google Generation" and on information seeking behaviour. Maggie Fieldhouse discussed the report "Information behaviour of the researcher of the future" commissioned by the British Library and JISC and conducted by the Centre for Information Behaviour and the Evaluation of Research (CIBER) at UCL. The SCONUL pillars were discussed, as one of the key findings of the report is that all of us - students, researchers and professors alike - appear to be increasingly adopting shallow search strategies:
CIBER deep log studies show that, from undergraduates to professors, people exhibit a strong tendency towards shallow, horizontal, `flicking’ behaviour in digital libraries. Power browsing and viewing appear to be the norm for all.SCONUL's seven key skills in information literacy:
Information behaviour of the researcher of the future, p.19
- the ability to recognise a need for information
- the ability to recognise different ways in which the information 'gap' may be addressed
- the ability to construct strategies for locating information
- the ability to locate and access information
- the ability to compare and evaluate information obtained from different sources
- the ability to organise, apply and communicate information to others in appropriate ways
- the ability to synthesise and build on existing information, contributing to the creation of new knowledge
The journey starts when someone becomes aware that they need information about their skills, and starts to look at possible ways of addressing that gap. Part of our work in the SkillClouds project is to explore some of the ways to 'mind the gap', and to support students as they explore the different strategies they can adopt.
Image from Flickr by Forzagaribaldi licensed under Creative Commons
Posted by Carol at 9:43 PM 0 comments
Labels: information-seeking-behaviour, jif08