Original Summary

Every team I've worked on has had the same problem: someone makes a call in a meeting or a DM, nobody writes it down, and three weeks later two people are arguing about what was actually decided (or why). So I built Doorlog, a Slack bot for logging decisions as they happen, right where the conversation already is. The core idea is borrowed from Amazon's "one-way door vs two-way door" framework: when you log a decision, you tag whether it's reversible or not. Reversible ones get an actual Reverse button with a reason field, so the history stays intact instead of just getting deleted and forgotten. Every decision also gets an owner (DRI), so there's no ambiguity about who's accountable. Right now it does: /log-decision: modal to capture a decision, owner, and rationale /list-decisions: last 5 active decisions in the channel /search-decision: pull up any past decision by keyword Reverse / delete with an audit trail (who, when, why) Stack is pretty boring on purpose: Node + Slack Bolt, Supabase for storage, deployed on Render. It's still early, I'm running it in my own workspace and a small group testing it out. I'm not trying to hard-sell here, genuinely just want to know: is this a problem you've actually hit, or is it a "nice to have" that nobody will bother using in practice? Would love blunt feedback, especially if you've tried something like this before and it didn't stick. Happy to drop a install link in comments if anyone wants to poke at it.   submitted by   /u/Infamous_Review_9700 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/1 02:21:39