A similar realization led me to finally ditch GTD a decade ago. I realized the ideal amount of chronic anxiety is not zero. The ideal inbox is not inbox zero. An anxiety prone, chronically stressed temperament is not necessarily pathological (contra Sapolsky’s zebra-ulcer thesis). It’s just an adaptation for a different environment.
If I wanted to milk this for status points, I’d say “I don’t have an anxious temperament; I’m neurodivergent and it’s actually an adaptive superpower in times of ”accelerating change”
What does a protocolized organizational map look like? One of the key items for Q3 in our process matters work is for teams to share out what they do. I’m in Europe though will share the protocol there when I’m stateside if you’re curious.
Also FWIW you’ve always presented as very cool calm and collected when we’ve interacted good sir.
If i had to reframe that question slightly, in order to elicit the protocol-based org chart, I'd ask teams two questions: What problems does your team manage? What teams do you have (productive) tensions with and why?
For lack of a better example, my go-to right now is the Ethereum Foundation’s new org chart. It’s a widely cited phenomenon that software companies org structures resemble their products. Because the EF’s “product” is a protocol, their org structure will be protocol-ish in shape
A similar realization led me to finally ditch GTD a decade ago. I realized the ideal amount of chronic anxiety is not zero. The ideal inbox is not inbox zero. An anxiety prone, chronically stressed temperament is not necessarily pathological (contra Sapolsky’s zebra-ulcer thesis). It’s just an adaptation for a different environment.
If I wanted to milk this for status points, I’d say “I don’t have an anxious temperament; I’m neurodivergent and it’s actually an adaptive superpower in times of ”accelerating change”
What does a protocolized organizational map look like? One of the key items for Q3 in our process matters work is for teams to share out what they do. I’m in Europe though will share the protocol there when I’m stateside if you’re curious.
Also FWIW you’ve always presented as very cool calm and collected when we’ve interacted good sir.
If i had to reframe that question slightly, in order to elicit the protocol-based org chart, I'd ask teams two questions: What problems does your team manage? What teams do you have (productive) tensions with and why?
Any good examples of protocols based org charts?
For lack of a better example, my go-to right now is the Ethereum Foundation’s new org chart. It’s a widely cited phenomenon that software companies org structures resemble their products. Because the EF’s “product” is a protocol, their org structure will be protocol-ish in shape