Open education often assumes a shared threshold, as if practitioners are all standing before the same door with the same key, the same confidence, and the same amount of time to turn the handle. They are not. For some, the door opens easily into spacious possibility. For others, it sticks, locked by uncertainty, time scarcity, inaccessible information, perfectionism, policy confusion, or the quiet fear of getting it wrong in public.
This session argues that if Open Education is serious about access, it cannot reserve its gentleness for students alone. It must meet practitioners at the threshold too, attending to the tiny details where entry is either made possible or made impossible. Drawing from two semesters of program design and implementation at a Hispanic-Serving Institution, I share a practical model of “mini structures” as threshold design: an inquiry-based OER exploration mini-grant that pays faculty for rigorous search and decision-ready documentation (rather than requiring premature adoption), paired with a scaffolded sequence of mini-lessons that translate complex Open Educational Practices into bounded steps with clear outcomes, examples, and time expectations.
The core claim is simple: a door is only open if someone can actually get through it. In many institutional contexts, the primary barriers are not ideological resistance. They are practical and quietly determinative: not knowing where to start, and starting alone.
I highlight the hinge details that repeatedly change follow-through without lowering rigor: bounded time containers (30–45 minute work sessions with a concrete deliverable), “what counts” guidance that reduces ambiguity, risk reduction through private drafts and optional publicness, and documentation-as-scaffolding (trackers, evaluation lenses, landscape briefs) that makes decisions visible, retrievable, and shareable.
Grounded in care ethics, I frame these choices as infrastructure rather than tone: care operationalized through systems that assume human variance as normal. Participants will leave with a replicable set of design patterns and a lightweight blueprint for building mini infrastructure in their own programs.
