Club Admiralty

v7.2 - moving along, a point increase at a time

Multilitteratus Incognitus

Pondering what to learn next 🤔

The Adjunct’s dilemma – how much do you tell your students?

Among the many streams of things happening these days is keeping tabs on some interesting things happening in my various internet circles.  I've resolved to just dip into my RSS stream and look at things periodically over a couple of days and not be as 'vigilant' as I have been in the past.  Too many things to focus on, not enough time for news.  That said, I came across an interesting post by Rebecca how  How much should you tell your students about the constraints/environment you are operating under when you are teaching? What do you think? Rebecca is teaching a course that I had taught before at UMass, and is teaching the introductory course in instructional design I taught last semester.

This is a really good question.  I've only taught credit-courses at UMass Boston (unless you count my internship last semester in Athabasca's  MEd program) and my own experience I've seen (and heard of) institutions that design everything for the instructor, and there is no leeway, and I've seen institutions that give a lot of leeway to their instructors.  Both extremes are problematic for me because they don't take into account the realities of hiring people to teach your courses.  You are, presumably, hiring experts to teach your courses because they are experts. So, the one extreme of giving them no leeway is problematic because it negates that expertise.  On the other hand, a lot of leeway, which at the extreme is actualized as "Here is the description and the learning objectives, you've got 13 weeks, do whatever you want...ah and class starts tomorrow! See ya!", is also problematic because it doesn't give that expert enough time (or guidance) to design an implement a good course.

That said, I think that it is important, for students in all levels, to know under what constraints the instructors are operating.  How much detail you provide really depends on what you are teaching, and who the learners are.  If, for example, you are teaching a group of History 101 students (college freshmen), I'd expect that you are not going to provide them with a lot of detail about the constraints. The reason for this is that a History 101 course has a diverse group of students, both majors and non-majors, people who are really interested in the topic, and people who need to get it checked-off a list of required courses.  Obviously the more interested the learner in the topic, the more detail they might want on constraints and the general environment.

In my own context, graduate courses in instructional design, people are there because they want to learn about instructional design, so there is a baseline motivation.  Furthermore, I would argue, that for a class taken by instructional designer the environment and the constraints are crucial to know.  We, as seasoned instructional designers and pedagogues, are expected to teach and mentor future instructional designers.  If our students know what that we operate under constraints as well (and not the rosey vision of academia that they've formed in their mind), I think they gain greater appreciation for the process of ID, and (hopefully) it gets them thinking about working through an ID process in a more agile way with the tools, skills, and constraints that they have at hand.

I think regardless of the audience (students in the class), it's important to explain to the students what's been decided on by the department's curriculum committee as a must and what is discretionary on your part as an instructor.  The reason for this is really to raise awareness of what we, as instructors, have and do not have control over.  If students complain about me because I always given them feedback late, and my feedback stinks, then that's on me.  If students complain about me, but the complaint is really about the materials assigned for class (and those materials are assigned, and the instructor does not have the ability to change them) then it's important to let the students know that.

From my own perspective - the case of 619 (aka 684):
The course that Rebecca taught last fall was something I had inherited previously from another instructor.  I considered the first semester of me teaching that course as a stop-gap measure for the department. The instructor that had taught it (and other courses) for a long time (11 years at that time, by my estimates).  I inherited a blackboard course with all the materials, I went through it, but I didn't agree with all elements of the design, and I wanted the course to be updated, but I considered myself a one-semester person (in other words I didn't expect a callback).  I kept the course as it was for that semester to get to see it in action.

In a subsequent semester I was called back to teach the course again - but again in a last-moment fashion, so I didn't have time to hit the library databases to find better readings (or heck - redesign from scratch).  I also didn't feel empowered to change the course in total because  I got the vibe from the department that they were pining for this person to return, and that the course was the pinnacle of good design.  Well, semester after semester I got to teach the same course, so I decided to go with a plug-and-play approach to design.  Change readings and different modules as I went along, instead of a wholesale re-design (my preference).  During this time I had conversations with learners in my class about instructional design, and the realities of both working on something from scratch, and having to work off something created by others, within specific organizational contexts.  My own experience teaching, and tweaking, the course I was teaching seemed like a good real life example for them; and I hope it made them more appreciative of the constraints and environments in which ID takes place!

In retrospect, I think that back then I could have gotten away with doing it my way, but being an adjunct means that you are not in a position of power, so you need to tread lightly. If the department doesn't give you the vibe that they are welcome to change (and how much change!), then it's hard for a newbie to really get invested in such a time consuming process.  New course developments carry a development stipend at my institution (subject to approval), but course re-designs do not usually, and if they do it's much smaller than the original course development stipend. This, too, keeping in mind, that a course isn't an island and that it needs to connect meaningfully with other courses in a curriculum. So being an adjunct means that you generally have only a piece of the overall curriculum puzzle, and if you're only hired to teach a specific course, it's important for that department to tell you explicitly what the connecting pieces are that need to be covered, and what the discretionary pieces are where you can discuss more emergent themes.

