Tribes

Earlier Laura talked about a communication gap between ESPs and ISPs.
My take on it is that it’s something more than just a difficulty in communicating, rather it’s a division due to differences in personality and approach of those individuals whose primary interest is themselves and those whose primary interest is the health of the overall email ecosystem.
The former group (who I mentally refer to using the shorthand “frat boys“) want to make everything all about them, and their companies revenue, and their visibility in the industry, and their ego resume. Broad generalizations with little need for understanding are adequate to raise their visibility and keep them employed. Details aren’t that important to them. Dominating the conversation is. (Lest that sound negative, these are exactly the individuals who can thrive in sales, customer relations, bizdev and marketing environments.)
The latter (shorthand “utilitarians“) instinctively want to make email work well and to be useful for everyone. They want email to be a healthy, useful system and tend to believe that that means optimizing for the greatest good for the greatest number. (If you’ve any philosophy background, think “felicific calculus as applied to email”). They tend to understand the system in much more detail than the frat boys, though maybe less than the mechanics. And they tend to be better at working together – as they’re more interested in hearing other peoples data in order to get better at what they do, rather than being there to convince others of their pre-decided agenda.
(There’s a third group I think of as “mechanics” who take more joy in the details of keeping the system running smoothly on a small scale, without much interest in the broader system, whether that be in a technical or business role. They tend not to be very interactive in public, though, so don’t have much impact at the level of conversations I’m thinking about).
While I hate the broad terms “senders” and “receivers” used to (falsely) divide the industry into two disjoint halves, I’m painting with a fairly broad brush here, so I’m going to stick with them.
There are quite a few of all three types of people at both senders and receivers – but their power and visibility varies.
At senders there’s a mix of frat boys and utilitarians in operational and policy making positions, but the frat boys tend to have a lot more public visibility – they’re the ones who are trying to be visible, to dominate the conversation, and they’re the people you tend to see doing all the talking and less of the listening, whether it be on industry mailing lists or at the microphone at a conference. Because of their greater visibility, they’re who you think of when you think of senders, and typically they’ll be the ones you end up interacting with most in any random mix of individuals from senders.
At receivers the  operational (as opposed to policy) level is where the real decision making power is as far as email is concerned, and it’s heavily dominated by the utilitarians. (In fact, the more visible frat boys I can think of who were in influential positions at receivers are mostly now working on behalf of senders).
Frat boys are very, very bad at communicating with utilitarians. And utilitarians find it very hard to discuss issues they consider serious with frat boys at anything deeper than a superficial level.
Mechanics aren’t great at communicating with strangers in anything other than a fairly friendly environment, but manage best with other mechanics or with utilitarians.
If you’re a C level manager at a sender, and you’re deciding which of your staff are well suited to collaborate with typical receiver staff that’s something important to consider. The public face of the recievers are probably utilitarians. Frat boys are the worst representatives to send out to talk to them.

Related Posts

Legitimate email marketers need to take a stand

I was reading an article on Virus Rants and the opening paragraph really stood out.

Read More

Problems at Cox: Resolved

People mailing to Cox in the wee hours of this morning may have received a rejection message citing the Invaluement DNSBL.
554 IMP a.b.c.d blocked.  IPBL100 – Refer to Error Codes section at http://postmaster.cox.net for more information.
I spoke with one of the folks at Cox and they said there was an error in the implementation causing non-listed IPs to be rejected erroneously between about 4am to 8am (Eastern) this morning.  The problem has been resolved as of 8am, and all traffic is flowing  normally.  The also stated that attempts to resend any blocked messages will succeed. They do apologize for any problems this may have caused.
For those of you with aggressive bounce handling, removing addresses after a single 550 bounce, you will also want to re-enable any cox.net subscribers that bounced off during this configuration problem.

Read More

Deliverability versus delivery

Deliverability is a term so many people use every day, but what do we really mean when we use it? Is there an accepted definition of deliverability? Is the concept different than delivery?
At a recent conference I was running a session talking about email delivery, senders and the roles senders play in the email industry and at that particular organization. The discussion went on for a while, and the subject of deliverability versus delivery came up. J.D. Falk had a comment about the difference that resonated with me. Paraphrased, he said:

Read More