The brief.

In this first (official) IP, we needed to shape our own idea of usability. Our idea needed to be clearly our own while using a related text to inform our discussion. After, we needed to consider what is missing from our ideas around usability through an educational lens. We needed to craft a well-thought out conception of educational usability. In the next phase, we needed to discuss a set of examples of ways in which users had been configured in a set of usability trials. Last, we needed to discuss the differences between two perspectives on the uses of usability.

Define configure (bonus).

  • shape or put together in a particular form or configuration.

    "two of the aircraft will be configured as VIP transports"

    Oxford Languages (Google)

  • arrange or order (a computer system or an element of it) so as to fit it for a designated task.

    "expanded memory can be configured as a virtual drive"

    Oxford Languages (Google), emphasis added

Define usability (for putative users).

The most usable tools, devices, and interfaces (referred to here as tools) are those whose affordances are clearly and efficiently effected. Users are those that interact with a given tool or interface. Thinking about how usability, interaction, and interactivity connect in Issa and Isaias (2015), usability might be considered as what makes up the factors that facilitate the quality of communication between the “domain and the task” and the activity between the domain, task, and users (p. 30). Tools become usable once they are made learnable with sufficient supports, easy to use, and afford users with whatever meets their needs.

Define educational usability (for putative learners).

Learners are not the only users using educational tools. For scope, we will narrow our perspective down to users as learners whose goals are ultimately those we focus on most closely in educational technology (aside from teachers/facilitators). Learners might share some common goals like developing the concepts and skills in a specific topic while also working toward relating specific topics to broader areas of study (Squires and Preece, 1996). We’ll refer to these as our epistemic goals. In interacting with technology in pursuit of those goals, learners are also interacting with the interfaces of educational software, the operating systems, hardware, and associated peripherals (Squires and Preece, 1996). We might say our technological goals are to use these tools in pursuit of our epistemic goals. The topic-based epistemic goals also become embedded in the task-based objectives of the technology (or the other way around).

Educational usability is therefore about learners’ epistemic goals, the role of technology in achieving them, and the context around how the epistemic and technology related goals are intertwined. If our goals as learners are not to learn the technology for technology’s sake, but rather to achieve our epistemic goals, then educational usability must emphasize reducing the learning curve associated with the tool, its continued ease of use, and its pedagogic affordances for learners by the lights of the intertwined nature of the technology and the learning. What usability in this context needs to safeguard is making sure the tools do not compromise epistemic goals but support them (Van Nuland et al., 2017). Then, the relationship between learning and learning technology relates to how the tool selected not only supports or undermines the epistemic goal, but how it configures the learner to learn.

Woolgar’s user configuration.

Example 1: The manuals

The manual as a literal text defines the role of users and sets of the goalposts for their approach to undertaking tasks. In Woolgar’s (1990) description of the usability trial, he describes the machine as not yet “settled” meaning that its affordances had not yet been completely delineated (p. 82). Likewise, the identity of users isn’t settled and so the relationship and nature of the interaction is still being negotiated between user and machine. One wonders about setting up the nature of this relationship with a manual before undertaking the test. Surely the test would begin by exploring the relationship without pre-configuring it as it were and tainting the test by priming the user to take actions in ways they might not ordinarily.

Example 2: The feedback.

By providing information in the form of feedback during the test, the facilitators again prime the users to form certain kinds of relationships with the machines they are using. By qualifying the actions of the users, the facilitators configured them (fit them) into what they wanted to see, not necessarily what they would naturally do. The users’ identity cannot be developed on its in relation to the machine and the machine cannot be appropriately tested in relation to real usability.

The differences between.

"…the usability evaluation stage is an effective method by which a software development team can establish the positive and negative aspects of its prototype releases, and make the required changes before the system is delivered to the target users" (Issa & Isaias, 2015, p. 29).

“…the design and production of a new entity…amounts to a process of configuring its user, where 'configuring' includes defining the identity of putative users, and setting constraints upon their likely future actions” (Woolgar, 1990, p. 59).

Issa and Isaias (2015) take the conventional view of usability testing in taking the tests at face value. There is no mention of users’ identities, the complexities of setting up and running effective tests, or how to measure usability in relation to the validity of what is being measured. Woolgar (1990) takes a closer view of usability testing as always having a configuring effect on users. Users are never ‘blank’, they are actively changing their behaviour due to the nature of testing and the nature of their relationship with technological tools. In this sense, it might be doubtful that usability testing ever actually tests the way makers of these tools would wish. But then, users in the real world aren’t blank either. But are they configured in the same or similar ways as those tested users?

References.

Issa, T., & Isaias, P. (2015). Usability and human computer interaction (HCI). In T. Issa & P. Isaias (Eds.) Sustainable design: HCI, usability, and environmental concerns (2nd ed., pp. 19-35). Springer.

Squires, D. & Preece, J. (1996). Usability and learning: Evaluating the potential of educational software. Computers and Education, 27(1), 15-22. https://doi.org/10.1016/0360-1315(96)00010-3

Van Nuland S. E., Eagleson, R. & Rogers, K. A. (2017). Educational software usability: Artifact or design? Educational software usability. Anatomical Sciences Education, 10(2), 190-199. https://doi.org/10.1002/ase.1636

Woolgar, S. (1990). Configuring the user: The case of usability trials. The Sociological Review38(1, Suppl.), 58-99.

Previous
Previous

Truth & Reconciliation

Next
Next

ETEC511 IP-2