I’m experimenting with pattern language to describe our next project. The second sentence of 3.4 feels like the right level. Hopefully, this conveys trust to people “walking the land” to make a call when they implement the relationship Vs ambiguity. I’m still calibrating .
In trying to instill this ethos I’ve been saying, “maker’s choice” to indicate as long as the relationship is satisfied, do what feels right (vs trying to predict upfront what will feel right). I’m finding this is where Shape Up and Pattern Language work beautifully together.
I’ve a long way to go to sharpen my pattern language/shape up technique but so far it’s been useful. ICYMI: Here’s the video of RJS talking about pattern language for a specific feature in BC4 Case Study: Shaping "Introductions" for Basecamp 4 and Writing a Pattern Language on Vimeo