Asteroid Field Navigation

A clergy friend posted a nice thought this morning that got me pontificating about the Asteroid Field again. (Not that it takes much to get me to pontificate.)

He wrote:

"When you are organizing a new kind of community you will make mistakes. Admitting when you are wrong is essential to successful organizing. Self awareness is healthy. But like any community the main thing is to have fun together and git 'r done. For my money this means foster creativity, celebrate liminality, open source crowd source strong networks, and grow this frickin' church. Spirit willing that is."

I replied:

"Count me in. And FWIW, I suggest pushing back even harder on the assumption that we shouldn't make "mistakes." Embedded in the notion of mistakes is the idea that a correct path exists that you cold, theoretically, follow correctly. Like a trail map through the mountains that you could deviate from by a mistake in navigation. Much of our context no longer even allows for the possibility of a map, because there is no terrain. We navigate the asteroid field now. There can be no map, and if you try to write one you'll get hit because you sat still too long while drafting it. In fact, I'd say that the most common "mistake" in our context is just that: sitting still too long. The only chance at survival (not to mention progress) is *constant movement and course correction.* Orient, Act, Repeat.

"As a side note... OAR navigation works much better with very small teams, I think. Taking a Star Destroyer into the asteroid field is lunacy. Going in with a TIE fighter or the Falcon is pretty darn risky... but survivable!"