| Wow,, your comment really resonated with me.
There’s a lot of insight in how you framed it. I’ve actually been thinking about this as primarily a technology problem and, somewhat embarrassingly, I’m building something to try to address it. When teams talk constantly across chat, calls, and meetings, a lot of the real work gets buried in the noise. Decisions are made. Tasks are implied. Commitments are spoken out loud and then they dissipate. What we’re building is a system that extracts only the actionable parts from those conversations, turns them into tickets, assigns them automatically, and in some cases even lets AI execute the task directly. Humans do what only humans should do. AI handles what can be automated. Recording conversations is important but motion is what creates value.
If nothing moves, nothing compounds. I don’t think adding another storage location solves the problem.
Understanding relationships and triggering execution might. Would genuinely love your thoughts on whether that’s directionally correct or if I’m still treating a wetware problem as software. |