Guides, research, and playbooks on in-video assessment, engagement analytics, LMS integration, and compliance. From the team building the engagement layer for learning.
The Annoto blog is written for the people who make video-based courses work: instructors, instructional designers, learning technologists, and the administrators who support them. Everything published here serves one question — how do you turn hours of watching into moments of learning? Some posts argue a position, some walk through a workflow step by step, and some simply report what we are seeing across the institutions that use Annoto every day.
A large share of the blog explores the teaching side of video: why active learning beats passive viewing, how social presence changes online courses, where reflection points and retrieval-style questioning fit in a syllabus, and what makes a discussion prompt worth pausing a lecture for. These posts are practical rather than academic — each one ends with something you can try in your next course.
Playbook posts get specific: setting up time-anchored discussions and in-video quizzes inside Canvas, Moodle, Blackboard, Brightspace, or Open edX; wiring completion and gradebook sync so participation counts; reading attention and comprehension analytics without drowning in charts; and running polls, reactions, and peer review on top of Kaltura, Panopto, Wistia, YouTube, or Vimeo. When a post touches configuration, it links to the technical reference at docs.annoto.net.
We also use the blog to explain what we ship and why — new capabilities in the Lumo AI copilot, improvements to notes and AI summaries, changes to analytics export — along with field notes drawn from institutions worldwide. These posts show how real courses use a feature, not just what the release notes say, so you can judge whether it belongs in your teaching practice.
New posts are added regularly, and the archive below is organized so you can browse by theme. If you are new to in-video collaboration, start with the pedagogy pieces to build the case, then move to the playbooks when you are ready to put it in front of students. Bring the questions those posts raise to your own courses — that is what they are for.
The archive below groups every post into the three streams described above — pedagogy, playbooks, and product — and each entry also carries tags for the LMS and the video platform it touches. That means a Moodle team can filter straight to Moodle material, a Panopto campus can skip player-specific posts that do not apply to it, and a Canvas instructor searching for gradebook guidance lands on the right walkthrough the first time. Formats vary deliberately: long-form essays build an argument you can bring to a curriculum committee, step-by-step guides assume you have Annoto open in a second tab, and field notes compress one course, one decision, and one result into a few minutes of reading.
Posts stand alone, so there is no required order, but they cross-reference each other wherever a topic continues. A guide to authoring in-video quizzes points back to the essay on retrieval practice that motivates it, and forward to the analytics post that shows how to judge the results. When a subject demands exact configuration detail — LTI 1.3 registration, completion sync, analytics export through CSV or the API — the post keeps its focus on the decisions involved and hands the technical steps to docs.annoto.net, so neither the blog nor the documentation has to do the other's job.
Instructors get the fastest return from the pedagogy stream. Begin with the posts on writing discussion prompts that justify pausing a lecture, then the pieces on reflection points and on responding to student comments without letting moderation swallow your week. Once the teaching rationale is clear, pick a single playbook — most instructors start with a time-anchored discussion or a short in-video quiz in one course — and run it for a module before expanding further. The archive also holds posts on reading your first attention and comprehension reports, which tell you within weeks whether the change is doing what you hoped it would.
Instructional designers tend to read across all three streams, because their work sits between teaching intent and platform mechanics. The most-used posts for this audience cover mapping interaction types to learning outcomes — when a poll serves better than a quiz, when peer review earns its overhead, and how densely to place questions in a recorded lecture before they become interruptions rather than checkpoints. Several playbooks are written as reusable patterns rather than one-off setups, so a designer can hand a faculty member a template for a discussion-led module or a quiz-paced lecture series instead of building each course from a blank page.
Learning technologists and administrators will find a dedicated thread of posts on rollout: sequencing an LTI 1.3 deployment across Canvas, Moodle, Blackboard, Brightspace, or Open edX; deciding which courses pilot first; wiring completion and gradebook sync so participation counts toward grades; and setting up analytics export so institutional reporting does not depend on screenshots. Field notes in this stream describe how other institutions structured faculty enablement — which training formats actually got used, which departments adopted fastest, and what support load to expect in the first term. If your job is to make the platform disappear behind the teaching, these posts were written for you.
Every post begins with something observed in a real course. Drawing on deployments across institutions worldwide gives us a steady supply of material, and it also sets the editorial bar: we do not publish claims we cannot trace to practice, we do not dress up a routine release as a breakthrough, and we would rather share a narrow, verified observation than a sweeping generalization. When a post describes an outcome, it describes the conditions that produced it, so you can judge whether those conditions resemble your own. Product announcements follow the same rule — they explain the problem a capability was built to solve and the teaching situations where it applies, not just what changed.
Many learning-technology teams use the blog as ready-made workshop material, and the archive supports that deliberately. A pedagogy essay works as pre-reading that gets a room of instructors arguing about teaching rather than software; a playbook becomes the hands-on portion, with each participant configuring a quiz or a discussion prompt in a sandbox course while following the steps; a field note closes the session with proof that a comparable department already made this work. Teams that run enablement this way report that the workshop conversation shifts from whether to adopt to which course goes first — a much easier conversation to be in.
The most common question readers send us is not whether active video works but how to prove it on their own campus. The pilot-focused posts give that question a shape: choose one course and one capability, define before you start what evidence would count — completion rates, comprehension scores, the volume and quality of time-anchored discussion — and let the analytics gather that evidence while the course simply runs. Because Annoto reports attention and comprehension per video and per cohort, a single semester is usually enough to produce a difference worth discussing with colleagues.
When a pilot ends, the same posts cover the step most teams skip: writing up what happened and circulating it beyond the pilot team. Several field notes in this archive began exactly that way — an instructor or designer documented a result, shared it internally, and the write-up became the case that moved a department from one course to a whole program. If your team runs a pilot worth telling, we want to hear about it; some of the strongest posts on this blog started as a reader's email.
Get the best resources and research on active video learning in your inbox, once a month.
Reading about it is one thing. Book a demo and watch Annoto work on your video, in your LMS.
Book A Demo
