Table of Contents

Definition

The move that asks whether the thing being repaired belongs at all, and builds something new instead of restoring something old. Exiting the frame the problem lives in — not solving the problem inside its current frame, and not solving the upstream cause inside the current frame, but dissolving the problem by stepping outside the category that contains it. Four-move frame-exit mechanism: recognize the frame, question the frame, imagine without it, build toward the new frame. Distinct from upstream-cause work, which fixes the cause while staying inside the existing frame. Failure mode: stopping at upstream-cause work and calling it innovation, or treating any problem as too small for this work — a rationalization that produces the repairman identity.

Explanation

The broken-plate example in the source material makes the frame-exit distinction concrete. Upstream-cause work asks why plates keep breaking and fixes the rack-stack — a real improvement, but one that stays entirely inside the assumption that plates are the correct delivery vehicle. [Innovation Work] asks a different question entirely: do plates need to exist in this operation at all, and what would delivery look like without them.

The failure mode named at the end is worth taking seriously, because it identifies exactly how an operator can believe they’re doing this work while actually just doing upstream-cause work with better branding. Calling a rack-stack fix “innovative” doesn’t make it frame-exiting — real [Innovation Work] requires actually stepping outside the category, not just improving execution within it. This is the direct antidote to [Repairman Conundrum]: an operator who only ever fixes causes inside existing frames is permanently building the repairman identity, no matter how skillfully they fix things, while an operator willing to question the frame itself has a path out.