Every July, development teams do the same thing. They close out the fiscal year, pull the final numbers, and start building the annual fund plan for the cycle ahead. Goals get set. Timelines get mapped. Someone makes a calendar. The plan looks right because nothing is running yet, and when nothing is running, nothing is visibly broken.
If you bought the tool and somehow made more of a mess, 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 the software’s fault.
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.
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.
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.