Higher education institutions are rarely short on ideas for improvement.
We conduct assessments, develop strategic plans, administer surveys, review performance indicators, attend conferences, and participate in countless conversations about what our institutions could be doing differently.
We identify challenges in employee engagement, departmental coordination, student retention, operational effectiveness, and leadership practices.
And frequently, we develop thoughtful recommendations for addressing them.
Yet I've come to believe that one of the most important questions in institutional improvement is also one of the simplest:
What happens after we recognize that something needs to change?
Throughout my years in higher education, I've observed that institutions can become exceptionally skilled at identifying problems without necessarily developing an equally effective process for resolving them.
A committee identifies communication concerns between departments. An employee survey reveals frustration with workload distribution. A student complaint exposes an unnecessarily complicated process. An internal review identifies a recurring operational weakness.
The findings are discussed. Recommendations are documented. Responsibilities may even be assigned.
But then the institution returns to the demands of everyday operations.
Employees continue processing transactions, responding to students, meeting deadlines, and addressing the immediate problems in front of them.
Eventually, the original recommendations become part of a report that everyone remembers discussing but few can describe implementing.
This isn't necessarily evidence of poor leadership or a lack of institutional commitment.
Sometimes the problem is that we've made identifying opportunities for improvement a separate activity from the actual work of improving.
And I believe that distinction deserves more attention.
1. Start With One Process Worth Reviewing
Institutional improvement doesn't always require a comprehensive transformation.
Consider a recurring problem involving two departments. Perhaps information arrives late, responsibilities are unclear, or students repeatedly contact multiple offices for answers.
The temptation may be to establish a committee, conduct a broad review, or develop an institution-wide initiative.
Those approaches may sometimes be appropriate. But what if we began by examining one specific transaction from beginning to end?
What triggered the process? Who received the information? What happened next? Where did communication become delayed? Who was responsible for ensuring the issue was resolved?
A narrowly focused review can reveal practical opportunities that broad conversations sometimes overlook.
The goal isn't to redesign the entire institution in a week.
It's to understand one process well enough to make a thoughtful improvement.
2. Have the Conversation Employees Actually Need
One of the most valuable sources of institutional insight is the experience of employees who carry out our daily operations.
Yet institutional conversations sometimes focus primarily on whether employees are meeting expectations rather than whether the institution has created reasonable conditions for meeting them.
We ask about productivity, deadlines, and performance.
But do we ask which tasks are unnecessarily complicated? Which responsibilities are unclear? Which recurring problems consume time without creating meaningful value?
And perhaps more importantly, do we create conditions in which employees can answer those questions candidly?
Meaningful leadership conversations require more than inviting feedback.
They require the willingness to consider what employees are describing, explain what can and cannot change, and communicate what will happen next.
Not every suggestion will be practical. Not every challenge can be resolved immediately.
But employees should not have to wonder whether their observations disappeared into another institutional report.
3. Learn From the Problems We Catch Before They Become Serious
Higher education operates in an environment where seemingly small administrative decisions can carry substantial consequences.
An incorrect student record may affect financial aid eligibility. A missed communication may delay an important enrollment decision. An inaccurate account entry may create confusion about a student's financial obligations.
Fortunately, experienced employees often identify these situations before they become significant problems.
The record is corrected. The student receives an answer. The immediate concern is resolved.
And everyone moves on.
But what if we treated those situations as opportunities for organizational learning?
Why did the problem occur? What allowed someone to recognize it? Was the correction dependent on the knowledge of one experienced employee? Could a reasonable adjustment reduce the likelihood of recurrence?
A near miss may demonstrate that an internal control worked. It may also reveal an upstream process that deserves attention.
Learning from these experiences does not require assigning blame. It requires understanding the circumstances that made the problem possible.
4. Make One Departmental Handoff More Reliable
I have frequently emphasized that students experience our institutions as a whole, even though we organize our work into separate departments.
Admissions, Financial Aid, Student Accounts, Academic Advising, the Registrar, and Student Affairs may each have clearly defined responsibilities.
But those responsibilities intersect throughout the student's educational experience.
And it's often at those intersections that operational problems emerge.
An employee completes their assigned portion of a process and forwards the information to another department. But who confirms the next department received it? Who follows up when a response is delayed? Who ensures the student receives an accurate explanation?
The challenge isn't always that departments fail to communicate.
Sometimes it's that communication occurs without a clearly defined responsibility for follow-through.
Improvement might begin by documenting one handoff, identifying the responsible individuals, establishing reasonable expectations, and confirming what happens when an expected action doesn't occur.
Small improvements in coordination can reduce avoidable confusion for both employees and students.
5. Give Employees the Capacity to Improve
There is an irony in many institutional improvement initiatives.
We ask employees who are already managing substantial workloads to participate in projects intended to make their work more effective.
They attend additional meetings, complete new assessments, document existing processes, and implement revised procedures.
Meanwhile, their regular responsibilities remain unchanged.
Eventually, improvement itself can become another source of employee frustration.
If institutional leaders believe an improvement initiative is important, the institution must consider the time, resources, authority, and supervisory support necessary to carry it out.
This doesn't mean every initiative requires additional staffing or substantial expenditures.
Sometimes it means narrowing the scope, adjusting priorities, reducing unnecessary meetings, or postponing less urgent work.
But continuous improvement should not depend indefinitely on employees making extraordinary personal sacrifices.
We cannot expect sustainable institutional improvement while consistently overlooking the conditions under which employees are expected to achieve it.
6. Decide What We Should Know by Next Sunday
Perhaps the most important step in moving from insight to action is establishing what meaningful progress would actually look like.
Statements such as "we need better communication" or "we should improve employee engagement" can express legitimate institutional concerns.
But they do not, by themselves, tell anyone what to do next.
A more productive approach might identify one action, one responsible individual or team, one reasonable review date, and one observable indication of whether the change helped.
For example, a department might decide to review its most common student referral process over the coming week.
By the following Sunday, the team may not have solved every problem associated with that process.
But it could understand where responsibilities were unclear, identify one preventable delay, and agree on a reasonable improvement to test.
That is progress.
And progress becomes easier to sustain when it is observable, discussed, and refined through experience.
From Institutional Reflection to Institutional Action
Yesterday's Institutional Reflection series focused on questions institutions may have stopped asking.
Today, I want to extend that conversation by considering what we do with the answers.
Institutional effectiveness isn't determined solely by the quality of our strategic plans, the sophistication of our performance measures, or the number of improvement initiatives we announce.
It is also reflected in the everyday experiences of our employees and students.
Are responsibilities clearer? Are processes more reliable? Are employees better supported? Can students navigate institutional services with less unnecessary frustration?
Those experiences may reveal dimensions of institutional improvement that formal reports do not fully capture.
And importantly, improvement doesn't have to mean adopting someone else's model or assuming that one solution will work everywhere.
Institutions differ in mission, resources, structure, student populations, and regulatory responsibilities.
The objective is to examine our own practices thoughtfully, learn from the people experiencing them, and consider what reasonable changes might make a meaningful difference.
Institutional improvement begins with insight, but it becomes real through action.
Throughout today's Rosenboom Workforce Institute professional-development series, I'll explore six practical questions about turning institutional observations into meaningful steps forward.
My hope is that these conversations encourage colleagues to identify something manageable within their own organizations—not necessarily something dramatic, expensive, or complicated.
Just something worth examining.
Because sometimes the most meaningful institutional improvement begins with one question, one conversation, and one decision to do something differently.
Today's question worth asking:
If your institution could make meaningful progress on just one operational challenge during the coming week, what would you choose—and what would the first practical step look like?