Many businesses in the analytics space say they want more insights – and they expect their analysts to come up with those insights.
But not many analysts know how to deliver that. Most don’t do anything analysis related at all. They find themselves trapped in the world of reporting, where they crank out dashboards and KPIs on a regular basis, while begrudging their executive overlords for telling them to “include more insights!”
I call this the “reporting trap.” And businesses and BI professionals alike want to escape it. Only they don’t know how.
Quality checking is one of those things we all say we love but secretly hate. We send our work over to another developer, believing they won’t find anything wrong with it, only to discover there are A LOT of things wrong with it.
You then go through the various stages of grief - denial, anger, bargaining, depression - before reaching the final stage, which is accepting that you are not the great genius you thought you were.
While I can’t take that emotional roller coaster completely out of quality checking, there are things you can do to make a better experience for both you (the developer) and the person who quality checks your work.