Recently, I had a chat with Kate Visconti, Managing Director of  Acumen Solutions, USA who takes care of the Sales Acceleration and Change Management Practice. She is also an Adjunct Professor with Santa Clara University, USA. It was an interesting & engaging conversation and here are the highlights of the discussion.

What was interesting to me was the points she made for successful adoption of technology in an enterprise - the importance of business process re-engineeering, change management as much the software or technology selection & upgrade itself and looking at the implementation itself thro' a customer lens.

I have believed for many years that these were the most critical aspects when it comes successful technology adoption & usage and often enough importance & attention is not paid within the organization and the stake holders to this area. Kate brought this out beautifully and reinforced this very well during our conversation.

Here is the summary of our chat:

Swami: How do you approach a technology implementation and what do you believe are key differences that you or your organization focuses on?

Kate: We always start any technology implementation with a first principle approach - how is the enterprise and their stakeholders currently thinking, feeling and doing with their workflow right now. We strongly focus on process innovation and not a run-of-the-mill implementation like other system integrators. We conduct multi-day workshops, build customer personas, enable collaborative  conversations across cross-functional groups to understand current issues and identify opportunities for optimization and automation. For us change management is as much important as the technology implementation itself. That's a key difference we believe we bring to the table & where I have seen successful technology transformation happen. 

Swami: When it comes to selecting or shortlisting technology platforms or software etc. and adopting technology across the organization, which are areas that are normally missed by them in your experience?

Kate: Most of them don't have an 'outside-in' approach and we bring that to play when we work with organizations. When a tech platform or software is selected, there is a lot of discussion on features, benefits etc. but very often during implementation, they don't see the technology from a customer's lens. We do a lot of shadowing to know how the current processes work, do customer research, customer experience benchmarking and often these are areas that are not often not given enough attention or missed most often.

Swami: Enterprises spend millions of dollars on acquiring licenses for tech & software and you have seen many successful technology implementations, adoption and transformation across enterprises, what do you believe is the secret sauce for their success?

Kate: What I have seen in enterprises where there have been successful technology transformation or adoption is that if there is an Engaged Executive Sponsor, the chances of success improve by at least 2 times! An engaged leadership committee which defines the vision & organizational priorities makes the next difference in the success as the technology road map, business outcomes and priorities get defined well. Engaged Stakeholders make the next difference - end-users, managers, executives, customers as they influence adoption and validate user experience across the enterprise. These I believe are the secret sauce to success and where I have seen this happen in organizations, things have been successful most of the time.

Swami: You also emphasize a lot on hand-holding the enterprises which your organization does after you implement the technology or software. That's a very interesting point that you make and in fact what kind of metrices do you track and for how long do you suggest one must do this?

Kate: I normally suggest we do this for 60-90 days ramp cycle depending on the scale and complexity of the project and implementation. We track a lot of metrices post implementation like:

1. Project Success - Both by way of budget and time
2. Adoption -  Quality of inputs that go into using the software or technology within the enterprise after roll-out - Timeliness, Completeness of the information, Not just no. of log-ins but demonstration of new user benefits and referrals etc.
3. Business before vs Business After - Benchmarking and looking at % increase in agreed business metrics, % decrease in, say, sales cycle or service cycle reduction etc.

These are some of the sample key metrices one should look at.

Swami: There is often an underestimation of the services costs which enterprises need to spend to make the technology transformation successful. There is a lot of focus on licenses fees, infra needed, maintenance & renewal fees etc. but much less attention is paid to services & costs associated with it. Right?

Kate: I totally agree with you, Swami. In my estimate, these may vary by project scope, complexity and these are directional just to give you a perspective that enterprises need to factor these services cost for a successful technology transformation - up to 30-40% factor for change management, engaged leadership, customer research, building alignment workshops, post implementation program adoption costs etc. These are over and above license fees and customization costs they would incur during the course of a 3-4 year project or program.

Swami: I saw that right at the start of our chat, you mentioned don't treat it like an IT project. What did you mean by that? 

Kate: I often quote from the point made by Forrester Research Chairman and Chief Executive Officer George Colony made on technology projects, that in this age it is transforming from IT projects to Business Technology projects thinking. This is a key difference to successful technology selection, implementation, adoption and usage. I also say - Don't treat it like an IT project but treat it like a customer project!

When I talk and work with people and clients on many assignments, the challenge I find for enterprises to be customer-centric is, how to bring marketing & technology together. Increasingly, technology is getting adopted in many customer-centric channels like never before and marketing is getting more & more real time & thefore technology is becoming a nerve-centre for marketing. The future , I have always thought is the changing( or can I call it merging) role of marketing & technology folks and the need for them to work together.

I read an interesting article today, if there is a need for a CMTO ( Chief Marketing Technology Officer)! I thought this was quite interesting. Who  is a CMTO and what does he or she do?

" A chief marketing technology officer (CTMO) — use whatever label you prefer — is simply the lead marketing technologist, organizing and managing that team. He or she reports to the CMO, not the CIO. Again, this is ultimately a marketing responsibility. There should be collaboration with IT, of course, assuring that marketing fully leverages its infrastructure and complies with technical governance standards. But collaborating is better than being solely dependent."

I find this very thought provoking and I do feel this is doable. The role of the CMTO is to ensure the right technology - either already invested is leveraged across the enterprise or if to be invested is partnered and led by this role - to collaboratively ensure this is adopted enterprise-wide.

Finally, customers must see the benefit of technology in their interaction experience with any company. The role of the CMTO is to make this happen.