Emerging-Tech Literacy for Faculty: The 90-Day On-Ramp

Nobody has time to “keep up with technology.” That phrase describes a treadmill, not a goal, and faculty are right to refuse it. What you can build — in about ninety days of small, scheduled effort — is something more durable: enough working literacy to evaluate any new tool on your own terms, so the next wave of hype breaks against your judgment instead of your calendar.

Here is the on-ramp I recommend, one month at a time.

Days 1–30: Use, don’t read

The first month has one rule: hands on tools, not articles about tools. Reading about AI is like reading about swimming — comfortable and useless. Pick the two categories most likely to touch your discipline (for most faculty right now: a general AI assistant and whatever is emerging in your field’s software) and use them on your own real work, twenty minutes at a time, three times a week.

Give the assistant your actual tasks: draft a quiz from your notes, summarize a reading you know deeply, propose feedback on a past student paper you already graded. The point of using material you know cold is calibration — you can see immediately where the tool is brilliant, where it is confidently wrong, and where it is wrong in ways a novice would never catch. That last category is the one that should shape your teaching, because your students are all novices.

Keep a friction log: one line per session on what worked and what lied to you. By day 30 you will have something no webinar provides — your own evidence.

Days 31–60: Map it to your course

Month two moves from personal literacy to course relevance. Take your friction log and your syllabus and ask three questions per major assignment: Could a tool do this? Would a student using a tool skip the thinking? Could a tool make this assignment harder and better? (Sort into those three bins and the redesign priorities fall out on their own.)

This is also the month to find your locals. Every campus has a handful of faculty quietly ahead on this — usually not the loudest voices, and often in departments you’d never guess. One coffee with a colleague who has run AI-aware assignments for a term is worth a semester of vendor webinars, because they know your students, your LMS, and your constraints. Ask what broke. The failure stories are the transferable ones.

If your discipline touches immersive tech — health sciences, trades, design, the lab sciences — month two is when you book thirty minutes with whatever XR gear exists on campus. Not to adopt it: to have a first-person answer when a student, dean, or vendor asks what you think.

Days 61–90: Ship one small thing

Literacy consolidates when it produces something. Month three, ship exactly one artifact:

One redesigned assignment from your bin-two list, run live with a disclosure norm; or
One AI-required activity where students critique, verify, or outwrite the model; or
One tech-evaluation exercise where students apply your discipline’s standards to a tool’s output — the transferable skill hiding inside every emerging-tech panic.

Small is the discipline here. One artifact, one section, one term. Collect the same evidence you’d collect for any teaching change: student work, a quick pulse survey, your own notes on what you’d change. Now you have a result — positive or negative — and a result makes you the colleague others take to coffee in month two of their on-ramp.

The literacy that lasts

Notice what the ninety days did not include: mastering any specific tool. Tools churn; this year’s interface will be unrecognizable in two. What persists is the evaluative stance you built — the reflex of testing claims against your own material, sorting capability from confidence, and asking “what thinking does this replace?” before asking “what time does this save?”

That stance is also precisely what students need from you. They do not need faculty who know every tool; they need faculty who model how an expert evaluates one. Every discipline already teaches evidence standards, source criticism, error analysis. Emerging- tech literacy is those same standards, aimed at new targets — which means faculty are not behind on this. You have been training the muscle for your whole career. The ninety days just point it at the machines.

Do the on-ramp once and maintenance is nearly free: one experiment per term, one conversation per month, one honest look at your assignments per year. The treadmill is optional. The judgment is yours to keep.

A final note on institutional support: if you lead faculty development, the 90-day structure scales cleanly to a cohort — same three months, same one-artifact finish line, plus a monthly hour where the cohort compares friction logs. The shared logs are the curriculum; the facilitator’s job is mostly protecting the twenty-minute practice blocks from everything else on the calendar. Cohorts finish with a dozen shipped experiments and, more valuably, a dozen colleagues who now answer each other’s questions first.

Emerging-Tech Literacy for Faculty: The 90-Day On-Ramp