What a saturated place to inquire about. I'd like to examine non-generic meetings with discussions that go heavily into domain specific problems.
Collaboratively writing a detailed technical document (eg, academic paper, product spec) is super challenging, but pays dividends.— Geoffrey Litt (@geoffreylitt) February 9, 2021
It's the best way I know to mind-meld a group around a complex idea -- requires clear alignment from big picture framing down to tiny details.
Team environments contain lots of activities (meetings, answering questions, reports, etc) which are quite tricky because they’re *sometimes* very valuable. And that makes it easy not to notice when you’re only doing them to hide when feeling aversion to tough creative problems.— Andy Matuschak (@andy_matuschak) February 19, 2021
- Variolite for meetings
- "Design docs are one of my favourite things about software engineering"
Andy Matuschak on "listening for enablement":
But if you’re doing something original, the most interesting aspects are the ones which others—and you!—understand least well. Particularly early on, you may not be able to articulate the new element you’re reaching for very clearly. It may just sound like an unusual adverb choice or an innocuous-seeming qualifier. Others’ replies will tend to emphasize the most mainstream elements, since they may not notice or know how to react to the aspects you least understand. Such conversation will often drag you back towards the mainstream. It’s a kind of “regression to the mean” for ideas.
Great colleagues and collaborators can take more active steps to mitigate the issue. For instance, if Michael hears me talking about some idea that seems fairly banal on the surface, he’ll deliberately tug at the vague spots where I’m straining to reach past typical interpretations. This was part of a broader practice he called “listening for enablement.” My Khan Academy research colleague May-Li Khoe would respond to my poorly-understood ideas by riffing in unpredictable directions. Her sketches would often explore wildly different paths, but those vivid reactions often helped me understand my own inklings better. Unfortunately, I’m not yet sure how to avoid the regression problem when discussing ideas regularly with a broad audience.
Talk about anything with anyone and have a system that is an active participant in molding all of that information into docs, processes, automations, even apps and products. How cool would it be to have the design doc _be_ the working prototype?— Chris Granger (@ibdknox) February 5, 2021