Begging the Question During Implementation

Share:

“Judge a man by his questions rather than by his answers.” ― Voltaire

Guest blog post from our friends at Frontline Services.

flsbanner_fullsize_distr

Driving an implementation is not unlike driving a car—there are many roads to take, but how you steer and what roads you choose can be the deciding factor in the overall time and resources spent in reaching your destination. With that in mind, it is paramount to always evaluate and reevaluate the tools you have at your disposal.

It is no secret that using a process which requires obtaining information, no matter how tried and true, is never a one-size-fits-all solution for every implementation. Each client has different needs, expectations and, most importantly, means of communicating these. This is exactly the reason it is so important to be mindful that not getting the answers you need is a symptom of not asking the right questions in the most efficient way. When facing the potential hurdle of a technical question, take it as an opportunity to change hats and consider another way of reaching for that key piece of information.

Take for example the BRD [Business Requirements Document]; any implementation manager is going to be familiar with what each section pertains to and what information is needed for them. However, placing it before someone who does not have the necessary level of familiarity with it can be potentially confusing, somewhat daunting and almost always counterproductive for them. The document in question is a priceless tool and the cornerstone of any successful implementation. Like all tools, it does not serve a purpose without its operator knowing how to properly use it.

Be sure you ask the right questions to make your implementation process much more efficient and productive.