As explained in our previous article, enterprise-wide tool adoption relied on many factors, one of them being good usability. But to drive change into the business, from users to executives, we need to make sure the processes are clear, and the tool reflects people’s needs.

And change does not necessarily come naturally. To support transformation, One2Team developed a one-of-a-kind consulting approach to drive adoption and maximize value delivery.

“The consultant, dedicated only to a specific company, takes the time to discover the pain points in both operations and management, then use their understanding to drive the entire scope of the project,” Stephan Schirrecker, CPO, explains. “Once we have analyzed all this data, we deploy One2Team on a single project to see if the customization fits the company’s needs. If it does, we deploy for all the projects.”

This is a starkly different approach than our peers. In the past, on-premise management consultants defined a strategy. The details of program work required extensive company-specific code to connect company-specific enterprise systems. Project managers functioned as a separate entity to track work completion as a third party observer. This paradigm is expected to be functionally extinct in the next 5-10 years.

In our cloud-based peer set, the measure of success is basic software rollout. The focus is on implementation as a deliverable without a view into how the business is facing disruption or change. Without a connection to larger strategies, this is the typical scenario for “shelfware”, where the product is purchased but never used.

What are the measurable differences in these approaches? The results. Our average tier 1 customer has a lifespan of 68 months with One2Team — and with our low churn, that lifetime value typically increases every year.

“The people at One2Team worked closely with us to show us how we could customize One2Team for our standard of work,” says Justin Horning, Team Lead, Project Strategy Execution. “That was a huge benefit to us.”

Indeed, it took only five days to get Morneau Shepell up and running on an instance of One2Team. Horning and One2Team personnel continued to refine the business rules in One2Team during the first few weeks, but the project managers were using One2Team productively from day five forward.

As you can see, enterprise-wide adoption relies on different key principles: great design, breaking silos across teams and training teams. Don’t miss a thing! Join our mailing list now to get the best content around digital transformation and best practices.

One2Team collects cookies to enable the proper functioning and security of our website, and help us offer you the best possible user experience. By clicking on Accept cookies, you consent to the use of these cookies. You can change your cookie settings at any time. For more information, please read the One2Team policy page.

Below you can choose which kind of cookies you allow on this website. Click on the "Save cookie settings" button to apply your choice.