Why People Don’t Use What We Build

What to Do When Your Governance, Templates, and Tools Get Ignored

You spent months building it. The intake process, the status template, the governance framework, the reporting dashboard—whichever artifact your PMO invested in this quarter. You ran the working sessions, gathered the input, refined the design, and rolled it out with training and documentation. And now you’re watching teams route around it or stop using it altogether. Worse, the feedback you’re getting isn’t useful: half the teams say it’s too heavy, the other half say it’s too light. A few have stopped engaging with the PMO altogether. The environment you dropped your artifact into is wired to reject it.

PMO output gets ignored for reasons that have almost nothing to do with the quality of the work. Templates compete with the dozen other places teams already report status, and governance frameworks land inside cultures wired to reward speed over rigor. Tools get adopted by the people who need them least and avoided by the people who need them most. When PMO leaders treat adoption as a training problem or a communication problem, they end up rebuilding the same artifact three times, each version slightly better and each version equally ignored.

This session gives you a way to diagnose why your PMO’s output keeps getting ignored, and a sharper approach for designing the next artifact so it gets used the first time. Walk away with a one-page diagnostic you can run on any artifact your PMO has shipped in the last year, plus a clearer view of which fixes are worth your team’s time and which are just polishing something the environment was never going to accept.