# Perceptual Inertia in Time-Scaled Efforts ## Current Form Related to ideas like diminishing marginal returns, temporal discounting, sunk cost fallacy, etc., I've been thinking about how the longer or larger-scale an effort, the less noticeable small changes become. Specifically, how we (and our peers) perceive effort in cumulative systems. If you ride a bike easily for 40 miles and decide to ride fast for 10, you'll *perceive* that it's relatively hard to move your average stats (pace/power/watts) in aggregate, and this has a net-negative feedback element without context. Similarly, if you start fast and maintain that intensity until ~40 miles remain you'll *perceive* a relatively slow decline in your average stats. The same sorts of things apply to group or workplace dynamics, where early and late-stage changes or efforts often feel respectively exaggerated or muted against the weight of accumulated time or precedent. Maybe there's some kind of **temporal endowment** where the time already invested makes people over or under value the current trajectory or status quo, based on the relative value of your net contributions over longer or larger-scale efforts? ### Spark Realized during a morning bike ride—riding 50 miles, and noticing how little a change in pace at mile 40 moves the overall average. It sparked a reflection on how effort is perceived in long-running projects or dynamics, and how that influences our behaviors in both the short and long term. ### Tensions or Unknowns - Is this primarily a cognitive bias, statistical reality, or both? - What frameworks already capture this? (e.g., marginal utility, law of averages, endowment effects?) - Does this effect motivate resignation, or can it be flipped into strategy? ### Next Evolution - Identify related concepts and research (behavioral economics, time perception, feedback loops) - Draw connections to workplace momentum and narrative shaping - Consider if this can inform better feedback mechanisms or change management strategies ### Wayfinding %% DATAVIEW_PUBLISHER: start ```dataview TABLE WITHOUT ID questions AS "Responds to", origins AS "Informed by" ideas AS "Developed alongside", concepts AS "Builds on", WHERE file.name = this.file.name ``` %% %% DATAVIEW_PUBLISHER: end %% >[!info]- Changelog >- [[2025-06-20-Friday]]: Seed idea captured from bike ride reflection.