3 ms·
That assumes that they know you're the person to contact. In several cases I know how to do something, but it's not totally clear to my coworkers that I do and
by geofft 11y ago
That assumes that they know you're the person to contact. In several cases I know how to do something, but it's not totally clear to my coworkers that I do and it's appropriate to contact me. Or, more commonly -- I know someone on the team knows how to make a system work, but I don't know who. (I don't think you need to poll more frequently than every 30 minutes to make this work well enough, so you can do Pomodoro-length blocks without checking every ten seconds if someone else needs you.)
The other thing about this model is it encourages things to be personally-directed disruptions. In a healthy, non-tiny engineering organization, there are important parts of the system where multiple people understand the subtleties (to avoid SPOF) but not everyone understands the subtleties (because they don't need it). Multiple pings will bother everyone for no good reason, when only one of them needed to be bothered. But to avoid that, you have to ensure that a broadcast query will probabalistically be answered by one person who knows the answer.
- manigandham 11y agoThis isn't a problem. A company big enough where someone doesn't know who handles what will already have a good chance of someone seeing the message. Direct pings for immediate responses, otherwise a reply within an hour or two is just fine. Or if that really doesn't work, I'm sure the first incorrect direct ping will redirect to the right person right after, it's not like you need to annoy everyone in a massive blast. And big companies will generally have managers, assistants and others who are more flexible and can deal with this very well as general routers of communications.