I have too many explores at my org at the moment which clutters the user experience. Are there best practices and also governance principles for data practitioners to implement and enforce at the implementation level?
Good basis is to leverage two things:
To me this is the beginning when I evaluate a Looker instance. Unfortunately it’s very easy to let th enumber of explores grow out of control 😄
@Dawid Thanks for your response. I completely agree its so easy to let the number of explores go out of hand. But is it too common a problem?
My question was more on the lines on how to cater to different business requirements before we even set out to build an explore. Should we have one explore with large number of use cases like multiple feature analysis on a website to build a omnichannel experience bundled in one explore,(e.g visits → conversions or cohort analysis of all features bundled into one ) which does need a lot of data modelling rather one explore for each feature?