Tag Archives: hands-on

Workshop Feedback and Moving Forward

I’ve now looked through the feedback from the workshop evaluation forms. Stupid problem number one was that several people only completed one side of the evaluation form. It is clear that they did not realize the form had two sides. I will need to be much more clear at the next workshop that there are two sides to the form. I’ll also update the form to say or something like that at the bottom.

Themes that emerged from the workshop feedback:

  • Resource: participants would like some kind of resource (handouts and/or eBook) to support the workshop. This resource should include a list of apps that are mentioned with their descriptions.
  • More hands-on: participants would like more hands on activities and less theory.
  • Slower pace: Pace of presentation was too fast. Some participants felt like there was too much information presented

In addition, the pre/post test indicated that the following items were already known by most participants, such that they need not be covered in the workshop:

  • Turning on and off the iPad
  • Using the iPad to buy an App from the App Store
  • Organizing icons on my iPad

As I mentioned previously, my plan is to restructure the skills lab to be problem-based learning scenarios. These will be supported by some form of resource as well as me (or the technologist) being present. It will be sort of liked a “flipped” classroom model, when learners are given a challenge and can work either individually or in small groups to work through the various activities. This will increase the amount of hands-on time, but also hopefully, help people feel like they won’t forget everything they learned the minute they walk out of the room. The resource will also contain a bunch of the theoretical information that originally covered in the skills lab. This information could just as easily be read, rather than presented. The key is to spend the face-to-face time doing hands-on activities.

My other plan is to provide some form of resource. I’m not 100% certain what that will be. Originally, I had planned on it being this website, but I’m realizing that the navigation on this site is much more conducive to looking up things you already know. They need a form that looks more like a book that they can easily follow in a linear fashion. So, I think I may end up building an iBook. I also think I need a few worksheets – pieces of paper that provide a checklist of activities for people to progress through. This model has the benefit to adapt to the level of the learner. Beginner learners can start at the top of the list, where more advanced learners can skip over the stuff they already know.

There will be lots of work involved in putting this resource together. I should be able to get enough together to prove the concept for the next workshop – and then hopefully have more time over the summer to fill in all the blanks.

Do I make an iBook?

One of the issues that came up at the initial workshop was a lack of resources for participants. This was not helped by the fact that this website did not yet have resources associated with it. But also, learners wanted a list of apps, they wanted things they could take home.

I have always wondered whether the website was the right medium for this type of content.

In addition to the need for a resource, the other issue is that the workshop needs to be more hands on. The theory part of the workshop needs to be filtered out – and put elsewhere. I thought the website was a good place for it, but I’m finding myself struggling with structure – but also, knowing that they likely won’t ever access it on the website. I think an iBook might be a better choice. An iBook would allow me to add in theory in a book format. They would be more familiar with a book, flipping through pages and reading the content. We use iBooks for other faculty development programs – so the use of iBooks is not unfamiliar – plus the iBooks tutorials are needed for other fac dev programs – on other projects, not just this one … so I could do up the iBook Tutorials and integrate them into several iBooks.

With our other program we also provide the iBook in PDF format. Here, I don’t think I would do that. All the content would be available in the iBook format and on this website. I want to force learners to use the iBook rather than a PDF version – I also think the multiple versions causes a confusion sometimes, as sometimes people will download the PDF into iBooks and then not know why the iBooks isn’t working properly.

So, there is that – once I create a bunch of content, I shall create an iBook to support that content. The big question now is, can I get that done in time for a workshop on May 15th? – assuming we can make the May 15th workshop happen!

Content remixing

I am thinking about the skills lab content again. One of the bits of feedback is that they want more hands-on – and it occurs to me that this is not just the case vignettes but also in the skills lab. The focus in the skills lab was a little wrong – it needs to be more activity centric. Sort of like the Icebreaker activity – which was successful – I think also the skills lab needs more “challenge” type activities – and the theoretical content can be left for the eBook or something – similar to what we do with Essential Teaching Skills – we need to keep the focus of the workshop on activities (on doing).

So, the skills labs need to be re-structured. They need to be activity driven. Content that is best explained via lecture or text, should be left to the text – the workshop needs to focus more on hands-on.

So, in looking at workshop one, what is the skills lab content? Editing and commenting in iBooks. Perhaps it should look more like:

  1. Organizing icons (creating folders, renaming folders, changing which page on icon is on)
  2. Finding apps (searching iMedcal Apps, searching the library – finding good apps)
  3. Using iBooks (which covers some gestures as well as adding content and sending an email)

This becomes enough – and I write it up as a challenge sheet and everyone gets a chance to “do” each thing and tick it off the list when they do it. That way, they are doing hands-on and I’m just helping them work through it – filling in the blanks and asking questions.

Now I’m wondering about a link between problem-based learning and teaching technology. I will need to go check the literature on this.

First Workshop – Initial reactions

My initial reactions after the workshop were that it worked well. I don’t think it needs two physicians, but it does need more structured activities. I need the activities for the icebreaker and skills lab written down. They need to be written out better. Perhaps for the skills labs, I need actual activities (hands-on workbook) that people go through, rather than me talking and explaining something. A few things I showed worked well, but others seemed like me talking too much, and I wonder if I caused more confusion than I needed to.

In looking at the feedback, people wanted a handout. They felt they were writing things down too much. The workshop definitely needs some kind of resource (this website, but also, perhaps, a one or two page handout that people have in the workshop itself).

We also had a large group (20-people). The workshop would be better with a smaller group – or broken up into smaller groups. The length of the workshop worked well. For most of the participants, they reported “just right”, with only a few wishing the workshop was longer.

The ice breaker activity worked remarkably well. The timing for the workshop was good (right on 1h30m according to the powerpoint timer) – however, we did 15 minute ice breaker activity, 35 minutes each session, and 5 minute wrap up.

So, some quick updates for the next workshop:

  • only two presenters (ice breaker could be led by either presenter – technology educator and physician demonstrator)
  • handouts with list of apps being presented (perhaps some info on context)
  • structured activities for the skills lab – getting them doing more hands-on in this section

Other feedback is that they wanted to know more about medical apps they could use. One challenge here is that many of the medical apps being presented are apps that cost money. I haven’t really figured out how to manage that conflict.