>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.
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