

Project Manager at Domain 6
Requirements gathering begins early. Mostly worked on by the presales and sales team, stakeholder committees, SMEs, and other influencers, it will eventually impact the future state of operations that are naturally going to be impacted by the service or product being adopted. Thus, it’s essentially important to be careful, especially on the consulting side when considering your answer. And, on the stakeholder/adoption side, especially careful when accepting an answer. Let’s look at the most common scenario we all face: does your solution do “XYZ” out of the box?
The temptation exists on both sides on the service provider side and on the customer side. The pressure is always on consultants to create and on the customer to always prefer a “YES.” To test this, you could even put an absurd question on the RFP, “Does your software perform acrobatics?” The most likely answer would be “Yes.” However, the true-er answer in such cases is more to the tune of, “The software/service handles air-to-air transfers and tight-rope walking. Additional scenarios can be accommodated for as-needed, however setup and configuration are required.”
As always, many will yield to the temptation to accept the “YES!” as the end-answer. And beware, because like everything, life is not so simple. The real work begins when both sides start to actively work to determine exactly how closely the particular customer requirement can be achieved. In working together to find out the real answers to your requirements questions, here are some basic tips:
Hopefully, with these guideposts in mind, you can better review responses, or if responding, “YES” to every checkbox requested, hesitate somewhat. There is never one solution that fits every scenario all the time, and even if it did for a season or two, as business needs change, so will the requirements as well. Your responses and/or system should respond, accordingly.