Directors of Care Operations, Regional Retail Sales Managers, and Directors of Learning & Development
Why do telecommunications initiatives take so long to become daily behavior?
In telecommunications organizations the gap between a decision and the behavior of people several levels down is where initiatives die. The decision is usually sound and the communication usually happened. What is missing is a named behavior, an owner, and a check that lands in week three rather than at the next quarterly review.
What this looks like in telecommunications
A carrier gives its retention desk an AI assist that surfaces a save offer priced to the individual account. Within a month reps are clicking straight past it and leading with the same two blanket discounts they have used for years, because those close fast and average handle time is what shows up on their scorecard.
Retention is priced per account precisely so the carrier does not hand every save the maximum discount. When every call routes to the same two offers the subscriber stays, the churn dashboard reports a win, and the margin that made keeping that subscriber worthwhile is gone before anyone upstream can see which offer did it.
How you know it is happening
Everyone can state the priority and nobody can name what they personally do differently because of it.
The initiative is reported as on track right up until the quarter closes and the numbers say otherwise.
Middle managers are translating the directive into their own words, and each translation loses something.
Why the obvious fixes do not hold
Repeating the message. Awareness was never the constraint. People heard it.
Adding a dashboard. Measuring a behavior that was never specified produces a number nobody can act on.
Cascading through more layers. Each additional layer is another translation, and the version reaching the floor is unrecognizable.
What actually works
Name one behavior, not a set of principles. A room can hold one changed action. It cannot hold seven.
Give it an owner who is not the person who announced it. Announcements do not survive the announcer moving on.
Check in week three. The interval between decision and first check is the single best predictor of whether anything changes.
What to measure
Measure time from decision to first observable behavior change, by team. When that number stretches, velocity is gone regardless of what the status deck says.
In telecommunications organizations the systems this usually touches are AI next-best-offer and retention engines, care and retail CRM desktops, field service dispatch apps, AI-assisted quoting for business fiber and managed services.
The part nobody names
The mechanism underneath all of this has a name. Dr. Noah St. John calls it taming the caveman in your brain, and it is not a metaphor for laziness. A 200,000-year-old survival instinct is making decisions about 2026 software. It treats an unfamiliar system as a threat, it prefers the known path, and it fires before anyone consciously chooses anything.
That is why the fix is behavioral rather than technical, and why it holds once installed. It is also why telecommunications organizations keep buying capability and capturing none of it: the instinct that decides adoption was never addressed by the rollout plan.
Dr. Noah has spent 29 years on this specific gap, with $3 billion in documented client results across 150+ countries and 27 books in print.
Common questions
How do you speed up execution in a telecommunications organization?
Reduce the distance between the decision and the first check. Name one behavior, assign an owner who is not the announcer, and check it in week three.
Why do initiatives report as on track and then fail?
Because status reflects activity rather than behavior change. Until someone specifies the behavior, everyone reports the work they were already doing.
Want your team’s number instead of a general answer?
Twelve questions, about three minutes. It scores your team on the four places execution actually leaks and gives you a dollar figure for what the friction costs you a year.
