When the room does not know who owns something, the comfortable move is to talk about the tool. Naming the owner does three things: it tells the owner this is theirs, it tells everyone else it is not theirs, and it tells the system what to optimize for.
The founder had built the thing she meant to build, and somewhere in the last twelve months had crossed a line she had not noticed crossing. The team had capacity. There was nowhere for the work to land that was not her inbox, and her inbox was where things went to wait.
A system held in heads is still a system; it just cannot be examined, adjusted, or handed off. What was missing for this team was not competence or leadership attention but a shared place to look. The build is mostly the act of making it visible and giving everyone the same place to find it.
Whatever is happening politically, whatever is being argued about on television, we can still stand up nonprofits and take care of them and do the work in them. That is democratization, in the form of a 501(c)(3). It is also the part of the world we actually get to control.
The communications person had not had a chance to look at the editorial calendar she had been meaning to build since April, because every Monday since then had arrived with a more urgent ask. The organizations that ship consistently outperform the organizations with better ideas. An editorial calendar that lists intentions is not a system.
Board reporting in 2026 is being asked to do more than it was built to do, and the reports most organizations have been producing were built for the old conversation. A board member reading a different chart format every quarter spends the first twenty minutes orienting to the format instead of weighing the substance.
Three weeks before the event, when someone went looking for proof the catering deposit had been paid, it had not been, because the handoff was verbal and the verbal handoff was to no one in particular. The shortfall in project management is rarely the software. It is the discipline underneath it.
The new development associate was three weeks in, two of her logins had not been provisioned, and her manager had rescheduled their one-on-one twice. The organization was, at that moment, in the slow process of giving her every reason to leave by month six, by accident.
Three versions of the same document sat in a shared drive, all contradicting each other, none updated since the person who wrote them left. A procedure written by one person, signed off by no one, never tested by a second pair of hands is not documentation. It is a liability dressed as one.
