Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One common problem when explaining ideas is that we often jump right into talking about the solution, and just assume prior knowledge of the problem we are talking about.

But since the audience probably doesn't know the problem as intimately as we do, this tends to make our explanation hard to understand - even if our solution is straightforward.

A simple trick I once learned is to structure the explanation into four parts, with one sentence for each part: (1) state the problem, (2) state the consequences of the problem, (3) state the solution, (4) state the consequences of the solution.

Since the explanation now automatically includes both the problem and the solution, it usually is both more compelling and easier to understand.



This is succinctly captured by a phrase from the video game industry: "Show locked doors before you show a key"


Very cool saying, thanks for sharing it.


2 & 4 are so crucial. They represent what 1 & 2 mean. Otherwise you have just put an idea in the ether, floating like Forrest Gump's feather but without truly communicating it to anyone in particular. 2 & 4 are the attempt to connect the idea to something in the other person's mind. To make it resonate with them (think about the physical meaning of that word). Or as another commenter put it, "why is it useful?"

It's always possible that your idea with land with something by accident, but it will be by accident and it may not land with the person you intended it to.

A similar pattern I try to use frequently is this:

1) what it is

2) what it means

3) an example


>A simple trick I once learned is to structure the explanation into four parts, with one sentence for each part: (1) state the problem, (2) state the consequences of the problem, (3) state the solution, (4) state the consequences of the solution.

That's a good structure! I have thought about it -- in the context of technical talks -- as Why/What/How. You start at a high level, and progressively zoom in. Why is the problem, What is the solution, and How is the technical details of the solution.

I have a longer explanation at https://twitter.com/zckzck/status/1483330904571494400


I think you just discovered Buddhism's 4 noble truths.


Amazing, I was just reading about Buddhism and this post at the same time. And you offered me enlightenment with this connection.


Wouldn't that be something like this?

(1) state the problem, (2) state the source of the problem, (3) state the solution, (4) state path to implementing the solution


well you would need to realize 1 and 3 are the same and there really isn't a need for 2 nor 4




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

Search: