I call this the Distraction Stack.

[working on code]

"Hey, can you look at this bug?"

[
working on code,
looking at bug
]

"Can I bother you for a second?"

[
working on code,
looking at bug,
being bothered
]

"When you're done with her can you stop by my desk?"

[
working on code,
looking at bug,
stopping by your stupid desk
being bothered
]

It's enough to make me pop.

Lol. Though mine would be multidimensional, as I'm usually juggling several, unrelated tickets

At work we're experimenting with posting at the start of the day what we plan to do and posting at the end of the day what we actually did. Maybe surprisingly to some, we aren't doing this to soothe the micromanagers but rather to show them how much these little interruptions can disrupt an entire day when added up. If the client wants to pull me off priority 1 task to work on priority flaming hot cheetos task then fine but they need to understand that this means that "priority one" task is going to come at a slower velocity, especially if they come up with several new tasks like that each day.

I snooze notifications when working focused

@HollowKitty
Velocity?! Phisics professors are TRIGGERED.
As a very bad phisics guy i suggest you to use speed instead of velocity to sadisfy pedantic people like me.

(that was particaly a joke)

@HollowKitty I love this. I just might start using it.

@Gregozor2121 why not use velocity if the direction is known

.

@HollowKitty that's an incredibly great idea!

@Gregozor2121 velocity is the correct term, because you can still be working hard, crushing tickets, etc, but fundamentally not moving as close to your end goal as you'd like.

It's a good way to visualise the cost of technical debt

@bezorp I like this.

Project difficulty is measured "as the crow flies," but technical debt raises the terrain from flat towards increasingly mountainous. Distractions are detours / side trails that exit at least half a mile behind you.