修复状态更新 - 我们的宣言
我们解决的问题是组织内部的摩擦和可见性问题。在每一个层级和每一次会议中，你会越来越远离真正了解发生了什么。我们构建了一款工具，让任何人只需点击一个按钮，就能看到项目的实际进展。无需与人工智能争论，也无需依赖甘特图进行推测。只需一个合理的人类解释。
当然，我们一开始不会达到完美。我们专注于做好一件事，让单个项目经理或主管点击“更新”，并以他们期望的方式获取更新。这意味着我们需要“了解”他们的项目。为此，我们正在使用人工智能。
我们并不指望用户在我们的工具中启动项目或调整他们的工作。我们会消化所有信息，并提供状态更新。这意味着我们将工具结构化，以便像项目经理一样理解事物。有些人可能会说这意味着我们无法完美适应他们的项目或程序。对此，我想说：“你并没有你想象中那么独特。”这意味着人工智能的规则和技能会自动调整，将信息分类。我们一开始并不复杂，只有Jira集成和文档上传功能。
当然，仍然有调整的空间。通常这些调整会在人工智能聊天中进行，而在我们这里则通过规则和技能以及结构化提示来实现。但用户对此并不关心。相反，当状态更新返回时，他们会调整一两次。然后，我们在后台调整规则，以便下次应用。因此，我们的准确率起初为80%，但每次使用后都会变得更好。而且，嘿，80%的准确率对于你的项目、你的混乱格式和语气来说已经相当不错了。
那么，最终结果是什么？对最终用户来说，这意味着打开工具，点击“运行”，看到它转动一两秒钟，然后获得一个可以直接使用的状态更新。我们提供的服务是将手动整理文件和项目以获取状态更新的过程，转变为一个简单的“一键获取状态更新”。
简而言之，想象一个这样的世界：当有人问“有什么更新”时，你只需按下一个按钮，他们就会离开，或者给你所需的信息以便继续。这就是我们的目标。
我们的愿景是什么？我的意思是，如果你曾在大公司工作，我们相信在制作状态更新时消除繁琐的艺术中有很大的商机。为此，我们的整体愿景是解决公司中耗时最多的项目管理环节。这意味着一开始的状态更新，但之后还有更多内容（例如项目章程、RACI等）。
想试试我们的Alpha版本吗？请通过[email protected]或[email protected]与我们联系。
查看原文
Our problem we solve is the issue of organizational friction and visibility. With each layer and each meeting, you get further from really knowing what is going on. We build a tool that lets anyone at the click of a button see what is actually going on with a project. No arguing with an AI. No divining with a gantt chart. Just a reasonable human explanation.<p>Of course, we won’t hit perfection right out the gate. We’re focused on doing one thing right, letting a single program manager or director hit “update” and getting an update in the way they expect. This means we need to “know” their project. To do that, we’re using AI.<p>We don’t expect users to start projects in our tool or to adjust anything they do. We digest everything and burp up status updates. This means we structure our tool to understand things like a program manager would. Some might say that means we won’t fit their projects or programs perfectly. To that, I say, “you’re not nearly as original as you think you are.” This means AI rules and skills out the gate that self adjust as it sorts things into categories. We aren’t fancy out the gate, we have a Jira integration and a document upload.<p>Now, there are room for tweaks. Where these normally live in an AI chat, these live in rules and skills for us along with structured prompts. But, users don’t care about that. Instead, as status updates come back, they tweak things once or twice. We then adjust the rules on the backend so they get applied next time. So, we start at 80% accuracy, but we get better every single time they use it. And, hey, 80% right on your projects,your janky format, and your tone is pretty good.<p>So, what’s the end result? To the end user, it means popping on to the tool and hitting “run” and seeing it whirl for a moment or two before they get a status update they can jam where they need it. Taking things from either manually sorting files and projects to get status update or the more modern version of corralling, begging, and finally compromising with Claude output to a simple “one-click, one status update” we’re offering.<p>In short, imagine a world where when someone asks “any updates,” you hit a button and they go away and/or give you what you need to continue. That’s it.<p>What’s the vision here? I mean, if you’ve been at a big company, we certainly think there’s a killing to be made in the art of cutting out the baloney in producing status updates. To that degree, our whole vision is to attack the project management pieces taking the most time for people in the company. That means status updates at the beginning, but many more things later on (looking at you project charters, RACI, and such).<p>Want to try our alpha? Reach out to us at [email protected] or [email protected]