Stumbled across this article on Measuring What Matters. A good read for those that want to consider the use of their learning analytics.

Source: Measuring What Matters – Axonify

4 Responses

  1. The point about timing landed. By the time a course ends, the numbers mostly tell you what already happened. The teams I’ve worked with get more from small things they check weekly — who dropped off after which module, which handout nobody opened.

    My own paperwork this week had nothing to do with analytics: a pile of signed consent forms from a workshop, all photographed on my phone at bad angles. I used LensUp to straighten the corners and turn them into a printable PDF, then squeezed it toward the size the upload portal asks for. The compression aims at the size you pick and can land a bit over, so I checked it before sending. Files stay on the device and processing happens in the browser tab, which I cared about since the forms had names on them. Same lesson as the article, I suppose — collect only what you’re actually going to look at.

  2. The weekly check thing matches what I’ve seen. I ran a short internal course last spring and the end-of-course numbers told me what I already knew. The useful signal was smaller: half the group stopped opening the reading pack after module two, and nobody filled in a form about it.

    That also meant I had to make the packs easier to actually open. A lot of my handouts started life as photos of printed pages. This week I put a stack of them through this free in-browser document scanner, turned each photo into a clean printable PDF and got them small enough to email round. The compression aims at the size you pick, so one landed a bit over, but it still went through. Files are never uploaded, which mattered with student names on the pages.

  3. The weekly-check idea landed for me too. I run a short onboarding session, and the end-of-course survey always comes back looking fine while the drop-off quietly happens in week two. Checking one small thing every Friday — who never opened the reading, which handout got skipped — told me more than the final report did.

    My own week had a matching paperwork chore. I had a pile of signed consent forms from that session and a portal that wanted them as one PDF under a certain size. I photographed each form on my phone and used lensup.ai to turn the photos into a printable PDF and bring it down toward the limit the portal asked for. Worth knowing the compression aims at the size you pick, so it can land a bit over and you might have to drop a page. Files stay on the device and the processing runs in the browser tab, which I cared about because those forms had people’s names on them.

  4. That point about timing landed for me too. I run a short internal course and the end-of-course numbers are basically a history lesson by then. What actually changed things was a Monday check — which module people stalled on, which handout link never got a click. Cheap to do, and there was still time to fix something that week.

    Handouts were my paperwork chore this week as well. Six pages of printed notes for people who missed the session, and the office wanted them as one file. I shot them with my phone and dragged the four corners straight in a browser-based scan to PDF tool I keep on my laptop, LensUp — the pages were a bit skewed and I didn’t want to reprint. The compressed version aimed at the size I picked and came out slightly over, so I checked it before sending. Files are never uploaded; it all runs in the tab.

Leave a Reply

Your email address will not be published. Required fields are marked *

Connect with Julian Davis

© Copyright The Digital Learning Guy

ABN 364 4183 4283