The topic of John Lewis’s #innochat group discussion this week was thinking about worst case scenarios as a means to innovation, a topic broached by Kim Flum.
https://twitter.com/JohnWLewis/status/1296482541420019713:
« As I understand the principle of what Kim is asking about, it relates to the ability/power of thinking ahead to prepare ourselves through developing innovate solutions to problems that we have not yet faced. Is that roughly it, Kim?! »
https://twitter.com/kimflum/status/1296483242053378048:
« yes, as i was reading about stoicism, i was inspired by the idea of premadiatio malorum (the premeditation of evils) in terms of how we can use the idea of worst case scenarios to innovate. #innochat »
https://twitter.com/kimflum/status/1296479808025776128:
« i wanted to explore how war gaming/scenario planning could lead to innovation in the real world. #innochat meaning, can we *imagine* the worst before it happens and innovate for it? »
https://twitter.com/skap5/status/1296478101711527936:
« Transformation isn’t an analytic act, it’s a generative act. The #innovation imperative is to try more stuff. Rehearse all the time! #PerpetualBeta #ExperimentAllTheTime #Innochat »
https://twitter.com/kimflum/status/1296479232508518400:
« so many folks confuse the two processes. you can’t do both at the same time. #innochat (artist corita kent) »
https://twitter.com/kimflum/status/1296478241302224897:
« perpetual beta is genius! #innochat »
https://twitter.com/andrewceverett/status/1296490439986610178:
I’m conflicted at perpetual beta because you’re shipping unfinished product. Another way to think of it as restarting a new product life cycle at the top of the S-curve.
I was not familiar with the term perpetual beta, but later found it has an entry on Wikipedia.
https://en.wikipedia.org/wiki/Perpetual_beta:
« Perpetual beta (or the ‘banana principle’) is the keeping of software or a system at the beta development stage for an extended or indefinite period of time. It is often used by developers when they continue to release new features that might not be fully tested. Perpetual beta software is not recommended for mission critical machines. However, many operational systems find this to be a much more rapid and agile approach to development, staging, and deployment. Perpetual beta has come to be associated with the development and release of a service in which constant updates are the foundation for the habitability or usability of a service. »
https://twitter.com/JohnWLewis/status/1296484644964237313:
« To my mind, whether it’s innovation or not depends on whether the solution that we find is novel. #innochat »
Articles of Interest 