You've defined yourself as a system with inputs, outputs, and a state. Now, let's introduce the concept that truly locks you into the digital grind: the feedback loop. A feedback loop occurs when the output of a system is fed back as an input, influencing the system's future behavior. It's a self-reinforcing cycle, and in the context of your notification addiction, it's a vicious one.
Think about it: A notification (input) triggers you to check your phone (output). Checking your phone exposes you to more content and potentially more notifications (new inputs), which further reinforces the behavior. Your output becomes the system's next input, creating a closed loop of engagement and distraction. Algorithms are masters of exploiting these loops, using your past behavior to predict and trigger future behavior, keeping you trapped in their engineered cycles.
Feedback loops can be positive (reinforcing growth or deviation) or negative (stabilizing and trying to maintain a setpoint). Your notification loop is often a positive feedback loop, driving increasing engagement. Understanding this cycle is crucial to recognizing how your own actions are used against you by the algorithms.
The visualization below illustrates a simplified feedback loop, showing how the output circles back to influence the input.
In a feedback loop, the output of a system, $y(t)$, is measured or sensed and then fed back, often modified, to influence the input, $u(t)$.
Mathematically, this means the input is not purely external but depends, at least in part, on the system's own output:
$u(t) = f(\text{external inputs}, y(t))$
The visualization shows the output arrow looping back to connect with the input side of the system.
The effect of the feedback determines if it's positive or negative:
Your digital feedback loops are often designed to be positive, driving continuous engagement and making it hard to break free.
In a typical feedback control system, there are additional components:
In the visualization, we include conceptual boxes for a Sensor and Controller in the feedback path. This is where you potentially fit in – can you act as a controller to break the loop?