• Build the Engine

    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.

  • Rebuilt, Not Refreshed

    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.

  • The First 90 Days

    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.

  • SOPs that Hold

    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.

  • The CRM Underneath

    The development director could not fully answer the board’s question about the pipeline because the data was in two CRMs, three spreadsheets, and a pile of handwritten notes from the gala. The system had not broken that week. It had been broken for a while, and that week was when the cost happened to be sitting at the head of the board table.

  • Who Owns What

    By the time the wall was full, more than a third of the sticky notes had nobody’s name on them. The work was happening; the accountability was not. Each departure leaves a quiet residue: the work the person was doing that was not in their job description, and the assumptions about who would do it next.