Making and Breaking Domain of One’s Own: Rethinking the Web in Higher Ed
On Friday, 12 August 2016, Martha Burtis gave one of two closing keynotes at the Digital Pedagogy Lab Institute held at the University of Mary Washington. Below is the text of her talk; the audio above is edited from the video recording of that morning’s keynotes.
I thought I’d start today by telling you a little bit about myself. While some of your faces are familiar, I don’t know most of you, and I doubt you know much about me.
I trust you know my name, and you now know from my introduction that I run the Digital Knowledge Center at the University of Mary Washington, which provides peer tutoring and consulting to our students working on digital projects and assignments. Here are a few other things I’d like to tell you about myself.
I attended this school (although at the time it was known as Mary Washington College), and I graduated from here 20 years ago this past May. I received a B.A. in English, and when I graduated I was dead set on going to graduate school, studying early modern British literature, getting a PhD, and, hopefully, eventually, teaching at a school just like this.
Instead, a couple of other things happened. The year I graduated from MWC was pretty close to the year the Web “broke big.” I discovered the Web between my junior and senior years in college (in a summer medieval literature course, of all places), and my primary use of it that following year was as a research tool for policy debate (I was on the debate team). By the time I graduated, I had been thoroughly charmed.
What I actually ended up doing in the year after I graduated was going to work at one of the finest places in the world: the Folger Shakespeare Library as a program assistant for the Folger Institute which organizes and runs seminars, workshops, and summer institutes for faculty and postdocs in early modern studies.
I spent a lot of time around mid- to late-career scholars who were fully and meaningfully employed in teaching and research positions and a lot of time around struggling graduate students who were working construction to make ends meet. And I was lucky enough in my job to be able to start doing stuff with the Web. The confluence of those two things — falling in love with the Web while falling out of love with the idea of never getting the job I wanted — took me down a different path. I ended up getting a masters degree in instructional technology from Teachers College at Columbia University.
I moved back to Virginia, and a few months after completing my thesis project and getting my degree I got a job — right back here at Mary Washington.
I was hired as an instructional technology liaison, and I worked up the hill a bit from this building supporting faculty in fine and performing arts. It was 2001, and I loved the faculty and the students, but I hated my job. At that time, I was basically providing technical support for faculty and their departments: fixing printers, setting up lab computers, and, occasionally, teaching someone something about Word or Powerpoint or Excel.
We had one tool in our instructional technology tool shed at that time: Blackboard. And faculty primarily seemed to use it to distribute digital files, email students, and post grades.
So that was my first full-time professional job in instructional technology. I wasn’t using anything that had to do with my degree. My boss at the time suggested that for professional development I consider becoming an Apple Certified Technician (this was pre-Genius days).
I did work with great people in my department, and, like I said, I loved the faculty and students and I loved, and still do love, this place.
I would like to say that lots of faculty were coming to me for help thinking through how they could use the Web to transform their classes, their teaching, and their students’ experiences — and that I was regularly inundated with bold, imaginative ideas and that I was capable and empowered enough to partner with them on these adventures. But I felt neither capable nor empowered, and the truth is, neither were they.
When I was working at the Folger and in graduate school in the late 90s the Web seemed like a place of infinite possibility, a great democratizing force, and a space in which anyone could build themselves something remarkable. Now, I was younger then, and I was, of course, naive. And the history of the Web is more complex than that, and technology nostalgia is like any other nostalgia — colored and softened by the long lens of the future.
But I do remember, for example, a tool that I played with in graduate school (this would have been spring of 2000) that allowed multiple people to leave public annotations on a Web site. And when I used it, I felt like I was connecting with people in a way that had never been done before. It felt like magic. And it didn’t work that well. The truth is bandwidth and code hadn’t caught up with our imaginations. But the Web was this powerful force that was washing over us, and we were all — in every field, in every industry, in personal and professional domains — trying to stay afloat and figure out what it meant.
It seems only reasonable to assume. No, not reasonable. It seems impossible to not assume that in the domain of education, a domain that is entirely about the creating, the building, the sharing of knowledge and learning that this new force of creation and knowledge sharing would be fully and authentically realized.
How on earth could it not be?
How could we all not see the power that this new medium was affording us and not be drawn to it, in every way?
Most importantly, how could we not, in fact, see it as our job to shape this new medium and to help the rest of the world understand what it could do? As a platform for transformational teaching? As a space for public research and dissemination of knowledge? As a place for collaboration on scales never seen before?
And yet. Blackboard.
What happened?
I have a few theories.
I think the Web hit us at a critical moment in higher education where we were already struggling with doing our work less like schools and more like businesses, and the tech industry and its vendors had already begun to infiltrate us with promises of how technology could help us achieve this goal. We had already bought into student information systems (which eventually became everything information systems), and with the promise of those systems came the promise of lots of data which would allow us to become more efficient and streamlined.
The first LMSs were actually built at schools, often under the guidance of faculty. I like to imagine that those people were as charmed as I was about the affordances of the Web for teaching and learning. I want to believe their intentions were very good, but what they focused their efforts on was building systems for disseminating content. Systems with common interfaces. Systems with standard tools. Systems that could integrate with other systems to make our work more efficient, our experiences cleaner, and our teaching and learning, as a result, more sterile.
What if the early Web adopters in higher education had imagined Domain of One’s Own instead of Course in a Box? Why didn’t they?
In part this question is about why our systems use courses as a unit of measure instead of people. And the answer to that is really complex and stretches far back into the history of education, which is beyond the scope of my 25 minute co-keynote. But, suffice it to say, courses have long been the way we have measured our institutions and the way we have organized our administrative processes. We understand ourselves and what we offer to students through the unit of the course. But I would argue that with the greater adoption of administrative systems in higher education we doubled-down on that unit of measure. And with the LMS we did something even bigger.
Because even if we had decided for centuries that in our schools the course would be how we’d standardize administration of our schools, we didn’t, systematically, believe that courses themselves were standardized. We valued the notion that within one professor’s course she had the freedom to enact and explore the topic at hand using the pedagogies of her own choosing. And, by extension, presumably the tools and technologies of her own choosing.
But when the LMS goes beyond merely providing administrative and management features and instead is offering features designed (perhaps badly) to build community, share information, and collaborate with others, it is obviously influencing pedagogy.
I don’t think we acknowledge this nearly enough when we talk about the technologies we use in education. We like to think that a tool is easily defined by its basic functionality: discussion board, wiki page, synchronous chat, quiz builder. But all of these tools are of course far more complex than that. They’ve been designed and coded and engineered by companies to provide functionality in particular ways. And that design and code guides our students’ and our experiences through their use.
Imagine, if you will, if someone told you that from now on when you conduct a discussion in your classroom you are bound by a series of rules, procedures, and steps. You must follow those at all times, and, everyone else at your institution must also. From now on, every classroom discussion at your school must be conducted using these sames rules, procedures, and steps. If you don’t like them? You’ll have to wait and see if the next update to them addresses your concerns. You would probably balk at this suggestion — and you should. But rules, procedures, and steps are exactly what code defines, and when we fail to acknowledge this we fail to see the pedagogical power that technology and the LMS can have in our classroom.
So the LMS underscores and further codifies a set of beliefs and values: courses should be used as a unit of measure to more