I have been invited several times to conduct a "health-check" assessment for situations where things went wrong in a big way from desired/planned/expected status.
Now let me clarify that these situations are usually mixed blends of technical and non-technical issues, and in most situations, I could easily see the client "wishful thinking" that I would be able to say "" Aha ,, this is where it went wrong, let me fix it for you".
Unfortunately, things in real life are not that simple and straight forward, and neither me, no one else has that magic wand to point at the situation and "Hoopla ! The situation is fixed ! Well ! I really cannot help it when I see my client getting a bit "disappointed" when I advise on what is possible and what is not. I could easily see the client losing enthusiasm and possibly losing interest in my service altogether. But, I really cannot oversell myself and give "false hope" that I can do miracles or even magic in such problematic situations.
Instead, I do apply my MV-BTC framework/methodology to explore what could have gone wrong at the business level, technology level and culture (people) level. While doing so, I often explain to my clients that the easiest thing to look for and fix would be the technology related problems as in the case of technology defects and failures which tend to manifest them in certain ways that can be discovered and identified through trouble-shooting and diagnostics techniques. I often explain to the client that having said so, does not necessarily mean that I would be able to fix such defects myself. technology/product specialists from authorized technology dealers are the appropriate ones to fix such problems.
Moving the ladder up, the next possible source of failures could be in the "business logic" in which wrong, invalid, inaccurate and/or incomplete "business rules" are coded into the system and executing things incorrectly.
Moving up to the next level, we will find "data quality" problems summarized in the famous saying "garbage-in/garbage-out" regardless how good the engine is. If the data is low-quality meaning wrong data, incomplete, inaccurate and/or out of date, then it would be expected to have failures.
The next level up may have to do with the people side of the model, and the "people-related problems" in dealing with the system. If there is a problem with the basic qualification of these people to deal with the system, their training/skill level, their operating procedures, their motivation, attitude and/or behavior.
This is how basically I deal with system failures through the MV-BTC framework to explore potential problems at the technology side, business side and/or culture side of the situations I deal with
Hopefully this is good and helpful into
Now let me clarify that these situations are usually mixed blends of technical and non-technical issues, and in most situations, I could easily see the client "wishful thinking" that I would be able to say "" Aha ,, this is where it went wrong, let me fix it for you".
Unfortunately, things in real life are not that simple and straight forward, and neither me, no one else has that magic wand to point at the situation and "Hoopla ! The situation is fixed ! Well ! I really cannot help it when I see my client getting a bit "disappointed" when I advise on what is possible and what is not. I could easily see the client losing enthusiasm and possibly losing interest in my service altogether. But, I really cannot oversell myself and give "false hope" that I can do miracles or even magic in such problematic situations.
Instead, I do apply my MV-BTC framework/methodology to explore what could have gone wrong at the business level, technology level and culture (people) level. While doing so, I often explain to my clients that the easiest thing to look for and fix would be the technology related problems as in the case of technology defects and failures which tend to manifest them in certain ways that can be discovered and identified through trouble-shooting and diagnostics techniques. I often explain to the client that having said so, does not necessarily mean that I would be able to fix such defects myself. technology/product specialists from authorized technology dealers are the appropriate ones to fix such problems.
Moving the ladder up, the next possible source of failures could be in the "business logic" in which wrong, invalid, inaccurate and/or incomplete "business rules" are coded into the system and executing things incorrectly.
Moving up to the next level, we will find "data quality" problems summarized in the famous saying "garbage-in/garbage-out" regardless how good the engine is. If the data is low-quality meaning wrong data, incomplete, inaccurate and/or out of date, then it would be expected to have failures.
The next level up may have to do with the people side of the model, and the "people-related problems" in dealing with the system. If there is a problem with the basic qualification of these people to deal with the system, their training/skill level, their operating procedures, their motivation, attitude and/or behavior.
This is how basically I deal with system failures through the MV-BTC framework to explore potential problems at the technology side, business side and/or culture side of the situations I deal with
Hopefully this is good and helpful into
No comments:
Post a Comment