【Hacker News搬运】启动HN：补丁（YC W24）-基于提要而非聊天的团队沟通
-
Title: Launch HN: Patchwork (YC W24) – Team communication based on feeds, not chat
启动HN：补丁（YC W24）-基于提要而非聊天的团队沟通
Text: Hey HN! We’re Nikki and Dhruhin, co-founders of Patchwork. We’re building a communication tool for teams that lets you stay in sync while at the same time staying in flow. It’s centered around a ranked feed instead of chat.<p>Edit: as requested, here are some screenshots: - Feed:
<a href="https://imgur.com/a/bvH7ypQ" rel="nofollow">https://imgur.com/a/bvH7ypQ</a> - Post Creation: <a href="https://imgur.com/a/HENe15A" rel="nofollow">https://imgur.com/a/HENe15A</a>, Chat: <a href="https://imgur.com/a/MVyVykY" rel="nofollow">https://imgur.com/a/MVyVykY</a>.<p>Over the last several years, we’ve noticed that it’s getting increasingly difficult to stay in flow. We believe it’s because chat (i.e. Slack, Teams, and similar tools) has evolved into something it wasn’t designed for. Chat originally served as a way to free us from our desk by giving us the safety that if we were needed for immediate matters, people could reach us. Now it’s become a dumping ground for all communication: daily updates, product and engineering discussions, announcements, etc. Both of us still reminisce about the days of in-office work, before Slack became mainstream, where everyone abided by the headphone rule—the unwritten pact that headphones meant someone was in deep work and not to bother them unless you really needed to. Compared to then, the onus has now shifted to be on us to determine which chats are urgent and should take us out of flow vs. which messages can be responded to later. It feels like the very tool that was meant to liberate us instead made us beholden to its pings.<p>Patchwork is our attempt to solve this problem by shifting the primary communication model from group chats to feeds. Posts are made in relevant groups and each team member has a home feed personalized to them.<p>The feed algorithm evaluates each post's relevance and urgency based on a bunch of factors, including the post’s content, user's role, ongoing projects, and recent interactions. Our goal is to maintain a high signal-to-noise ratio with our feed’s algorithm so we can surface the most important information first. When you’re not in flow or in between meetings, you can check the feed to stay in sync.<p>There have been feed-based work communication products before, but they’ve often overlooked the fact that writing a post has more friction than writing a chat message, which is why people often revert back to doing everything over chat. We’re combating this by using LLMs to create a better writing experience (ie. generate title and tl;dr, simplify selected content, change the tone, etc.).<p>As a product team ourselves, we know that much of our work happens on different platforms. We’re building integrations with the likes of Github, Linear, Figma, GSuite etc. Having all of this activity from different platforms also rolling into our feeds allows us to stay in sync with all the different work being done on our team instead of having to check various sources of data.<p>Lastly, we do have chat on the platform, but chat looks and feels like chat. It’s meant to be used for immediate needs.<p>Here’s a demo of the product: <a href="https://www.youtube.com/watch?v=SA3rmSjNjDw" rel="nofollow">https://www.youtube.com/watch?v=SA3rmSjNjDw</a><p>Since it’s a team communication product, it's hard to use it in single player mode, so we don’t have a “try it now” link to jump straight in. But you’re welcome to email us at hackernews@atpatchwork.com and we’ll onboard your team.<p>The product is still early with a basic feed, a few integrations, and simple LLM assisted post creation, but the main flow is already there, so if the message resonates with you, we’d love for you to give it a try.<p>More importantly, we’d love to hear your ideas about team communication and getting it back to working <i>for</i> people, not <i>at</i> them!<p><a href="https://www.atpatchwork.com/">https://www.atpatchwork.com/</a>
嗨，HN！我们是Patchwork的联合创始人Nikki和Dhruhin。我们正在为团队构建一个沟通工具，让您在保持同步的同时保持流畅。它以排名提要为中心，而不是聊天<p> 编辑：根据要求，这里有一些屏幕截图：-Feed：<a href=“https://；/；imgur.com/：a/！bvH7ypQ”rel=“nofollow”>https:///；imgur.com/；a；bvH7ypQ</a>-后期创建：<a href=“https://；/；imgur.com/：a/！HENe15A”rel=“nofollow”>https:///；imgur.com/；a；HENe15A</a>，聊天：<a href=“https://；/；imgur.com/：a/！MVyVykY”rel=“nofollow”>https:///；imgur.com/；a；MVyVykY</a><p> 在过去的几年里，我们注意到保持流畅变得越来越困难。我们认为这是因为聊天（即Slack、Teams和类似的工具）已经演变成了它不适合的东西。聊天最初是一种让我们从办公桌上解放出来的方式，它给了我们一种安全感，即如果我们需要处理紧急事务，人们可以联系到我们。现在，它已经成为所有沟通的垃圾场：日常更新、产品和工程讨论、公告等。我们两人都仍然回忆起Slack成为主流之前的办公室工作日子，在那里，每个人都遵守耳机规则——这是一个不成文的约定，即耳机意味着某人正在深入工作，除非你真的需要，否则不要打扰他们。与那时相比，现在的责任已经转移到我们身上，决定哪些聊天是紧急的，应该让我们摆脱困境，哪些信息可以稍后回复。这感觉就像是这个本应解放我们的工具，却让我们受制于它的ping<p> 补丁是我们试图通过将主要通信模式从群聊转移到订阅源来解决这个问题。帖子在相关的小组中发布，每个团队成员都有一个个性化的主页<p> 馈送算法评估每个帖子；基于一系列因素的相关性和紧迫性，包括帖子的内容、用户；的角色、正在进行的项目和最近的互动。我们的目标是通过提要的算法保持高信噪比，这样我们就可以首先显示最重要的信息。当你不在会议中或在会议间隙时，你可以查看订阅源以保持同步<p> 以前也有基于提要的工作交流产品，但他们经常忽略这样一个事实，即写帖子比写聊天信息更有摩擦，这就是为什么人们经常回到通过聊天做所有事情。我们正在通过使用LLM来创造更好的写作体验（即生成标题和太长了，读不下去了，简化所选内容，改变语气等）<p> 作为一个产品团队，我们知道我们的大部分工作都发生在不同的平台上。我们正在与Github、Linear、Figma、GSuite等建立集成。将来自不同平台的所有这些活动也纳入我们的订阅源，使我们能够与团队中正在进行的所有不同工作保持同步，而不必检查各种数据源<p> 最后，我们确实在平台上聊天，但聊天看起来和感觉都像聊天。它是用来满足急需的<p> 以下是该产品的演示：<a href=“https://；/；www.youtube.com/！watch？v=SA3rmSjNjDw”rel=“nofollow”>https:///；www.youtube.com/；看v＝SA3rmSjNjDw</a><p>由于它是团队通信产品；很难在单人模式下使用它，所以我们没有“立即尝试”链接直接进入。但欢迎您发送电子邮件至hackernews@atpatchwork.com我们将加入您的团队<p> 该产品还处于早期阶段，有基本的提要、一些集成和简单的LLM辅助后期创建，但主流已经存在，所以如果信息与您产生共鸣，我们希望您尝试一下<p> 更重要的是，我们很想听听您关于团队沟通的想法，并让它回到<i>为</i>人工作，而不是在</i>为他们工作<p> <a href=“https://；/；www.atpatchwork.com/”>https:///；www.atpatchwork.com/</一Url:
Post by: shahflow
Comments:
phailhaus: From the video:<p>> The homefeed is ranked <i>specifically</i> for me, so it shows me what it thinks is most important for my work first<p>How can it really know this? It feels like this could fall in the trap that social media has, where there is no common shared experience because everyone has a unique feed based on opaque rules. Not only does this lead to fractured bubbles, but it's hard to know what you're missing, why, and how to "train" the algorithm to do better.<p>I agree that chat solutions tend to overwhelm users, but there is a huge advantage to everyone being able to go to a channel and see the same things sorted by time. Does Patchwork still support viewing a feed chronologically?
phailhaus: 来自视频：<p>>；homefeed是专门为我</i>排名的，所以它首先向我展示了它认为什么对我的工作最重要<p>它怎么能真正知道这一点？感觉这可能会落入社交媒体的陷阱，因为每个人都有一个基于不透明规则的独特订阅源，所以没有共同的共享体验。这不仅导致破裂的气泡；很难知道你在做什么；re失踪，为什么以及如何"；列车“；算法做得更好<p> 我同意聊天解决方案往往会让用户不堪重负，但每个人都能进入一个频道，看到按时间排序的相同内容，这是一个巨大的优势。Patchwork仍然支持按时间顺序查看提要吗？
Brajeshwar: Ideas seem to come when their time has come, irrespective of who conjures them and/or executes them. The new waves of Team Chat evolution are interesting to watch.<p>Recently, Manish and his team introduced Struct[1] in their Show HN, which was a breath of fresh air in a forum-ish avatar. It is modern, sensible, and appropriate for today.<p>Things will eventually change, and we will move on to the next. PatchWork looks interesting. Have you thought of your pricing plan? Best of luck to the team.<p>While I'm in an ideation mode, I think team chats might be more effective if treated as ephemeral, just like Text or WhatsApp. They are either to be acted on or moved to a more permanent format if they deserve to be. There was a video-conferencing tool that does just that: fire up a specific URL for a room and invite whoever you want and talk, then bye-bye. But right now, team chats are trying harder and harder to replicate how people converse in person, like in a meeting.<p>I do hope these new waves succeed; people like to use it and use it -- I usually can get used to any tooling or patterns that the others are comfortable with.<p>1. <a href="https://struct.ai" rel="nofollow">https://struct.ai</a>
Brajeshwar: 想法似乎是在时机成熟时出现的，而不管是谁变出来的；或者执行它们。团队聊天发展的新浪潮非常有趣<p> 最近，Manish和他的团队在他们的Show HN中介绍了Struct[1]，这是一个论坛式化身中的新鲜空气。它是现代的、明智的、适合今天的<p> 事情最终会改变，我们将进入下一个阶段。PatchWork看起来很有趣。你有没有想过你的定价计划？祝球队好运<p> 而I；我处于构思模式，我认为如果像文本或WhatsApp一样，将团队聊天视为短暂的，可能会更有效。如果他们值得的话，他们要么被采取行动，要么被转移到一种更永久的形式。有一种视频会议工具可以做到这一点：为一个房间打开一个特定的URL，邀请你想要的人聊天，然后再见。但现在，团队聊天越来越难复制人们面对面交谈的方式，比如在会议上<p> 我真的希望这些新浪潮能够成功；人们喜欢使用它——我通常可以习惯其他人熟悉的任何工具或模式<p> 1<a href=“https://；/；struct.ai”rel=“nofollow”>https:///；结构.ai</a>
gwbas1c: FYI: Your voice in the video is very quiet. You really need to normalize / boost / compress it.<p>One thing that's easy to forget is that technology does not solve political / social problems. The big problem is that far too many people think they can run around and interrupt people at any time for any reason, and no piece of technology will solve this. If you send them to a tool that breaks their ability to interrupt, then they will figure out a way to bypass the tool.<p>I think it's more important to advocate publicly to be conscious of how we interrupt each other. It's very important that interrupters recognize their behavior.
gwbas1c: 仅供参考：视频中你的声音很安静。你真的需要规范化/；boost#x2122；压缩它；人们很容易忘记的是，技术并不能解决政治问题；社会问题。最大的问题是，太多的人认为他们可以在任何时候以任何理由到处乱跑并打断人们，而任何技术都无法解决这一问题。如果你把它们发送到一个破坏了它们中断能力的工具，那么它们就会找到绕过该工具的方法<p> 我认为；更重要的是公开提倡要意识到我们是如何打断对方的。它；打断者认识到他们的行为是非常重要的。
eightnoteight: people who need to monitor a lot of channels are usually in senior/leadership layer, but one technique usually they follow is focus on a specific problem and consequently some set of specific channels for few weeks or a month and shift focus as the project/task changes<p>how are you thinking about capturing such dynamic decisions to choose focus area, happening outside the communication tool - like zoom or meetings etc,... algorithm can be real-time but even with data points from meetings etc,... can it be made in such a real-time?<p>instagram feed algo is pretty real-time but the number of unique behaviours or behaviours to people ratio is quite low. but I'm guessing in a work environment that ratio or the unique behaviours would be too high for the algo to react quickly, right?
eightnoteight: 需要监视许多频道的人通常处于高级的；领导层，但他们通常遵循的一种技术是在几周或一个月内专注于特定问题，并因此专注于某组特定渠道，并随着项目的进行而转移注意力；任务变化<p>你是如何考虑捕捉这种动态决策来选择重点领域的，发生在沟通工具之外的，比如缩放或会议等，。。。算法可以是实时的，但即使有来自会议等的数据点，。。。它能实时制作吗<p> instagramfeed-algo非常实时，但独特行为的数量或行为与人的比例非常低。但是I-；我猜在工作环境中，这个比例或独特的行为会太高，算法无法快速做出反应，对吧？
timwis: One of the best ideas I’ve heard for having Slack without the pressure to keep up with it is to configure it to delete messages after a short time period. This lets you keep the live chat going with those who are around, but people know to put important notices they want others to read into some other outlet.
timwis: 我听说过让Slack在没有压力的情况下跟上它的最好想法之一是将其配置为在短时间后删除消息。这可以让你与周围的人保持实时聊天，但人们知道要把他们想让别人阅读的重要通知放到其他渠道。