Final reflections [crosspost]

[This post was originally made on a university-locked platform]

Expectation and First Impressions

keyhole
Peeping in. Source

When I first started this course, I was looking forward to learning more about areas of digital technology that I had heard about but had little experience of. Generally I’d say I’m aware of new technologies and changes in the digital sphere, but tend not to use or investigate them in detail if they don’t seem immediately useful to me in my day-to-day life.

I was apprehensive about the play and blogging activities. I had never been expected to learn in this way before in a university context. I was much more accustomed to the standard readings-lecture-tutorial-assignment structure, and was admittedly a bit skeptical that I would get the same learning outcomes from this difference style. But I came to appreciate that this participatory style was better suited to this topic.

The Learning Experience

As I completed more of the fortnightly activities, I was forced to participate in much of the digital technology that I had previously only passively observed or consumed. This really became clear during the Wikipedia editing activity – while I knew how Wikipedia was written and edited, it was not until I actually had to do some myself that I started to appreciate the scale of effort and dedication that goes into creating the site. I also realised that participating in these technologies was better suited for learning, since so many of the topics were user-driven – whether via users creating data, creating content, shaping online environments or through the democratisation of technology and online activity – being an active user was by far the best way to experience these technologies.

The most frustrating part of the learning activities was easily having to use the Blackboard blogging platform. The post editor seems to clunky and old-fashioned compared to others I’ve used, and it was unnecessarily difficult to get a well-formatted and user-friendly post together. Similarly, the lack of interconnectivity between each person’s blog was frustrating. I was interested to read what my peers were posting each week but it was tedious having to click into each individual’s blog to get an idea of what was being discussed. The ability to tag posts with topics, see all posts, tag other users in comments or search all blogs would have been much more useful and conducive to discussion.

Highlights and Omissions

The biggest highlight of this course for me was easily my visit to Brisbane Hackerspace. This was a fascinating place with a community that seemed engaged and welcoming. Something about the place also seemed to be in the same ‘spirit’ as libraries – I’m still thinking about how makerspaces and libraries could work together and hope to see (or maybe even make) developments in this area in the coming years.

maker icons
Makerspaces <-> Libraries? Source

I also enjoyed Dian’s lecture on the Internet of Things, and wish we could have had more time to consider this topic in depth, as it seems a genuinely different beast to the websites and apps that we’re accustomed to, deserving of more investigation.

hiq at qut
HiQ at QUT. Source.

In terms of downsides, I would have preferred to spend more time learning about how some new technologies are being applied in contemporary libraries and information professions. This could take the form of case studies, field trips or asking us to find examples of the application of new technologies. The recent launch of HiQ at QUT seems like an obvious candidate: How was it developed? Which technologies were or weren’t incorporated and why? How does something like HiQ fit in to overall trends in libraries and information spaces? As a project, it would have a lot of potential for learning about technologies in information practice, so it would have been great to have included it in this course.

Overall insights

The biggest message I took from this course is to keep an open mind about how new technologies can shape and improve information practice – but be mindful that every new technology will present new challenges. These days it’s cliche to talk about how ‘change is the new normal’ – but it’s genuinely true, particularly in information professions. Technology will not only be a constant source of disruption but also of opportunities to grow and expand what our profession is. If we can learn to take a balanced approach to new developments, not seeing them as either dangerous threats or magic bullets, we can change and guide our professions in the best possible ways.

Developing a UX Persona: Some Theory and Practice [crosspost]

[This post was originally made on a university-locked platform]

Personas are used in the sector of technology design known as user experience or UX. They are essentially archetypes of the technology’s users: a constructed persona that represents a particular type of user who has been given a full back-story and can be considered as if they were a ‘real’ user. Using personas assists the design process, as they are more concrete than the data they represent, and are thus easier to design for: it’s more straightforward to think about persona ‘Anna’ with a known set of behaviours and traits, than to think about ‘the segment of our user base that is female and under 25′.

