A recipe for RCA meetings. 1. Include everyone affected in the RCA meeting and preparation. 2. Prepare a timeline *before* the RCA meeting. 3. Bring a technical analysis to understand possible causes. 4. Start with the client impact. 5. Ask why, ignore the who (blameless RCA). 6. Poll all meeting participants to identify all possible causes and problems. 7. This should feel uncomfortable; If not, you are doing it wrong. 8. Identify *proportionate* follow-up tasks and get those task *scheduled* within a week (or done, if urgent). Ref: https://podcasts.apple.com/es/podcast/troubleshooting-agile/id1327456890?i=1000654912905