As a technical lead, have you had this experience?
The system has clearly been tested, yet after launch problems multiply like bacteria. At every meeting the client's representatives look unhappy, the PM's real skill turns out to be apologising sincerely, and the development team says glumly, "But we tested everything on our side..."
I suspect plenty of people know this scene well.
You hired SQA, but the problems are still there?
Many companies have a standard answer: "Let's get an SQA team!"
So the company spends a lot of money on a professional testing team. And they really do work hard:
- They write lots of test cases
- They build lots of automated tests
- They produce good-looking test reports every day
But... problems keep popping up one after another.
At this point you might think: "Is our SQA team just not good enough? Should we replace them?"
Wait! Before replacing anyone, let's think about a more fundamental question.
Do you really understand your problems?
Before talking about solutions, we need to be clear about what kind of problems are actually troubling us.
Let's break it down in the simplest way:
1. Functional issues
- A feature does not work at all
- Calculation results are wrong
- Data is displayed incorrectly
2. Performance issues
- The system responds slowly
- It crashes when processing large amounts of data
- Memory leaks
3. Compatibility issues
- It does not work in certain browsers
- The mobile version displays incorrectly
- API integrations fail
4. User experience issues
- The workflow is not intuitive
- The interface is cluttered
- Feedback messages are unclear
Each type of problem needs a different testing strategy and a different way of handling it.
The way forward
- Start by categorising and counting
- Record the type of every issue
- Count how often each type occurs
- Identify the areas that most need attention first
- Build a matching test strategy
- Strengthen testing for the issue types that occur most often
- Choose suitable testing tools and methods
- Design more targeted test cases
- Keep tracking and adjusting
- Review the issue statistics regularly
- Evaluate whether the improvements are working
- Adjust the test strategy when needed
Remember, finding the pattern in your problems matters more than blindly adding tests. Just like a doctor, an accurate diagnosis is the first step of treatment.
Conclusion
Rather than constantly asking "why can't we catch the problems?", take a moment to ask: "Do we really understand our problems?"
Once you start analysing and categorising problems systematically, you will find that testing is not about blindly increasing coverage. It is about finding the right direction.
In fact, when we keep running into "why did we miss it again?", it often points to deeper problems:
Flaws in the development process
- Are requirements correctly understood and defined?
- Does the architecture take all the usage scenarios into account?
- How well is code quality managed?
Gaps in team communication
- Does the development team really understand what users need?
- Do the testing and development teams work together smoothly?
- Is customer feedback fully passed on to the team?
Blind spots in project management
- Does the schedule leave enough time for testing?
- Are the trade-offs between quality and schedule sensible?
- Is risk assessment thorough enough?
So when "testing keeps missing the problems" is bothering you, rather than rushing to hire more testers or add more test cases, step back and ask: "Is our software development process healthy?"
After all, testing is only the last line of defence in quality assurance. If something has gone wrong earlier, no amount of testing will do more than patch the holes. It is like a leaking bucket: instead of endlessly wiping up the water underneath, find where the hole is and fix it at the source.
The real solution is to build a healthy software development ecosystem, where quality starts with the requirements and runs through the whole development process, rather than resting all our hopes on the final testing stage.
That way, we will stop asking "why can't we catch the problems?" and instead prevent them from happening much earlier.