Incident File for App Icon Relocation
Moving a distracting application off the home screen does not remove it from the user's attention budget.
Incident summary: a user moved a distracting application from the primary home screen to a secondary page, then to a folder, then to a folder on a secondary page. The application is now four taps from the surface. The user opened it eleven times yesterday through search.
This is an incident file for app icon relocation.
The initiating observation requires no interpretation. Someone moves a distracting app off the home screen but continues finding it through search. The app was not deleted. It was not disabled. It was made less immediately available, which accomplished the organizational goal of a less cluttered surface without addressing the behavioral goal of using it less.
App icon relocation steals one extra check of the screen. The check converts a passive visibility (the icon was there, idle, generating no particular pull) into an active retrieval (the icon must be found, and finding it requires engaging with the phone). The check becomes habitual even after alerts are muted, because the habit formed before the muting, and muting alerts does not modify behavior that predates the alerts. Attention management turns into another inbox, one that must be processed separately from the applications it was designed to manage.
The contradiction is familiar. The alert is called noise while ignoring it creates more attention. Moving the app produces a small, clean victory in the morning when the home screen looks organized. By afternoon, the search bar has routed around the organization seventeen times.
Under the governing rule, app icon relocation becomes procedure once repetition feels safer than reconsidering it. The procedure is: move the app, feel resolved, search for it later. The resolution and the search are the same event spread across the day.
Incident status: recurring.