The verb description of the word “swirl” means moving in a twisting or a spiraling manner. Well, my favorite pub has many swirls, in fact every month there’s a new swirl concocted. As we stumble through the new normal, leaders are affected, challenged and are in a swirl. The leadership realm most caught up in the current swirl of events is the CIO domain.
The CIO today is caught up in 4 vectors of a swirl. That’s a heady swirl, putting a long island tea to shame. Vector 1 – Coping up with staff augmentation. Vector 2 – New business requirements and change requests. Vector 3 – Dealing with legacy applications. Vector 4 – Managing new projects with severe cash constraints.
Enough has been said on how to cope up with all the 4 vectors. The CIO’s screen is filled up with panel discussions jostling for attention on webinars. Management gurus speaking. Consulting organizations’ pitching ferociously. And, yes, the internal leadership of the organization speaking. The question is where does the CIO begin tackling and consuming the swirl.
The answer has been staring at the CIO’s face for the last 5 years. The answer is – Eliminating coding from the application build part, or at least containing the coding to a minimum level. A single swipe of a decision actually stalls the swirl. Let’s look at the vectors pushing the swirl.
Vector 1 – Coping up with staff augmentation – today the skill sets required by the CIO with-in her staff are different from the ones 3 years back. A single decision of movement on to no-code platform will spur the efficiency of the organization by minimum 8-12%. And we have not even begun talking about touching the core applications. Difficult to believe? Well, proof’s in the pudding. Connect with me for a PoC
Vector 2 – New business requirements – The new normal has spurred the business requirements at a never before pace, we did see that happening during the Y2K days. CRs of the legacy applications are a constant niggle which the IT team has to endure. The best way to approach business requirements and CRs are – building them on no code platforms. Why? – simple, it is about speed. Building an application on a no code platform speeds up the process by 10x, and here’s the best part – no code development reduces the manpower required by 70%. We build CRs on a no code platform, connect via APIs. We can even build new modules of an ERP by no code, and then connect the built modules to the core application. Easily done – WEM, the no code platform is brilliant in integration
Vector 3 – Dealing with CRs – This is the close cousin of vector 2, the solution is to build CRs via no code and then integrate CRs to the application
Vector 4 – New projects – This is the core strength of WEM, our no code platform. The TCO is exceptional. WEM is a PAAS – Platform as a Service. The entire infrastructure comes along with-in the cost. The best part? WEM can be deployed on cloud, private cloud and even in a data center.
So, here’s the swirl stopper. Go the no code way