I’m hoping some of you folk will have good ideas about this stuff.
Part 1: Data structures for conversations?
Since hearing Robin Weis speak at 2017 QS conference in Amsterdam last summer, I’ve been thinking about ways to be more intentional about tracking open conversations and keeping track of conversations that I want to have with my partner.
A lot of these discussions happen over email, since that’s a nice medium for longer form, more discursive, or in depth topics. So there’s already a record of a lot of our conversation, but I still think it would be interesting to have some more structure to it. I wonder if it would work to, off the top of my head, use github issues in a private repo for this… we could have discussion back and forth, use labels, schedule things, search for topics, explicitly close topics when we agree on a resolution (or agree that it’s stalled)…
Has anyone done anything like this? How crazy (awesome) does I sound? Who keeps an actual conversation stack of their conversations with their partner? Or other tales of unusual tracking of conversations, or unusual tools / software for conversing?
Part 2: Beeminding the conversation stack (of course)
Any ideas on this? I thought at first that I’d label all the email threads with a special label and start an inbox goal for those conversations, but I don’t think that’s really quite what I want. I want to allow room for the stack to grow, so it’s not strictly a backlog problem. But I also do want to incentivize myself to keep touching base and not let old topics starve (or explicitly resolve / close them, I suppose if the topic is exhausted). So beeminding number of threads with a particular label doesn’t seem like quite the right metric, because I don’t just want to remove threads from the backlog, I want to incentivize engaging, and give credit for being responsive and stuff.