Once in awhile, a riddle so obscure and enigmatic comes along that it baffles and stumps most of our brightest thinkers and deepest philosophers, qualifying as a Zen koan. Like the sound of one hand clapping or the sight of your face before you were conceived, the answer cannot really be found in any conventional sense. Well, in my humble opinion good people, the tension between current state and future state and the need to document and analyze the “as-is” prior to taking on the “to-be” doesn’t qualify as a Zen Koan or a crossword puzzle for that matter. There is no question. You have to understand the present dynamics and process in order to sensibly develop something new.
I know that I will offend some of the business process management wizards and high priests by saying as much but my position is one of firmly believing in the value of documenting and analyzing the current state to ensure a high quality future. Frankly, jumping into the design of the future state without regard for a rather precise current state is irresponsible. Not unlike asking someone how they’d like to perform in graduate school without first ascertaining whether they can read or not. Or promising someone full health without first diagnosing their diabetes. The present state in business tells a vast and deep story that shapes the possible and potential future.
I attended a conference recently (devoted to the adoption of EMR in physician practices) whereupon I was able to listen to a discussion at our lunch table between a woefully ignorant doctor who wondered aloud what it would take to implement such a thing as an electronic medical record and an “expert” across the table who piped up and assured him that he needn’t worry about how things are done in in his practice today. He would only be required to imagine what life would be like with his new system. What a load!
Notwithstanding that particular “consultant” and his advice to the good doctor, it got me wondering, “How many of my colleagues would suggest the same?” I wish I could survey all of my BPM brothers and sisters out there. Do you honestly think you can account for all of the business rules, decision-making, forms, customer preferences, suppliers, and key metrics involved in a process without concerning yourselves with the current state. Do you really think you can skip that step and begin modeling the future state without compromising quality or any other vital business attribute? I think not.
Change without consideration for the present is invention
Don’t get me wrong. I love to invent stuff and get wickedly creative when given a chance to roam free. However, invention cannot capture all of the good reasons why my system dynamics are what they are and cannot account for the benefits and value inherent in my current state without first elucidating them. Failing to harvest and capture the good, the rules, the data, the preferences, and the logic and simply launching into invention risks losing a lot including compliance with standards of all kinds. The risks involved can cause an invented business process to become fatally flawed in short order, grinding business to a halt.
Take your time and carefully document what you do today and how you do it. Inventing the wrong thing, failing and trying weeks or months later to return to an undocumented state is fools work.