Remember the story of the tortoise and the hare? “Slow and steady wins the race”? Econ 101 lectures about economies of scale? Business truisms like “Nobody ever got fired for buying…” (insert any large, established vendor name here)?
Such nuggets of business wisdom seem to no longer apply. Today, in the words of author Jason Jennings, “It’s not the big that eat the small, it’s the fast that eat the slow.” Competitive advantage comes from reworking business processes and service delivery models to improve speed not by 10% or even 100%, but by multiples. Consider:
According to a recent Financial Times story by Lisa Pollack, “A Berlin company, founded in 2013, built an online service that allows new customers to open a bank account in under eight minutes…The company, Number26, has signed up more than 30,000 customers after launching what it deems ‘Europe’s most modern bank account’ in January.”
There’s increasing interest among enterprises in IaaS (Infrastructure-as-a-Service). Many organizations are moving their servers to cloud-based providers like Amazon Web Services (AWS) and Microsoft Azure, among others. The promise of the cloud is fast and cheap infrastructure, but that needs also be balanced with security and control.
All cloud providers offer API integration to their services; Amazon has a vast array of services and completely documented APIs (and even a Ruby SDK), making the work of creating integration with these services fairly easy—if you have the right tools.
But while automation technologies broadly speaking (robots, “smart” machines, and software) may not destroy many jobs (if any) on net, they will certainly change the nature of the future of work.
The work of the future will be technology-assisted, data-driven, and collaborative. Simple, autonomous tasks (e.g., scanning a barcode) are easy to automate. Complex tasks requiring a mix of expertise (e.g., designing and developing a business software application) are far more difficult, and not candidates for automation any time soon.
As the Kinetic Vision blog approaches another significant milestone, its 200th post, here’s a look back at the top 20 most-read posts since the blog’s launch in March of 2011.
Not surprisingly, the phrases that occur most frequently in the posts below indicate readers are most interested in industry research about request management (that’s what we do), its applications (service catalogs, employee onboarding, BYOD) and its benefits (cost savings, process automation, risk management).
It’s also not surprising many of these are “evergreen” posts; these are articles with a long “shelf life” that continue to draw significant numbers of views month after month. The most-read post so far in 2015 (How IT Will Change by 2020 – Research From HDI) narrowly missed the list below, coming in at #23 all-time.
The increasing sophistication of data thieves, proliferating number of potential breach points, and growing value of stolen data combined to drive the number and cost of data breaches to new highs last year. And the risks to enterprises continue to expand.
But despite the growing threats, many enterprises remain woefully unprepared—even after investing in IT security solutions. According to recent research from Lieberman Software reported in Infosecurity magazine, “69 percent of (IT professionals) do not feel they are using their IT security products to their full potential. As a result, a staggering 71 percent…believe this is putting their company, and possibly customers, at risk.”
Project glitches—and sometimes even outright failures—are unfortunately common. But they are by no means inevitable.
According to CIO Insight, “45 percent of large IT projects go over budget, while delivering 56 percent less value than promised.” Yet many of the frequent causes of project setbacks are well understand and can be avoided with proper planning and execution.
Based on research compiled by Dennis McCafferty, here are 10 common sources of project management problems, along with guidance on how to avoid each, illustrated with the example of implementing an enterprise request management (ERM) strategy.
The tsunami of change washing over the landscape for CIOs can perhaps best be summed up by the phrase “digital enterprise”—a catchall term encompassing the fundamental redesign of business processes to adapt to big data, the Internet of Things, the consumerization of IT, cloud computing, and other developments.
The movement is nearly universal: in a recent Altimeter Group survey, 88 percent of “digital strategy executives interviewed said their organizations are undergoing formal digital transformation efforts this year.”
And there is no shortage of opinion about how this is reshaping and expanding the responsibilities of CIOs: a Google search for “CIO role digital enterprise” yields more than 920,000 results.
“The Internet and e-commerce were major disruptors, but what we’re seeing now is the biggest disruption ever from a technology perspective.”
Those were the words (reflecting a notion previously explored here) of Adriana Karaboutis, CIO of Dell, discussing “what leading the digital enterprise means for today’s top IT executives” at last year’s MIT CIO Symposium. Karaboutis defines the current wave of technology disruption as everything from connected devices (the Internet of Things) and social media to wearables.
The panel focused on two strategies for addressing today’s unprecedented level of technological disruption: embracing digital technology in order to lead the change, and immersion in the customer experience in order to develop customer-centric technology processes.