Getting full completion on mobile-only devices

Full completion on mobile-only training is an operations problem, not just a course-design problem. The basics matter: mobile-first modules, fast login, clear deadlines, and managers who can see who is stuck. The harder part is exception handling for leave, late hires, broken devices, and locations that need direct follow-up. ## Define eligible learners Full completion should mean every active learner in scope finishes inside the deadline window. Exclude long-term leave, terminated workers, and learners added after the cutoff. Include a short buffer for new hires who join during the rollout. ## Make the mobile path boring Login should be fast, resume should be reliable, and every module should work on the smallest common device in the network. A broken mobile path creates manager workarounds immediately. ## Give managers the exact list The dashboard should not make managers hunt. It should show who is not started, who is in progress, who is overdue, and which device or access issue is blocking them. ## Close exceptions deliberately The last holdouts need an owner. Aristotl keeps the learner list, deadline state, and exception notes together so HQ can distinguish real gaps from legitimate exclusions.

Ready to put this into practice?