| This article really frustrated me the last time it was posted, but now I think I have a clear enough idea why to put it into words. You absolutely can tell people things! But to tell someone something, you need to do three things: - Establish enough shared context that they can understand you
- Speak about something they actually care about (or convince them to care)
- Use a format that works for what you're trying to communicate
I've told people about technical topics in conversation or presentation plenty of times. I don't really understand how you can be an engineer and not tell people things.The article is frustrating because it puts the blame onto the listener. But that's not how communication works! You don't have the right to just "tell people things" - you have to put in the work to be understood and to show people it's worth their time to pay attention. Communicating well is part of the job. The author does this even in this piece. He says: "For example, with just a few magic HTML tags we could stick avatars on a web page — pretty much any web page. For months Randy kept getting up at management meetings and saying, “We’ll be able to put avatars on web pages. Start thinking about what you might do with that.” Well yeah - if someone stood up in a management meeting and told me to think about what I might do with an avatar, my first thought would be "What's an avatar" and my second thought would be "I'm already busy with other things". He hasn't said what an avatar is or why anyone should care about them. So people pay no attention. Then the demo shows what an avatar is and lets people see immediately how it might be useful, in a format that works regardless of the skill of the communicator. And so of course now they understand! And maybe the thing you're trying to communicate is so novel that you can't establish context or convince people to care without showing them a demo. But at least take the time to understand why you can't tell people about it. |
For example, in the story about the Japanese, he assumes some context from the reader: "What are they building? What is Fujitsu and what is Habitat and why does Japan need their own special version of it?" It's not even clear they're building anything technical, so I wondered, "Why do they need a client and server? And also, didn't you ever think to check their internal technical details before? What did you think would be the result?"
> “who’s going to pay to make all those links?” or “why would anyone want to put documents online?”
These are good questions and you better have a well-worded answer! In fact, it is easy to answer these if you have prepared for them. Did you just assume that the potential customer would already have familiar with the technicals of your product? If that was the case, they would have bought it from someone else already. Your target demo is the uninformed.