Why QA Matters

One seemingly small and supposedly inconsequential change can have extreme repercussions on a system’s process.

Having incredible Quality Assurance is like watching a movie with great special effects. If the experience is flawless, then it means everyone has done a great job.

Unfortunately, this is rarely the case. Unless you have the quality insight needed to be prepared. Here’s what we mean: Even the simplest of projects can get complicated very quickly. This is especially true when you’ve got thousands of customers and millions of dollars on the line. In an ideal world, creating a system would simply mean establishing your requirements at the start of a job, implementing them, and then calling it a day. Years of experience have taught us that this is never the case. The reality is that there are a million factors that can change the scope and increase the complexity of a project: time, scheduling, new features, and availability of resources are just a few. What some businesses don’t realize is that it’s never just about adding in things like new features. It’s about figuring out how each new feature affects every other component of the system. We like to think of this as the butterfly effect: One seemingly small and supposedly inconsequential change can have extreme repercussions on a system’s process. This is where having qualified QA experts is critical. In QA, there are usually two approaches:

Approach #1: The Boring “Only You Can Prevent Forest Fires” Method:

This is all about being prepared from the get-go by having what we like to call a “Smart-Flexibility” mindset. It means thinking through all potential possibilities, requirements and potential problems at the start of a project, with the flexibility and intelligence to address and adjust to any changes that may occur throughout. It also means creating a well-documented process so that teams can be held accountable, and processes can be repeatable if needed. This may require more investment up front, but it almost always saves more in the end.

Approach #2: The Super Sexy Heroic Firefighting Method:

This is when the “you-know-what” hits the fan. It’s when companies don’t prepare and then find themselves caught up in a massive fire that has to be put out. Companies ironically love this approach because it often feels heroic and builds camaraderie for having the project team come together in a time of need. In reality it’s extremely detrimental. All vital QA processes such as documentation and communication protocols are typically thrown out the window, creating all new problems and defects that typically lead to further fires, issues, and of course, more heroic firefighting. Approach #2 often destroys the primary objective of the project, namely, to create a functional system that offers a quality experience for the end-user. At Insight Quality, we can handle both approaches. We just prefer the first one. It’s why we’re so intense about thinking the plan through ahead of time. It’s what comes from spending years in the trenches, in seeing first hand what can go wrong when you fail to plan, and also what can go right when you ask the tough questions. It leads to a special kind of insight. A new level of Quality Assurance. It’s why we call ourselves Insight Quality. Having quality insight means having the foresight to see what can happen 30 moves ahead. It’s about removing the element of surprise so you don’t find yourself deep in the heart of a major forest fire (with millions of dollars on the line). It’s about being flexible when changes happen but without compromising quality along the way. It’s about making your life as boring as possible (from a technical emergency standpoint). Having the best QA will make you look like a genius to your clients. Because they’ll never even know we were there. We’re Insight Quality. Nice to meet you.