Scaffolds are helpful and sometimes necessary. Example: To understand and eliminate costly dependencies, you’ll need to observe those dependencies. To accomplish that, you might set up an intricate system to specify and view dependencies across the organization.
Not product related, but a very interesting exploration of our relationship with scaffolding (in an urban context) can be seen in https://www.hbo.com/how-to-with-john-wilson/season-1/2-how-to-put-up-scaffolding - maybe interesting from another angle. I appreciated how both of you reflect on how scaffolding reflects our systems' vulnerability and our ways to deal with it.
I like this although it is using a fairly reductionist view of scaffolding. Scaffolding is temporary, but that doesn't mean that it always needs to be removed. Expanding the typology of scaffolds can make this even more powerful. See here https://cynefin.io/wiki/Scaffolding
Not product related, but a very interesting exploration of our relationship with scaffolding (in an urban context) can be seen in https://www.hbo.com/how-to-with-john-wilson/season-1/2-how-to-put-up-scaffolding - maybe interesting from another angle. I appreciated how both of you reflect on how scaffolding reflects our systems' vulnerability and our ways to deal with it.
I like this although it is using a fairly reductionist view of scaffolding. Scaffolding is temporary, but that doesn't mean that it always needs to be removed. Expanding the typology of scaffolds can make this even more powerful. See here https://cynefin.io/wiki/Scaffolding
Agreed. I tend to take the reductionist view as a start to ease people into an idea.
I can probably learn something from that a approach.
Would be good to hear or be pointed towards any thoughts on SaFE.