Skip to main content

SME Relationship-Building: Tips of the Week

A couple of things came to mind during some recent SME conversations that I want to share. You may be already doing these things, but I think it helps to put them down here for all of us to think about and discuss...
  1. Given our mandate from Nancy Davis to consult to our SMEs on pedagogical issues related to learning outcomes, FOs, etc., it's likely that we'll run into SMEs who are not used to spelling out their instructional rationales and strategies as specifically as we're asking them to, even if they are at some level "good teachers." I try to motivate them by noting that the coursemap is now viewed as much of a ‘document of record’ as the Prospectus and Syllabus are – so it needs to show the rigor and clarity of outcomes of a 'premier' e-learning experience. And if a SME's LO/FO/assignment connections aren't as Bloom-worthy as they need to be, let's communicate to him or her that "my job is to help your expertise shine through"... in other words, align with his or her content knowledge and desire to create a sound, effective, engaging course for students. (I suppose you can also look at it as appealing to their professional ego: we want the coursemap to represent their "best" academic/instructional self.) I know that if I don't keep these frames in mind for myself, I may get frustrated at the process -- or even give up trying to improve the draft -- before a SME's coursemap is as instructionally sound as it can be.
  2. First-time SMEs might be taken aback by how "early" we need detailed course content, as they may be used to putting an on-ground course together in the last few weeks before it starts, or even week-to-week during the term (!). One of my current SMEs is in that boat, and I think it helps that I started by normalizing her reaction: "Yep, it IS early, isn't it!" Of course it's critical to give concrete reasons for this timeline -- e.g., the iterative draft process, the required Chair review, and everything extra that comes with building a Web-based course vs. an on-ground one. But if it's a big change for a new SME, then it's a big change -- and I want her to feel I understand that. ***Disclaimer: 'Experienced SMEs who still fail to meet deadlines' not included. Your results may vary. Void where prohibited.***
Okay... we'd love to hear about any strategies that have worked for you re: these two topics. My goal is to post at least one tip like this per week.

Comments

Popular posts from this blog

Encouraging student voice and video comments

Hey team, Won and I are at the Sloan-C Emerging Technology conference (#et4online), and I wanted to share some ideas with you all regarding the utilization of audio and video features in our discussion boards.  The presenter who inspired this post is Michelle Pacansky-Brock who wrote an ebook about VoiceThread. Her institution bought a site license so that students could make comments on VT via phone, ensuring that technology wouldn't be a barrier to student participation. My thoughts are that our online and most blended students have both computers with webcams/microphones and smartphones. I think that in Canvas we don't need to rely so much on VT to facilitate an audio/visual discussion, as these features are integrated into the learning platform. Michelle conducted research in her classes via surveys and discovered that when she as an instructor left voice and video comments, 97% of the students appreciated such comments. However, 75% of the students were unwilling ...

What's all this talk about APIs?

These application programming interfaces (APIs) are all the rage these days.  We hear about them in online commerce, social media, and now they are flooding the world of education and online learning.  So what are they exactly? An API is a way for websites, programmers, and applications to communicate with each other, exchanging information.  If I have a database with information that I would like to disseminate then I can develop an API and make that accessible to the world.  External developers can then create APIs with the purpose of communicating with my  API, and thus extract the information that I am making public.  It's similar to the notion of "my people will contact your people and we'll make this happen".  Only the people in mention is actually a software-to-software exchange. Why APIs are important APIs are a way to access information or databases which would otherwise be inaccessible.  For example, my database might be protected ...

Recap of L&L

I just wanted to put up a recap of what I went over yesterday. This should be useful for Nicole and Gia, who didn't make it for that portion, as well as for anyone who would like to go over that again. The short description of my portion yesterday was that there are a wealth of resources and materials built right into PowerPoint that most people don't know about (or they don't realize the possibilities available). We are able to take what is given to us and modify it and truly make it our own.