Skip to main content

DIGITAL STRATEGY NOT A SEPARATE EXERCISE

Driving-Digital-Strategy
Driving Digital Strategy

The book "Driving Digital Strategy", by Sunil Gupta, came at the right time as I have been studying many aspects of the business transformation and the disruption that is happening across the different industries.

In this era, as a company leaders, just doing what brought you to this present, not embracing change, not renewing yourself, and important aspects of your business; is an indication that your ego, or comfort, or your fear to change, is not allowing you to move forward... and that potentially will be the "end". That "end" can come in one year, two... perhaps five years... but make no mistake, it is coming.

The introduction of this book have key notes that I found extremely relevant to my current research. One of them being the following:
  • "The leaders who achieve 'transformative' results go all-in on digital. That is they don't treat digital strategy as separate from their overall strategy. Instead they lead with a digital-first mentality and make sure their digital strategy touches ALL aspects of their organizations"
As I continued reading, I found in this book the same question that I have been placing in my internet searches, as part of the research: "Where companies go wrong with their digital strategies". The point of view of the writer is interesting as it presents around three (3) strategies:
  1. "creating an independent unit is like launching a speedboat to turn around a large ship. Often the speedboat takes off but does little to move the ship".
  2. "To run experiments". Doing experiments out of control over the organization groups causes a proliferation that causes silos, preventing synergies. Too many initiatives, going in different directions, with the same goal or intentions, causing multiple investment streams, and therefore causing issues for the organization.
  3. "Leverage technology to reduce costs and improve efficiency of operations". Improving efficiencies and minimizing cost are good strategies and technology is one of the elements to use. However is when you rely solely on this approach when the formula may or may not be flawed.
To conclude this post, I believe is true that "some" are using "band-aid" for the real problems around the organizations, and in a lot of  cases are full of cliché approaches instead of truly making digital strategy and integral part of the overall business strategy. 

I could not have said it any better, that DIGITAL STRATEGY IS NOT A SEPARATE EXERCISE, it is an essential piece and " you must embed it into the operations and DNA of your organization".

Trending posts

Adobe Summit 2022 - Experience Platform

 Our hero image features many air balloons flying, scattered in a blue sky. Each of them has characteristics in their designs that are “part of a whole”, which in this case is an exhibition that is part of a festival. Now, let us leverage this analogy, mapping it to the elements that are relevant for this post’s agenda. Think about the pieces of data scattered through different systems, which combined (behaviour and PII data) becomes part of a whole: an enriched consumer profile that can provide you a “360 view”. This allows corporations to find opportunities, and turn them into value: “enabling ways to engage with that customer(s) to meet a cluster of business goals.” Photo by Lad Fury from Pexels   The objectives for this article are: To provide our takeaways from two (2) Adobe summit 2022 sessions, related to the Adobe Experience Platform and Real-time CDP (Customer Data Platform). Those sessions being S401 (AEP a modern foundation - by Klaasjan Tukler) and  S408 (DMP vs CDP:

Quality Assurance for mobile applications

By: Herak Quality Assurance is an important aspect of Software Development Cycle and it has become even more important with the advent of mobile applications. This is because mobile applications are typically more complex and needs to be supported across a plethora of platforms. Often the same application needs to be coded in different programming languages to support different platforms for example Objective C for iOS and Java for Android. This results in multiple code base and requires multiple streams of testing. QA also need to pay special attention to ensure that the user experience of the app remains somewhat similar across the multiple environments. Thus traditional QA practices need to evolve to adapt to the needs of the mobile app testing. In this article I am going to discuss the first two phases of QA, Preparatory Phase and Testing Phase. I will discuss how QA needs to adapt to the testing need of mobile applications and include links to resources which will help

AWS Amplify as low-code for infrastructure

Low-code development platforms are dominating many conversations lately. Many believe that low-code development platforms will account for millions of USD in revenue in the next five (5) years. An article by Forbes highlights that “ it will account for more than 65% of application development activity by 2024 ”. Some believe it will be the answer to all their development needs. Photo by Tima Miroshnichenko from Pexels  But low-code is not a new concept. The difference now is that its audience has amplified. For developers (or even advanced users) who have been in the Microsoft  ecosystem for a while have already experienced the assembly of software solutions with little effort using tools such as Microsoft Excel, Access, Visual Studio (assembling forms) and others. Putting Microsoft aside, and prior to this “low-code revolution” which has reached high altitude in the last couple of years, there have been many online veterans which allow a user to assemble simple to medium complex

Research around JIRA vs TFS

By: Carlos G.    An opportunity came from a colleague to discuss the case of company “X” for improving the ALM by introducing tools to this company. The challenge was to decide between Microsoft and Attlasian . He came to me because I’m a Microsoft kind of guy and he wanted the opinion from my perspective, not as a consultant, but as a friend of what he was trying to accomplish. He said that even though I was inclined to a technology I was able to explore other things and be “fair”. I agreed to be a part of his research because of 3 things: because of my curiosity I'm always willing to learn new techy stuff. Sometimes is good to be the dumbest one of the group. You learn so much! This was a story that I could blog about. (Of course no names are used in this post). My first impression was thinking “cool”; let’s compare Visual Studio TFS vs JIRA. Immediately I got a comment back with: “ Sure but JIRA by itself is more like an issue tracker in simple terms ”. That sa

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed