Except for the first, none of these teams set out to “do Aufhebung”. We read their solutions through the four questions because they show the shape clearly. Each example follows the order of those questions: what ended, what was kept, what lifted both.
Film
Montage: a third meaning from two shots
Where does a film’s meaning live: in each shot the camera records, or in the order the editor builds?
- Move past
- the idea that a shot carries its meaning alone.
- Keep
- both shots, untouched; nothing inside them changes.
- Lift
- side by side they produce a third meaning, such as hunger, that neither shot contains.
Lev Kuleshov showed this around 1920: the same blank face of an actor, cut next to a bowl of soup, a coffin or a woman on a sofa, was read as hunger, grief or desire. Sergei Eisenstein then built his theory of montage explicitly on this line of thought: for him a cut is a collision of two shots, and from the collision a new concept arises. Limit: Kuleshov’s original footage is lost and modern repeats of the experiment give mixed results; editors rely on the editing principle, not on the exact experiment.
Pricing
Versions: let the buyer choose the price
A low price brings many buyers; a high price brings margin. One price cannot do both.
- Move past
- one price for everyone.
- Keep
- the low entry price and the high-margin offer, side by side.
- Lift
- tiers let each buyer pick their own level, so the price list itself sorts customers by what they value. No single price can do that.
Carl Shapiro and Hal Varian described this as versioning in 1998; it is why so much software sells as Basic, Pro and Business. Limit: badly designed tiers turn back into a compromise, with every tier a little too expensive for the people it is meant for.
Manufacturing
Toyota: stop the line so it stops less
Keep the line moving to hit output, or stop it to fix defects?
- Move past
- the belief that every stop is a loss.
- Keep
- high output, and no defects passed down the line.
- Lift
- any worker can stop the line at a problem; the cause is fixed where it starts, so over time the line stops less and quality rises with output.
This is the jidoka principle and the andon cord of the Toyota Production System, described by Taiichi Ohno. Limit: it works only when a stop is followed by real root-cause fixing; without that, a stop cord is just a slower line.
Product
iPhone: a keyboard that appears when needed
In 2006 phones chose between a physical keyboard for typing and a large screen for viewing.
- Move past
- fixed plastic keys that sit there whether you need them or not.
- Keep
- typing, and a full screen.
- Lift
- a keyboard drawn in software: it shows up only when you type and changes with the app and the language.
Steve Jobs set out the clash himself when he introduced the iPhone in January 2007. Limit: something was lost too, the feel of physical keys, and some users missed it for years. A real Aufhebung can still have a cost; the question is whether the gain is greater.
Software
Speed and stability together
Ship fast, or keep systems stable? For years teams treated this as a trade-off.
- Move past
- big, rare, risky releases.
- Keep
- speed and stability, both.
- Lift
- small, frequent, automated releases. Each change is small enough to check and undo, so going faster also makes the system safer.
Several years of survey research by the DORA team, published as Accelerate (2018), found that the strongest teams lead on speed and stability at the same time. Limit: the research is survey-based and shows an association across many companies; it does not prove that any one team will gain by copying the practices.