Don't touch that button...

Or what is that thing called 'Configuration Knowledge Power'

But before we go there...

Replacing a lamp

So, you're replacing that broken lamp in the living room. And you want to be 100% on the safe side, so, you switch off the main power. Although... The washing machine is currently running and your daughter is just about to start an online school session. And you just remember your wife is halfway downloading that 35Gb MacOs upgrade... Luckily, you know exactly what switch in your switchboard you need to flip to cut off the power in your room. Or, well, you don't. So, perhaps you should postpone replacing the lamp. Or simply not replace it yet, although it's clearly broken and you need the light. Well...

You will not remember...

Salesforce orgs can be a little like this situation. It's not about will there be a lack of insight, but when. You (or your predecessor(s)) have added stuff to the basics. Because business asked for it. Or with all the good intentions, you thought it was a useful addition. We do it all the time. We're humans. You want to be helpful. It's also human to focus on short term results: Cut the crap, just do it. You'll remember what you added or changed. So, here's your first a takeaway: You won't. Simply because tomorrow is another day. As you know you cannot remember everything or this particular change is pretty important, you've scribbled down your notes on a piece of paper using an Excel list which you've stored on a Google drive or Sharepoint. You have scribbled down those other changes of last week as well. Using Powerpoint, Word or perhaps some drawing-tool in the cloud. But quite often on a piece of physical paper that lays somewhere between those other notes...

All these change notes - sometimes called documentation - , even when stored on an Excel in the cloud, are isolated and out of the business context at the moment the change was created. And that's the part you also won't be able to remember: What was changed is one thing, and how it was changed is really useful (if you wrote it down), but why it was changed, is another. The last being the most important from a business perspective.

If it ain't broke, why fix it?

You know your configuration is not right. But hey, it works for months like this.

It's a bit like driving a car from home to work and there is that strange engine sound. Again. But hey, the car is still driving for months. And there's not even a light burning (remember replacing that lamp above?). So, why bother. Until... Your boss asked you yesterday to drive to that other location for a really important task and Google maps just reported it takes 650 miles to get there. And another 650 to get back. Oh, and you need to go tomorrow. Public transport is no option, as it's in the middle of nowhere and there's quite a lot of stuff to take with you. Failure to get there is no option. Would you take the risk? Well, you would if you'd known where that sound is coming from and how serious it is. Second takeaway: You don't have to fix everything all the time, as long as you can properly judge both short term and long term impact.

The ever changing context of now

Replacing the lamp without impacting the rest of your householding is, what I'd call, the art of knowing and understanding the crucial elements of your configuration. Ignoring the strange engine sound is absolutely fine as long as you know the possible impact and it's safe. Being in control doesn't mean to measure, document and understand everything at all times, but measure, document and understand those things that matter in the ever changing context of now. But you need to try to be as complete as you possibly can. As simply that one little thing in your configuration, could make a big difference. So, you'd like to build a knowledge asset that you can trust and gradually gains value; you cannot boil the ocean. This asset is called Configuration Knowledge Power.

Configuration Knowledge Power

As you cannot boil the ocean, but you have to start somewhere, you eat the elephant bit by bit. And the first byte starts with understanding the value of this documentation practice. So, give it some thought tomorrow in the office, collect those strange engine sounds and see for yourself how many times you think you can safely ignore them. In the end nobody wants to disrupt his wife or husband downloading that 35Gb upgrade, postpone the laundry. Although your daughter would go: "Online school? Nah... just flip the main power."