The 10 Rules Of Digital Transformation

Mukesh Gupta

In my work at SAP, I support a community of SAP customers in India – INDUS. One of the initiatives of this community is a micro-community of people who are working in their respective organizations around the topic of digital transformation. Members of this community are from organizations of all sizes, differ in their positions in the organizations, and come from varying functions. The passion for digital transformation is what unites them.

They come together on a virtual meeting every month for about 90 minutes to listen to a thought leader or a practitioner and their approach to digital transformation. The first practitioner we hosted was Rahul Raghuraman from Mahindra and Mahindra. He is part of the Group Strategy office and shared his thoughts and perspectives and how digital transformation is viewed in his organization. Following is what I learned from the session.

He started with the 10 rules of digital transformation. I think this is a great set of rules to keep in mind before embarking on a digital transformation project. You can access the recording of the entire session here.

Rule 1: Leadership vision and commitment are key

In any large-scale transformation project, or for that matter, any transformation project, commitment of the leadership plays an important role in how the project finally pans out. According to a survey by McKinsey, leadership matters as much in a transformation project as in day-to-day activities. Leaders can’t just delegate the transformation project to a program team and expect results.

In my opinion, these projects need executive support in three different forms:

Access and attention: Everyone in the team or organization needs to see that the executives are paying attention to the project, that they are actively following up on the progress being made on the project, and include these in their regular updates and business reviews.

Budget and belief: It is not enough to just pay attention; leaders also need to ensure that the team has enough budgets (money, resources) to be able to continue their work on the transformation projects. When it comes to digital transformation projects, it requires them to truly believe that these projects have transformative potential and invest in their beliefs.

Communication and continuous action: It is important that there be two-sided communications at all times about what is being done, why it is being done, and the results. The project team needs to communicate this with the leaders. Leaders then need to take that and continually communicate back to the larger organizations and take actions that reflect the progress made.

Rule 2: Create business value

This is so critical for the digital team to get right as quickly as possible. Almost every organization requires a business case to invest in any project, let alone a digital transformation project. When you are launching your first project, trust in the ability of the team to create business value – a currency you are usually short of. In this situation, leadership belief and commitment are key. This can get you started, but unless the team continues to earn the trust of the leaders and the larger organization, the transformation effort will be short-lived.

But how do you go about ensuring that you create business value?

Easy: There are many who approach this from the perspective of quick wins or addressing the low-hanging fruit. This could mean automating a manual process either using a mobile app or a website.

Leveraged: Then there is the approach to pick projects that have the potential for disproportionate and outsized results, compared to the investments that they need. These projects are not easily visible. One needs to search for them. They can be found in the complaints that you hear around the coffee corners and during water-cooler conversations.

Transformative: Most organizations have a preferred key activity that drives success for them. They could be product driven, R&D driven, sales driven, partner driven, marketing driven, service driven, customer driven, etc. One only needs to listen in to the water cooler or coffee corner conversations of people in that group to find these complaints. If you can find a complaint that is most emotionally charged and find a way to address it using digital technologies, that is a great start. This will give you visibility and earn you much needed trust to go after ever bigger transformation projects.

Rule 3: Think customer journey first

Once you have identified the project, it is important that you start thinking of this not as a project or a program, but as a product. The simple shift in your mindset can pay off rich dividends in terms of your approach to the transformation effort. Once you start approaching this as a product design effort, you then need to identify your target customer (sales executive, marketing manager, R&D head, plant head, accounts manager, or whoever else) and look at their entire journey – both current and future.

The ability for you to document the current journey and how the future journey might look enables you to quickly develop prototypes and seek early user feedback to be incorporated into your final product or service. This also addresses the biggest deterrent of many digital transformation initiatives – lack of adoption. If users believe that they have been a part of the process of developing the product or service, the chances that they will adopt it once you go live is much higher.

In addition, your initial contrast frame can serve as a great reminder to all about the journey that you took. Keep that image front and center when you communicate the progress made on the programs.

You can read more about how product managers think and approach product development in my blogs here, here, here, here, here, and here.

Rule 4: The front end and back end must talk

Most organizations already have a lot of digital systems in place. Whatever you build as part of your digital transformation projects should live among them and not outside of them. Here, I meaning that you need to ensure that the digital products or services that you will end up creating need to talk to all the different systems that already exist in your organization.

I know that this comes with its own set of challenges, but is an important characteristic of digital transformation projects that succeed. They break silos (both within organizations as well as in the data) rather than build them, unless you have a strategic reason to keep your work separate from the corporate systems.

This also comes with the added advantage of leverage. I am sure that any digital transformation project is not a once-and-done effort. You will continue to explore ways to add new capabilities and projects (products or services). Any and all data that you gather or create as a result of these projects could then be potentially be used elsewhere if it is all available in the same enterprise data warehouse.

Rule 5: Go for product-market fit

One of the reasons digital transformation projects fail is because the focus is mostly on the digital aspect of digital transformation and not really on the transformation part of the program. However, it is important to look at this entire thing as transformation enabled by digital. If we agree on this, we can then also agree that it is important to ensure that whatever you develop should actually solve a problem for a specific kind of a person, who in turn leads to a transaction of value (money, attention, or status).

