Order degradations by impact on task completion
Aliases: cut order · task completion · progressive cut · nonessential effects
What it is
Things you can turn off contribute unequally to finishing the task. Shadows, blur, decorative images, autoplay, and entrance motion can go first; search, submit, pay, and reading the critical passage cannot. Order degradations by "after this is gone, can the main task still be finished", not by "which line is easiest to delete" or "which animation costs the most GPU". Animation is one item on the candidate list, not the list.
This is cut order — not which signal decides whether to cut, and not whether function entries remain after the cut. Reachability demands that functions stay; order decides which presentation moves first.
Why it happens
Task completion is a path: find the object, understand it, act, get a result. Nodes on the path (search, primary button, form, result) drop completion to zero if they are removed or slowed past use. Decoration off the path (blurred backgrounds, parallax, autoplaying hero video, hover-zoom on every card) mostly spends paint and bandwidth; remove them and the path still runs, completion barely moves. Cut off-path first so remaining budget can sit on path nodes when the budget is short.
Sort by implementation cost and developers delete what is easy: maybe one box-shadow, maybe they also turn off list virtualisation because it looks like an "optimisation to drop", and the list janks more on the low end. Sort by GPU and animation goes first, while an uncompressed hero image stays — bandwidth kills first paint, and the task still cannot finish. Order has to be inferred from the task: list the main path, tag each item as path node or decoration, cut decoration high-cost first, and only at more extreme tiers reduce density on nodes, without deleting entries.
Where it stops holding
Media products whose task is browsing and immersion may have video and motion as path nodes, not decoration to cut first; then adjacent recommendations, comment motion, and super-resolution go first. When accessibility users request reduced motion, motion becomes "this can make me ill", not decoration, and should turn off on that declaration without going through a performance sort. Offline or about-to-drop networks raise the priority of bandwidth items (images, video) so they can be cut before shadows. If an A/B shows "this decoration actually helps completion" (image quality affecting add-to-cart), retag it as path rather than insisting "pictures are decoration". Order is a function of the product task; a settings page and a checkout must not share one sitewide ladder.
Applying it
- Write the surface's main task path and tag every item as path node or decoration. Rank decorations by runtime cost into a degrade ladder: autoplay → blur/shadow → extra images → inessential motion.
- Path nodes stay off the first rungs. Only at lower tiers reduce density (list page size, image resolution). Do not delete search, submit, or pay.
- Do not sort by "easy to delete" or "animation is the most visible".
- How to check: under CPU and network limits, turn rungs off one by one and complete the main task at each. The rung where the task starts failing cut a node and should move later. Confirm that early rungs, cutting decoration, make completion faster, not slower.