When I started in tech, I worked in consulting. For months I sat at the edge of internal debates about whether we should call ourselves an innovation agency or a boutique software consultancy. It didn't matter.

Six months into a new role, a senior PM asked her team why a key feature had been built the way it was. Nobody knew. The person who made the decision had left. Out the door went not only a person — another number for the attrition count — but also the context and the memory. The Jira ticket said "per discussion." The Confluence page hadn't been updated since Q3 the year before

Product teams spend enormous energy aligning, communicating, and rediscovering context. We tend to treat this as a coordination or collaboration problem. But in most product organisations, it’s something else entirely. It’s a visibility problem.