If the focus is on digital technologies and not on solving real problems in a way that makes life better for the users, it results in low or no adoption of the solution. It is important to get this product-market fit right. Usually, it takes a few iterations for anyone to get this fit right. This also means that we need to use agile methodologies and iterate quickly, learning from each iteration and building upon it.

You only launch it wide and deep when the team is convinced of having attained a good product-market fit. Till then, the project has to be in beta mode. The development of the product never ends. I personally believe that if your product reaches Version 5.0 and beyond, that is when you will truly see the big benefits (outsized impact when compared to the investments) start coming in.

Rule 6: Partnerships, partnerships, partnerships

Digital transformation projects are not just IT or technology projects. They cut across organizations. It is imperative that you partner with the part of the organization that is both affected by the initiative and also that benefits by the initiative. (And yes, both can be different, depending on which project you are running. The earlier they get involved and contribute, the better the adoption will be. Their engagement will also bring in the much-needed business perspective that they have built over years of running the process. You bring in the fresh perspective. It is at the intersection of experience and fresh perspectives that you find fresh insights, the secret ingredient for successful digital transformation projects.

It is also a good idea if you partner with start-ups or other potential partners (technology or otherwise) who also bring their expertise to the team. In some cases, the initiatives that we run require a very specialized set of expertise that we may not have internally, such as building and training AI/ML algorithms or AR/VR experience.
What we need to remember is that all partnerships should have a win-win proposition for all parties involved. When choosing an external partner, be very careful that they can support the team in all phases of the rollout and not just while doing pilots. This is a sure recipe of disaster later when you decide to scale the project.

Rule 7: Business models and the power of platforms

One thing that all teams need to do is to understand the different business models that your existing business is using currently. A simple and comprehensive one-page explanation is the business model canvas built by Alexander Osterwalder and team. Businesses can and potentially do operate with multiple business models.

Having a thorough understanding of these models can help you in the following ways:

  1. Give you an understanding of potential new business models that you can enable through digital technologies (create new revenue models, customer engagement models, ways to reduce cost, enable new partnerships, optimize existing processes, etc). This also tells you which part of the business you need to partner with.
  1. When you go speak to the business, this gives you credibility and builds trust. When they see that you understand how things operate in their part of the world, they will respect you, which is the foundation on which you can build the partnerships.
  1. This also gives you a language that you can use when engaging with the business leaders like the CEO/CFO. This will help you in getting the necessary approvals and the resources for completing these processes.

Most digital transformation projects never take off because of a lack of a business case, and the team is unable to convince the business to give them the resources needed for the projects.

Rule 8: Enable a cultural revolution

Digital transformation, or for that matter any transformation initiative, typically brings with it change in how things are done.

There is enough written about the criticality of good change-management practices in any transformation initiatives, but I will only reiterate the following:

  • Culture is transformed one conversation at a time. Involve everyone who will be impacted by what you are doing early, often, and regularly.
  • If your project will involve people using new tools or processes, you need to provide them with all the training necessary to use the new tool or process.
  • The primary reason for resistance to change is fear of the unknown. If there is any chance that your project will involve significant change, bring it up and talk about it. Plan for these tough conversations and have them as early as possible. The key idea here is that they need to feel in control of what happens to them.

I have written a lot about culture and how to transform culture. You can find them here, here, and here.

Rule 9: People = uber allies

Ultimately, all transformation projects boil down to people. The more people you have as your allies, the better your prospects for success. This includes your leaders, the business associates who will get affected (positively or negatively), and the external partners. All transformation projects, in the end, are about changing behaviors.

Rule 10: Genius is eternal patience

This is a contradiction of sorts. On one end, you need to be able to demonstrate results quickly. You also need to instill patience in your stakeholders about the time it takes to see tangible results.

This becomes critically important as the scale of your projects increases. The scope of any transformation project is inversely related to the speed at which the project will deliver results.

Add to this the fact you will start getting your transformative results when you reach Version 5 or 6. That’s why you need to iterate, and in order to do so, your stakeholders must show patience and allow you to work on the project till you reach that version.

In conclusion

I can only reiterate the importance and relevance of these rules that Rahul shared in his presentation. Creating transformations is tough, as it should be. Do not start a transformation project (digital or otherwise) if you don’t intend to go through the entire journey.

The other critical factor is the ability to shut down a project if at any stage you find out that it doesn’t make business sense. Nothing will erode the trust that you have built with your business faster than continuing to work on a transformation project knowing fully well that it will not deliver the results that you have promised.

If and when you decide to shut down, do it in such a way that you are able to share what you learned in the process. You should be able to articulate your thinking about why you initially thought that the project was worthwhile, what changed, and why you now think this is no longer the case. This will increase the trust of the business, thereby allowing you to continue to work on transformation projects.

This blog was first published on “Musings of a Neo-Generalist” and has been republished here with permission.

About Mukesh Gupta

Mukesh has more than 2 decades of experience in starting and growing organisations. He has written three books including “Thrive” & “Your Startup Mentor” and has an upcoming book on B2B Selling. In his role as Director - Customer Advocacy, he works closely with the SAP User groups in India, Singapore, Sri Lanka, Malaysia, Philippines, Indonesia and Thailand and actively represents them within SAP and brings the united face of SAP to the user groups. He has an active blog called “Musings of a Salesman” and hosts the popular podcast “Pushing Beyond the Obvious”.