May - when spring really starts for many of us in the 'north'. So, just a short blog - more of a request.
This week, instead of looking at what's not working all the time, try 2 times, just 2, to find what's working, why it's working and how you can make that happen more. Try this at work, at home, wherever you want - but please, try it - just twice, that's not asking a lot....
“Find what’s working & why! #BrightSpots”
Let me know how it goes! Feel free to share!
So often, when a project or product doesn't go well or fails, organizations do "post-mortems" - they go over what went wrong, why, sometimes rushing to blame people first instead of looking at processes.
What if we started doing pre-natals instead of post-mortems? What if our cross-functional teams, at various steps in project or product development, examined why, what and how they were doing, what was working and why, what wasn't and why, and discussed all the things that could go wrong from that point on and why they could go wrong and how they could mitigate or eliminate those risks? Then they could prioritize all that based on probability and possibility, make sure they are on top of those and do this regularly throughout development.
This isn't a fail-safe, but chances are a lot of problems could be caught, corrected and learned from before they happen and the more you do pre-natals, the better you'd get!
Worth a shot isn't it?
Thank you Irene Becker for sharing your blog with me! What if we started doing Tree Cause Analysis!
"Root Cause Analysis (RCA) – sounds like a blast doesn’t it? We can all agree it’s important and should be a habit we adopt in our organizations, but few of us do it. Why? It takes time, self-reflection (personal and organizational), analysis and…. it’s focused on the negative, what didn’t work, what didn’t go well. Makes you wonder if Root Cause Analysis isn’t an oxymoron." Read on....
Deb is here to reveal to organizations their beginner's mind while giving them the tools to execute.
