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

栏目: IT技术 · 发布时间: 6年前

内容简介:What is the best way to have careful, deep, written discussions among distributed teams? Are there tools meant for this? Would something like a BBS work. If so, are there good modern options?We use distributed teams. We communicate using a mix of email, Sl

What is the best way to have careful, deep, written discussions among distributed teams? Are there tools meant for this? Would something like a BBS work. If so, are there good modern options?

We use distributed teams. We communicate using a mix of email, Slack, and Zoom. Our work involves lengthy discussions and deep dives into complex issues. This type of 'deep discussion' benefits from carefully written arguments and counterarguments.

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.

Slack is too chatty. Other chat-based solutions are the same. I've never seen it work for this type of 'deep discussion.' Conversations get scattered across channels and threads within channels. Maybe we're using it wrong. To me it's the worst way to encourage deep discussion.

Zoom, calls, and in-person meetings are hit or miss. The advantage is they seem to cut to the chase on simple issues. But for deep discussion, they often go nowhere. They favor speaking ability. No one prepares enough. Instead of careful thought and discussion, you get hot takes. A lot of our discussion benefits from going away to gather evidence or think more. Rarely is there a need for synced discussion. And there's never enough time.

I've tried to find off-the-shelf solutions. A simple, old-fashioned BBS seems best. It breaks things into the right unit of discussion. It works for short- or long-form discussion. It creates a coherent timeline of discussion, etc.

I worry that without the bells and whistles of a modern app, getting the team to use it will be a challenge. It'll be viewed as a stale company discussion board. A lot of options I've looked at have clunky interfaces and tough learning curves for what should be super simple and intuitive.


以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持 码农网

查看所有标签

猜你喜欢:

本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们

高效团队开发

高效团队开发

[日] 池田尚史、[日] 藤仓和明、[日] 井上史彰 / 严圣逸 / 人民邮电出版社 / 2015-7 / 49.00

本书以团队开发中所必需的工具的导入方法和使用方法为核心,对团队开发的整体结构进行概括性的说明。内容涉及团队开发中发生的问题、版本管理系统、缺陷管理系统、持续集成、持续交付以及回归测试,并且对“为什么用那个工具”“为什么要这样使用”等开发现场常有的问题进行举例说明。 本书适合初次接手开发团队的项目经理,计划开始新项目的项目经理、Scrum Master,以及现有项目中返工、延期问题频发的开发人......一起来看看 《高效团队开发》 这本书的介绍吧!

JS 压缩/解压工具
JS 压缩/解压工具

在线压缩/解压 JS 代码

RGB CMYK 转换工具
RGB CMYK 转换工具

RGB CMYK 互转工具