Knowledge workers spend 28 hours every week writing emails, searching for information, and collaborating internally. | Allen Yang
6mo
Knowledge workers spend 28 hours every week writing emails, searching for information, and collaborating internally. The breakdown gets worse. A full 𝟷̲𝟿̲% of working hours goes to hunting down information you need to do your job. Another 28% disappears into email. That's before you add time spent in meetings, on calls, or doing the actual work you were hired to do. Another study tracked this problem at scale and found that workers spend 25% of their time just looking for information or expertise that already exists somewhere in their organization. At one company, managers were spending between 5 and 20 hours a week just reading and writing emails, with only 15% of those emails deemed useful. This is a 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 problem, though most people don't frame it that way. We've built systems that are great at storing information but terrible at surfacing it when you need it. Every company talks about being data-driven, but most people can't find the data that's relevant to their actual work. The information exists. But it's locked in email inboxes, siloed in departmental drives, or buried in tools that weren't designed to make knowledge flow across an organization. The research suggests that fixing this could reclaim 35% of time spent searching and 25% of time spent on email. That translates to roughly 14% of your workweek. For companies that solve this problem comprehensively, the productivity gains for knowledge workers could reach 20 to 25%. Those numbers sound transformative until you understand what it takes to capture them. The gains come from transforming how organizations share information, breaking down functional silos, and creating cultures where knowledge flows freely. Most companies aren't set up for that kind of change, which is why we keep seeing incremental improvements instead of step-function gains. We've normalized inefficiency because it's invisible. No single person loses an entire day to searching. They lose 15 minutes here, 30 minutes there, spread across a week. You only notice the cost when you map it out.
Morgan Moncada 6mo
I suffer from this daily. I'm curious what your thoughts are on AI-integrated knowledge bases (GPT connected to Drive) or MCP to solve this, and what AI-native teams are building for this.
Reply 1 Reaction
To view or add a comment, sign in