Unless it's effecting your performance review or whatever, who cares, honestly? The obsession with efficiency and Taylorism is what's wrong with the current state of affairs in business.
Not saying people shouldn't want to be productive just that understanding delays and simply pyschologically dealing with them would go a long way in modern culture. Not everything needs to happen 5 minutes ago, is late, or is so critical it can't wait a few hours.
>Unless it's effecting your performance review or whatever, who cares, honestly? The obsession with efficiency and Taylorism is what's wrong with the current state of affairs in business.
being blocked on a task due to missing knowledge isn't really "efficient". Especially when someone can point you to the right place in the span of a single slack message line instead of spending hours wandering through legacy code and still missing the full scope of the change I want to make.
Sure, if it's a one-off bug fix task someone internal discovered, it can wait a day. But these kinds of issues when highlihgted are never because "it happened once" One is coincidence, twice is happenstance. thrice is probably a habit and you learn that certain people aren't a reliable resource in terms of, well, co-working.
It's not just about efficiency, it's about not hitting the brakes. When you've got momentum and you're in the flow, killing it is deeply unsatisfying, and I for one have a hard time getting it back. Obviously that doesn't justify bugging someone 10 times a day, but there's a balance to be found.
Not saying people shouldn't want to be productive just that understanding delays and simply pyschologically dealing with them would go a long way in modern culture. Not everything needs to happen 5 minutes ago, is late, or is so critical it can't wait a few hours.