Hacker News new | past | comments | ask | show | jobs | submit login

Leaders Eat Last was one of the best books I read this year. Extreme Ownership was also quite good but Simon really explains the “Why” of leadership that most books are missing. High-Output Management is another classic.



I understand the “why” of leadership very well, but as a high-functioning autistic person, I struggle very much with the “how”, especially around communication.

Like - for all possible values of X, if X is what I want someone to do, how do I communicate that so people (a) understand that I want X from them and (b) aren’t offended and understand that it is meant kindly/charitably (which it really is, I often just don’t know how to say so without sounding weird or changing the value of X).

Here’s a small example scenario from home life: my son was crying in his room. I was in the middle of something but wanted to take care of him and let my wife rest. She got up and started down the hall. I said “I was going to get it” expecting her to say “OK” and come back. Instead she sighed and did it anyway, and later said she felt frustrated that I made an excuse instead of either taking action or not. I explained to her what I wanted and asked what I should have said instead, and she said to say “Please stop. I’ve got this.” Next time I said that instead, and was amazed how different her response was - she was happy/grateful to let me take cars of it.

I guess I need a book full of “scripts” that would help me communicate both text and subtext accurately. Any resource suggestions?


This is not a book full of "scripts," but will hopefully help inform future actions:

The "Please stop. I've got this." is an action-oriented message that is conveyed before the action. It says "I would like for you to do X because of Y." It is conveyed in an imperative structure, which is used for a command or a request. "Please stop." <- request. "I've got this." <- followed by a rationale for your request. The request is conveyed first, followed by the rationale for why you are making it. "Do this. Here is why." The "I've got this" also carries succinct subtext of "I agree with you that our son crying is a problem that someone should take care of, I just think it should be me instead of you."

Conversely, when you say "I was going to get it," it is a declarative message rather than an imperative message. It does not tell your wife what you would like for her to do. It is merely additional data that does not help her make better decisions, which means it is mostly useless for her. An extreme comparative example is looking at a person who has just burned their hand at the stove and then saying "that stove appears hot."

Humans don't like to receive an array of "reasons" data before they've received the "request." We don't like statements in the form of "because of Y, Z, A, B, C... please do X." Our subconscious can typically detect that we are receiving a stream of "reasons" and we are starting to brace for the "request" (because the request might be unpleasant).

People like to know what others expect of them. Your comment says you would like to know what your wife expects of you. When you follow the <command> <rationale for command> order of operations you are giving people what they want (what you expect of them) followed by your reason for wanting that. When you go in the opposite order, you are conveying the converse: "I want something of you but I haven't told you what it is yet."


This is probably some of the most helpful advice I've ever received. I think it will be challenging (and scary) to learn to use imperative requests instead of declarative statements. Thank you so much for helping me understand and speaking my language!


Thank you. I'm sorry I can only upvote this once.


I feel you. I think you'd like Good Authority. Very concrete and actionable on all kinds of management practice:

https://www.amazon.com/Good-Authority-Become-Leader-Waiting/...

If you're looking for office communications, I've heard good things about "Difficult Conversations":

https://www.amazon.com/Difficult-Conversations-Discuss-What-...


"I was going to get it" is past tense. Using past tense for something can imply that it's something that was true in the past, but not now.

This can irritate people because it comes off as trying to claim credit for intent to do the task without actually doing it.

While "Please stop. I've got this" is the best phrasing because its what your wife has requested as well as what the other commenter stated, I imagine you would have still got a fine result if you used present or future tense. "I"m getting it" or "I'll get it".

Tenses, and other grammar on their level, is definitely something you will be able to find scripts for.


- High-Ouput Management - Five Disfunctions of a Team - The Goal - Principles by Ray Dalio - Good Profit by Charles Koch

All of the books above cover some aspect of what you want but don’t seem to cover the whole picture. Further, a lot of it comes down to shared mental models. If you are coming from the perspective of action taking then the other person also assumes that you will take the action. I think Leader Eat Last explains this brilliantly and actually significantly changed the way I am trying to approach leadership as well as how I work with other people in general.


Hi Tim, this had happened to me a lot before I finally realized that effective communication comes after good emotion. Try listening and talking about her emotions and feelings, and then communicate the subjects. I believe there may be "full of script book", but I doubt that gonna help you. Cheers,

Robert




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: