The Orbital Queue
- Joel Larson, PhD
- Feb 10
- 4 min read
Why Everything Feels Like a Priority in Higher Education IT
In higher education IT, many projects don’t move forward or stop. They enter what I’ve come to think of as an orbital queue.
Once you notice this pattern, it becomes hard to unsee. Projects drift in and out of focus, pulled closer by urgency, leadership attention, or external pressure, then pushed outward again when windows close or another priority eclipses them. Nothing disappears. Nothing truly resolves. It just… orbits.
This is the missing piece that ties together everything I’ve been writing about time, people, memory, and planning in higher education IT.
When Everything Is a Priority
In higher education, “everything is a priority” is rarely hyperbole.
Everything matters to someone:
students navigating systems that shape their daily experience
faculty relying on tools to teach and research
staff supporting operations that cannot pause
leaders accountable for institutional risk and trust
But those priorities operate on different clocks.
Academic calendars, budget cycles, governance timelines, operational realities, and student tenure do not align neatly. When no single clock can dominate for long, prioritization stops being linear.
Instead of a clean queue, projects begin to rotate.
From Backlog to Orbit
In many environments, work moves through a pipeline. In higher education IT, much of it enters a holding pattern.
Projects are:
approved but not executable yet
understood but not alignable right now
funded but waiting for the “right” window
Over time, they stop behaving like items waiting their turn and start behaving like objects in orbit.
That’s the orbital queue.
In an orbital queue:
nothing is forgotten
nothing is fully resolved
and nothing stays still
Projects move closer when gravity increases. A complaint resurfaces. A deadline approaches. Leadership asks, “What’s the status of Project X?” Suddenly, the work is back in focus.
Then the window closes. A new urgency appears. Another clock asserts itself. The project drifts outward again.
This isn’t chaos. It’s motion under competing forces.
Why the Orbit Exists
The orbital queue exists because of everything that came before it.
Competing calendars mean there is rarely a single “right time.” Parallel systems are used to buy recoverability, not speed, increasing cost and complexity. The human toll shows up as decision fatigue and cautious stewardship. Memory mismatches mean students experience friction briefly, while staff and faculty carry the long memory of failure.
Add one more factor: risk ownership is uneven.
The people who ask for change are often not the ones who will carry the consequences if it fails. The people who will still be there during recovery, explanation, and trust repair tend to optimize for survivability, not velocity.
That combination produces orbit.
How Orbit Feels on the Inside
From the inside, orbital queues are exhausting.
Teams revisit the same work repeatedly, each time re-explaining context, re-validating assumptions, and re-negotiating scope. Progress feels real, but fragile.
Momentum builds, then dissipates.
From the outside, it can look like indecision.
From the inside, it feels like stewardship under uncertainty.
This is why status questions land the way they do. “Where are we on this?” isn’t just a request for information. It’s a gravitational event.
The Student Perspective
Students often notice issues early and loudly. They experience friction in the moment.
But their clock is short.
A student may raise a concern in their first year or junior year. It can take a full academic year to evaluate and align, and another year to implement. By the time the change arrives, the student who identified the issue is often gone.
New students arrive with no memory of how it used to be. To them, the improvement simply exists.
From the student perspective, change feels invisible or absent. From the institutional perspective, it was a long, careful orbit.
Both experiences are true.
Why This Matters
If we don’t name orbital queues, we misdiagnose the problem.
We assume:
lack of urgency instead of competing clocks
resistance instead of asymmetric risk
inefficiency instead of recoverability
inaction instead of cyclical prioritization
Once you see the orbit, many familiar frustrations make more sense. Projects don’t keep coming back because no one is paying attention. They come back because the system is constantly renegotiating which clock gets to matter right now.
What Leaders Can Do With This
Naming the orbital queue doesn’t magically resolve it. But it changes the conversation.
It allows leaders to ask better questions:
What is pulling this project inward right now?
What will push it outward again?
Who owns recovery if this fails?
Which clocks are we optimizing for this time?
It shifts the discussion from “why won’t this move?” to “what forces are acting on it?”
That’s a more honest place to plan from.
Closing the Series
Higher education IT doesn’t run slowly. It runs carefully, across multiple clocks, with long memories and uneven risk.
The orbital queue is what happens when all of those forces act at once.
Once you see it, the earlier posts fall into place:
why time works differently
why parallel systems persist
why people feel the weight of decisions
why change often arrives after the original askers are gone
This isn’t a failure of planning.
It’s the physics of the environment.
And understanding that is the first step toward leading well inside it.
Comments