Followup to: Ask and Guess
Ask culture: "I'll be in town this weekend for a business trip. Is it cool if I crash at your place?" Response: “Yes“ or “no”.
Guess culture: "Hey, great news! I'll be in town this weekend for a business trip!" Response: Infer that they might be telling you this because they want something from you, conclude that they might want a place to stay, and offer your hospitality only if you want to. Otherwise, pretend you didn’t infer that.
The two basic rules of Ask Culture: 1) Ask when you want something. 2) Interpret things as requests and feel free to say "no".
The two basic rules of Guess Culture: 1) Ask for things if, and *only* if, you're confident the person will say "yes". 2) Interpret requests as expectations of "yes", and, when possible, avoid saying "no".
Both approaches come with costs and benefits. In the end, I feel pretty strongly that Ask is superior.
But these are not the only two possibilities!
"I'll be in town this weekend for a business trip. I would like to stay at your place, since it would save me the cost of a hotel, plus I would enjoy seeing you and expect we’d have some fun. I'm looking for other options, though, and would rather stay elsewhere than inconvenience you." Response: “I think I need some space this weekend. But I’d love to get a beer or something while you’re in town!” or “You should totally stay with me. I’m looking forward to it.”
There is a third alternative, and I think it's probably what rationalist communities ought to strive for. I call it "Tell Culture".
The two basic rules of Tell Culture: 1) Tell the other person what's going on in your own mind whenever you suspect you'd both benefit from them knowing. (Do NOT assume others will accurately model your mind without your help, or that it will even occur to them to ask you questions to eliminate their ignorance.) 2) Interpret things people tell you as attempts to create common knowledge for shared benefit, rather than as requests or as presumptions of compliance.
Suppose you’re in a conversation that you’re finding aversive, and you can’t figure out why. Your goal is to procure a rain check.
- Guess: *You see this annoyed body language? Huh? Look at it! If you don’t stop talking soon I swear I’ll start tapping my foot.* (Or, possibly, tell a little lie to excuse yourself. “Oh, look at the time…”)
- Ask: “Can we talk about this another time?”
- Tell: "I'm beginning to find this conversation aversive, and I'm not sure why. I propose we hold off until I've figured that out."
Here are more examples from my own life:
- "I didn't sleep well last night and am feeling frazzled and irritable today. I apologize if I snap at you during this meeting. It isn’t personal."
- "I just realized this interaction will be far more productive if my brain has food. I think we should head toward the kitchen."
- "It would be awfully convenient networking for me to stick around for a bit after our meeting to talk with you and [the next person you're meeting with]. But on a scale of one to ten, it's only about 3 useful to me. If you'd rate the loss of utility for you as two or higher, then I have a strong preference for not sticking around."
The burden of honesty is even greater in Tell culture than in Ask culture. To a Guess culture person, I imagine much of the above sounds passive aggressive or manipulative, much worse than the rude bluntness of mere Ask. It’s because Guess people aren’t expecting relentless truth-telling, which is exactly what’s necessary here.
If you’re occasionally dishonest and tell people you want things you don't actually care about--like their comfort or convenience--they’ll learn not to trust you, and the inherent freedom of the system will be lost. They’ll learn that you only pretend to care about them to take advantage of their reciprocity instincts, when in fact you’ll count them as having defected if they respond by stating a preference for protecting their own interests.
Tell culture is cooperation with open source codes.
This kind of trust does not develop overnight. Here is the most useful Tell tactic I know of for developing that trust with a native Ask or Guess. It’s saved me sooooo much time and trouble, and I wish I’d thought of it earlier.
"I'm not asking because I expect you to say ‘yes’. I'm asking because I'm having trouble imagining the inside of your head, and I want to understand better. You are completely free to say ‘no’, or to tell me what you’re thinking right now, and I promise it will be fine." It is amazing how often people quickly stop looking shifty and say 'no' after this, or better yet begin to discuss further details.
My family has a guess-culture ("you must not love me enough if you don't notice that I'm too busy to for what you request!") I'm guessy about things by instinct.. but don't like being guessy about receiving requests - it feels manipulative to place the burden of my feeling offended on the person asking. From the perspective of receiving requests, I've started trying hard to play by Crocker's Rules (to the usual mixed success).
In making requests - I prefer to be telly and have tried to incorporate that into my life. But what I notice is that other people sometimes don't realise you're making a request - or get caught up in the long explanation and miss the "call to action" - so an actual ask is often useful even with the telling.
So I'd have phrased it as: "I'll be in town this weekend for a business trip. I would like to stay at your place, since it would save me the cost of a hotel, plus I would enjoy seeing you and expect we’d have some fun. I'm looking for other options, though, and would rather stay elsewhere than inconvenience you. So, is staying with you ok?"
Remember - sometimes the "telling" is even longer than this short phrase...repeating the question at the end helps people with weaker short-term memory.
Also I have started to lead groups of mixed ask/guess-culture people... and asking for things from people of multiple cultures (without offending any of them accidentally) is a skill I'm just starting to have to figure out.
I am well aware of the negative feelings of burdening somebody (presumably of guess-culture) with a request that they really don't have the time/inclination to fulfil - but they feel obliged to say yes to when i ask. So I'm working on ways of minimising that situation.
I have tried pure-telling - but given it doesn't have an explicit question in it, my experience so far is that too many people will not realise there is actually a call-to-action there or that it means YOU. This is especially in the case where it takes a page of explanation to get across what's going on and why they need to care about it. The request easily gets lost in that.
So I've instead been trying my hand at new skills of asking-without-offending. My favourite request-structure so far being:
"These are all the reasons and background about why I'm making this request... Will you X? It's absolutely ok to say no."
It incorporates aspects of all three cultures: You tell exactly why, so that guessers aren't inferring incorrect assumptions based on your implied motivations. You are explicitly asking. You are giving them an explicit get-out-of-request-free card by giving explicit permission to say no.