Working with your client on developing software can often seem like a never-ending tennis match of QA and Re-QA. Tweaks here, an adjustment there, pieces of functional makeup scattered about. In the natural progression of a project, we’re always faced with the decision of how much flexibility we’ll give to those last (sometimes lengthy) to-do lists of QA changes provided by a client.
QA time can last forever because it’s sometimes hard to anticipate what questions might arise at the end of a project when budgeting for it at the very beginning. Frankly, QA time usually ends simply because the project must be launched. But, a better way to end the tennis match is to have clients focus on why the experience isn’t perfect, rather than what should be added, subtracted, or modified.
Next time, get your clients to list out what feels wrong, rather than what should be done to amend it. When clients start venturing too much into solving problems rather than detecting them, we’re in for the potentially dangerous ride of going down a path of no return. This way, you’re QA time is all about making the application feel great to use and not about checking off three-dozen items that may not have actually solved all the problems.