The whole concept of "grazing" - introduced yesterday - is still resonating. I've long wondered if there's a specific order to our framework. While we sense a certain logic in navigation, with the left side feeling different from the right, one can essentially move through it in a knight's-move fashion. This is because we're dealing with layers and the notion that problems are often not solved at the level where they originate.

Yes the framework has structure but it is non-directional or determent

If we are truly approaching 'future ready' as an agile way of working, instead of moving strictly top to bottom or left to right, you need to be able create your own path based on what the situation asks. I know this sounds somewhat conceptual, but it's something we've been pondering for a while now.

Levy Flight pattern Yesterday's term, "grazing," reminded me of an old study about large grazers on the savanna. This pattern has been studied and compared to other patterns, from migrants to searching for your keys. There's a kind of similarity that even Google has used as a basis for its search engine: the Lévy flight pattern. In simple terms, it suggests that we pause somewhere and search/graze in detail, then move a distance and focus in detail somewhere else. We essentially hop through an unknown space.

I think this is literally how I ultimately envision a participant navigating through our framework, through our world. Here is some more info on the Levy Flight pattern: https://en.wikipedia.org/wiki/L%C3%A9vy_flight#External_links

The Levy Flight pattern is not 'linear' but also not random (left).