How to KonMari Your Domo Instance, Part-Two

by Jun 17, 2019

Practical tips for ensuring your Domo instance sparks joy
and delivers business value

In our first post, we discussed how in our work, as in our homes, we can apply rules for bring­ing order to our prac­tices and our tools not just to clean things up but to create effi­cien­cies going forward. This second post in our two-part series will continue to apply some KonMari Method™ prin­ci­ples to your Domo instance to do just that.

A messy and un-governed Domo instance leads to data secu­rity prob­lems, user frus­tra­tions that can impact further adop­tion, and overall main­te­nance night­mares. Are you having issues figur­ing out where to start clean­ing up an instance or with data gover­nance in general?

Let’s continue on our tidying journey…


The Last Three Rules

These sections are based on the KonMari Method rules, and they aren’t steps to perform in order. Instead, develop processes in your gover­nance ecosys­tem that consider each of these rules. Rules 1–3 live here…

Rule Four: Tidy by category, not location.

In the KonMari Method, every­thing gets tidied accord­ing to cate­gory and in order. This helps get every­thing orga­nized at once to help it stay orga­nized later. For your Domo instance, let pages, cards, datasets, users, and groups be your cate­gories, and begin orga­niz­ing them in order (see below). Even though the methods and processes will be differ­ent for each cate­gory, aim to outline and execute a compre­hen­sive plan for each cate­gory so that all users can adhere to a set of stan­dards that are easy to abide by.


Next, perform secu­rity audits to deter­mine who has access to differ­ent cards. Provide access based on what adds value, and keep in mind that any process you intro­duce to the ecosys­tem should be eval­u­ated by a gover­nance perspec­tive. For example, if you aim to enable secu­rity that puts up a fire­wall to restrict access, you’ll need to deter­mine (and commu­ni­cate) what IP can access the instance, how someone outside of the orga­ni­za­tion might get access, and how to onboard new users.

Rule Five: Follow the right order.

In data gover­nance, all cate­gories are inter­con­nected, so chang­ing a part changes the whole. This is all the more reason to ensure that the steps you take toward tidying are effi­cient. We recom­mend tidying pages, then cards, then datasets.


For each cate­gory ask at a minimum, the follow­ing ques­tions:

  • Who owns this? If no one, assign an owner
  • Is it being used? If not, mark it for dele­tion
  • Do you need this? If not, mark it for dele­tion
  • Does it follow all docu­mented stan­dards? If not, mark it for cleanup

In addi­tion to that, you’ll want to ask more specific ques­tions within each cate­gory:


  • Are all cards orga­nized into collec­tions? If not, think about the hier­ar­chy and orga­nize accord­ingly (“at a glance” type infor­ma­tion at the top, more detailed data under­neath)
  • Is this a produc­tion-ready page? If so, consider locking it so it’s not inad­ver­tently altered.
  • Does every card on this page belong here? If not, remove the strag­glers.  


  • Has this card been viewed in the last couple of months? If not, verify need with owner
  • Does this card belong to a page? If not, mark for dele­tion.


  • Has this dataset been updated in the last couple of months? If not, verify need with owner
  • Has this dataset been viewed in the last couple of months? If not, verify need with owner
  • Is this dataset being used in a card or dataflow? If not, mark for dele­tion
  • Is this dataset a dupli­cate? Is so, consol­i­date all usages to one dataset
  • Does this dataset contain sensi­tive infor­ma­tion? If so, ensure that access is prop­erly granted/restricted


  • Has this user been inac­tive? If so, consider remov­ing them
  • Is this user assigned to a group? If not, assign them as applic­a­ble, creat­ing groups as neces­sary during this process
  • Does this user have the proper access level? If not, ensure that they do at this time


  • Does this group not have access to any pages? If not, mark for dele­tion if it’s older than 30 days
  • Does this group not have any users? If not, mark for dele­tion if it’s older than 30 days


If some­thing is not being claimed or used, or if it isn’t adding value, then it needs to be tagged for dele­tion or deleted.

Rule Six: Ask yourself if it sparks joy.

While the phrase “adds value” may not make your heart leap as much as “spark joy,” there is a certain tacti­cal cheer involved in inten­tion­ally govern­ing your data to answer busi­ness ques­tions. When you finish your process and know that your Domo instance or data strat­egy is stream­lined and action­able, you can be confi­dent that you and your orga­ni­za­tion are doing your best, master­ful work with optimal ease. If that isn’t anal­o­gous in data gover­nance to joy, then I don’t know what is.  


What sparks joy for me is helping people imple­ment their ideal data gover­nance. I’d love to help you discover tidy gover­nance solu­tions. Contact us for more infor­ma­tion.

For some other prac­ti­cal tips on how to stay on top of things going forward, here are Five Steps for Using Your BI Tool to Manage Your BI Tool by Senior Busi­ness Intel­li­gence Manager, Alan Hyman.

All of this tidying would be a lot easier with a sound data strat­egy! Make sure to check out Plot­ting Your Data Strat­egy by our Senior Direc­tor of Data Strat­egy, John Lovett.

Ready to get started?
Reach out to learn more about how we can help.

I consent to having Search Discovery use the provided infor­ma­tion for direct market­ing purposes includ­ing contact by phone, email, SMS, or other elec­tronic means.