Essay
I Am Jack's Anti-Jack
When organizations reward completed work without measuring whether anything improved, they become excellent at maintaining yesterday.
- work
- organizations
- software
- the ongoing administrative project of appearing
I am Jack’s anti-Jack.
Every organization eventually invents an anti-version of its stated purpose.
Agile becomes process.
DevOps becomes platform bureaucracy.
Observability becomes dashboards proving the dashboards are working.
AI becomes governance around prompts.
The anti-version of meaningful work is not completion.
Completion is necessary.
The anti-version is completion treated as meaning.
Completion is measurable
Meaning is not.
So organizations optimize for completion.
Move the ticket.
Merge the pull request.
Close the incident.
Attend the meeting.
Write the review.
Update the dashboard.
Every box receives its checkmark. Every graph trends in the expected direction. Every sprint is declared successful.
The machinery works.
Yet almost nobody asks the dangerous question:
Did we make anything that mattered?
Not:
Did we ship?
Did velocity increase?
Did compliance improve?
Did the sprint close on time?
Did everyone attend the ceremony?
Did we actually improve the system?
The distinction sounds philosophical until you spend your days inside it.
Then it becomes payroll.
The completed nothing
An engineer spends an afternoon investigating infrastructure.
He documents security improvements.
He identifies hidden failure modes.
He measures architectural risk.
He forecasts delivery problems.
He reduces future operational cost.
He designs a governance model before the absence of one becomes an incident.
Nothing changes.
The documents are archived.
The recommendations are acknowledged.
The sprint burns down.
The quarter proceeds exactly as before.
The engineer receives the same credit he would have received for waiting all afternoon for someone to review a pull request.
Completion succeeded.
Meaning failed.
The organization can see that the ticket moved.
It cannot see the future that was made slightly less stupid.
The safe contribution
Organizations teach this lesson every day.
The safest contribution is the requested one.
The most valuable contribution is often the unrequested one.
One advances the sprint.
The other advances the organization.
One has acceptance criteria.
The other begins with somebody noticing that the criteria are wrong.
One is easy to assign, estimate, track, demonstrate, and close.
The other may arrive as a prototype, an investigation, an architectural warning, an inconvenient document, or a question nobody authorized anyone to ask.
Only one is reliably measured.
So only one is reliably rewarded.
This is not because organizations hate improvement.
Organizations usually claim to love improvement.
They simply prefer improvement that has already been converted into approved work.
An idea becomes legitimate after it receives a ticket.
A risk becomes real after it becomes an incident.
A technical problem becomes important after management learns its name.
Before that, it is merely someone thinking beyond the workflow.
This can be interpreted as enthusiasm.
It can also be interpreted as insubordination.
The proxy becomes the purpose
This failure is older than Jira.
Charles Goodhart warned that a statistical relationship can break down once it is used for control.
Donald Campbell made the organizational version more explicit: the more a quantitative indicator is used for decision-making, the more pressure there is to corrupt the indicator and the process it was meant to observe.
A sprint metric begins as evidence about work.
Then it becomes the definition of work.
A dashboard begins as a window into the system.
Then the organization begins arranging the furniture for the window.
The numbers do not have to be false.
They can be completely accurate measurements of the wrong achievement.
The dashboard is not lying.
It is faithfully reporting the thing everyone was taught to optimize.
Rational surrender
Eventually intelligent people adapt.
They stop proposing.
They stop investigating.
They stop building tomorrow’s improvements because today’s workflow has no field for them.
They learn that noticing more creates more work.
They learn that preventing a problem produces less recognition than responding heroically after it occurs.
They learn that finishing a small assigned task is safer than questioning whether the task should exist.
Research gives this retreat a less dramatic name.
Completion-contingent and performance-contingent rewards can weaken intrinsic motivation. Research on organizational creativity has likewise treated intrinsic motivation and the surrounding work environment as central to whether creative ideas appear and survive.
People do not stop caring because a memo instructed them to stop.
They stop because the system repeatedly converts caring into unrecognized labor.
The work becomes smaller.
Not because the people became smaller.
Because the incentives did.
The organization does not need to order anyone to stop caring.
It merely needs to make caring professionally irrational.
The Anti-Jack Principle
This is the Anti-Jack Principle:
A system that perfectly rewards completion while ignoring meaning will eventually produce people who complete everything and create very little.
It is not a failure of effort.
The people may be working constantly.
It is not necessarily a failure of competence.
The people may be highly capable.
It is a failure of measurement.
The system sees motion and calls it progress.
It sees closure and calls it value.
It sees a full sprint and assumes something worthwhile must have happened.
Meaning refuses to cooperate.
Meaning does not fit neatly inside a Jira field.
Architecture does not always arrive attached to a story.
The best idea this quarter may have no product owner.
The improvement that saves a hundred engineer-hours next year may begin life as an inconvenient Markdown document nobody requested.
The failure prevented by a quiet afternoon of investigation will never appear on a dashboard.
Nothing happened.
That was the achievement.
Permission to think
Not every suggestion should be adopted.
Not every prototype deserves production.
Not every engineer with an idea has discovered the future.
The answer is not endless invention without responsibility.
The answer is preserving the ability to think beyond the next ticket.
Healthy organizations leave room for work whose value has not yet been translated into workflow.
They distinguish exploration from distraction.
They allow evidence to change the plan.
They recognize that the person closest to the system may notice something before the roadmap does.
They understand that meaning is not the enemy of completion.
Meaning is what completion is supposed to serve.
Completion keeps the lights on.
Meaning determines whether we are building anything worth lighting.
Confusing the two is how organizations slowly become excellent at maintaining yesterday.
I am Jack’s anti-Jack.
I completed every assigned task.
I attended every meeting.
I updated every ticket.
I improved nothing.
The dashboard is green.
Receipts
- Manifesto for Agile Software Development ↗ and Principles behind the Agile Manifesto ↗ — The original texts prioritize individuals and interactions, working software, motivated people, technical excellence, self-organizing teams, and the continuous delivery of valuable software. The process was supposed to serve the work, a detail later implementations have handled with characteristic restraint.
- Charles A. E. Goodhart, “Problems of Monetary Management: The U.K. Experience” ↗ — The source associated with Goodhart’s warning that statistical regularities tend to break down when pressure is placed on them for control purposes.
- Donald T. Campbell, “Assessing the Impact of Planned Social Change” ↗ — Campbell’s analysis of evaluation systems describes how heavy reliance on quantitative social indicators creates pressure that can distort both the indicator and the activity being measured.
- Edward L. Deci, Richard Koestner, and Richard M. Ryan, “A Meta-Analytic Review of Experiments Examining the Effects of Extrinsic Rewards on Intrinsic Motivation” ↗ — A meta-analysis of 128 studies found that several forms of expected tangible reward, including completion-contingent and performance-contingent rewards, significantly undermined free-choice intrinsic motivation.
- Teresa M. Amabile, “A Model of Creativity and Innovation in Organizations” ↗ — A foundational model connecting creativity and organizational innovation to domain skill, creativity-relevant processes, intrinsic motivation, and the surrounding work environment.
- Jason Pollard, professional portfolio ↗ — A first-person practitioner record centered on outcomes rather than adjectives: clarifying ambiguity, validating assumptions, reducing risk, improving systems, and documenting operational reality. This essay grows from that perspective, because apparently a man may serve as a primary source for his own colon.