10 ms·
>Mistake 3: Communicating something one time is enough I joined a company once where a particularly skilled engineer had become a manager. She was very good
by duxup 6y ago
>Mistake 3: Communicating something one time is enough
I joined a company once where a particularly skilled engineer had become a manager. She was very good at her job and I'm fairly certain had something like 'perfect recollection'.
We were in a meeting and she went on about how she was upset people were doing a troubleshooting process wrong despite having sent out a detailed email.
Not wanting to do that thing wrong I searched my email, but couldn't find it. I asked about it and she told me "Oh it was before you joined us.".
I had been with that team for two years...
People tend to remember important things like it was yesterday, but don't always realize that other people can only absorb so many important things / don't always know how important it is... and email is kinda a terrible way to communicate it too. Let alone 2+ years earlier ;)
- harryf 6y agoThere’s some cognitive bias in which we assume that when we regard some information as important, that anyone exposed to that information will fully absorb it. The reality is - while learning how to communicate well is hard, actually getting anyone to listen is many times harder. I used to joke that in any meeting with more than 4 people, at any given time at least 1 person is day dreaming. And since mobile phones and social media all this has got many times harder; attention spans are shorter and there’s a higher expectation that information should be somehow entertaining. These days communicating something simple like an important date to 10+ people inside a company requires multi level marketing; email, calendar invite, Slack, face to face time ... use it all and still one of the 10 will somehow miss the message.
- savanaly 6y agoYou can't tell people anything. [0] [0] http://habitatchronicles.com/2004/04/you-cant-tell-people-anything/ http://habitatchronicles.com/2004/04/you-cant-tell-people-an...
- Johnwbh 6y agoInteresting essay. Reminds me of some of the issues that come up in teaching. Even when you think you have explained something at the simplest possible level you are often missing background assumptions that seem to obvious to you that you can't even conceive of not knowing them
- andrewem 6y agoI’ve read that essay before and I re-read it just now and I still don’t understand what is meant by “avatars walking around on top of our company home page”. So I guess the essay proved its point.
- kovvy 6y agoIf you miss a word in a conversation, you automatically fill it in. This is usually pretty reliable even with unfamiliar material, since if you follow standard grammar rules there's a decent amount of redundancy. Sometimes, though, this doesn't work. You think you were paying attention, but you missed parts and filled them in with what you wanted to hear. Ideally there is a back and forth that checks that important information was correctly passed on. Failing that, some redundancy can make a big difference.
- gkop 6y ago> multi level marketing This phrase has a specific meaning I’m quite sure you did not intend: https://en.wikipedia.org/wiki/Multi-level_marketing https://en.wikipedia.org/wiki/Multi-level_marketing Perhaps “requires a multi-pronged approach” captures your meaning clearly?
- harryf 6y agoAh yeah - NOT a pyramid scheme - multi pronged is what I meant
- jhanschoo 6y ago> I used to joke that in any meeting with more than 4 people, at any given time at least 1 person is day dreaming. This was a big problem with me in college. While going through proofs in a lecture, I would frequently have questions in my head and try to pursue them, and in 10 seconds I would have lost the line of reasoning of the proof.
- hansvm 6y agoFunny, I've always viewed that behavior as more conducive to learning than trying to follow a proof or lecture exactly.
- jhanschoo 6y agoIt's alright if there the proof is sketched down somewhere, but I had a couple advanced courses where there were important concepts that weren't already written down anywhere.
- watwut 6y agoFor me, writing notes work to overcome that. If I write notes, I can keep focus longer. Plus, I would scribble all those questions on side and come to them later if they were not answered by something in lecture after.
- throwawayboise 6y agoThere's also the problem (for me, and I have observed for others) that emails sent to lists or large numbers of recipients/CCs automatically get less attention and priority than emails sent to me individually. If I get an "all hands" type of group email, I skim it, or maybe just read the subject line, depending on who it's from. Over time I've learned that there's almost never anything directly actionable for me in these messages. The day is too short and there's too much to do to spend time carefully reading long-winded broadcast messages.
- jjoonathan 6y ago> at any given time at least 1 person is day dreaming I dunno, I'd maybe weaken that a bit before putting money on it: > at any given time at least 1 person isn't day dreaming.
- vishnugupta 6y ago> I used to joke that in any meeting with more than 4 people, at any given time at least 1 person is day dreaming. This is my experience too. Based on this I concluded that 3 is the optimal number of participants in a meeting. Two would be having an active conversation the third one would be actively absorbing the content of that conversation chiming in once in a while. In fact even in a meeting with 6-8 people I noticed this pattern of 3. Just that members of this 3-clique would slowly change over the course of the meeting. Edit: wording.
- pc86 6y agoJust because 3 means that theoretically everyone is paying attention the entire time (certainly not the case) doesn't mean it's the optimal number.
- afarrell 6y ago> There’s some cognitive bias in which we assume that when we regard some information as important, that anyone exposed to that information will fully absorb it. Part of the problem is that people get really upset when you don't assume that.
- kqr 6y ago> I used to joke that in any meeting with more than 4 people, at any given time at least 1 person is day dreaming. You don't even have to joke: you can put it in statistical context. If people day dream around 45 % of the time spent in meetings, and assuming that day dreaming time is distributed independently among meeting-goers, there's only a 0.55^5 = 5 % chance of nobody day dreaming at any given moment. If you're willing to accept a lower p-value and go for an even money bet, people only need to day dream for 14 % of the meeting for you to win money in the long run. Of course, in practise, day dreaming time is probably not independent: multiple people probably think of the same part of the meeting as dull.
- kwanbix 6y ago100% agree. The problem of knowing too much. I recently joined a great team that has lots of different services that do things. Some people explain to you how things using names of things you don't know about, they don't realize that telling me and then we get "info from dragon" means nothing to me.
- ryanSrich 6y agoI’m always blown away when companies don’t have a knowledge base. Imo, if it’s not written down, shared with me, and told how important it is, then it’s your fault. Email isn’t your knowledge base. Slack isn’t your knowledge base (unless you’re using a tool like Guru). Use Notion, use Roam, shit even organized GDocs can work. There’s no excuse to not have things written down, maintained, and constantly shared.
- cm2012 6y agoI agree with Tafster. I've been a consultant for 6 years and so I've seen dozens of knowledge bases and wikis. Some companies even have great processes to fill them in. I have never, ever seen a company where those wikis are actually read. One company I worked with had a very detailed weekly logging of changes, important things etc. The goal was to keep other teams informed of what each team was doing. It took many times many hours a week to keep it up to date. When they looked at the usage log, literally no one logged into to read the stuff except when going into to upload their part.
- etothepii 6y ago> I have never, ever seen a company where those wikis are actually read. The problem with documentation is that it is the making of it that creates most of the value. Like so many things the value looks like duplication.
- antonvs 6y ago> I have never, ever seen a company where those wikis are actually read. This misses a key point. When I get a query that's answered by something on the wiki, I reply with a link to the wiki. If the wiki link isn't fully relevant, if possible I update it before replying. If I have to write significant new content to respond to the query, I create a wiki page. Your attitude of "docs are useless" is self-fulfilling. Docs are only useless in companies that actively want them to be useless. And those companies are, with no exceptions, seriously dysfunctional.
- afarrell 6y ago
- Minor49er 6y agoThis reminds me of my last job. There were some instances where two teams would work on the same feature. The team leads and devs would regularly get together to make sure that we were on the same page in terms of who was developing what and what the specifics of the design were. It worked well. However, management would sometimes feel the need to bring in a developer from neither team who was supposed to facilitate development, I believe to cut down on meetings (because developer meetings that weren't standups, retros, or refinements were bad, apparently). What ended up happening is that this dev would have a meeting with Team A, get the details about the project, then go to Team B and talk about the implementation. Team B would have another idea for how the development should go, so the median dev would agree that the plans would change. That dev would not write down any of the details, let alone communicate back to Team A about Team B's changes. It caused a lot of unnecessary friction and wasted time. Management pretended like this wasn't something that could be avoided. So long story short (and also to your point): communicating once isn't enough, but not communicating at all is unacceptable
- gregmac 6y agoI wish everyone would treat email as the temporal medium it is. It's fine to use email to announce for example that a new procedure/policy exists, but if it's not posted in some canonical location (where the latest copy will always be found) it might as well not exist. Email is where your keystrokes go to die. Just the other day I asked about something and was forwarded a document titled ".... FINAL-v2 (July 2017)". I can't tell you how much that enrages me. [1] https://jamesclear.com/keystrokes https://jamesclear.com/keystrokes
- lumost 6y agoThe problem with email is that it ported letter writing culture to the internet. A big internal announcement at my company can take days to write and undergoes multiple rounds of review. Once people have put in that effort they aren’t going to bother redoing the effort for another medium. Meeting notes are the same way.
- eyelidlessness 6y agoNot to be contrarian, because you’re not wrong, but to provide a little additional flavor... I don’t have anything close to perfect recollection but I do have good attention to detail and how problems intersect, and a career-long recognition for it. I’ve found myself repeatedly in a position similar to the one you describe for your former teammate but where I’d been regurgitating the same information for anyone who’d listen for months on end, often multiple times a day. I was on the newer end of the spectrum so I couldn’t imagine it being brand new information to anyone. But I had to repeat the same details, including how they related to other recurring problems, for months before I could get any kind of shared understanding of the general problem. And even when I achieved that it would flit out of existence at the presence of any new shiny thing, even as I tried to butt in and explain how the problem was known and how I knew it related to the underlying problem. People just don’t listen. They might want to. They might even embrace it. But unless they’re targeting the problem you’re trying to raise awareness about it’s all too easy to treat something as novel and all too easy to dismiss a repetitive voice.
- duxup 6y agoPeople can only listen so much too. Like if you go over 6 critical issues at a meeting once or more times a week.... how many issues can you really 'know' / remember. And when you're troubleshooting all those symptoms rarely just present themselves just like the examples and so forth. After the fact it is easy to match and say 'this is just like that' but that's miles away from trying to do that every step of the way as something develops.
- eyelidlessness 6y agoWell in the case I was describing it was just the same symptoms recurring. The reason they recurred so long is that the people who weren’t listening were focused on the symptoms and ignoring the root cause.