Research proposal / Visual executive brief
Digital Friction in Learning Environments.
What happens when the work of navigating school technology gets in the way of the work of learning?
A source-grounded interpretation of my 2025 research proposal, Reducing Digital Friction in K–12 Learning. This is a proposed study, not a report of experimental results.
The design problem
A simple assignment can require a surprisingly complicated journey.
During my AmeriCorps mentoring work at Oceanside High School, I observed students navigating Chromebooks, Google Classroom, Drive, assignment links, and repeated authentication just to finish routine work.
The proposal describes tasks requiring roughly five to seven steps, sometimes with additional logins. Those observations motivated the research question; they are contextual observations, not baseline measurements from a completed experiment.
Digital friction means avoidable work created by the interface or workflow—not the productive difficulty of thinking, practicing, or learning. The research asks whether removing that unnecessary burden could narrow the gap between intending to work and actually beginning.
Intention → action
Navigation, re-logins, unclear handoffs, and feedback delays may interrupt follow-through.
Illustrative interpretation of the proposal; it does not depict measured drop-off or an observed causal effect.
The routine digital micro-flow
Authenticate → Open → Act → Feedback- 01AuthenticateGet into the required system; possibly sign in again.
- 02OpenLocate the class, link, file, or assignment.
- 03ActComplete and attach the work through the required interface.
- 04FeedbackConfirm the submission and find the next signal.
This sequence is the analytical framework described in the proposal. Individual classes and tools may require different steps.
Conceptual foundation
This is a learning-design question—not just a clicks question.
The proposal draws from three connected lines of reasoning. It distinguishes avoidable interface complexity from the challenge that makes learning meaningful.
Learning science
Cognitive load theory
Unnecessary navigation and fragmented interfaces can consume working-memory resources better spent on learning.
Sweller (1988), as discussed in the proposal
Behavior design
Fogg Behavior Model
The ability to act matters alongside motivation and a prompt. Extra digital steps may interrupt the moment a learner is ready to begin.
Fogg (2009), as discussed in the proposal
Access and equity
Friction is unevenly distributed
Inconsistent workflows may create additional burdens for multilingual learners, students with executive-function challenges, and those with limited device or internet access.
Literature synthesis in the proposal
An important distinction
Not all friction is bad. Security safeguards, confirmation steps, and productive struggle can serve real purposes. The research concerns unnecessary digital burden, not removing every pause or challenge from learning.
Proposed research
Compare the familiar workflow with a simpler alternative.
Comparison condition
Current flowMulti-step submission
Students use the existing Google Classroom workflow, including its normal links, file handling, and authentication requirements.
Proposed intervention
Not yet testedFriction-minimal submission
Students use a proposed one-screen submission flow with pass-through single sign-on. The goal is to remove unnecessary handoffs without sacrificing safeguards.
Illustration of experimental conditions, not screenshots of an implemented prototype or evidence that one performs better.
Research question 01
How do step count and repeated logins affect time-to-first-action and completion of routine assignments in a Google Classroom ecosystem?
Research question 02
To what extent does a friction-minimal workflow improve students’ perceived usability and task completion compared with the current flow?
Evidence plan
Measure what changed. Ask why it felt different.
Quantitative measures
The proposal specifies system logs, completion records and student survey instruments—not post-hoc performance claims.
- 01Navigation burden
- Workflow steps and repeated authentications
- 02Task initiation
- Time from assignment release to first action
- 03Follow-through
- Assignment submitted or not submitted
- 04Perceived experience
- System Usability Scale (SUS) and NASA-TLX workload
Qualitative evidence
Student voice + teacher observation
Brief student reflections would identify what frustrated or helped them. Teacher notes would record hesitations, help requests, and workarounds.
Planned analysis
Descriptive statistics, t-tests, and chi-square comparisons alongside thematic coding of open responses. Triangulation would connect the behavioral measures with lived experience.
Interpretation & responsibility
The contribution is a testable design question—not a proven result.
What a future study could clarify
- Whether streamlined submission reduces time to start and increases assignment completion.
- Whether students perceive a simpler workflow as more usable and less demanding.
- Which interface steps produce the greatest avoidable burden across different learner contexts.
- Where classroom workflow, system integration, and access policies should change.
Ethics & limitations
- Small, single-school sample and two intact classes limit generalizability and causal certainty.
- Novelty effects and the author’s prior mentoring role could influence observations.
- Research with minors requires voluntary student assent, parental consent, privacy protection, and district safeguards.
- Usability is not the same as subject-matter mastery; any future learning claims would require appropriate outcome evidence.
The ambition: keep learners’ effort directed toward learning—not toward finding their way through the software.
The paper reviews relevant literature and proposes a study. It does not report that a prototype was deployed, students were enrolled, or improvements were measured.