“Never walk away from failure. On the contrary, study it carefully and imaginatively for its hidden assets.”
Working on OctopOSS projects can be a humbling experience. There are so many tentacles that can whack you and your colleagues over the back of the head. Every project seems to have its own tentacles. Sometimes it’s only small elements of a project that fail and can be recovered from, whilst other times it’s catastrophic project failure unfortunately.
Part of the reason for this blog’s existence is to work back through past successes and failures that I’ve been involved with and study their events for the purpose of identifying and communicating their hidden assets.
My extensive risk matrix is a double-edged sword. It is a demonstration of too many failings (ie “hidden assets”) identified over my years on past OSS projects, but when looking from the alternate perspective, this matrix is a valuable asset to help mitigate those risks for future customer projects.
What are the mechanisms that you use to find hidden assets of your own or others’s fails?