After a Failure, Revert to the Last Known Working State

In this article I share some reflections on how to deal with failures when working in complex projects. I borrow ideas from optimization problems and software development. Then, I apply them to the different stages through which projects evolve.

The secret is to ask why as often and as many times as needed in order to identify the moment in which the project's path diverted from the expected one. Not all paths lead to the same outcome, and some can prove to be future dead ends.

The earlier we can revert to the last known working state, the quicker we'll be able to recover. Failures have an emotional toll that must not be overlooked. Loosing motivation is right behind the corner.

You can read the entire article on the following link:


Want to receive more content like this in your inbox?