Featured image of post Dare to Be a Dissenter - More on Testers' Perception of Their Role

Dare to Be a Dissenter - More on Testers' Perception of Their Role

Because of the "trap of intellectual conformity", many avoidable wrong decisions get pushed through. And testers can play a more critical role in this

Preface

A few days ago, I read a blog post by the foreign blogger Vitaly Sharovatov, about the “trap of intellectual conformity” in enterprises and R&D teams. Because of the trap of intellectual conformity, many avoidable wrong decisions get pushed through. And testers can play a more critical role in this.

It was quite inspiring to read; after some deep thought, I wrote this article to share with you all~

The Trap of Intellectual Conformity

The trap of intellectual conformity refers to the tendency of an individual who holds a certain position or perception to selectively accept information consistent with it while ignoring or overlooking inconsistent information, thereby forming a self-reinforcing cognitive loop that makes it difficult to assess reality objectively.

In the 1950s, psychologists such as Festinger, Carlsmith, and Solomon Asch conducted many related experiments, confirming the widespread existence of cognitive conformity bias:

  • When performing boring tasks, subjects paid less were more likely than those paid more to change their original evaluation, to rationalize the conflict between their behavior and the outcome.
  • In another experiment, most subjects changed their originally correct choice because of other people’s wrong answers.
  • When the same food was priced differently, subjects tended to believe the more expensive food tasted better.

In short, the experiments above are what we call the “conformity mentality”

Quality Risks Caused by Intellectual Conformity

In enterprises, quality problems caused by the “conformity mentality” above and going along with the majority opinion are not uncommon.

  • A development build that cannot even pass smoke testing is hastily submitted for testing, simply because the developers “feel” it is fine
  • A feature that a leader thought up on a whim is rushed into development, and because it does not meet real user needs, it becomes a white elephant or even has to be rolled back
  • Without investigation of the user base or analysis of real usage scenarios, a new feature is completely unusable

For the problems above, did really no one feel beforehand that something might be wrong? It is just that most people had no opinion, or the process reached a certain node, and it was pushed through by default.

I once saw a view from a startup CEO: software testers are “more harmful than helpful” in terms of cost-effectiveness. If you hire only excellent developers with quality awareness, you do not need a dedicated quality role.

But is that really the case? In my earlier articles, I discussed the difference between “developer thinking” and “tester thinking”:

  • Developers tend to pursue certainty. Based on definite requirements and steps, they define how the product should behave.
  • Testers need to consider various possible paths and branch scenarios based on uncertainty, and assess the product’s possible behavior based on the unknown.

Moreover, in a performance-driven organization, developers are hired to deliver results, not to question. They are evaluated on their ability to build, not on their ability to find and respond to problems.

And based on the trap of intellectual conformity, in an output-oriented organization, dissenting voices are continuously weakened, so even developers with excellent quality awareness find it hard to put quality first in such an environment.

Testing, the “Dissenter” Assigned by the Role

Many people with a “conformity mentality” can actually sense that something is wrong; they just lack the courage to raise a “dissent”. But once a challenger appears who points out the problem, they too can actively offer opinions.

And the testing role, by its very design, is assigned and expected to raise questions and challenges.

This is precisely the necessity for the testing role to exist and matter: lowering the threshold for others to dissent and creating space for critical thinking in the team.

As testers, we should not confine ourselves to the limits of the development lifecycle; we should actively shift testing left and participate more in earlier phases, so as to better demonstrate the value of the role.

Of course, recognizing this also means accepting the positioning of being the “bearer of bad news”. Face it calmly; a team’s path to success cannot do without such a role.

Conclusion

Those who enjoy watching historical costume dramas should be familiar that in every dynasty there was an office such as the “censor” or “remonstrance official”. As advisers who spoke truth to power, they were mostly unwelcome to emperors and ministers, yet the operation of the system could not do without this function of supervision and review.

And testers are very much like the “censors” in the system of software development.

Do not fear the “fail” on a test report; that is precisely the meaning of the testing function’s existence.

Built with Hugo
Theme Stack designed by Jimmy