One important element for me is that the framing should be as specific as possible. The article's example, regrettably isn't the best example of this, but: by

One important element for me is that the framing should be as specific as possible. The article's example, regrettably isn't the best example of this, but: by saying "one of the main problems..." the author (quite reasonably, not click-baiting) is trying to say "this paper is about something important and is worth reading, or at least reading the abstract". Unfortunately for me (not necessarily others) these kinds of context act as framing, so I am less likely to match to a similar case in a different domain. Here's a CS example: let's just say you might have found a way to, say, compress the TLB or use fewer instructions to use it which speeds things up in most cases but slows them down in a few corner cases. You could start by talking about the problem of paging systems under high load or large RAM or something -- great! But if you described a novel hashing architecture, later in the paper pointing out that it's "..useful, for example in a pager", I might read the paper and say "holy cow this would work well for this thing I'm working on". That's why I prefer just the dry bones. I can hang whatever flesh I want onto them. But I know not everybody is like that, and that's OK. The world isn't supposed to pander just to my need (though it should, dammit!)