CROs are infallible. We believe data! We trust science over opinions! We are LITERALLY never wrong, right?
Well, sometimes we may be right, but we can still be rude about it. đ«Ł And no one wants to work with that one guy who, while they may be right, has to let everyone know how right they are EVERY. DAMN. TIME.
I enlisted the help of Michael Aagaard, nicknamed "Shrek" (for very good reasons...) to explore how it is that some #CROs may actually be problematic. And how their own behavior may actually be the reason why CRO and experimentation isn't being adopted or used in an organization.
We got into:
- Messaging and tone matters. You may be right, but HOW you say it may be the difference between "let's run that test" and "I fucking hate that idea"
- You're in the wrong industry if you are "testing to be right"
- Balancing "confidence" without being "arrogant" as a CRO
Timestamps:
00:00 Episode Start
04:46 Soft Skills Which Indicate You May Be a Bad CRO
13:05 Collaboration is Key - SEEKING Out That Collaboration Is King
18:26 It's Not What You Say - It's How You Say It
26:05 Risk Tolerance IS Different for Everyone - Don't Project YOUR Risk Tolerance for Others
33:25 Shit You Need to Know: Jason Haddock (How Layoffs Impact CRO)
Go follow Michael Aagaard on LinkedIn (https://www.linkedin.com/in/michalaagaard/)! And go check out Jason's post too! (https://tinyurl.com/FromAtoBJason)
If you have listener questions, submit them at https://tinyurl.com/askfromatob for a chance to be featured too!
