When projects don’t stack: the fine art of understanding mistakes
By Mark Di Somma When a project doesn’t meet expectations, I’m fascinated by what gets asked, who does the asking and what, if anything, emerges as the key learning. My view is that we should treat projects that don’t go to plan not so much as wreckages but rather as breakages: they occur when the picture we have in our minds of what will occur shatters, splits or simply falls a different way than we had led ourselves to expect. That can mean something as elemental as having the wrong picture in the first place – or it can come down to developments that pulled things out of alignment. Faced with picking up the pieces, here are 22 questions I use to try and get to the truth, and to move on: 1. What exactly went wrong? (What did not happen?) 2. How “wrong” was it – in the sense that how much did it differ from what we had told ourselves would happen? 3. How realistic was our prediction in the first place? (How …