It's more about finding one person to give responsibility to (or who can delegate responsibility). Emailing a whole team means a whole team ignores the emails.
It isn't about blame, it's about finding one person (and only one person) who is likely to be able to fix the bug or at least know who to delegate the bug to. The workflow is around reducing signal to noise, so that if you get an email from Squash, it's something you need to take action on. Either fix the bug or find someone who can. That's why it always tries to find one person to give responsibility to.
The origins of Squash predate Errbit. In addition, Squash is laser-focused on solving a specific problem, the signal-to-noise ratio in dealing with exceptions. The idea is get the bugs assigned or fixed as soon as possible, and bother as few people as possible.
The emphasis is on finding someone who can either fix the problem or knows someone who can. The idea is that when you get an email from Squash, you should pay attention and respond immediately, rather than getting thousands of emails that you don't really care about.
