Developers waste hours searching for answers. Here's the fix

"Was it in Notion, or the Slack thread, or the GitHub issue? Maybe the Google Doc from the offsite?" If that sentence sounds familiar, your team doesn't have a knowledge problem. It has a findability problem: the answer exists, but nobody can say where.

This post looks at how much time that costs, why adding more tools rarely helps, and a lightweight system any team can set up in an afternoon to cut the searching down.

How much time goes into searching

The numbers here are consistent across surveys, and they're not small.

Atlassian's State of Developer Experience 2025, which surveyed 3,500 developers and managers, found that 50% of developers lose ten or more hours a week to inefficiencies, and 90% lose six or more. The top time-wasters were finding information (services, docs, APIs), adapting to new technology, and switching between tools. Developers reported spending only about 16% of their time actually coding.

The Stack Overflow 2024 Developer Survey points the same way. About 61% of professional developers spend more than 30 minutes a day searching for answers or solutions, and 29.6% run into knowledge silos ten or more times a week. That's not new: in Stack Overflow's 2022 survey, 68% of respondents said they hit a knowledge silo at least once a week.

Half an hour a day is two and a half hours a week, per person. On a team of 20 that's a full-time engineer, spent looking for things.

People know where to look, but can't find it fast