We are running into an issue that I'd love some feedback and suggestions on. We have a nice Looker model running for which my team is responsible on the data side of things. We make sure the data ends up in the correct database, but also maintain the Looker model. We have prepared a couple of dashboards for the end users, so that even people with no Looker experience can see the data.
This setup worked fine when we were slowly releasing Looker into the organisation with a couple of end-users and the communication lines were short and easy. Due to the success of the tool, more and more people take an interest in the data. This on itself is awesome of course! However, this means we have to find another way to communicate some of the properties and quirks of the data and model to the end user.
I am looking at a central place to communicate this to all users, a bit similar to a .README for the model. Any suggestions for this? Interested to hear how other people deal with this as well.
I'll finish with an example of something we'd like to communicate:
Say we get data from web and app use and we distinguish between the two. For two days, iOS app data fails for whatever reason. An end-user looking at the data might make the wrong conclusion that nobody uses the iOS app, because there is no data for it.
Ideally I'd put this on a README/disclaimer page, where I can say that iOS data is not available for now, so it is clear to everyone what's going on. Once fixed, I simply update the page and all is well.
Looking forward to seeing some thoughts on this one!