Well, that's it for me.  At the end of the day, the answer is "it depends on the audience".

Your thoughts?

Stacks Image 20


 Aug 2023 (1)
 Jul 2023 (1)
 May 2023 (1)
 Apr 2023 (4)
 Mar 2023 (5)
 Feb 2023 (2)
 Dec 2022 (6)
 Nov 2022 (1)
 Sep 2022 (1)
 Aug 2022 (2)
 Jul 2022 (3)
 Jun 2022 (1)
 May 2022 (1)
 Apr 2022 (2)
 Feb 2022 (2)
 Nov 2021 (2)
 Sep 2021 (1)
 Aug 2021 (1)
 Jul 2021 (2)
 Jun 2021 (1)
 May 2021 (1)
 Oct 2020 (1)
 Sep 2020 (1)
 Aug 2020 (1)
 May 2020 (2)
 Apr 2020 (2)
 Feb 2020 (1)
 Dec 2019 (3)
 Oct 2019 (2)
 Aug 2019 (1)
 Jul 2019 (1)
 May 2019 (1)
 Apr 2019 (1)
 Mar 2019 (1)
 Dec 2018 (5)
 Nov 2018 (1)
 Oct 2018 (2)
 Sep 2018 (2)
 Jun 2018 (1)
 Apr 2018 (1)
 Mar 2018 (2)
 Feb 2018 (2)
 Jan 2018 (1)
 Dec 2017 (1)
 Nov 2017 (2)
 Oct 2017 (1)
 Sep 2017 (2)
 Aug 2017 (2)
 Jul 2017 (2)
 Jun 2017 (4)
 May 2017 (7)
 Apr 2017 (3)
 Feb 2017 (4)
 Jan 2017 (5)
 Dec 2016 (5)
 Nov 2016 (9)
 Oct 2016 (1)
 Sep 2016 (6)
 Aug 2016 (4)
 Jul 2016 (7)
 Jun 2016 (8)
 May 2016 (9)
 Apr 2016 (10)
 Mar 2016 (12)
 Feb 2016 (13)
 Jan 2016 (7)
 Dec 2015 (11)
 Nov 2015 (10)
 Oct 2015 (7)
 Sep 2015 (5)
 Aug 2015 (8)
 Jul 2015 (9)
 Jun 2015 (7)
 May 2015 (7)
 Apr 2015 (15)
 Mar 2015 (2)
 Feb 2015 (10)
 Jan 2015 (4)
 Dec 2014 (7)
 Nov 2014 (5)
 Oct 2014 (13)
 Sep 2014 (10)
 Aug 2014 (8)
 Jul 2014 (8)
 Jun 2014 (5)
 May 2014 (5)
 Apr 2014 (3)
 Mar 2014 (4)
 Feb 2014 (8)
 Jan 2014 (10)
 Dec 2013 (10)
 Nov 2013 (4)
 Oct 2013 (8)
 Sep 2013 (6)
 Aug 2013 (10)
 Jul 2013 (6)
 Jun 2013 (4)
 May 2013 (3)
 Apr 2013 (2)
 Mar 2013 (8)
 Feb 2013 (4)
 Jan 2013 (10)
 Dec 2012 (11)
 Nov 2012 (3)
 Oct 2012 (8)
 Sep 2012 (17)
 Aug 2012 (15)
 Jul 2012 (16)
 Jun 2012 (19)
 May 2012 (12)
 Apr 2012 (12)
 Mar 2012 (12)
 Feb 2012 (12)
 Jan 2012 (13)
 Dec 2011 (14)
 Nov 2011 (19)
 Oct 2011 (21)
 Sep 2011 (31)
 Aug 2011 (12)
 Jul 2011 (8)
 Jun 2011 (7)
 May 2011 (3)
 Apr 2011 (2)
 Mar 2011 (8)
 Feb 2011 (5)
 Jan 2011 (6)
 Dec 2010 (6)
 Nov 2010 (3)
 Oct 2010 (2)
 Sep 2010 (2)
 Aug 2010 (4)
 Jul 2010 (9)
 Jun 2010 (8)
 May 2010 (5)
 Apr 2010 (4)
 Mar 2010 (2)
 Feb 2010 (3)
 Jan 2010 (7)
 Dec 2009 (9)
 Nov 2009 (5)
 Oct 2009 (9)
 Sep 2009 (13)
 Aug 2009 (13)
 Jul 2009 (13)
 Jun 2009 (13)
 May 2009 (15)
 Apr 2009 (15)
 Mar 2009 (14)
 Feb 2009 (13)
 Jan 2009 (10)
 Dec 2008 (12)
 Nov 2008 (6)
 Oct 2008 (8)
 Sep 2008 (2)
 Jun 2008 (1)
 May 2008 (6)
 Apr 2008 (1)
Stacks Image 18