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

In particular, it took me a long time to a realise that for a lot of people communications is parsed by treating a series of requests or pieces of information as a FIFO. If you're lucky, it's fairly deep, but for some people it can only hold 1 or 2 entries at the time.

But when it's an e-mail or other interaction that they understand as "conversational", these people tend to not start acting on the output until the end.

So ask for 3 things, and chances are only the last one will still be in the queue by the time they've read your whole message. The rest will have just popped out of their mind and no longer exist in their world until they're prompted to re-read your message.

For people who act like that, seemingly the only way around it short of drip-feeding them questions one at a time that I've found is to present them with a document attachment and only one request: "Please follow the procedure in the attached document." And make them sign off. And provide a checklist if they're particularly difficult.

You basically need to make it clear that the list is not conversation. You can find people who are pathologically unable to process a list of instructions in an e-mail who are at the same time completely OCD about processing lists of instructions in a document, because they context-switch completely.

Of course in this context of "sabotage" this can be exploited to: Mercilessly attach all information in a bunch of separate documents, and add checklists and signoffs to everything. Especially to unimportant stuff.




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

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

Search: