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.
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.
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.
Low joy arrives as a signal before anything shows up in a revenue report. The organizations that take this seriously stop asking how to make people happier and start asking what the friction is costing them. Those are very different questions, and only the second one has an answer you can act on.
The development director silenced the debrief alarm without opening it, because the campaign was done and the team had already pivoted to the spring appeal. She knew from the four Novembers behind her that she was unlikely to write down what she had learned before January, by which point she would be working from a partial and self-flattering record of how it had gone.
The wrap changes how a gift is received and whether the giver is remembered. The same is true of fundraising data: information can be accurate, complete, and on time and still fail to land if the presentation does not respect how the reader processes it. The pipeline view a development director needs on Tuesday morning is not the same view a board chair needs on Thursday afternoon.
