Telemation was a relatively new CRM platform in 1997. During the early adoption phase, people struggled due to their aversion to the computerized environment, coupled with the new database system. This roll out serves as a foundational piece to my leadership approach to emerging technologies and communication strategies within the team.

PageNet was one of Canada’s newest paging and wireless messaging companies during a period when the industry was expanding quickly. In 1997, the organisation implemented Telemation, a customer relationship management platform designed to centralize client records, track sales activity, and give management real-time visibility into pipeline performance. On paper, the rationale was sound. In practice, the rollout landed in the middle of a high-volume inside sales environment where fifteen experienced representatives had built their workflows around disjointed personal systems, handwritten logs, and institutional memory accumulated over years of customer interaction.

As the Inside Sales Manager responsible for that team, I could see within the first week of deployment that we had a problem. Telemation wasn’t failing because it was a poor product. It was struggling because the team had never been given a reason to trust it, a framework to understand it, or the time to integrate it into the rhythm of a demanding sales day. Support requests were immediate and constant. Productivity dipped. More troubling was the quiet resistance that began settling into the team’s daily behaviour, where representatives kept defaulting to their personal notebooks and informal tracking methods while nominally using the new platform to satisfy reporting requirements.

This wasn’t a technical fix situation. It was a people situation, and it needed to be treated as one.

Reading What Was Actually Happening

Before developing any response, I needed to understand what was actually going on. Spending time working with the team over several days made it clear that there wasn’t a single problem but a cluster of related ones. Some representatives were uncertain about data entry conventions and were making inconsistent decisions about how to log client interactions, which was quietly undermining their confidence in the records they were producing. Others couldn’t connect the platform’s features to the actual steps of their sales process. They were treating Telemation as an administrative obligation rather than something that served their work. A smaller number were openly sceptical that the system would stick or that management would hold consistent expectations around its use.

What the team didn’t lack was capability. These were skilled, motivated sales professionals who’d demonstrated their competence across years of results. What they lacked was a coherent mental model of how Telemation fit into work they already knew how to do, and a structured opportunity to build real fluency without the full pressure of production volume bearing down on them at the same time.

Building the Training Response

The initiative that followed was grounded in a fairly straightforward premise: adults learn new systems most effectively when the learning is anchored to familiar tasks, delivered in manageable increments, and supported by a culture that normalizes questions and mistakes during the acquisition period. A formal vendor training session had already been delivered at implementation, but it had prioritized feature demonstration over practical application and had treated the team as a uniform group rather than accounting for the real variation in individual starting points. The redesigned approach started with small-group sessions organized by workflow similarity rather than seniority or alphabetical assignment. Representatives who shared similar client portfolios and call patterns worked through Telemation’s core functions together, using real scenarios drawn from their actual accounts. The learning was immediately transferable rather than abstract, and it allowed the sessions to surface the specific friction points that actually mattered to each group rather than working through a standardized script that fit nobody perfectly.

Alongside the structured sessions, a peer coaching model was introduced. Two representatives who’d demonstrated early comfort with the platform were identified and formally recognized as internal resource contacts for the rest of the teams. This wasn’t treated as an afterthought. It was a genuine designation that carried real status within the team. The effect was significant. Representatives who were reluctant to surface confusion in front of leadership were willing to ask questions of a respected peer, and those conversations accelerated fluency across the team in ways that scheduled training alone couldn’t have produced.

The third element was management consistency. Clear expectations were established around platform use and applied uniformly without exception. This wasn’t punitive in character; it was stabilizing. The ambiguity that had been quietly permitting parallel systems to persist was removed, and with it went most of the organisational permission for quiet resistance.

What the Numbers Showed

The results became measurable within sixty days of the restructured training launch. Support requests to both the internal team lead and the external vendor contact dropped by more than eighty percent within the first month. That shift reflected more than improved technical confidence. It reflected a qualitative change in how the team was relating to the platform. Representatives were troubleshooting minor issues independently and sharing solutions laterally rather than escalating upward. The sales performance data from the subsequent quarter told a more significant story. The team recorded a fifteen percent increase in documented follow-up activity compared to the equivalent period in the prior year, a figure attributable in meaningful part to Telemation’s ability to surface client interaction histories that had previously existed only in individual memory or personal notes. Deals that had stalled or been lost to follow-up gaps were being recovered. Pipeline visibility allowed for more targeted coaching conversations, and those conversations were showing up in closed business numbers by the end of the fiscal year.

Perhaps most telling was the attitudinal shift within the team itself. By the end of the third month, several representatives who’d been among the most vocal in their early frustration had become informal advocates for the platform, describing its client history features as genuinely useful to their work rather than as a compliance burden imposed from above.

What This Taught Me About Leading Change

The Telemation implementation at PageNet remains one of the clearest illustrations in my professional experience of a principle that’s informed my approach to organizational change ever since: the technical quality of a new system is rarely the primary variable in whether adoption succeeds. The determining factors are almost always human ones. They include whether people understand the purpose behind the change, whether the training they receive is designed around their actual work rather than the system’s feature set, whether they have structured support during the period of greatest vulnerability, and whether the organizational environment sends consistent signals that the change is real and here to stay.

A team of fifteen experienced sales professionals didn’t need to be convinced that technology could improve their performance. They needed to be shown, in concrete and immediately applicable terms, how this particular technology connected to the work they were already doing well. Once that connection was made, and once the training environment gave them the safety to build competence without consequence, adoption followed with a speed and completeness that exceeded what anyone had initially projected.

That lesson has travelled with me across every leadership role since. The platform changes. The underlying human dynamic doesn’t.