Blog

Educational developer skills, knowledge and competencies

Lavender Field (Beauty of Simplicity)
Over the past few days, I have re-read a few texts that address the skills, knowledge and competencies of educational developers. (The texts are listed at the bottom of this page).

Rather than re-hash the details here (and because I can’t reproduce the useful [copyrighted] visuals), I want to point you to specific sections of these resources as they are useful for helping educational developers articulate, assess and reflect on the skills, knowledge and competencies that we bring to our work.

To see figures that visually depict competencies of entry-level, senior and director-level educational developers, go to pages 19, 20 and 21 of the McDonald, Kenny, Kustra, Dawson, Iqbal, Borin, & Chan (2016) publication (similar visuals are in the Dawson et al. paper).

For example, a look at Figure 3.2 on p.20 of the Educational Developer’s Portfolio Guide (McDonald et al., 2016) shows:

Senior Educational Developer: Competencies

Educator, Course Design, Instructional Strategies, Program Development Strategies, Educational Strategies

Senior Educational Developer: Skills, Abilities and Knowledge

Interpersonal skills, Conflict Resolution, Mediation, Diplomacy, Trust, Listening, Empathy, Educational Leadership, Self Reflection, Peer Mentor/Coach, Model, Consultation, Formal Education in Pedagogy, Organizational Behaviour, Literacy

(I am highlighting the senior level because this is where I position myself)

Want to rate/assess your own skills, knowledge and attributes? –> Go to Appendix C (pages 67 and 68) of the Educational Developer’s Portfolio.

To read more about skills, knowledge, competencies and threshold concepts in educational development, see:

And though I haven’t written directly about Dr. Julie Timmerman’s work in this post, her paper is excellent and well worth the read:

  • Timmermans, J. (2014).  Identifying threshold concepts in the careers of educational developers.  International Journal for Academic Development, 19, 305-371. doi:10.1080/1360144X.2014.895731

 

A FAILFaire in educational development

FAILFares are not about celebrating failures, but rather about providing ‘a space in which people can celebrate taking risks and the open and honest sharing of information …so that we could learn from these things.’  – (Trucano, 2011)

I recently read an interesting blog post, by Michael Trucano (@trucano), that described his experience of organizing and hosting a FAILFaire for the World Bank. It got me thinking about the application of this concept to educational development. 

A FAILFaire, I learned from the post, is an event that recognizes projects, within an organization, that have not worked: “the pilots that never got anywhere, the applications that are not delivering, the projects that are not having any measurable impact on the lives of people, and the cultural or technical problems that arise.”(MobileAction NGO, quoted in blog post). The philosophy driving FAILFaire initiatives is that sharing lessons about what doesn’t work can encourage people to be innovative and entrepreneurial because lack of results if a likely outcome of any innovation.

Trucano cautions that these events are not about celebrating failures, but rather about providing “a space in which people can celebrate taking risks and the open and honest sharing of information (even and especially about what doesn’t work or isn’t working) so that we could learn from these things.” 

He proposes that FAILFaires have two main objectives:

  1. to generate lessons learned from experience and determine how these may be useful to other colleagues working on similar projects;
  2. to encourage open dialogue among colleagues about how to respond to professional challenges, in the hopes of addressing these more productively.

In his blog post, Trucano shares seven ground rules for presenters and also offers other practical suggestions and lessons learned from his own experience.

Possible Applications to Educational Development

Within our educational development community, I see many applications. Keeping the two overall objectives in mind (above), FAILFaire events could include:

  • A FAILFaire within your Centre for centre staff only
  • A FAILFaire at a conference (i.e. lessons learned from educational development lessons or learned in SoTL research design or implementation)
  • Help a receptive department or Faculty organize a FAILFaire in which faculty members and other instructors share lessons learned from their teaching and learning failures (if you manage this, please let me know!)
  • Encourage those you work with to reflect on lessons learned from risks they took in teaching or educational development
  • If you blog or do podcasts, consider sharing an educational development or teaching failure and what you have learnt from it (I’m going to hold myself accountable to doing this in the next few months).
  • And/or, as University of Waterloo’s Centre for Teaching Excellence has done, make it the theme of your annual teaching and learning conference (for 2016, this CTE has made the theme “Learning from Challenge and Failure” — well done Julie Timmermans and colleagues!)

Why bother? Because:

Only if we understand what doesn’t work in this field, can we collectively learn and get better.* 

 

*FastCo article “How FAILFaire Turns Epic Fails Into Successes”

Thank you to the lovely Dr. Julie Timmermans for the conversations that inspired this post.

 

Educational developer’s portfolio

Educational developer’s portfolio: Resources for creating your own

For the past two years, I have had the pleasure of collaborating with a dynamo group of educational developers on the Educational Developer’s Portfolio*. This initiative allowed me to take my interests and experience in the area of teaching portfolios, and apply it to educational development. Good stuff!

The authors of that Guide are delighted to be able to share this free downloadable resource with our community!

Also, Judy Chan and I recently offered a webinar on the Educational Developer’s portfolio for the Educational Developers Caucus. Below are some resources that might be of interest:

