Adding layers of detail certainly helps the data, but that is an exponentially greater amount of work, so I'm afraid the cost/benefit wasn't there to break down pace/score. I could load the play-by-play data into a GitHub and parse it with a programming language, but I'd still have to adjust for time between plays etc. unless someone better at building that code would make it automatically do it. (If > ___ seconds, then ____ type of layers into the code for scraping the data itself, or perhaps a second code once the data is scraped).
Building in score adds an additional layer of score (for instance, yards per pass is heavily influenced by situation, as teams are just fine letting you get 8 yards a play passing into the MOF when they have a nice lead late).
Generally, I'd like to use success rates, but even those are flawed in my mind as to the situation. A successful second down play is heavily influenced by how successful the first down play was, as is the third down play by how successful the second down play was etc.
I'm trying to find a happy-medium to where I present data in an easily digestible format that doesn't make me appear as though I'm trying to be the smartest guy in the room, but also going deeper than simply stating "the defense ranked ____ for this season."
If that makes the sense I'm hoping it does in my head.
