{"id":5040,"date":"2026-03-17T22:41:21","date_gmt":"2026-03-17T13:41:21","guid":{"rendered":"https:\/\/morningmate.com\/blog\/?p=5040"},"modified":"2026-03-17T22:41:35","modified_gmt":"2026-03-17T13:41:35","slug":"why-change-fails-and-how-to-make-it-stick","status":"publish","type":"post","link":"https:\/\/morningmate.com\/blog\/why-change-fails-and-how-to-make-it-stick\/","title":{"rendered":"From our CEO: Why Change Fails (And the Surprisingly Simple Things That Make It Stick)"},"content":{"rendered":"\n
We invested in three different collaboration tools over the years. Not counting the ones we tried for a few weeks before quietly abandoning them.<\/p>\n\n\n\n
The first time, we bought into something comprehensive. It had every feature. Gantt charts. Resource allocation. Beautiful dashboards. We ran a training session. We sent the link. We told everyone this was the new way.<\/p>\n\n\n\n
Six weeks later, people were back on WhatsApp.<\/p>\n\n\n\n
The second time, we were more deliberate. We picked something simpler. We ran proper onboarding. We appointed an internal champion. We had executive buy-in. We launched with momentum.<\/p>\n\n\n\n
Three months later, usage had dropped by 70% and the tool was effectively dead.<\/p>\n\n\n\n
The third time, we finally understood what was actually going wrong. And it wasn’t the tool.<\/p>\n\n\n\n
\n\n\n\n
The Real Reason Change Fails<\/h2>\n\n\n\n
There’s a researcher at Harvard Business School named Amy Edmondson who’s spent years studying why organizations struggle to change. Her conclusion, broadly, is that the obstacle isn’t information, and it’s not capability. It’s fear<\/strong>.<\/p>\n\n\n\n
Not dramatic fear. Quiet fear.<\/p>\n\n\n\n
\n\n\n\n
<\/figure>\n\n\n\n\n\n\n\n
This fear shows up as inertia. “The old way works fine.” “I don’t have time to learn this right now.” “We tried something like this before.” “Let’s just keep using WhatsApp for now.”<\/p>\n\n\n\n
These are rationalizations. The underlying feeling is just discomfort with change. And discomfort with change is universal. It’s not a flaw in your team. It’s human.<\/p>\n\n\n\n
\n\n\n\n
What Doesn’t Work<\/h2>\n\n\n\n
Before getting to what does work, it’s worth being honest about the interventions that almost never work.<\/p>\n\n\n\n
\n\n\n\n
Approach<\/strong><\/td>
Why It Feels Like It Should Work<\/strong><\/td>
Why It Usually Fails<\/strong><\/td><\/tr>
Mandating adoption<\/td>
Clear, simple, top-down<\/td>
Generates compliance for 2 weeks, then slow drift back<\/td><\/tr>
Training sessions alone<\/td>
People understand the tool<\/td>
Knowledge doesn’t automatically become habit<\/td><\/tr>
“We’ll figure it out as we go”<\/td>
Low friction, flexible<\/td>
Without clear agreements, people default to familiar patterns<\/td><\/tr>
Same structure, same outcomes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\n\n\n
Mandating adoption<\/strong> rarely works. Telling a team “you must use this system from Monday” generates compliance for a week or two, then a slow drift back to old habits. The mandate doesn’t change the underlying preference \u2014 it just suppresses it temporarily.<\/p>\n\n\n\n
Training sessions<\/strong> rarely work on their own. People can sit through a demonstration and understand how something works without developing the habit of using it.<\/p>\n\n\n\n
The “we’ll figure it out” approach<\/strong> almost never works. A tool is deployed, people are told to use it, and the expectation is that everyone will self-organize. They won’t. Without clear agreements about what goes where, people default to familiar patterns.<\/p>\n\n\n\n
The common thread: treating adoption as a one-time event rather than a change management process.<\/p>\n\n\n\n
\n\n\n\n
Strategy 1: Start With the Most Painful Problem<\/h2>\n\n\n\n
The single most effective approach I’ve seen is deceptively simple. Don’t try to change everything at once.<\/strong> Find the team that is most visibly suffering from the current way of working, and fix their specific problem first.<\/p>\n\n\n\n\n\n\n\n
<\/figure>\n\n\n\n\n\n\n\n
When one team experiences a genuine improvement \u2014 when the handover actually works, when the photos are findable, when the three stores are on the same page \u2014 that story travels. People hear about it from a colleague they trust, not from a manager telling them to adopt a new system.<\/p>\n\n\n\n
The credibility of peer experience is completely different from the credibility of a top-down mandate.<\/p>\n\n\n\n
\n\n\n\n
Strategy 2: Make the Benefit Personal<\/h2>\n\n\n\n
The other thing that consistently works is making the value proposition personal<\/strong>, not organizational.<\/p>\n\n\n\n
Leaders often frame adoption in terms of what’s good for the company. Better visibility. Improved efficiency. Reduced miscommunication. These are real benefits, but they’re abstract to someone who just wants to get through their day.<\/p>\n\n\n\n
\n\n\n\n
“The message that lands isn’t ‘this is good for the company.’ It’s ‘this means fewer messages in your evening.'”<\/em><\/p>\n\n\n\n\n\n\n\n
“You’ll stop getting called about things you already finished”<\/td><\/tr>
“Reduces miscommunication”<\/td>
“You won’t have to redo work because someone got the wrong brief”<\/td><\/tr>
“Increases operational efficiency”<\/td>
“Your Friday afternoons stop being catch-up marathons”<\/td><\/tr>
“Enhances accountability”<\/td>
“When something is clearly yours, nobody else muddles it”<\/td><\/tr>
“Centralizes information”<\/td>
“You’ll find things in 10 seconds instead of asking three people”<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\n\n\n
One thing that genuinely works is addressing the surveillance concern directly<\/strong>. When employees see that work is being made visible in a shared system, a common instinct is to feel monitored. This needs to be addressed explicitly, not hoped away.<\/p>\n\n\n\n
The framing that works: this isn’t about checking up on you. It’s about making sure nothing gets lost between people. It’s so that when something is yours, it’s clearly yours \u2014 and when something isn’t your problem, that’s visible too.<\/em><\/p>\n\n\n\n
Transparency, when it’s genuinely bidirectional \u2014 when leadership is as visible in the system as everyone else \u2014 feels different from surveillance. It feels like a shared operating picture.<\/p>\n\n\n\n
\n\n\n\n
Strategy 3: The Leader Has to Go First<\/h2>\n\n\n\n
This is the one that probably matters most. And it’s the one that most leaders underestimate.<\/p>\n\n\n\n
\n\n\n\n
<\/figure>\n\n\n\n\n\n\n\n
In every case where I’ve seen a new way of working genuinely stick, the senior person was using the system themselves. Visibly. Consistently. Not just endorsing it from a distance, but actually putting their tasks in there, updating their own status, giving feedback inside the tool rather than via a separate email.<\/p>\n\n\n\n
And in every case where adoption failed, you could usually trace it back to a point where the leader quietly stopped using it. Once that happens, the signal to the team is clear: this isn’t actually how we work. This is how we’re supposed to say we work.<\/em><\/p>\n\n\n\n
People follow behavior. They don’t follow policy.<\/p>\n\n\n\n
\n\n\n\n
Strategy 4: Make the Rules Simple and Clear<\/h2>\n\n\n\n
One reason people default to WhatsApp isn’t because it’s better. It’s because the rule is clear: everything goes here.<\/strong> When you introduce a new tool without equally clear rules, you’re asking people to make a judgment call every time they want to communicate or track something. That cognitive overhead is exhausting.<\/p>\n\n\n\n\n\n\n\n
Decision<\/strong><\/td>
Agreement Needed<\/strong><\/td><\/tr>
Where do tasks live?<\/td>
One named system \u2014 not “wherever makes sense”<\/td><\/tr>
How do we signal something is stuck?<\/td>
Specific status label, not a vague message<\/td><\/tr>
How do we notify someone work is ready?<\/td>
Tag in the system, not a separate WhatsApp<\/td><\/tr>
What goes in the tool vs. a message?<\/td>
Decisions and tasks \u2192 tool. Quick questions \u2192 message.<\/td><\/tr>
How often do we update status?<\/td>
Daily, before end of day \u2014 not whenever<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\n\n\n
These agreements don’t need to be elaborate. They just need to exist and be consistent. Once they do, the friction of using the new system drops dramatically.<\/p>\n\n\n\n
\n\n\n\n
The Long Game<\/h2>\n\n\n\n
I want to end with something honest. Changing how a team works takes longer than most people expect. Even with good leadership, good tools, and clear agreements, the first month is usually rough. Old habits are persistent. People forget. They revert.<\/p>\n\n\n\n
\n\n\n\n
<\/figure>\n\n\n\n\n\n\n\n
The businesses that get through the dip \u2014 the ones where the change genuinely sticks \u2014 are the ones that treat the first few months as the hard part and don’t give up on it. They notice when things slip and address it without drama. They reinforce the new behavior when they see it.<\/p>\n\n\n\n
What comes out the other side is a team that works differently. Not just with better tools \u2014 but with a fundamentally different relationship to information, accountability, and their own time.<\/p>\n\n\n\n
The work becomes more visible. The wins become more visible too. People start to notice what they’ve actually accomplished in a week rather than just feeling like they ran fast on a treadmill and ended up in the same place.<\/p>\n\n\n\n
That shift is available to any business, at any size. It just requires being honest about what’s broken, making a few deliberate decisions, and having the consistency to follow through.<\/p>\n\n\n\n
\n\n\n\n
The Series in One View<\/h2>\n\n\n\n
You’ve made it through all five. Here’s the full picture in one place.<\/p>\n\n\n\n
\n\n\n\n
Article<\/strong><\/td>
Core Problem<\/strong><\/td>
What To Do About It<\/strong><\/td><\/tr>
1. Why your team is busy but nothing gets done<\/td>
Busyness \u2260 productivity. Coordination tax grows with team size.<\/td>
Acknowledge it’s structural, not a people problem.<\/td><\/tr>
2. The alignment problem nobody talks about<\/td>
85% of employees can’t name company goals. Teams optimize locally.<\/td>
Give context, not just instructions. Create shared visibility.<\/td><\/tr>
3. The 60% problem<\/td>
Only 40% of work time goes to actual work. Rest is overhead.<\/td>
One place where work lives. Visible status. Kill redundant reports.<\/td><\/tr>
4. What AI actually does<\/td>
AI amplifies existing systems \u2014 good or bad.<\/td>
Fix structure first. Then AI multiplies what’s working.<\/td><\/tr>
5. Why change fails<\/td>
Fear, inertia, and leaders who don’t go first.<\/td>
Start small. Make it personal. Leader goes first. Clear rules.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n\n\n\n
The through-line in all five pieces is the same: the way most small businesses work right now wasn’t designed for coordination. It was designed for individual communication. And that gap \u2014 between how information flows and how decisions get made \u2014 is where most of the frustration, inefficiency, and missed opportunity lives.<\/p>\n\n\n\n
The good news is that it’s fixable. Not with a massive investment or a transformation project. With a few deliberate decisions, held consistently, by a leader who’s willing to go first.<\/p>\n\n\n\n
\n\n\n\n
This is the final piece in a 5-part series on how work is changing in the age of AI. If any of this was useful, share it with someone who’s running a small team and quietly struggling with the same problems.<\/em><\/p>\n\n\n\n
Morningmate was built by people who spent a decade watching small businesses fight these battles. If you’re ready to try a different way of working \u2014 one place for work, visible to everyone, simple enough that your team will actually use it \u2014 start free at morningmate.com<\/a>.<\/em><\/p>\n\n\n\n
![\"Why](\"https:\/\/morningmate.com\/blog\/wp-content\/uploads\/2026\/03\/1st_pt5.png\")
<\/figure>\n\n\n\n![\"Why](\"https:\/\/morningmate.com\/blog\/wp-content\/uploads\/2026\/03\/2nd_pt5.png\")
<\/figure>\n\n\n\n![\"Why](\"https:\/\/morningmate.com\/blog\/wp-content\/uploads\/2026\/03\/3rd_pt5.png\")
<\/figure>\n\n\n\n![\"Why](\"https:\/\/morningmate.com\/blog\/wp-content\/uploads\/2026\/03\/4th_pt5.png\")
<\/figure>\n\n\n\n