They were deemed a reference customer for the industry and one of the favorites of the big name vendor and solution provider. Over a long period of the relationship they had acquired almost every solution from the same vendor for any business problem. At times the price was quite attractive to turn down the offer, and at times the perceived time taken, complexity of evaluating and then implementing another solution appeared to be too big a task. So the CIO and her team continued to invest with their preferred IT partner.
Life would have continued for them with incremental innovation and harmonious coexistence with their vendor ecosystem had not events overtaken them. The company was caught up in an industry turmoil which required information agility they had never experienced before. Their strategy to stay with one solution provider had given them a basket of solutions for every stated need; the implementations technically successful and were declared live. The business use found them lacking in the new paradigm when efficiency mattered.
Earlier business had continued to use parallel systems and created business critical spreadsheets that became the lifeline for the enterprise. The level of (in) efficiency was deemed acceptable as change required them to actively participate in the definition and building of the solutions. It appeared easier to let the IT organization manage the complexity of IT’s favored solution which ended up becoming a system of records while business users added headcount to solve problems. Now the murmur of disenchantment grew louder.
The CIO was in a fix and wondered why her winning strategy was no longer deemed effective? They had bought from one of the largest providers in the world and the vendor had in many meetings acknowledged the leadership in implementation of some of the solutions. Business had participated in the selection of the solutions in almost all cases and signed off the choice. Now how could they be pointing fingers and distancing themselves? Okay, there were some disagreements on the solutions and partners, but…
The applications lead had grown within the ranks and his first implementation of any major system was from this big solution provider. The success of the first big step gave him sense of invincibility if he continued to bet on the same provider. Guess what, it actually worked for a while and the resultant growing arrogance made him deaf to the occasional issue and limitation. After all not every wish list can be fulfilled by the solutions; why did they not admire the brilliance of simplicity of integration of parts from the same vendor?
The CEO instructed the CIO to benchmark with specific companies to find out how they stacked up in comparison and what they can learn from some of the finest companies. Initially skeptical and full of themselves, the CIO and the team ventured out to explore the world and how others lived. The chosen benchmark had a much awarded CIO who was seen as an early adopter and trend setter. He was always happy to share his success with others and welcomed the team to spend time with him and his IT and business teams.
There were many common solutions deployed between the two companies; they had the same big name vendor as their primary provider and that is where the similarity ended. The CIO had given the freedom of choice to his team to seek solutions beyond the initial investment. In fact he challenged his team to find alternatives just to be sure that they had covered all options before making a choice. They were cautious of the fact that they did not want compromise solutions and were willing to stretch to get the best.
Both companies having started their IT journey had taken different paths at the crossroads; one had gone down the well-trodden path of low risk and reaped the fruits that came along the journey. The other created their own path and enjoyed the journey and the new experiences that it brought. The first was finding her achievements pale in comparison to the risk taker who had the business totally in sync with the decisions, the pains and the success. Two different paths enabling business, two different outcomes, two tales of success.
Which path have you taken and what is your story?
The CIO was doing quite well; he had good credibility within the company as well as outside with peers in the industry. He wasn’t the flamboyant type, neither was he a pushover; he participated in industry discussions and was seen as the strong, silent and effective leader. His company had invested well in IT; they were not early adopters, neither laggards, a balanced view of technology investments and business was happy with what they had. The company was growing faster than the market and placed well in the industry.
Working with business leaders and the CEO who understood the value of IT, he managed the budgets pragmatically. The CEO gave him enough latitude to work independently and he kept abreast with the technology curve to field any challenge thrown at him. IT vendors were happy to work with him as he was straight and forthright in his approach telling it as it was. His team was made up of business focused professionals who had invested their careers in the company. The turning point for him was when the CEO moved off to greener pastures.
The new CEO had grown through the ranks; he restructured the organization and the CIO found himself under the tutelage of the CFO. An ostentatious man, the CFO never lost an opportunity in the game of one-upmanship. He met the IT team and vendors with visible disdain with a clear message that the golden era of IT spends was over. The mantra set by the new CEO was to deliver a better bottom-line and he, the CFO was going to leave no stone unturned in his quest. The budget shall be cut by 20% with immediate effect.
The CIO a logical man attempted to discuss the irrationality of the step as it would impact operational efficiency. IT budgets did not have any buffers, the CIO never needed to pad his budgets with the trust he had from the earlier CEO. Support charges for ERP, CRM, and office automation licenses apart, the network links to global offices and sustenance of support services for users and data center took up the larger part of the operating budget. He had limited choices and began the process of rediscovery for cost control.
Negotiations and calling in favors he was able to bring down operational cost by 10%. The balance appeared unachievable and he sought help from the CFO to evaluate options. Why does everyone need an expensive license? Why do we pay so much on software maintenance contracts? We should move to cheaper solutions, embrace open source, bring in garage mentality into our team. Move to lower cost options on email, start using common ids at remote locations, move to cheaper hardware; and make sure the “management” does not get inconvenienced. Thus the CFO spoke!
His protests on operational impact being overruled, the CIO got down to execution; mail was migrated to a lower cost option of a popular personal public free mail services’ corporate offering. Onsite engineers were reduced at locations, development work brought in. The change was seen as a retrograde step across the enterprise. The trickle of problems from the alternative solution slowly became a barrage which had every function head tearing their hair in frustration on lost functionality and team efficiency.
Slowly and steadily the noise ebbed when people realized the change was driven by the new CFO; citing business impact some teams sought and received approvals to move back to the older system. Soon enough everyone was attempting to go back to the past, though not very successfully. People learned to live with the new, factoring in the inefficiency into their work schedules, discussing and debating the gap in communication. It was fairly evident that the resultant reduction in performance cost the company a multiple of the savings.
Do organizations measure such a consequence where deployment of a new tool or process has an adverse impact on the outcomes? Consultants tout their new success when the change is even slightly positive; I haven’t seen instances of the adverse impact or degraded efficiency being elevated or discussed openly. I believe that this costs enterprises significantly almost to the tune of 20% reduction in productive time. Change is rarely sanctioned due to costs involved which is typically a fraction of the lost hours. How long will pennywise and pound foolish continue?
It’s an opportunity for the CIOs to take a stand and lead the way!
I have been flooded with articles, case studies, and the benefits of DevOps; every newsletter that I subscribe to (over a dozen that arrive in my inbox every day) has at least one link that headlines DevOps. In the initial days I read a few of them with curiosity and forwarded some of the articles to friends and peers in the industry. The flood of discussions and seminars raised my anxiety if I had missed any salient point in my analysis and understanding. So I dug deeper to understand the subject and its relevance to good IT departments.
What is interesting is that many vendors are now offering tools and consultants providing frameworks and expertise on helping organizations create DevOps centers of excellence. It’s the new buzzword that promises to fix the issues faced by enterprises when they deploy new custom solutions. The most interesting and highly impressive manifestation appears as “a cross-disciplinary community of practice dedicated to the study of building, evolving and operating rapidly-changing resilient systems at scale.” Do you get what it says? I don’t!
If you search for the term online, the definition on Wikipedia is as follows: “DevOps (a portmanteau of “development” and “operations”) is a software development method that stresses communication, collaboration and integration between software developers and Information Technology (IT) professionals. DevOps is a response to the interdependence of software development and IT operations.” Note the keywords that stand out, communication, collaboration and integration between IT and developers!
Over the decades there were many methodologies that evolved since we needed to develop “for purpose” software. I am not discussing one over the other or their pros and cons; there are proponents and opponents to each depending on what has worked for them. The point is that whether you followed one or the other, all of them required communication to flow between the stakeholders (Business, IT teams and developers). Else how do you ensure that everyone understands the problem or the opportunity and what is needed?
When in a group people collectively work together towards a common objective, I would safely assume that they are collaborating. There are instances when differences of opinion or point of view may result in conflict or disagreements; that does not imply that they are not collaborating. The level of integration is determined by the crisp and clear communication from the top as well as within, and a shared vision and objective of their goal. That is how I have seen almost all projects, IT or otherwise, – big or small – getting off the ground.
What changed in recent times that gave birth to this new term and the wave that is following? The underlying assumption is that development teams and operations teams are independent (which they are in many cases though not a universal truth) and that they don’t talk to each other; that is an interesting hypothesis and rare occurrence when both teams are collocated. Companies who outsourced support operations of applications or moved them away from core teams did suffer often requiring rework and occasional disruption.
So should CIOs be bothered or worried about DevOps? The starting point would be to diagnose if there is a gap, perceived or real. Once deployed, are applications able to scale and sustain themselves? Or they slowly wither away into the IT Orphanage (where applications who no one wants rest until they find a benefactor). Are business users happy with the solution provided and the support rendered? Some of these questions would probably point you into the right direction on what needs to change to the desired state.
Simplistically many solutions may endeavor to push for additional investments in tools, technology and consulting; my belief is that tools and technology do not solve a problem if the underlying process and culture don’t support it. As the CIO or for that matter the CEO, it is necessary and essential to look at the facts and data before beginning to get paranoid about competition or next door neighbor doing it. Even if you have your support teams sitting across the seas, if the development team has thought about support, you are already there!
“This is awesome, I love it! Let’s make this live next week; and don’t tell me that it cannot be done in that timeframe! After that we will work upon models for the other parts of the business and zap them with data that they have never seen before.” So said the CXO who had just been given a demonstration of the Proof of Concept that the vendor and the IT team had developed to highlight the capabilities of the tool. The Business Intelligence lead tried to get in a few words sideways and was brushed aside brusquely with a wave of the hand.
The company had history of failed projects and challenged BI implementations with business users running berserk. A new CIO had brought some semblance of order to the chaos with an IT governance framework. With some fresh talent as the journey progressed, the information needs started getting addressed which in turn raised the expectations bar. Earlier attempts at BI had faced multiple challenges which resulted in their being shelved. The new resources the CIO brought in had a pedigree of success and the result was visible.
In the initial stages of education the primary requirements revolved around reporting; can fragmented systems deliver consolidated reports from the data warehouse? Any amount of persuasion would not deter them from their resolve for reports; so the first set of milestones did reports that did not require large investments in tools or great amount of intelligence. Some of the newer business users who had experienced a different reality in the world outside craved for dashboards and analytics. They were heard but not prioritized by the powers that be.
Seeing an opportunity the BI Subject Matter Expert worked with the business members to define the landscape and put in the extra effort post work hours to build the cubes and models. He sought new tools which were granted and with renewed vigor he created working prototypes that excited him and the business users who helped him. Tentatively they approached the self-professed technophile CXO who they felt would be excited with the new way of looking at information. They were however not prepared for the reception they received!
The CXO in his inimitable way was seen as the person who exuded overdoses of confidence and threw technology jargon liberally in every meeting. Know it all, been there done that was what he wanted everyone to believe; for the knowledgeable it was massacre with unrelated keywords interspersed with unverifiable anecdotes and visions of peaks achieved in the past. He was closed to ideas from others, derogatorily critiquing the world at large for not believing in him. The team feared his acidic behavior and kept away to whatever extent they could.
Recovering from the ridiculous, the BI SME stood firm that Proof of Concepts are exactly that and they cannot be deployed or scaled. He explained that for analytics to work effectively, he needed to build the model, test all data sources for efficacy, check for exception conditions and stress test for load. Almost all – barring the sycophants and the ignorant – agreed with him silently, putting the CXO in a spot. Taken aback not used to being challenged, he directed one of the minnows to ensure that his wish and command be done and huffed away.
Put in a spot the team member frantically looked around for a solution to his predicament. Gathering information from multiple sources to create a strong argument, she was able to enroll the business champions into her cause; they too wanted the new BI solution. It took some time and effort by the business champions to educate the CXO who reluctantly agreed to let go of his tantrum. Back on track the team worked together to build the solution which promised to open up new possibilities for the business.
The generally accepted new belief is that business knows what they want; the level of awareness and understanding has improved. Decisions are now information and data driven; BI solutions deliver this and more. Change management is a critical success factor towards adoption and the journey on the evolution curve. The data deluge and associated tools to manage them has created new challenges and opportunities; the ability of enterprises to leverage these will be determined by their maturity towards analytics.
The BI solution was a great success; everyone loved it. The CXO was last seen ranting about why the team did not use big data!
When I came across my CIO friend who looked like he had been trampled multiple times by a runaway cattle herd, I was anxious to find out more about the cause of his pitiable condition. His demeanor suggested that he was on the brink of giving up, ready to throw the towel, just run away and retire into the Himalayas, to hell with the fabled Ferrari and take up the way of the monks. For someone always willing to help with a ready smile, it was a sight that concerned many of us to do a root cause analysis and help the poor soul.
He was not a recluse or introvert but in recent times conferences and seminars had been prominent with his absence. He was a busy man, everyone knew it; he was also known to be a master in time management rarely forgetting an appointment or being late or making anyone wait. So his growing hermetic avatar was a surprise to many of us who surrounded him to hear the cause of the rainy clouds replacing sunshine. Hesitant at first, after a few drinks he decided to share his predicament to lighten his heavy heart and seek a solution from collective wisdom.
His mega project that was on the watch list of many vendors, partners and the industry had run into some minor challenges. He engaged a specialist consulting company to review the situation and suggest the way forward. They had suggested shift in approach for the issue and resource augmentation with specialist skills which appeared to be a rational approach. Some internal stakeholders taking advantage of the situation wanted to take control with infusion of their coterie. Despite no skill match, they had prevailed to further damage of the project.
Like termites the project was soon crawling with unskilled people ignorant of business or ability to manage complexity and were projected as God’s gift to mankind and specialists. Despite the situation deteriorating, status reports were altered to reflect progress. This continued for some time with the CIO being asked to back off. Protests and discussions with key stakeholders and management changed nothing. The project in a tailspin now, the CIO could only watch from the sidelines; he was hurting from the damage to his toil and blood.
The large business and IT project team disillusioned by the downward spiral were of broken spirit indifferent to the outcome. Unable to bear the incompetence some quit the project and the company weakening the now shaking foundation and structure. Timelines slipping further and expert opinions overruled, there was little hope for the transformational project that was to be the savior and enabler for the business and enterprise. Unable to bear the hurt to his passion child and with no recourse, the CIO had decided to detach from the company.
We listened with stunned and angry silence absorbing the pain, empathizing with the CIO living his agony, everyone unanimously wanted to reach out and touch his wounds to heal them. No one disagreed with his decision, many wanted to help his recuperation; there was shock at enterprise apathy and silence by a large affected group to the value erosion. Lightening his burden the CIO managed a fleeting smile which lifted the gloom from the group. He joined the light banter that typically follows a serious discussion.
Time flew by, months passed away, the CIO moved on to newer ventures and greener pastures, happy and successful again with no visible scars of the past. It was as if he had buried the bitter experience never to be unearthed again, any discussion on it a taboo. But morbid curiosity never lets’ go especially when someone you know and respect has been wronged; you want the perpetrators to get their due punishment. Meetings with common industry peers and vendors does raise queries on progress and status.
A year into the intervention, the project had seen slippages on timelines consistently; some of the leadership team finally found a voice and challenged the continually sliding deadlines. Running out of excuses though unwilling to acknowledge their limitations they shifted the blame to the business folks for not defining the requirements, cooperating and providing accurate data; it seems there is no hope for redemption. Last heard there was pressure to shape up or ship out; a new date has been set to go live in whatever state, business disruption be damned!
X had just completed 4 years in his role and grown to take on additional business responsibility. He had built a team which worked across business units and corporate IT on the forefront of some of the new technological innovations. Accolades came from peers and industry acknowledging his ability to take risks and succeed. Life appeared to be going well for him and he was enjoying his professional life. After a few quiet months or was it quarters, he was suddenly looking for a change with agitation that was alien to his happy go lucky nature.
Having spent almost a decade in the company, Y had seen career growth that would be the envy of many; his profile encompassed local and global responsibility. Staying with one industry through his career made him a specialist of sorts and he became a star. His efforts outside of work also made him quite popular in his chosen field. His company had maintained leadership in a competitive industry locally and globally carving a niche with their products. Out of the blue one fine day he called seeking greener pastures.
He was a jolly good fellow and so said all of us ! The life of any gathering, ready with a joke (sometimes too quick), Z had steadily risen through the ranks with some help from his Mentor. Through the 5 years in his company, he had strengthened the foundation and completed seemingly impossibly difficult projects that his predecessors could not. Promoted every alternate year, he had taken new challenges as they came and successfully dealt with them. Over a drink he broke down seeking to leave the company that launched him.
The 3 incidents above spanning 3 different companies and 3 different industries had the 3 CIOs reaching out to me within a span of few months. Maybe it was coincidence, but it was almost as if there was concerted action against my former team mates. All of them had high levels of anxiety and all of them wanted to get out as quickly as possible. Their stories were quite different and then they had many common elements too. They were victims of the same malaise which appeared to be more widespread than reported.
Take the first case, the company management reins passed from founder to the next generation. X found joy working with him as his new manager with an Ivy League pedigree used technology as a native. He drove the company fast and furious, recklessly at times as seen by the old school, he wanted to get somewhere in a hurry. X attempted to run with him and soon found himself at the receiving end frequently irrespective of root cause. He soon realized his non Ivy League or named Institute stature made him an outcast in the inner circle.
Y had done well through the years growing from mid-level to heading the function eventually. His sharp and quick eye for detail made him a popular choice to be included in any team struggling with a tricky problem. The company saw CEOs change thrice over his tenure; all of them nudged him to greater heights. Law of averages caught up with him; the latest CEO hired across layers from his previous company sidelining most old-timers. Y used the last resort calling global compliance which saved his position but killed his career.
Z had a new manager who was task oriented; the resultant change in workload gave Z a high. He rose to every occasion and delivered to promise. Some of the initiatives were industry firsts giving the company a competitive talking point. He was outspoken which was not a negative, his quick wit and mannerism portrayed him of lesser maturity. His work was commended but his manager thought he needed to grow up. Thus despite the success a search for a senior leader above him was launched forcing him to introspect and seek options outside.
Success is no longer a guarantee for continuity; political hues and cronyism seem to be the new mantras required in large doses. Managers are looking for comfort within their teams in new environments thereby throwing enterprise culture and values out of the window. In the quest to succeed, tolerance to such behavior is accepted as part of the game. Collateral damage with some exits does not appear to perturb owners and Boards. By the time the realization hits the company, the damage is already done which takes a long time to recover.
The new email is a retrograde step and not an upgrade; life was so good with the older system. What is happening with our IT? The world is moving ahead and we are going backwards. How do you expect us to be effective when we cannot even communicate with our customers? I don’t know what to do, probably this year again thanks to IT we will have some unhappy customers!
I had approved the investment almost 2 months back and you are telling me that we still have not placed orders? How do you expect us to work? What is the problem? As the Business Head when I have given the go ahead who can challenge the decision? Why are you trying to save a few thousand dollars? Do you know that the loss to business due to this delay is in hundreds of thousands?
These are a sampling of lunch time ranting as described by CIO friends. One of them was a good guy, dedicated, focused, always ready to please; his team imbibed the same ethos and worked hard, always available to the business. He was successful in a typical way with conscious budgets and a fair set of initiatives that kept the engine humming. Inorganic growth and lateral expansion caught him capacity constrained which was beginning to hurt. He did not like the lunch time discussions anymore which ended up embarrassing him most of the time.
A long time back one of my managers gave me an interesting insight; we all typically have our office lunch with our teams. If you look around in the lunch room you will see a finance table, legal table, an IT group, and so on. These groups get together automatically and enjoy shop talk and extended work discussions over the rice, curry and bread. In open organizations there is a reserved table for the Managers where you will find the CXOs quietly having a meal with small talk. Most employees stay away from this table and likewise the CXOs.
My manager who became and stayed a friend believed that the world should not be polarized this way. He too ate at the staff canteen whatever food was served and consciously sought new groups every day to share a meal with. Likewise he expected all of us at C-level to break our comfort zones and network with staff across levels and functions. The discussions though initially polite became a tool to measure the pulse of the company. Employees warmed up to the idea and based on their ease opened up with some of us.
Observing this through the years I realized that the behavior is universal; birds of feather flock together. People gravitate into groups with familiar faces and shun the relatively unknown; if they find no seat within their groups they rather sit alone and not with another group; they did what they did, it was automatic. I saw similar behavior in social gatherings, networking dinners and wherever people got together. Off course there are exceptions who love to meet new people and merge into any group easily.
Practicing what I learned whenever possible, the initially forced experience soon made me welcome into any group. No walls went up or conversations died when I joined a group for lunch. The connect with people created empathy that I could use in various discussions around problems and opportunities as well as driving change which came along with the interventions IT created. We connected beyond work related transactions and built many friends who light up when we meet even in a casual encounter on the streets or a mall.
One of the answers would be that it is all about anticipating requirements, partnering the business and being proactive in your discussions. If you are a good CIO who is aligned to the business, blah, blah … lunches can be fun. Your customers’ perceptions are your reality; any change takes a lot of effort and consistency. Another view is that some people will never be satisfied whatever you do; so don’t get impacted by all these ramblings, manage them separately and keep going. Go and sit on another table rather than get indigestion.
Once upon a time there was a disruptive technology that took the corporate world by storm. Every executive aspired to own it and badgered their respective managers and IT to provide it across the ranks. The investment was quite high and thus it was rationed off down the hierarchy incrementally. The haves strutted it proudly and for the wannabes it was a classic case of owners envy, neighbors pride. It took a while to become a commodity and then the paradigm changed again. I am referring to mail on the mobile that every executive wanted.
It was fashionable to have a message footer which indicated which device you used to send a message especially if it was not a PC or laptop. Notifications and alerts from these devices ensured that you knew 24X7 whenever a message arrived. Initially due to enthusiasm and then by habit replies were almost instant. Whether in meeting, at a social event, getting the nightly beauty sleep, or traveling including driving, there was an intrinsic urge to respond. The resultant impact to mind and body created rifts in relations, disease forms and cures.
Multitude of newer devices and smartphones eliminated the divide between the privileged and the bourgeois. Consumerization of IT created newer possibilities which the CIOs struggled with; added to this social media addiction completed the digitization of the populace. Armed with multiple devices to separate personal from corporate, the demands on the individual from peers, friends, acquaintances, and the illuminati made everyone a slave in the connected world with pings and vibrations of all kinds vying for attention.
We want to achieve more in lesser time and thus multi-task in a hope that within the same time more will get done. Thus people flit from moment to moment with their attention darting from one thought to another; the flurry of activity divided between competing tasks and priorities. Interruptions now enter less in physical form and more on multiple connected devices attached or surrounding us. The result is that everything ends up taking longer and little gets done which pushes us to do more of the same entrenching us deeper into the quicksand of inefficiency.
Empirical data from numerous studies has proven that attention span stands reduced by 3X over the last few decades and continues its downward spiral. We don’t have time is the pet peeve of busy corporate executives buried under the mountain of unfulfilled tasks and missed deadlines. Numerous apps, email alerts, and push notifications keep us bound to the devices and habitually pressurizes us to take notice and demands action. Unable to comprehend the nemesis they struggle to stay afloat with no evident way out.
Everyone is working harder in their quest to get much done; longer hours has become the norm. Work life balance anyone? Shun the thought and take some work home; get it done while you travel and the rest when you get there. There are no options for the individual; enterprises now have choices from the downsized, unwanted and freelancers; there is always someone who will do it cheaper, faster, probably in the neighborhood or oceans apart. Technology also makes it possible to automate many processes and eliminate the inefficient.
Effectiveness of meetings dwindle and urgency overrides the important with perceived time value of information becoming a key measure even when it influences no change in outcomes. Time is getting filled with activity leaving no discretionary activity possible. People attending “Time Management” seminars find that it sets them back with the time spent. The urgent has overtaken our lives and the important is neglected.
A generation of digital slaves emerges from the shadows; they walk with bowed heads with their hands at diaphragm level holding their (master) devices, attentive eyes glued to glowing screens beckoning them to the inane and unimportant. Some devices strapped to different body parts communicate with other things which in turn influences the slave’s behavior. The promise of a better future keeps the addicts hopeful and asking for more. It is scary that we are beginning to forget what life used to be and what it can be.
Times are getting better for most CIOs with economy looking up, growth back on the agenda, business wanting to create a digital enterprise, the hype around various technologies like Cloud, Social Media and what have you dying away. CMOs and CIOs have figured out a way to work together while CFOs have set the governance on budget management and are not obsessed with Return on Investment as the only measure. IT budgets are beginning to show signs of revival and so are expectations on the new projects and possibilities.
Some mature companies used the lean period to reinvent themselves and re-engineer processes; they invested in refresh of not just the servers and other hardware which could be had for a steal with piled up inventories with vendors, they also used the spare capacity with people to upgrade their ERPs and build new systems. Many CIOs were busier in the last few years than they had been when business was booming. They also started seeing attrition in the team with the job market opening up which added to the challenge.
Good times bring a lot of events, seminars, offsite meetings, and invitations to all kinds of gatherings which have great headlines to attract all and sundry. One of the CIOs whose spouse was traveling mentioned that she hadn’t cooked for a week by just accepting these. Except that they rarely offer any major learning or insight; after a while even the networking turns stale with the same people ending up in every event. It is another matter that the structure of events has remained the same over the years defying logic and evolution.
I was thus surprised to hear about a CIO who never attended any events or seminars or exotic trips that are organized by the friendly vendors. No one had ever seen her in any of the events despite the long years she had put in into the industry. She never responded to any phone calls, messages or emails or any attempts to reach her. It did not matter who was inviting her, Chairman, CEO, Account Manager, she remained a hermit. Her reclusive ways created many stories and not all of them were flattering or positive.
Her team did not know how to react to such a situation; they wanted to network and socialize and get exposure to what was happening in the world outside. They were reluctant to ask as they never saw their Boss ever accept any or go to such gatherings; her demeanor did not invite anyone to venture to ask. New team members who came from different environments found this quite unusual. A few who were bold enough to participate on their own enjoyed the benefits; their rationale, it is better to ask for forgiveness than permission.
So when I met with one of her brave team members I thought I would attempt to unravel the mystery. I was perplexed by what I heard. Her calendar was double booked many times with internal meetings; she was always flitting between meetings without spending enough time to get to the bottom of the issue or to understand the impact or action items. She almost always turned up late for the appointment and would be out of the room no sooner the meeting started with a phone call interrupting her transient presence within the first five minutes.
She spent a lot of time on the phone, but then she never took calls from the vendors and most people internally found her phone busy. Few who had spent long years with her knew it was not her partner. The interruptions had become part of her persona that people no longer saw that as abnormal behavior. Within her company they had gotten used to meetings without her even when she accepted them. Someone dared ask her about the calls; if looks could kill, the poor inquisitive lady would have died on the spot.
Everyone speculated about her leadership, effectiveness, longevity and survival; difficult to comprehend unless your family owns the business or there was a relationship of another kind (neither was the case). Her team was at the receiving end of rebukes while she remained immune to the environment. Her team was adequately effective and the business had limited expectations from her. Working at her lowest level of inefficiency she had rarely been challenged for innovation or transformational leadership.
I wonder what would happen to her should she join another company?
She received an alert from credit card Company of a debit of $50 from the neighborhood grocery store. She panicked and then remembered that it was probably the refrigerator ordering replenishments (My refrigerator has gone shopping). She was however worried about what did it end up ordering. Having finished the orange juice from the last purchase and not wanting anymore, nor the horrible cake that came as an offer last time (She was anyway trying to lose weight). She then received the e-bill on mail and was shocked to see sausages and beef steak! These did not exist in the master list and decided to visit the store on the way back to find out what had gone wrong.
Recently I was at a cybersecurity conference in the country which boasts of the maximum number of IT security startups and companies. They continue to redefine information and cyber security in ways that most of us would find hard to imagine. The new and old are not focusing just to make better antivirus or firewalls or mobile device management solutions; their R&D has transcended conventional boundaries. With Internet of (Every)Things and all kinds of devices communicating with again all kind of devices, the channels need to be secured.
The use cases discussed sounded straight out of science fiction or futuristic movies except that all were stark reality which we are rarely exposed to. The innocuous IP audio-conferencing phone in the meeting room as a listening device or the video conferencing equipment transmitting images or streaming live unknown to everyone. Directional antenna sniffing the airwaves and breaking wireless networks or RFID tags or readers in a manufacturing facility misbehaving and making a mess of the inventory and production plan.
At our homes the number of connected devices is increasing; for me it started with my streaming media box, then the television followed by the gaming console which was fighting with multiple tablet and laptop computers. My new car wants to send messages to the service station when it felt sick and my GPS has a mind of its own routing me through lesser known roads in a quest to get me to my destination faster and screwing up. When I have not finished my daily dose of walking my fitness ban posts on social media embarrassing me.
It is not a stretch of imagination to believe that these devices can be infected with malicious code which may change behavior or purpose. Individuals unknowingly changing their daily pattern or nudged in an alternate direction by compromised devices can impact their professional actions and outcomes. Why do you need to break into a trading system, break the trader, it’s easier! Shutting down an electrical grid is big effort, shut down people or change them; use sensors to hack into the system. I was stunned by the possibilities.
In the future with every device connected and transmitting or receiving information, intelligence is corruptible and creates new scenarios of what can go wrong. Recent demonstrations though not malicious in intent of some highly computerized cars being hijacked predict an unstable future. The ability to patch or secure the large number of devices (estimated at 20 billion plus), company provided or individual owned BYOD enabled will be a veritable nightmare for the enterprise security managers and CIOs.
Enterprises are pushing to create new opportunities that become possible with IoT; some of these maybe seeded with hare brained ideas though I believe many will survive and become the next big thing of tomorrow. I believe that everyone needs to be cognizant of the fact that IoT is here to stay; how we leverage it within our ecosystem will give a differentiated advantage that success stories are made of. Every new hyped technology falls through the trough of disillusionment before becoming mainstream. Stay invested.
She reached the store and challenged them demanding a refund and the fact that they had goofed up majorly. In return they showed her the order which did contain specific brand of sausages and steak. She called the refrigerator company who informed her that the last software upgrade had added social media features and her refrigerator had accepted a request from the specified company to receive promotions. The conversion of the promotion to order was probably a bug which they will investigate and patch the firmware.
I wonder if a virus were to infect the refrigerator, what would it do?