Rework Is a Design Signal, Not a Performance Problem
By Andrew M. Vasquez, M.P.A., PMP
Founder & Principal Consultant, AMV Consulting
Leadership. Enrollment. Student Success.
In higher education, stalled initiatives are often explained the same way.
Not enough follow-through.
Not enough urgency.
Not enough buy-in.
The assumption is behavioral.
The solution becomes motivational.
Push harder.
Remind more often.
Increase visibility.
Add meetings.
But rework rarely originates in effort.
It originates in design.
Rework feels normal
Across institutions, rework is routine.
Policies are revised repeatedly.
Templates are rebuilt midstream.
Communication clarifications follow initial announcements.
Programs relaunch with “minor adjustments” that are not minor.
Committees revisit decisions that were never fully operationalized.
This cycle becomes institutional muscle memory.
People expect instability.
They hedge their commitment.
They wait to see whether something will stick before investing deeply.
Over time, momentum slows before work even begins.
Rework feels normal.
But normal does not mean optimal.
Ambiguity multiplies downstream
When scope is unclear at the start, every downstream conversation becomes interpretive.
People ask:
“Is this what we meant?”
“Who has final approval?”
“Are we aligned on what success looks like?”
“Is this version final?”
These questions consume time and energy.
They are rarely malicious.
They are rarely political.
They are usually attempts to compensate for ambiguity that should have been resolved earlier.
High-performing professionals will absorb that ambiguity for a while.
They will translate intent.
They will clarify expectations.
They will smooth confusion.
But no individual can permanently compensate for unclear structure.
Ambiguity multiplies downstream.
And multiplication compounds.
Competence cannot fix structural gaps
Talented teams can tolerate friction.
They cannot eliminate it.
When deliverables lack defined success criteria, revision is inevitable.
When stakeholder alignment is assumed instead of secured, friction emerges.
When ownership is diffused, accountability blurs.
When dependencies are unsequenced, timelines slide.
These are structural issues.
Not motivational ones.
When rework is framed as a performance problem, institutions misdiagnose the source.
They apply pressure where clarity is required.
And pressure without clarity increases strain.
Rework is expensive in invisible ways
The cost of rework is rarely captured in budgets.
But it is absorbed in other forms.
It increases emotional labor.
It reduces trust in timelines.
It normalizes skepticism.
It erodes willingness to fully commit to the next initiative.
Staff begin hedging.
They delay full investment.
They keep backup plans.
They temper enthusiasm.
Because experience has taught them that things will change again.
Students feel this too.
When processes shift midstream or information changes repeatedly, confidence weakens.
Not dramatically.
Quietly.
Rework does not just cost time.
It costs credibility.
Design is prevention
Reducing rework does not require stricter personalities.
It requires earlier clarity.
Define success before work begins.
Align stakeholders before public launch.
Sequence dependencies before announcing timelines.
Clarify ownership before assigning tasks.
Identify reinforcement mechanisms before declaring change complete.
These are not bureaucratic burdens.
They are protective mechanisms.
They protect energy.
They protect morale.
They protect institutional memory.
They protect trust.
Most importantly, they protect momentum.
Iteration versus instability
Not all rework is negative.
Iteration is necessary in complex environments.
Learning requires adjustment.
But iteration is different from instability.
Iteration is informed.
Instability is reactive.
Iteration builds toward clarity.
Instability revisits clarity that was never defined.
The difference lies in intentional design.
When scope, ownership, sequencing, and reinforcement are explicit, iteration becomes refinement.
When they are absent, rework becomes repair.
Higher education does not need fewer ambitious initiatives.
It needs stronger execution architecture.
Rework is not a failure of people.
It is a signal about systems.
Signals are invitations.
They invite leaders to look upstream.
To ask:
Was success defined clearly?
Were stakeholders aligned early?
Were dependencies sequenced intentionally?
Was ownership explicit?
If the answer is unclear, rework is predictable.
Institutions that scale effectively are not those that avoid mistakes.
They are those that design work clearly enough that mistakes do not multiply.
Design is leadership.
Execution is where leadership becomes durable.
Let’s build momentum together.
