I feel like this is a mixture of the aforementioned hammer and nail analogy along with incident scope obscurity. Helpdesk folks may be on a call with an end-user and are then unloaded upon with mixed signals. Maybe they're told that since problem A has occurred, issue B has arisen. And because they are being sensitive to the performance of their system, perhaps because their workflow was impacted by A and B, they throw in issue C. So now the helpdesk tech is looking at A, B, and C and due to this obscured view of the problem, the only commonality must be the profile, after all not everyone is reporting A, B, and C together so surely it's not the machine/image and is just something unique to this user's profile... OR they convince themselves A, B, and C must be related somehow... so they reach for the hammer that, based on their previous experience, seems to line-out multiple odd cascading issues, often with less callbacks. Could have simply used the pliers and addressed A; then B and C wouldn't have been an issue to the user. But of course the user needs it fixed like right now top priority. So to avoid a followup they give a quick smack, and then they're starting FRESH😅 But yes it's a dying art to even be able to use the pliers on problem A. Much less to recognize and stay scoped to problem A rather than make it into a bigger ABCDE problem that really isn't even the issue.