Does a quick interruption that unblocks me and allows me to continue working outweigh allowing you to finish your thing first? Because maybe you're unblocked but I'm blocked by you now, and the thing that's actually blocking me. So only 1 person is able to work.
Understandably this can lead to a lot of context switching, but so can someone swiveling in a chair to ask a question or go down a rabbit hole. You can optimize the process a bit by shifting perspective and having a path to follow if you get blocked, rather than lamenting on how you're blocked(not you in particular, but people in general).
*I feel like it is somewhat rare that a person only ever has 1 specific thing to work on.
No, absolutely not. As my coworker you have no right to my time, at all. Certainly not on-demand.
You are in no position to prioritize my time, especially in the context of you finishing your task.
> Because maybe you're unblocked but I'm blocked by you now, and the thing that's actually blocking me.
No, you are blocked by whatever you are blocked by. Solving your problems is your problem. Not mine.
> So only 1 person is able to work.
If you can't do your job without also consuming my time in parallel what exactly are you contributing? If you are blocked and need input then go work on something else until you can get the input. This is elementary time management and respect for your coworkers.
What you say sounds pretty selfish though. If someone came to me and asked for help with something I'd be happy to drop tools and come and help as I'm not just a 'colleague', I'm a team member.
If you need clarification then send an email, add a comment in your issue tracker or set up a meeting. There's no reason to interrupt someone doing productive work to get clarification on a story. You should be able to manage parallel stories and make progress as you get clarification.
Yes, all of those things are true and I do all of those things. I am speaking specifically about interrupting a coworker who is doing productive work.
> "siloed," "completely independent," and "unanswerable to anyone."
I didn't say anything about this. Respecting your coworkers time does not require any of it.
What part of this statement says 'team player' to you?
The whole part about working as a team-player is that solving their problems is your problem, because it is the teams problem.
What you are describing is being assigned a list of stuff and working on it independently, then not helping anyone else unless it's convenient for you. This is colloquially called 'not being a team player'.
The part where each member of the team is trusted with their own time management. I will also not interrupt you when you are working, because I respect you and your time.
> The whole part about working as a team-player is that solving their problems is your problem, because it is the teams problem.
Yeah, no. The team has problems so we divide the work. Each of us takes ownership for some small part of it. Asking for input from teammates is fine, that is the responsibility of that owner. But that doesn't mean they can interrupt someone to get it. To be an effective teammate you need to earn the respect of your peers and interrupting will undermine that trust long term. Obviously I want my coworkers to solve their problems because we all work toward a common goal and of course I provide input to help them do that.
You must be very good at your specific tasks because it sounds like you are not very good at your job (which includes "teamwork," "mentoring," and "problem solving"), at least if you behave the way you're saying you behave.
I have never ever gone into a team environment and felt the need to earn respect from my teammates or have them earn mine. This is a glass half full or empty thing. You can go into a team and require others prove themselves and vice-versa or you can give people the benefit of the doubt and let them lose the trust if something happens. Both lead to vastly different experiences.
Just because I ask you in person for help from time to time does not equate to me not contributing anything.
Just because someone asks you for help in person does not mean you can't say 'no, can you try me at this time or send me an email detailing the issue'.
Solving problems can be a siloed experience, but depending on the organization or team, most problems in today's businesses are team efforts, and require team collaboration. Having blinders with comments like 'solving your problems is your problem' is a great way to overlook when a problem someone is having is actually YOUR problem because you overlooked a bit of code or configuration or documentation.
That's not what I said. My comment was about working in parallel and demanding immediate coworker input to advance.
> Just because someone asks you for help in person does not mean you can't say 'no, can you try me at this time or send me an email detailing the issue'.
The situation is not asking for help in person, it is interrupting to ask for help.
> Solving problems can be a siloed experience, but depending on the organization or team, most problems in today's businesses are team efforts, and require team collaboration. Having blinders with comments like 'solving your problems is your problem' is a great way to overlook when a problem someone is having is actually YOUR problem because you overlooked a bit of code or configuration or documentation.
I never said anything about working in silos. We still have a daily standup, we still do sprint planning, we still to regular operations reviews. I take ownership for my own actions and deliverables and help coworkers. This is simply a matter of how to request that assistance and the expectations around when that is provided.
Asking for help in person is literally interrupting someone, no matter what they are doing because their attention has to be re-directed from whatever they were doing to you. So there is no meaningful difference between asking for help and interrupting to ask for help. But through social cues I can tell what level of concentration you might be on, and with some precision judge when a good time might be to check in. Hell, I will definitely be wrong some of the time, but that's just life.
The situation is obviously different for someone that is always co-dependent on others for getting work done.
No, solving the company's problems is both our problems. You have a tremendously adversarial attitude toward your coworkers. Why don't you trust them to know the cost of interrupting you and decide whether or not it's a net gain?
Yes, this requires effective collaboration.
> You have a tremendously adversarial attitude toward your coworkers.
I do not have an adversarial attitude toward my coworkers. In fact I am very well liked by the people I work with. Probably because I treat them with respect.
> Why don't you trust them to know the cost of interrupting you and decide whether or not it's a net gain?
How can they possibly know this? That would require everyone on the team having complete knowledge of what everyone else is doing at all times. Further, if you believe you know more than your coworker about their situation then it speaks to a distrust of their abilities.
Asking "hey you got a minute?" is a waste of everyone's time because either the answer is "yes" and you could have asked your question already or the answer is "no" and you just disrupted someone who was doing productive work and still doesn't know if your actual question is worth answering right now. Just ask your question and I will answer it when I have time. This is why it is better to ask in email, IM or a meeting, depending on the nature of the question.
Like I said, everything you're writing speaks to you.
In the office respect for the headphone signal is not universal. Also, sometimes I don't want to wear headphones just to signal I am in flow. Nor do I want to have to use them drown out all the other distractions. People are still walking around and doing things, all are potential distractions.
In the first case, it does seem a lot more reasonable to interrupt and trade-off the productivity of the blocker in favor of the blockee. At worst, that's an even trade and at best it incentivizes not being a blocker.
In the second case, I'd rather not create a distributed denial of concentration scenario for SWEs who are rarely stuck to optimize for those who are more frequently stuck.
There's another angle here which is that ad-hoc in-person conversations tend to be low value because there's no record. The process of simply writing down a question before asking it goes a long way toward finding a solution.
It's one of the things I really appreciate about working from home. There are no unwelcome interruptions because everyone controls their own time and interactions I do have are higher value because they have been more thoroughly considered.
I can skim the first few words of a Slack message without losing context and if those first few words demand an immediate response, I can "save" what I am doing to my notes.
I had a co-worker who did this in a past job, even though he sat behind me. It was quite helpful.
Absolutely.