Generally a persona would be constructed from the results of research, and with a particular technology or goal in mind. For example, a software company seeking to overhaul the user interface of a product would develop personas to anticipate how the redesign would be received and adopted by users. The exact behaviours researched will depend on the technology being developed, but common questions might include:

  • Demographic information
  • What technologies, devices and apps they currently use
  • Frequency of use and patterns of use at differing times or circumstances
  • Level of proficiency with technology
  • Goals, desires and frustrations when using technologies

Once user data has been collected, it would be parsed to find specific user ‘types’. These types are then re-imagined as a specific user with characteristics that represent those of similar users. A name, photo and history will be given to the user – and thus they become a persona.

A persona can only be as useful as the data upon which it is based. Personas are valuable because they are archetypes – based on real life users, rather than stereotypes – based on a developer’s assumptions or misconceptions. On the other hand, when the research is used well and truly representative personas are created, they can give new and deeper insights into how real users interact with technology.

My own use of technologies

Before I undertook this task, I considered my use of digital technology to be mostly concerned with organising my life: I thought mainly about Google calendar, Todoist (which I use to manage personal, academic and work tasks) and Gmail. I also thought of the ‘Quantified Self’ sites I use to keep track of books, films, exercise and budgets.

However, on reflection I found that while these apps were vital to my staying organised and making sure my days ran smoothly, they were not as heavily used as apps used for direct communication, work or leisure.

Direct communication was a clear leader over social media for me. I still make lengthy voice calls to catch up with friends and family on a regular basis. Facebook messenger has largely replaced SMS for text communication, but my use of Facebook itself is more focused on keeping up with my wider circle of friends and with current events generally, than on posting for social reasons, as I find that information that has been posted by those I am closest to doesn’t show up in my feed. Finally, email was used across all devices. In my work the vast majority of communication is done by email, both internally and with external stakeholders, and university communications also contribute heavily to my use of email.

Also prominent were my use of note-taking and file management apps: Google Drive, Google Docs and Evernote. My reliance on these apps clarified and reflected my overall need for data to be accessible on all devices and be fully based in the cloud. Particularly at work, the ability for all members of our team to access and edit a document ‘in situ’ – without needing office software on each individual device – allows us to work flexibly from home or the office, and means formatting of documents does not differ depending on the software used to view it. Similarly, my university materials and personal notes in Evernote can be accessed from any device and through any browser without needing to install file editing software.

Apps that I use for leisure and entertainment were also more heavily used than I had initially assumed. I expect this is because most of this usage takes place while I multitask, such as watching YouTube as I commute or listening to podcasts while I do chores. Also, the entertainment I consume is usually in longer form: most podcasts I listen to are at least 45 minutes long, and some are up to 2 hours. This means the podcast app is used for a long duration, but often without looking at, or engaging with, the device.

Overall I found that the apps I value most and rely on daily, while vital, do not take up a lot of my usage time. Nor should they, I like these organisational tools because they are fast, simple and work across all devices. The apps that do use more time are for work and study (Google Drive and Google Docs) and for leisure or relaxation (podcasts and YouTube). It makes sense that the utility apps that organise my life, use less time that the apps which I use to actually carry out my life.

While the process of developing a persona has been interesting, I am most looking forward to seeing others’ posters. I have tried to present traits and behaviours that I consider representative of a ‘type’ I might represent, but without comparative data it is difficult to know what is distinctive and what is common to others.

Sources:
Bernstein, Gregg (2015) How To Create UX Personas. Retrieved 16 April 2016, from http://uxmastery.com/create-ux-personas/
I
lama, Eeva (2015) Creating Personas. Retrieved 16 April 2016, from http://www.uxbooth.com/articles/creating-personas/
US Department of Health & Human Services (n.d.) Personas. Retrieved 16 April 2016, from 
https://www.usability.gov/how-to-and-tools/methods/personas.html