Thanks for sticking around for issue #2. I received some gentle feedback about last week’s: it was too long. I guess I was just too excited to share with you all! Breaking my long emails into multiple small ones will help me maintain a steadier pace, so I’ll give that a go.
This week, I’d like to talk about disciplines.
What’s a discipline? A discipline is a way to categorize activities and knowledge. It’s a label that helps us identify what a person does. “Librarian”, “historian”, and “teacher” are all disciplinary labels.
We tend to think that these labels are specific, but they’re not: a librarian might be a front-line representative, helping patrons find books or other items; they might also help researchers manage their research data; they could also work with community groups to provide the physical and other resources necessary for their success. These are vastly different activities, only some of which we regularly associate with the disciplinary label “librarian”. No doubt you can look at your own discipline and see just how varied it is.
Now, it makes a lot of sense that we use labels. They’re convenient. They provide a quick reference to a broad range of activities. We love to categorize, and for good reason—it helps us to speak in a common language and hopefully to have more productive conversations as a result. But it’s when we get trapped within these labels that their utility begins to ebb.
One of the problems that comes up in disciplining is that we forget (or never realize) just how transferable skills and knowledge really are. I was talking with some folks at last week’s Ottawa Civic Tech meetup. One of them, a university professor, mentioned that many students in their research methods course questioned why they had to take it: they were in a coursework-based master’s, so why did they have to study research methods?
We then discussed how the skills taught in social science research methods courses are extremely in demand nowadays. Looking through my political science methodology textbook, I realized that I’ve already learnt many of the tools and approaches covered in it via Erika Hall’s Just Enough Research. (Once I realized this, I questioned whether I should bother reading the textbook any further, but that’s another point.) Hall’s book is for designers—a specific discipline—but the methods she teaches are the exact same as those taught by social science methods courses. Learn them once, apply them anywhere, under any disciplinary label.
Really, most skills are like this. They’re highly transferable, but we tend not to realize it because we couch them in discipline-specific terms. (Jargon, ugh.) Disciplinary categories are handy, but they’re limiting. How can we fight against that?
I’m not altogether sure. It’s something I’m always working toward, but along the way I just find new challenges, new questions. I never quite know how to describe what I do: am I a designer, a developer, or something in between? Does it matter? Do I need a label? And how do these questions extend to academia? I straddle faculties here at uOttawa: Arts for history and Social Sciences for political science. Neither quite describes what I want to do, but they’re the distinctions I’ve had to shoehorn myself into. Ultimately these distinctions are arbitrary human constructions, but they carry the weight of objectivity and certainty with them. Chipping away at such perceptions, bit by bit, is perhaps the most we can hope for. That, and ignoring them as we get on with doing the work that matters, whatever its labels.
Sent from Ottawa, Ontario on September 17th, 2017.