Testing Ask Me Anything: Managing Risk with Alex Schladebeck

Description

1. How do you define a risk?
2. How do you convince/lead/influence stakeholders that exploratory testing can cover the risks?
3. How do you tackle 'known' risk? How do you find 'unknown' risks?
4. How do you assure your team that you've covered risk with your test approach to the best of your resources/time allow?
5. How do you deal with scenarios where identified risks might have detrimental outcomes but are ignored by devs, BA and POs.
6. Should the whole team be coming up with risks or does it completely rely on the testers?
7. If risks come true, how to help the team overcome the blame game and to start a root cause analysis?
8. Having raised the risks, how do you deal with management/business want to deploy at all costs?
9. How to ensure that missing/forgotten risks, will not be forgotten on the next occasion. Any tips on methods or tools?
10. Here's your segway - tell us more about microheuristics!
11. Do you deal with self-blaming, when you could not find risk earlier before release? I am asking, because I catch myself doing this often 
12. How can you identify when you're being too stubborn?
13. How do you convince people that long-term risks (something that will really bite us in the future) cause as much impact as a short-term show-stopper?
14. I see exploratory testing as Testing Mindfully. Do you see a link between Exploratory Testing and mindfulness?