To me this is critical for both Engineers and folks running a business. We all make mistakes, I make loads and it’s part of the job. It is what allows us to continue. We end up funded, we end up moving forward and we must. As we progress the team strengthens and that is a good thing, but it’s all built on errors, just like any code base is.
It’s like fishing and with every cast that does not catch a fish being seen as bad management of the fisherman, regardless how many fish he catches. To me any project is like that, any job is like that, otherwise it’s a very repetitive simple job that a robot should be doing.
Introspection and criticism work well when founded. Public forums make that difficult, but it is important. The key, to me, is read between the lines, get a general feeling of consensus on many things, but then (and this is the hard part), figure out a route. That route may not be obvious (close offices, set up a loan scheme, 4 day week, flatter structure etc.) and may not work, so we go another route 
(cast the line a little bit more down river etc.)
It’s about the team in projects like this, real true collaboration and tough thinking. The leadership does make a difference and that has changed a lot recently, an awful lot. We will see what 2020 brings.