The Long Memory of Institutions and the Short Memory of Students

Joel Larson
Jan 27
3 min read

Why Change Often Arrives After the People Who Asked for It Are Gone

In the last two posts, I’ve been writing about why time works differently in higher education IT and the human cost of operating inside a multi-clock institution.

This week, I want to look at a discrepancy that quietly shapes many technology decisions on campus:

The long memory of staff and faculty, and the short institutional memory of students.

Two Groups, Two Very Different Clocks

Staff and faculty often experience the institution over decades.

They remember:

previous systems
failed implementations
promises made and quietly abandoned
workarounds that became permanent
“new” ideas that are actually very old ones

Students experience the institution very differently.

A traditional undergraduate may be on campus for four years. A community college student may be present for one or two. Many never see a full system lifecycle from proposal to deployment.

Both perspectives are valid.

But they live on radically different clocks.

When a Student Notices a Problem

This is a familiar pattern.

A student notices something in their junior year.Or during their first year at a community college.

Maybe it’s:

a clunky system
an accessibility issue
a confusing workflow
a missing integration
a process that clearly “could be better”

They raise the concern. They submit feedback. They talk to faculty or staff.

And then… nothing seems to happen.

What Happens Next (That Students Rarely See)

Behind the scenes, the clock starts moving. Slowly.

The issue is evaluated. The scope is clarified. The need is weighed against others. Funding is discussed. Governance bodies review it. Risks are assessed. Dependencies are identified.

That alone can take an academic year.

If the answer is “yes,” the real work often begins after that.

Another year for planning, procurement, configuration, testing, and alignment with academic calendars.

Sometimes longer.

By the time the change is deployed, the student who raised the issue has often already graduated or transferred.

They never experience the outcome they helped create.

Meanwhile, a New Student Arrives

The new student encounters the improved system for the first time.

They don’t remember how it used to work. They don’t know there was ever a problem. They don’t see the years of discussion and effort behind the change.

To them, this is simply “how it is.”

The institutional memory resets.

What felt like a long, careful journey to staff and faculty feels like an instant, invisible change to students.

Why This Gap Creates Tension

This mismatch in memory creates frustration on all sides.

Students feel unheard because they never see results. Staff and faculty feel impatient pressure because they remember why things take time. IT teams feel caught between urgency and stewardship.

From one perspective, change feels painfully slow. From another, it feels almost imperceptible.

Neither is wrong.

They are just operating on different clocks.

The Long Game Clock

Higher education often plays a long game.

Not because it doesn’t care about student experience, but because changes must survive:

multiple cohorts
leadership transitions
funding cycles
policy shifts
and the next unforeseen crisis

That long-game clock is invisible to most students by design. But it shapes nearly every decision.

It is also why many of the people who make meaningful improvements never get to enjoy them as users.

They build for someone they will never meet.

Why Naming This Matters

If we don’t acknowledge this discrepancy, we misinterpret feedback loops.

We assume inaction where there is deliberation. We assume indifference where there is long-term care. We assume failure where there is simply a different definition of “now.”

Understanding how memory and time intersect helps explain why higher education IT decisions often feel disconnected from the moment they were requested.

They aren’t disconnected.

They’re just aimed at a future audience.

Looking Ahead

In the next post, I want to explore what happens when institutional memory itself becomes a risk and how past failures can quietly dictate future decisions long after the original context is gone.

Because in higher education, time doesn’t just move forward.

It remembers.