Effective Vs. Efficient in QC

 

Here is the definition from dictionary:
Effective (adj.): Adequate to accomplish a purpose; producing the intended or expected result.
Efficient (adj.) Performing or functioning in the best possible manner with the least waste of time and effort.

There is a saying "Being effective is about doing the right things, while being efficient is about doing the things in the right manner."  Efficiency and effectiveness are improvement to a process. However, to some people, they may mean "almost" the same thing. I sometime mix the meaning and usage when using them too.

We can be an efficient QC if we can do the same with less.
We can be an effective QC if we can do more with the same.

We can be an efficient QC if we emphasize on the intended time to produce the same outcome.
We can be an effective QC if we emphasize on the intended outcome with the same time.

We can be an efficient QC if we let the machines set up our environment and run our test.
We can be an effective QC if we let the human do the analysis and investigation.

We can be an efficient QC if we constantly response to change.
We can be an effective QC if we religiously follow a plan.

We can be an efficient QC if we trust more on Process and Tools.
We can be an effective QC if we trust more on Individual and Interaction.

We can be an efficient QC if we automate as many of our test cases as possible.
We can be an effective QC if we could detect more bugs early during the development cycle.

We can be an efficient QC if we are able to test the smaller incremental code changes.
We can be an effective QC if we are able to detect and fix the bug from the incremental code changes.