Live data from Hacker News

How do you have deep, written discussions with your teams?

news.ycombinator.com

11–20 of 30 posts

Re: How do you have deep, written discussions with your teams?

#11
> Emails often start fine. Someone sends a well structured, well written argument. The first few replies will be strong. But then it diverges into a mess of threads that are hard to follow. People resort to color-coding their responses in-line, etc.

This is the worst. "Answers in bold" -- then they forget to bold one. Or "Answers in ALL CAPS." Too easy to leave people off or some jackass gets added.

Re: How do you have deep, written discussions with your teams?

#14
Slack threads seem to work just fine in my experience. Not uncommon for a meaty subject to reach 80+ replies from 10 different people. Usually finish it off with a Zoom call once everything has been laid out and it's time to decide on actions items, if they haven't been decided already.

Re: How do you have deep, written discussions with your teams?

#15
We use Discourse for all complex conversations that can happen asynchronously (meaning not urgent) and we want to capture/document decisions for. Discourse is also great as internal knowledge base. Moving this sort of comms out of Slack has also made Slack better for us, as there is less FOMO and thus more deep work.

Re: How do you have deep, written discussions with your teams?

#16
(Obviously biased.)

So, instead of using tools primarily designed for chatting and commenting, you could use a tool specifically designed for the facilitation, capturing and representation of complex arguments.

We have spent the past 8 years building just such a tool, it’s called Kialo (https://kialo.com). It’s nowhere near as perfect as we would want it to be, but it gets the job done nicely.

In a nutshell, Kialo is an argument tree on steroids, with claim/comment separation, voting, claim multi-linking and switching of user perspectives, for single and multi thesis arguments.

Discussions can be real-time or async, private or public and worked on via desktop or mobile browser.

Here is a discussion Ethereum did whether they should use Kialo: https://kialo.com/28996 (103 claims)

And as an example of a multi thesis debate, have a look at this US politics one: https://www.kialo.com/24431 (>1k claims)

Two months ago we launched Kialo Edu (https://kialo-edu.com), our dedicated site for educators, as we wanted to build some extra functionality for them, additionally to giving them a more controlled environment without the public discussions.

We plan on releasing a custom site with additional decision-making features for teams and organizations soon (drop us a mail if you want to be notified support@kialoXXcom), until then, feel free to experiment/use kialo.com.

All feedback is welcome.

Re: How do you have deep, written discussions with your teams?

#19
Our team recently started using Notion for similar reasons. We all heavily use Google Doc’s but sending a link to a read-only or comment enabled doc gets messy for discussion very quickly.

Notion enables you to embed any number of Google docs along with other media: screen captures, screenshots, etc.

The trick is creating a documented process to moderate the discussion.

Jury is still out on long term viability as a tool, but we’re super happy with it so far.

Re: How do you have deep, written discussions with your teams?

#20

Basecamp. Their product is designed to make long-form written communications enjoyable/easy. I even wrote a blog post about what they have to say: https://blog.pixelic.io/jason-fried/

We use Trello and GDocs (slack only for shallow stuff). Curious how Basecamp is different in terms of discussion threads. trello seems fine, but something is a bit weird when discussions are deeper or longer. I can’t exactly put my finger on it, that’s why I wonder how it compares to Basecamp
Post reply on HN