Additional resources can be found on WikiPODia, from the conference session that Jeanette McDonald, Debra Dawson, Erika Kustra, Judy  Chan and I co-facilitated (Natasha Kenny and Paola Borin collaborated to plan the session but were not able to make it to POD 2015 ).

Resources from POD include, but are not limited to:

  • framework for aligning a portfolio.
  • worksheet for beginning to develop a section of your educational developer’s portfolio (‘workshops facilitated’)

And, for those who like to see samples, here are portfolios Judy and I showed and talked about during the webinar:

Celebrating the ED GuidePhoto: taken by Jeanette McDonald. Cake made in honour of first EDC Guide (ours!) in the Series.

 

*”An educational developer’s portfolio is a tool used to articulate, reflect upon, and provide evidence of an educational developer’s beliefs, values, ethical principles, practices, approaches, development, and impact.” (McDonald et al., 2016, p.12)

 

Guide reference:

McDonald, J., Kenny, N., Kustra, E., Dawson, D., Iqbal, I., Borin, P., & Chan, J. (2016). Educational Development Guide Series: No. 1. The Educational Developer’s Portfolio. Ottawa, Canada: Educational Developers Caucus. Download here.

For more information about the EDC Guide Series, see here.

Liberating structures

LiberatingStructures-jewels

I recently had the pleasure of participating in a Liberating Structures workshop in Vancouver. Liberating structures can be defined as “microstructures that make it quick and simple for groups of people of any size to radically improve how they interact and work together” (Lipmanowicz & McCandless, 2013, p. 21). At the core of Liberating Structures’ philosophy is the idea that small and simple shifts in our routine interactions can make it possible for everyone to be included and engaged.

During the 2 1/2 day workshop, I tried out a variety of approaches that I can use in my facilitation, teaching, small group interactions, and individual activities. Several of the approaches were new, while others I had encountered before –usually, in a slightly different way than they were presented at the immersion workshop (see here for full description of all the miscrostructures).

I have been thinking about what made some of the microstructures feel more purposeful at the immersion workshop as compared to in other settings where I have used and/or encountered them (or variations of).  I’ll use 1-2-4-all as an example because of it’s likeness to think-pair-share as I think about the differences and similarities:

  • The invitation: During the LS workshop, participants were encouraged to pay close attention to the invitation (one of the 5 design elements in all the microstructures). Though the invitation in think-pair-share is just as important as in 1-2-4 all, I have tended to create the wording ‘on the fly’.  I have typically used “Reflect on…”, “On your own, think about…”. Now I am paying more attention to how I choose my words for even a ‘simple’ activity and writing these out before hand.
  • Purpose: The invitation (and all other design elements) are closely linked to purpose. The importance of purpose has always been top of mind, and the point was made over and over during the workshop.
  • Sharing in foursomes: In think-pair-share, I sometimes ask pairs to join and discuss in fours before we begin to report out in the large group.  In 1-2-4-all, the foursome piece is key to the activity because the purpose of this activity is to provide a venue for expressing thoughts, gathering diversity of input and building meaning-making among the group.  When doing 1-2-all, and the foursome piece is left out, I think there is less opportunity to achieve the purposes described previously.
  •  Sharing an important/valuable/worthwhile idea to the large group: What made this step most useful for me was that our facilitator instructed (“invited”) us to consider and come to some agreement (as a foursome) on: “What is one idea that stood out in your conversation?” He also suggested that only those ideas that were important and valuable to the whole group be shared with the whole group. In doing so, he made me think carefully about what I wanted to share and why.

Thank you to Leva Lee and Tracy Kelly from BC Campus‘s Professional Learning, UBC CTLT and others who organized this worthwhile event!  See here  for two related posts on Liberating Structures by Tracy Kelly.

Teaching and learning inventories

Photo by inthepotter’shands

I am currently reading the second edition of Maryellen Weimer‘s excellent book titled “Learner-Centered Teaching: Five Key Changes to Practice“.

In it, she refers readers to a number of inventories relevant to post-secondary teaching and learning (many of these I have not heard of and would like to follow up on). Here is a list of all those she has written about up to page 158 (that is as far as I’ve gotten in the book), with links to some further information.

Motivated Strategies for Learning Questionnaire (MSLQ) -self-report instrument designed to measure students’ motivational orientations and their use of different learning strategies. (p.35 in Weimer’s book). See here for more information.  And/or, see here for article by Pintrich & De Groot.

Revised Study Process Questionnaire (R-SPQ-2F) – assesses students’ deep and surface approaches to learning. (p. 32 in Weimer’s book). See here for article by Biggs, Kember, and Leung (scroll to page 19 for questionnaire)

Approaches to Teaching Inventory – provides insight into how academics approach their teaching (p.32 in Weimer’s book). See here (PDF).

Classroom Climate Inventory – gives instructors input on the actual climate within a class in order to evaluate how conducive that atmosphere is to learning. (p.147-148 Weimer’s book). See here (Word version of inventory can be downloaded).

Autonomous Learning Survey – short survey that helps students assess themselves as autonomous (or dependent) learners.  (p.150 Weimer’s book) See here for a Faculty Focus piece with the inventory.

 

Please email me at isabeau.iqbal(at)ubc.ca or send me a tweet @isabeauiqbal if you have more I can add to this list!