How can I get my team to actually use the new project management software?

[Matthew32]

I’m struggling to get my team to actually use the new project management software we invested in. I’ve explained the benefits and provided training, but they keep reverting to old habits like email chains and spreadsheets. I’m wondering if I should enforce the change more strictly or if that will just create more resistance.

[StellaT]

We tried making the new project management software mandatory for all new projects, but the pushback was immediate and people still emailed updates and attached files.

[Robert65]

The training was solid and attendance was decent, yet on the ground folks default to old habits because it feels slower to log something than to ping in a chat.

[Abigail_M]

We did a soft rollout with a couple of teams and watched usage climb from 20 percent to around 45 percent over two weeks, then it stalled.

[Steven_R]

Maybe the real issue isn’t adoption but the workflows; the tool didn’t map to how we actually work, so people just kept bypassing it.

[Robert33]

I tried enforcing with consequences for not using it, and that created tension, so we paused and asked what would make it worth the switch.

[AlexanderL]

One concrete thing we did was build a few templated tasks and dashboards so people could see a quick win; it helped a handful, but not everyone.

[Kyle_M]

Do you think the problem is deeper than tools, like leadership or culture? I keep wondering if we’re chasing a solution to the wrong thing.