|
|
|
|
|
by sctechie
4937 days ago
|
|
I'm sorry but I have to interact with non-technical managers on a regular basis. I consider it part of my job responsibilities to ensure that we are communicating using the same terminology. When I tell a client his conversions are up 35% because of some change we made before A/B testing, I need to know that he understands what that means. I didn't mean toxic as a personal slight, sorry if you took it that way. If the other person 'calls it the wrong thing', then how do you know they understand what you're talking about? I think it's worthwhile in that situation, if not necessary, to take a few minutes and define, specifically, what the terms you're using mean. I simply disagree that communication is not as important as I claim. The value you bring as a statistician is not running a z-test. Any high-school kid with a computer can go to Wikipedia and be running a z-test on some data 10 minutes later. The value comes from being able to understand the results and communicate them effectively to your clients. |
|
but I am a little worried that you call them z-tests instead of t-tests (even when using Gaussian critical values) (and, to belabor the point, I try to call them "Gaussian" critical values because "Normal" may be interpreted ambiguously by a non-technical reader, but I can usually tell whether someone I'm talking to means "normal" in a technical or vague sense).
:)