Frank Zdanowski emailed the following interesting “use case” for decision mapping/bCisive:
“In my work as a project manager, I hope to use your product to build decision maps to document the thought processes of the “why” of a project during preliminary planning. This way, when [if?] we reach a crisis point in project execution where the key stakeholders ask “why did we ever commit to doing it this way?”, I can bring out the decision map to show them exactly how we got to that point. Instead of using it to deflect blame, I hope to use the map to identify where we went wrong and refine our thinking about why we chose the approach we did, where we went off the rails, and how to get back on track. Over time, I hope that this will introduce more rigorous thinking in planning.”
It’s probably more to deflect the blame off the Project Manager rather than to blame it on someone. I have published an excellent article on gate meetings that are made for the same purpose.