[hintymad]

There are two frameworks. I'd suggest you combine both. The first one is STAR: situation, tasks, action, and results. The second one is used by product managers a lot: MECE, or mutually exclusive, collectively exhaustive. Use the first framework for your narrative with a focus on why, or so-called working backwards. Use the second framework to narrow down what you need to dive deep.

I can't stress enough how important it is to work backwards and explain the why of your work. Too many geeks mistake claims for reasons, and got dragged into irrelevant details to the point that their work appears irrelevant too. On the other hand, the bigger a problem, a more impressive a solution. If you can articulate why you're solving a problem and why you solved it in the way you described, people can probably figure out the how part easily.