What Good Looks Like: Offboarding
If your organization loses something every time a person leaves, you are not behind and you are not alone. It is one of the most common things a growing team runs into, and it is rarely about the people who left.
If your organization loses something every time a person leaves, you are not behind and you are not alone. It is one of the most common things a growing team runs into, and it is rarely about the people who left.
If you have grown fast and almost nothing is written down, you are not behind and you are not alone. It is one of the most common things a growing team runs into, and it is rarely a discipline problem.
If you cannot say what is in your pipeline right now, you are not behind and you are not alone. It is one of the most common things a development leader runs into, and it is rarely about the software.
The documents were written to be complete rather than to be used, and those are different goals. A process written to be followed offloads the knowledge it describes. A process written to be complete just describes it, expensively.
The spreadsheet was doing two jobs at once: holding the friction and holding the knowledge. Automating the follow-up can oversaturate the people you were carefully tending. The wrong system does not just fail to help; it quietly erases the thing that was generating the growth.
Six months after the rollout, the work has routed back to inboxes because the platform was treated as the system when it is not. Who owns a piece of work, what done means, who owns the system itself are calls a leader has to make and then stand behind. None of that ships with the license.
There is a meeting on your calendar that you have moved twice, and a thinking partner set up correctly will not let you look away from it. The starter prompt that makes this work closes the back door: “You are not here to validate my thinking” cuts off what avoidance is looking for in the first place.
Ninety-two percent of nonprofits are using AI. Four percent have built a workflow. Eight people in the same organization can be using the same tool in eight different ways, with no shared prompt library and no internal agreement on what data goes into a model.
The decision was made in March, or at least everyone on the leadership team remembered it being made, though none of them could name the meeting where it happened. A closed decision has a shape: something executes, the loop closes. The half-decided state has neither.