That's such a strange metric. Of course any company of a nontrivial size cannot (and should not) strive for 100% project completion. It's entirely rational to abandon / roll back some projects, or to treat an 80% completion as good enough, after reaching diminishing returns.
As for what ClearWork does - I'm sorry to say that it sounds to me like exactly the sort of employer spyware that they'd want to use to make it easier to replace employees with $CORPORATE_BUZZWORD.
The processes and tasks in scope of a project are defined by the project team and the activities to "record" as pushed to the end users who click start and stop when they are next completing that activity. We also only capture the activity data and meta data - no screen capture to risk sensitive data exposure.
The true challenge we are tackling is that projects often face substantial monetary and time related set backs from not understanding how their people actually complete their jobs - missed requirements, planning based on an idealized state, not reality, etc. This is a way for the end users to be a part of future technology their people roll out.
abrooks43•6mo ago
Everyone’s trying to redesign processes or roll out new tools—but no one knows how work actually happens across teams and systems. What's on the slides rarely matches reality.
So we built ClearWork—a lightweight browser extension + backend system that captures real user interactions (across apps like Salesforce, Workday, SAP, etc.) to give transformation leaders a clear view of what’s really happening.
Think: • Process discovery for workflows • “Flight recorder” for user journeys • Instant insight into friction, workarounds, and shadow processes
We're still early, but opening up early access to get feedback from builders, operators, and transformation geeks like us.
Would love your take on what we’ve built so far: https://www.clearwork.io
Happy to answer any questions!