We talk an awful lot about what we should be testing, is it copy, landing pages, an image here or there? And let’s be honest, we get all excited.
Then we get onto the big question,“how should we test that?”
You know what to do, you’ve got the growth mindset down – but – it turns out the impact you dreamt is a project plan, a missing team member, a quarter, or a development cycle away. Slightly less excited now.
You still get sign off, you’ve got it all figured out, you are testing this asset and that asset, and you’ve gotten a good idea how. Here’s a biggie though – who’s going to do it? Is there capacity? Is there a cross functional appetite? Is this even your responsibility?
There are many old adages about tests failing and succeeding, as well as more than a little advice around what to do about them from there.
The reality is though, most tests never failed, never succeeded; they were never even tried. Why you think, why you?
Oh well. You barely have time to do your own job, you didn’t want to do it anyway, it’s not your fault, it isn’t even your problem.
This talk will help you navigate the vague, complex, often impenetrable world of roles and responsibilities so that thing you wanted to change, that problem that wasn’t even yours, that dream you dreamt, gets off the starting blocks.
Find your A Team, get that rubber on the road – and get where you are destined to go.