At Opendoor, there’s a healthy default towards transparency. While we are a Slack-heavy company, we still use email a good amount --especially for communicating with external parties. However, email and transparency aren’t something that go hand-in-hand, unless you’re Stripe I II.
Luckily, BCC can be used to build openness and keeping relevant internal parties in the loop when emailing external parties. I never really used to BCC or get BCC’d until I worked here but now it's become indispensable. That being said, getting BCC’d or BCC’ing somebody has also become one of my biggest fears.
Every once in a while my fear comes true...Case below: I BCC'd "C" but they ended up replying-all!
Email clients should build BCC Protection that would reduce the chances of ending up in one of the above scenarios in two steps:
We’ve already gotten used to this when the word attachment is mentioned but there’s no attachments on the email…this would be a nice addition to that.
Note: I would usually send this note to my good friends at Polymail but I’m actively attempting to give them a break from my ramblings