请问HN：你们团队是如何保持UI/用户流程文档的更新的？
我小型的工程团队经常收到来自运营、客服和合规部门的用户流程文档更新请求。这些请求并不总是简单地说“这个过时了，可以更新吗？”更多时候是“这个还是最新的吗？”这同样需要花时间进行审核和核对。我们感觉运营团队似乎从未对他们拥有的入职和客户操作指南材料的最新性感到自信，因此我们花费大量时间创建和/或审核用户流程文档，而这些文档很快就会变得过时（即使只是稍微过时）。
还有其他人遇到这种情况吗？也许我们只是没有足够关注这个问题？有没有什么推荐的工具或方法来处理这个问题？
查看原文
My small engineering team gets a bunch of requests for user flow documentation updates from ops/customer service/compliance. The request isn't always just 'this is out of date, can you update it?' it's often 'is this still up to date?' which still requires taking the time to review/double-check. It feels like our ops teams don't ever feel confident that they have up-to-date materials for onboarding and customer how-tos, and we spend a bunch of time creating and/or reviewing user flow docs that quickly go out of date (even if only slightly).<p>Anyone else deal with this? Maybe we're just not on top of it enough? Any favorite tools or approaches for handling it?