In 1993, Kenneth Cooper published a trilogy of papers identifying a mechanism he called the Rework Cycle: the tendency of projects to accumulate undiscovered errors while unwittingly reporting false progress.
Cooper’s work wasn’t academic theory. His modeling was critical to a $500M US Navy shipbuilding settlement, won by the contractor against the Navy. The Rework Cycle itself is codified in John Sterman’s Business Dynamics, the standard graduate text in system dynamics.
The core insight is simple: Work that looks done isn’t done. Errors compound silently. By the time the schedule officially slips, the real damage happened months ago.
Almost nobody in data product management has heard of the Rework Cycle.
I’ve spent the last several years applying Cooper’s framework not to explain project failure after the fact, but to drive stalled roadmaps to completion — unblocking platforms stuck in rework loops, stabilizing chaotic product lines, and delivering under timelines others declined. The pattern was consistent every time. Months of undiscovered rework compounding beneath the surface, invisible to every status report and standup in the organization.
The Rework Cycle didn’t just explain the failure. It showed where to intervene — and how to prevent the next crisis.
The Rework Cycle remains trapped in system dynamics journals, heavy construction conferences, and hyper-specialized consultancies advising mega projects in defense. It has near-zero penetration in the world where CTOs, CDOs, and PMs actually live: matrixed data organizations shipping products under PE timelines.
That gap is what this advisory practice exists to close.
I run an independent advisory for CTOs, CPOs, and CDOs at data and information services firms, built on translating Cooper’s Rework Cycle into the operational vocabulary of data product organizations.
You get a diagnostic framework your team doesn’t currently have — one that shows you where rework is accumulating right now, which decisions are compounding it, and what to change first. I don’t replace your team. I make their existing effort land.
This is a short, focused conversation to determine whether the Rework Cycle makes sense for where you are right now.
30 minutes. You’ll describe what’s stuck or slowing down. I’ll tell you whether the Rework Cycle applies to your situation and what an engagement would look like. No pitch, no follow-up sequence — just a direct read on whether this is worth pursuing.
Book a Free Discovery Call