Claims

A significant portion of participants said they would have exited LER onboarding without live human support

Claim · All claims
Evidence · 1 study · design r2 · q2
Currency · newest study 2023 · not yet checked against its sources · not reviewed by a person

Subclaims

Reading the evidence codes

q is the design tier, i the impact, n the sample, and the kind with its r the rigour judged within that kind: what each code means.

This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.

q2 i? A significant portion of participants in each workshop reported they would have abandoned the onboarding process without the live support available in the workshop. → live-support-1

Evidence

live-support-1

Hodge, M., Shah, Z., Patterson, M., Luke Luna, C. (2023, September). Onboarding and Education Design Principles for Learning and Employment Records. Digital Promise. https://doi.org/10.51388/20.500.12265/194

q2 · i? · design · r2

Self-reported finding from the two co-design workshops, where participants onboarded with facilitators and vendor representatives present. The report notes participants were "hesitant to adopt the tool or give the application numerous attempts independently" after completing onboarding with tech glitches.

"A significant portion of participants in each workshop admitted they would have exited the onboarding process had they not had live support in the workshop to persist."

Discussion

Page metadata
Field Value
type claim
id live-support-prevents-ler-onboarding-exit
title A significant portion of participants said they would have exited LER onboarding without live human support
description A significant portion of participants said they would have exited LER onboarding without live human support
status review
evidence_strength moderate
newest_evidence 2023
generated by process:wiki-ingest on 2026-10-09
trust unverified — no one has confirmed this page's content
sources 1 — live-support-1

Frontmatter is the page's machine-readable record — see the Schema & Guide.