<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bassam Fawaz on Medium]]></title>
        <description><![CDATA[Stories by Bassam Fawaz on Medium]]></description>
        <link>https://medium.com/@bassam.fawaz?source=rss-33704155f258------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*aQOV9NpQv0uuCN906oFkTw.jpeg</url>
            <title>Stories by Bassam Fawaz on Medium</title>
            <link>https://medium.com/@bassam.fawaz?source=rss-33704155f258------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:00:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bassam.fawaz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Wither the IT Department?]]></title>
            <link>https://medium.com/@bassam.fawaz/wither-the-it-department-a54338308bdb?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/a54338308bdb</guid>
            <category><![CDATA[it-leadership]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[it-department]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Sat, 22 Jan 2022 16:22:43 GMT</pubDate>
            <atom:updated>2022-02-01T20:10:17.924Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*pU3q9iff9wRsPYr5FIr9Yw.jpeg" /></figure><p>For the decades that I’ve been in the IT profession pundits have predicted the demise of the role of the Chief Information Officer (CIO). So far, those predictions have not come to fruition. In fact, not only has the role of the CIO transformed multiple times and thrived, it became progressively <a href="https://www.wsj.com/articles/pandemic-supercharged-the-role-of-chief-information-officer-11632164313">significan</a>t as organizations grew more technology-enabled and management information became increasingly vital to business as we chartered the world of digital, mobility, and AI.</p><p>A new mantra is now in the air, predicting the demise of the IT department and arguing that it is no longer relevant or needed. It is a tempting thought, especially for those who have grown frustrated with their IT departments (often for good reasons). An <a href="https://www.wsj.com/articles/get-rid-of-the-it-department-11637605133?st=kj7og9edata0iv6&amp;reflink=article_gmail_share">article</a> in the Wall Street Journal last November, titled <em>“It’s Time to Get Rid of the IT Department”</em>, garnered a lot of attention and equipped those frustrated souls with well-articulated arguments to pull the trigger on their IT departments. Similar articles on the theme have appeared in business publications and online blogs.</p><p>The case made by the “R.I.P IT Department” (or “RIP IT”) camp deserves notice. In summary:</p><ul><li>What keeps breathing life into IT departments is antiquated legacy systems that are too costly or complex to replace with simpler solutions that provide superior business value.</li><li>Today’s workers are far more technology-literate than their brethren of yore. Many of them know about some technology products more than the IT staff.</li><li>The average consumers’ IT experience in daily life (web, mobile, IoT) is smoother and more self-empowering than what they face at work with onerous IT processes, rules of conduct, and slow responsiveness.</li><li>Technology is now in the fiber of business. It no longer makes sense to have a “department” dedicated to it.</li><li>The Cloud has been a game-changer: rather than wait months for IT to design, build, and deploy an environment, it can be acquired and put to use in days (or hours).</li><li><a href="https://en.wikipedia.org/wiki/No-code_development_platform">No-Code</a> or <a href="https://en.wikipedia.org/wiki/Low-code_development_platform">Low-Code</a> solutions enable business users to build and launch applications without the involvement of the IT department. These tools accelerate time-to-market, with the secondary benefit of reduced cost of development.</li><li>Doing away with the IT department resolves the chronic problem of IT and Business alignment. IT would become a piece and parcel of business activities, requiring no distinct strategy, budget, or alignment.</li></ul><p>The <em>WSJ</em> article goes further by averring that “having an IT department is exactly what will prevent companies from being innovative, agile, customer-focused and digitally transformed”, and that it has become an island inside the business.</p><p>IT professionals may find it difficult to refute these harsh pronouncements entirely. Some are statements of fact, others indictments against IT departments that, in many organizations, have failed to adapt to current realities and reconfigure themselves to better assimilate the work demands and habits of IT consumers.</p><p>But are these declarations true for every organization and do they make the case to “de-fund” the IT department?</p><p><strong>For Real or a Pipe Dream?</strong></p><p>To answer this question, let’s journey through the mind of fictional Carl, the CEO of a $500M, 1100-employee company, with multiple divisions in the US, Europe, and Asia. Carl reads business publications religiously, especially articles about IT. The subject is not his expertise, but he knows enough to recognize its importance to his business in today’s digital world and to be mildly skeptical of its ostensive cost/benefit equation.</p><p>Doing away with the IT department that is costing his company a little over 2% of revenue (though he never quite understood the significance of this number) is an enticing idea, especially since it was recently brought up by a director of his company’s board. He sits on his porch one Sunday morning daydreaming about a life without the IT department.</p><p>Thanks to insightful narratives like the aforementioned <em>WSJ</em> article, the rosy side is easy to size up. A judicious executive, Carl knows there must be drawbacks. Thoughts rush through his head:</p><ul><li><strong>Can we pull this off?</strong> We had a heck of a time staffing implementation teams for every major technology project we’ve undertaken. We sought people with excellent business and technology skills to fill the roles, but we still made the statistics of <a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41">troubled IT projects</a>. Why would turning IT over to these same people yield a better outcome than when we asked them to co-drive or partner on IT projects?</li><li><strong>The No-Code/Low-Code panacea</strong>: While the adoption of no-code tools by business users is on the rise, in nine out of 10 cases IT departments continue to be involved, according to a Creatio <a href="https://www.creatio.com/page/the-state-of-low-code-no-code-2021-report">survey</a> of 1,000 IT executives who have introduced the platforms into their environments. Stunningly, a Zdnet <a href="https://www.zdnet.com/article/even-in-low-code-software-development-it-departments-still-need-to-hold-users-hands/">article</a> on that topic reports that only five percent of low-code/no-code development moves faster than traditional IT-centric development. The low-code development approach still requires a basic understanding of underlying technologies and IT acumen, hence the need for IT to hold users’ hands, according to the article.</li><li><strong>I only ride ’em…:</strong> There is a scene in the WW2 movie “<em>Kelly’s Heroes</em>” where the Master Sergeant asks his platoon tank commander, Sgt Oddball, why he was not helping the crew fix a broken-down tank, and Sgt Oddball sardonically replies <em>“I only ride ’em, I don’t know what makes ’em work”.</em> Today’s workers see technology as a tool to accomplish a task, but very few of them have a desire to get under the hood and “fix the tank”. I doubt that the expensive Ivy League MBAs we hired last year would prefer to tinker with apps and servers instead of the specialties we hired them for (Finance, Marketing, Supply Chain, etc.).</li><li><strong>Will this improve our data health? </strong>Our digital transformation journey and business intelligence efforts have been marred by poor data quality. We are on par with the 71% of respondents to a <a href="https://data2020summit.com/wp-content/uploads/2019/09/Enterprise-Data-Quality-Survey-2019_FINAL_MC_190620.pdf">survey</a> that expressed shaky confidence in the quality of the data that is sent to their analytics platforms. And this is with an IT department that tries desperately to maintain a data governance framework. What will happen when we have more departmental data sources with little or no consistency?</li><li><strong>Will the dominoes tumble?</strong> When I took over this company, which had grown in part by a series of acquisitions, divisions were operating with a high degree of IT autonomy. As a result, these divisions were running different versions of the same industry-specific software, causing excessive costs from computing maintenance to management reporting because of lack of integration. It was only after a long and arduous IT architecture effort that we established ownership of business applications, security and system administration, complex integrations, and overall consistency in the IT landscape. Will we be at risk of losing control again?</li><li><strong>Any security worries?</strong> Brian, the tech wizard in Sales, became his department’s hero recently by installing an online sales system in days. But he neglected to secure a copy of the transaction file that exposed customers’ credit cards and personal details (this actually happened, and Brian’s defense was “I am not an IT guy!”) With cyber breaches on the rise and hackers becoming more sophisticated, will do-it-your-way departmental IT make our corporate data more secure or vulnerable?</li><li><strong>Where will we house the unpleasant stuff?</strong> Our IT Service Desk is perhaps the busiest group in the company. They field and resolve users’ problems and queries related to hardware, software, and anything with a button on it. We track their issue-resolution time to ensure that they are effective in getting people back to work. Will every department in the company need to have its own help desk? Will every department choose its vendors to procure similar products? What else will fall out of the basket that we’ll need a home for?</li></ul><p>Carl awakens from his daydream with unease. It did not take him long to think of a few critical areas that would make this pill hard to digest. Doing away with the IT department may indeed boost departmental agility, but he could not see his company doing better overall. Perhaps the next CEO will have the nerve to try this out when conditions are more opportune and the concept more mature.</p><p><strong>No Pass for the IT Department</strong></p><p>Our astute fictional CEO gave us a brief illustration of the cost of dispensing with the IT department in a company like his. That does not prove the “RIP IT” enthusiasts wrong, only that what they advocate does not apply to every organization. Some organizations <em>can</em> do without an IT department:</p><ul><li>Start-ups with limited scale and resources that would rather shift capital from IT investments to other parts of their operation</li><li>Smaller enterprises with a narrow operational scope and minimal technology requirements</li><li>Companies with minimal collaboration needs where employees do not need a cohesive platform</li></ul><p>For most of the rest, shedding the IT department will likely be akin to a do-it-yourself root canal.</p><p>None of this makes the IT department immune to irrelevance. A decade or so ago IT departments complained about and cracked down on “<a href="https://www.mcafee.com/enterprise/en-us/security-awareness/cloud/what-is-shadow-it.html">shadow IT</a>”, when they should have seen it for what it was — a no-confidence vote by IT users who sought modest (and often crude) tools to go around the IT department and accomplish their work unhindered. They now have a wide range of better choices.</p><p>The centralized, protectionist, IT department that owns all the solutions and plays internal technology cop is no longer relevant in today’s environment. How it can remain a core of the enterprise is a topic for another post, but it starts with delineating between what IT should own (i.e., security, architecture, integration) and what it should orchestrate through counseling, training, and co-creating policies with peer departments. This is a job for the IT department, but it must be choreographed by the entire organization to respond to workers’ needs and preserve the core value of IT — with or without an IT department.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a54338308bdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Conundrum of IT-Business Alignment]]></title>
            <link>https://medium.com/@bassam.fawaz/the-conundrum-of-it-business-alignment-a5e01bb659b?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5e01bb659b</guid>
            <category><![CDATA[business-it-alignment]]></category>
            <category><![CDATA[it-leadership]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Fri, 24 Sep 2021 15:13:29 GMT</pubDate>
            <atom:updated>2021-10-21T00:33:17.526Z</atom:updated>
            <content:encoded><![CDATA[<h3>It Takes Two to Tango…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*-N1l9KLICfCYd4mDoOaM4w.jpeg" /></figure><p>In 2003, when IT professionals were still celebrating triumphs of the previous decade (<a href="https://www.nationalgeographic.org/encyclopedia/Y2K-bug/">Y2K disaster</a> avoidance, ERP implementations, pre-bust Dotcom wizardry), Nicholas Carr published a controversial <a href="https://hbr.org/2003/05/it-doesnt-matter">article</a> in the Harvard Business Review with the provocative title <em>“IT Doesn’t Matter”</em> in which he argued IT had become a commodity and that companies should think twice before investing in IT as a differentiator. IT workers were indignant, maintaining that someone who had never written code, stood up a server, or manned a service desk, had no business opining about IT. They objected to him treating IT like pork bellies.</p><p>Many of us, however, knew that Carr was on to something: We had watched and heard of companies spending fortunes on IT products, with little or nothing to show for it. Many were still suffering from botched (and expensive) IT upgrades. Whose fault that was is still open for debate. There was a conundrum: IT was recognized as a business necessity, yet viewed as a cost pit gulping pricey ware that quickly becomes obsolete; businesses were vexed that their enormous technology spending had not delivered the silver bullet that leapfrogged them ahead of their competitors; and the techies were just not <em>getting</em> what the business wanted.</p><p>Carr struck a chord with frustrated top executives now looking to tame IT. In a prior era, IT (EDP or MIS, as it was called then) was largely a back-office facility confined to specific uses, and a black box the intricacies of which were known only to its operators. The Internet, Client-Server, and the Y2K-fueled ERP wave that took place in the Nineties, their associated high costs and impact on the enterprise, made IT emerge from the shadows. Sins that were previously buried quietly in the family plot now received scrutiny from senior managers who were keen to know what’s in the black box and how to make IT hum with the rest of the orchestra.</p><p>The ability to “align IT with the business” became the most desirable trait sought in CIO candidates. Many IT leaders (including yours truly) listed “IT alignment” as a key competence on their resumes as if it were the elixir of all alignment disorders. Countless books and articles have been written about the subject, and consulting careers flourished to help companies address the elusive alignment. In IT circles and industry conferences, the subject is always on the agenda, and IT leaders delight in recounting how they led their companies to alignment nirvana.</p><p>Yet, the problem persists. Even in this day and age of ubiquitous technology when virtually everything we touch is IT, “<a href="https://www.forbes.com/sites/peterbendorsamuel/2021/04/26/why-is-it-and-business-alignment-so-elusive/?sh=3f599b0627b4">the business/technology chasm</a>” is still a problem.</p><p>This is no surprise. For one, the term has been applied generically to a variety of conditions: misalignment between corporate and regional (or divisional) IT; conflicts between IT and go-it-alone departments (exacerbated by the Cloud, where departments prefer to bypass corporate IT in favor of their solutions); disagreement over who owns the technology roadmap (autonomy); personality conflicts and ego clashes; etc. None of these situations is necessarily unique to the IT department, and each is a product of elements particular to the organization and the people involved.</p><p><strong>Different Strokes for Different Folks</strong></p><p>Two types of organizations seldom gripe about IT-Business alignment: (Typically) small companies where IT is a utility to maintain essentials (email, networks, lights on), with competent enough IT staff to do the job; and enlightened companies that have long incorporated IT into everything they do and consistently stride ahead. For the struggling rest, a few — or all — of the following factors might be present:</p><p><strong>Pin the tail on the donkey:</strong> It happens more than you think: In a time when technology and digital have become central to every aspect of business, CIOs are still left out of the business strategy discussion and, at best, merely informed of it. This leaves the CIO trying to accurately divine the business intentions and IT catching up with initiatives already in motion.</p><p><strong>Miscasting:</strong> CIOs with profiles that made them wildly successful in one company can struggle in another, because of management culture, support, and control mechanisms. Also, some companies set out to hire “innovative” and “strategic” CIOs when in reality they simply want a supreme help-desk technician.</p><p><strong>Tech babble:</strong> Perhaps the most frustrating aspect of dealing with IT, when conversations about business solutions are shrouded with technical jargon that sounds to the listener like obfuscation and turf protection.</p><p><strong>Scapegoating:</strong> Many technology projects are flawed from the start, and when they run into trouble, IT is most likely to be blamed when in reality the <a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41">entire organization may be culpable</a>.</p><p><strong>Free-for-all:</strong> Lack of processes to plan and prioritize IT projects and resources, and assign responsibility for outcomes, leads to chaos and results in disappointment all around.</p><p><strong>Budgeting:</strong> Companies often allocate a bucket to the IT department to serve the entire business, instead of earmarking budgets for specific business projects and needs. This causes department heads to vie for IT resources and, in the absence of any governance, pits the CIO against her peers should she prioritize one project over another.</p><p><strong>Outdated delivery methods</strong>: Many IT departments still adhere to old project and development methods that simply do not deliver fast enough while keeping their business counterparts largely in the dark until the (often disappointing) unveiling.</p><p><strong>Can’t We All Get Along?</strong></p><p>Let’s be blunt: Misalignment is a euphemism for <a href="https://www.inc.com/lolly-daskal/50-forms-of-dysfunction-in-the-workplace.html">dysfunction</a>. Repairing dysfunction is not the concern of one department or leader, but an organizational undertaking. CIOs can do a lot to influence the conduct of their departments, but can be effective only in a broader organizational context.</p><p>Alignment happens when two (or more) people have the same vision of what must happen one, two, or six months downstream and row together to the destination.</p><p>The first dose of the remedy is to stop talking about Business and IT as if the latter is a wagon to be hitched to the train, rather than an integral part of the machine. The conversation may happen, but I don’t recall ever hearing about aligning Finance, Operations, HR, Sales — or any part of the value chain — with “the business”. So, why is IT still the object of alignment when it has become indispensable to every enterprise and inextricably connected to successful business outcomes?</p><p>IT has probably undergone more drastic changes in the last decade or two than any of its peer business functions. Activities and roles that were once embedded in IT have now moved into the business and, often, IT professionals have moved into operational roles outside of IT. This cross-pollination can help to get everyone to row in the same direction — if leveraged correctly.</p><p>IT workers must recognize that their business peers constantly interact with technology (i.e., smart devices, <a href="https://en.wikipedia.org/wiki/Internet_of_things">IoT</a>), and now expect the speed and convenience of a downloaded phone app from corporate IT, and see in Cloud-based solutions attractive alternatives to it. Their business colleagues must educate themselves on the complexities of enterprise IT, the importance of integration and data management in the age of big data and <a href="https://techbullion.com/data-quality-why-it-matters-in-machine-learning/">Machine Learning</a>, and the business and security risks involved in implementing enterprise-grade solutions.</p><p>Cultivating this mutual understanding within a culture that fosters trust and cooperation is hard work, but it paves the way to healthy dynamics and eventual alignment of purpose</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5e01bb659b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation or Transfusion ?]]></title>
            <link>https://medium.com/@bassam.fawaz/digital-transformation-or-transfusion-85c183c18524?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c183c18524</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Fri, 02 Apr 2021 19:05:19 GMT</pubDate>
            <atom:updated>2021-10-03T21:16:39.340Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Digital Transformation or Transfusion ?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*-DXuLdhhD00fthdWfwzMzQ.gif" /></figure><p>At an IT conference dedicated to <a href="https://en.wikipedia.org/wiki/Digital_transformation">Digital Transformation</a> a little over a year ago, I listened to the CIO of a major retailer vaunt the advances his company had made with digital transformation using state-of-art technologies and products from innovative technology vendors. Impressive, I thought. A few weeks later, my wife bought an item on that retailer’s website which arrived missing a part. On a Sunday afternoon, we stopped by the retailer’s store nearby to exchange the item. After explaining the problem to the customer service person and requesting an exchange, she stunned us when, without saying a word, she handed us a refund slip. As we tried to explain again that we wanted an exchange and not a refund, her supervisor intervened and explained that a) they do not stock the item in the store; b) their online system does not link to their in-store system; and, c) the in-store system does not allow an exchange for an online purchase, so she can only issue a refund. The two employees behind the customer service desk remained indifferent as my wife murmured she could buy the product on Amazon since it was available and a tad cheaper.</p><p>A few weeks ago, a similar experience with another large retailer, also claiming digital prowess: their online system shows an item out of stock at all locations in my area, and it won’t be back in stock for another week. Can I place the order anyway to be fulfilled when the retailer has the item back on the shelf? “No, sorry. Our system does not allow that. Please check again on the 29th when we expect the item back in stock” explained a very polite customer service agent. You guessed it — I found the item on Amazon, and for less.</p><p>These are but two examples of what I have encountered frequently since “digital transformation” became the buzz phrase du jour, and that makes me wonder about the kind of digital transformation these companies are touting, and perhaps explain why a company like Amazon has been encroaching on traditional retail for so long while everyone plays catch-up.</p><p>Definitions of Digital Transformation abound, but one fundamental aspect that is generally agreed upon is that it is about building digital front lines (customer-facing, loyalty) and modernizing the business backbones (efficiency, quality, supply chain). Consider the few glaring breakdowns that the stories above illustrate from a customer’s perspective:</p><ul><li>Failure to deliver a more agile, efficient experience to the customer</li><li>Ineptness in a technologically driven market</li><li>Poor enablement of their employees with digital technology</li><li>Poor or no digital integration as a centerpiece of their operations (online and brick-and-mortar)</li><li>A weak motivation to deliver a better experience across all aspects of their operations–employees, customers, and suppliers.</li></ul><p>These companies, and others like them, may have implemented <a href="https://www.ibm.com/cloud/learn/what-is-artificial-intelligence?mhsrc=ibmsearch_a&amp;mhq=Artificial%20intelligence%20">Artificial Intelligence</a> engines, invested heavily in sophisticated analytics tools, and use <a href="https://www.investopedia.com/terms/m/machine-learning.asp">Machine-Learning</a>, <a href="https://www.investopedia.com/terms/c/cloud-computing.asp">Cloud</a>,<a href="https://www.ibm.com/topics/mobile-technology"> Mobile</a>, <a href="https://www.investopedia.com/terms/i/internet-things.asp">IoT</a>, and other tech credentials often cited as evidence of earnest digital transformation. Yet, none of those prevents customer defection–and a sour experience-when implemented with the wrong focus or priority.</p><p>A digital transfusion of the hottest technologies does not a transformation make; certainly not when organs of the business are dysfunctional, outdated, or unreceptive to the brew.</p><p>Digital transformation journeys have a <a href="https://cio.economictimes.indiatimes.com/news/enterprise-services-and-applications/heres-why-80-of-digital-transformation-projects-fail/74450907">failure rate</a> akin to most technology projects. The reasons vary, but the essential elements I talked about in a <a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41">past post</a> are very much present. In fact, because digital transformation is not a product or a one-time event, but reflects a mindset and business execution that embraces constant change and agile integration of technology, it is more prone to failure in the short and long terms.</p><p>Happily, there are digital transformation <a href="https://www.inc.com/jason-albanese/these-4-companies-have-been-saved-by-digital-transformation.html">success stories</a> and companies that achieved <a href="https://biznology.com/2016/12/11-inspiring-case-studies-digital-transformation/">remarkable results</a> from their digital transformation efforts. Those organizations have a few things in common:</p><p>1. Their digital strategy is driven from the top, adopted across the board, and anchored to specific goals and results</p><p>2. They focus on improving the customer experience, engaging, and making it easier for the customer to do business with them</p><p>3. They prioritize increasing revenue (by growing their business) over cutting cost (by downgrading quality and service) (the airlines are a notable exception!)</p><p>4. They do not seek to reinvent themselves as <a href="https://www.investopedia.com/terms/d/digital-native.asp">digital natives</a> by haphazardly acquiring technology, but extend their traditional offering and value through carefully deployed new digital capabilities</p><p><strong>Digital for the Rest of Us</strong></p><p>Realistically, not every organization has the aptitude and traits to pull off successful transformation projects. The attentive ones, however, know that they need to act before they become digital refugees in their own markets.</p><p>Worthy volumes have been written about digital strategies, the dos and don’ts of digital transformation, and prescriptions for reincarnating as a digitally enabled organization. The material is enlightening, but it can make the task look daunting to most organizations. So, they react in one of two ways: 1) they get stuck in inertia, fearful of failure and the unknown, while the digital storm passes them by; or 2) they take the plunge, in a panic, buying a Hodge-Podge of technical gear, hoping to join the digital club–too often with disastrous results.</p><p>So, what is the average organization to do?</p><p>The answer depends on each organization’s make-up, priorities, digital stance, and intention (many airlines, for instance, made impressive strides with digital, but the traveling public has not seen that translate into better service or product). One thing I know is that digital transformation does not have to be one-size-fits-all or done on a scale that only Fortune 100 companies can afford. Nor does it have to be expensive and complicated.</p><p>A few points to consider:</p><ul><li>For much of my career, business strategy and needs drove IT plans. Many of us CIOs perfected the art of pinning every IT expense to a business initiative. Today’s digital market upends that line of thinking and requires smart organizations to build their strategies around what IT capabilities make possible. Making this cognitive transition is the first step on the road to digital bliss.</li><li>Starting a digital transformation with big, expensive legacy replacement systems and activities is a perilous approach. It will consume too much money and people resources, exhaust the organization, and distract from delivering the transformation benefits. A wiser approach would be to map out the business and, wearing the customers’ and employees’ shoes simultaneously, identify possible improvements across the customer experience from the perspective of each group, and determine what can and needs to be digital.</li><li>When the desired experience is defined, specific options and technologies that lead to the desired outcome can be identified. (For example, IT professionals know exactly how to integrate a supplier system to an in-store one, as they did for decades with more complex and cruder technology. That was not thought of as digital transformation, but simply as a routine business project).</li><li>Use an iterative approach. Consider <a href="https://www.atlassian.com/agile/scrum/sprints#:~:text=What%20are%20sprints%3F-,A%20sprint%20is%20a%20short%2C%20time%2Dboxed%20period%20when%20a,better%20software%20with%20fewer%20headaches.">sprints</a> of smaller, well-defined, technology-enabled projects. Those can quickly deliver measurable value to customers and provide quick feedback to inform the next value-adding step or project while reducing risks.</li><li>Lastly, there is no shame in being a smart follower. Study other companies’ digital journeys and learn from their <a href="https://www.forbes.com/sites/blakemorgan/2019/09/30/companies-that-failed-at-digital-transformation-and-what-we-can-learn-from-them/?sh=17ec3e4603c4">mistakes</a> and experience.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c183c18524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Missing the Mark: The Riddle of Troubled IT Projects]]></title>
            <link>https://medium.com/@bassam.fawaz/missing-the-mark-the-riddle-of-troubled-it-projects-a0d74ba7c30e?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0d74ba7c30e</guid>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[it-project-management]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Wed, 28 Oct 2020 19:10:29 GMT</pubDate>
            <atom:updated>2021-01-11T17:55:21.836Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Missing the Mark (II): The Riddle of Troubled IT Projects</strong></h3><p><strong><em>Part II</em> <em>–The Technical Factors</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7H1D7owqPxE2qLqvanQV5A.jpeg" /><figcaption>&lt;a href=”https://www.vecteezy.com/free-vector/mistake&quot;&gt;Mistake Vectors by Vecteezy&lt;/a&gt;</figcaption></figure><p>Failure seldom results from only one factor, but from the convergence of many that conspire to ruin even the best plans. <a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41"><strong><em>Part I</em></strong></a> of this article described the Organizational Factors that contribute to enterprise technology project failures. Equally significant are the <strong>Technical Factors</strong>, which entail the technology, methodology, and overall quality of the implementation. The most notable errors in this area include:</p><p><strong>Choosing the Wrong Software: </strong>In the 1990s, during the rush to implement <a href="https://www.investopedia.com/terms/e/erp.asp">ERP</a> systems to avert the Year 2000 (<a href="https://www.nationalgeographic.org/encyclopedia/Y2K-bug/">Y2K</a>) problem, SAP ran the motto “The best-run businesses run SAP” (later refreshed to “The best run SAP”). It was an appealing slogan. Many companies, large and small, hastened to acquire SAP believing it was the panacea that would not only inoculate them against the impending Y2K disaster, but also fix the flaws in legacy processes that had accumulated over many years, and enable them to join the club of the “best-run businesses”. The results were too often disastrous. SAP is a superb ERP system. Just like a Ferrari is a formidable car. But not everyone has the driving skills to handle a Ferrari (or can afford its upkeep). Those who conducted a poor evaluation of the software, its transactional demands, its implementation requirements, and its fit for their business practices, suffered failures in many aspects of their projects. Some companies that managed the implementation relatively well discovered afterward that they had bought “too much system” -overly complicated, too demanding, and too expensive to maintain.</p><p><strong>Ill-Defined Scope and Loose Boundaries: </strong>Poorly defined outcomes, and a lack or weak governance to ensure that milestones are met without distraction are a prescription for project failure. The proverbial “scope creep” creeps in only when confusing or changing requirements plague a project, the lines between the “must have” and “nice to have” are blurred, and project resources are shifted to accommodate the whims of a loud voice or someone in authority.</p><p><strong>Ambiguous Ownership:</strong> With the first sign of trouble, blame-shifting and finger-pointing arise, often making a bad situation worse. This is especially bad when a third party (i.e., a <a href="https://en.wikipedia.org/wiki/Systems_integrator">System Integrator</a>) is involved, with the hot potato being tossed among the customer, the vendor, the SI, and whoever else can serve as a convenient scapegoat. None of this can rescue a troubled project, but avoiding the situation from the outset by establishing clear roles and ownership of outcomes can save a ton of discord.</p><p><strong>IT in the Driver’s Seat: </strong>Because they are cast as technology projects, IT implementation efforts are often assigned to IT to lead (or IT jumps in to lead them) with nominal support from the rest of the organization. This is a mistake. It leads to the organizational disconnect mentioned in <a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41"><em>Part I</em></a>, shifting the responsibility for an enterprise transformation project to one department, and leaves IT with the master role of designing the business for the new system. Eventually, a drift occurs between what <a href="https://www.zdnet.com/article/qantas-airways-a-perfect-storm-for-it-failure/">IT builds and what the users of the system expect</a>, and the project fails.</p><p><strong>Inadequate Skills: </strong>In one case, a large organization assigned the leadership of a major technology project to a mid-level IT manager who had risen through the ranks as a competent programmer, earning the confidence of the company’s senior managers. He had no experience with large enterprise system implementations, and his knowledge of project management was limited to his own sphere within the IT department. Yet he was now managing a large-scale multi-million-dollar project, staffed by personnel from across the entire company, and managing third-party consultants and system integrators for the first time. Try as he could to learn on the job, grave problems were inevitable.</p><p><strong>Technical Architecture: </strong>In many companies, the IT environment grows by accumulation as there is seldom time to routinely examine the entire technical architecture. With the speed of change in technology, IT departments dedicate most of their time and resources to ensuring the stability of critical systems and introducing new components. That state is severely tested when the requirements of modernization or a new system expose deficiencies that the organization had learned to tolerate, such as poor data quality, fickle interfaces, antiquated hardware, and critical legacy systems past their <a href="https://www.pcmag.com/encyclopedia/term/end-of-life">end-of-life</a>.</p><p><strong>Poor Project Management:</strong> Project management methodologies have become like cults, with the fans of each (Waterfall, PRINCE, Agile, Scrum, Lean, etc.) strongly advocating their preferences. Too often, more time is spent on adhering to the methodology and the tools than on managing the project. Things gradually, then rapidly, get off the track, and energy is spent on keeping up appearances -the more desperate the situation, the more optimistic the progress report. A proficient project manager, an adept project team, and a supportive corporate culture make all the difference between success and a story for the annals of failures.</p><p><strong>Short-changing Training: </strong>When a project runs into trouble, the effort to bring it back on track will predictably tackle the budget. One item I have too often seen immediately targeted is training: Shrink the time allotted for it, reduce the number of people involved, and trim the budget allocated for those activities. (Ditto for User-Testing). Keeping with the Ferrari analogy mentioned earlier, it is like spending two hundred thousand dollars on your first state-of-the-art muscle car, but skimping on driving lessons. During Go-Live week, everyone is scrambling to navigate the new system, the few people who have been trained are stretched between their own duties and fielding questions from colleagues, and the users of the new system grow frustrated and turn hostile to the technology.</p><p><strong>Size Matters:</strong> A <a href="https://thisiswhatgoodlookslike.com/2012/06/10/gartner-survey-shows-why-projects-fail/">Gartner study</a> found that the failure rate of large IT projects with budgets exceeding $1 million was almost 50% higher than for projects with budgets below $350,000. There is a thrill in the Big-Bang approach, but the dynamics of large tech projects are too many to fully identify and mitigate. Breaking a large project into smaller ones of limited size, complexity, and duration, and making contingency plans to deal with unavoidable risks will do much to reduce the pain.</p><p><strong>Final Thought</strong></p><p>Here’s the conundrum: The culprits outlined in the two parts of this article have been known and written about for decades; so why do technology projects continue to fail or -to use a less traumatic term- become impaired? One simple answer is that organizations continue to commit the majority (or all) of these blunders, believing that their projects are somehow immune to the ills that afflict other people’s projects.</p><p>There is no magic solution to this chronic problem. Complex projects are hard to get right. Their success is predicated on the skillful blending of organizational and technical elements. As obvious as this perspective may appear, the experience and wisdom to make technology projects successful are regularly underestimated.</p><p>The leadership and rigor required for introducing a product, launching a marketing campaign, or taking on a competitor, are just as crucial for implementing transformative technology. As global companies become more reliant on information and analytics to run their businesses, refreshing their technology systems periodically is inevitable. But so are the risks involved. Alleviating those risks requires the diligence and attention of top managers, and expert hands to guide the process.</p><p>My intent in this piece is to provoke a few diagnostic questions from organizations that are contemplating technology endeavors. A candid readiness assessment of organizational and technical strengths, and ability to absorb likely bumps, should be a prerequisite to any tech project to improve its chances for success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0d74ba7c30e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Missing the Mark: The Riddle of Troubled IT Projects]]></title>
            <link>https://medium.com/@bassam.fawaz/missing-the-mark-the-riddle-of-troubled-it-projects-307c8114ad41?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/307c8114ad41</guid>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[it-project]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Wed, 14 Oct 2020 22:38:49 GMT</pubDate>
            <atom:updated>2021-01-11T17:48:15.114Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Part I</em> — <em>The Organizational Factors</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*ctmIflAD6hmKxFgDRY7oaw.jpeg" /></figure><p>Run an Internet search for “IT project failures” and you will see page upon page of entries recounting the woeful state of information technology project implementation, along with the catalog of casualties. The statistics are scary. Some estimate the rate of IT project failure as high as 70% or more, others contend it is far less. While some respected and credible sources <a href="https://news.gallup.com/businessjournal/152429/cost-bad-project-management.aspx">cite</a> shockingly high failure rates, it is difficult to know an accurate number, as too many sources of this information rely on small samples and questionable surveys that can mislead. There is also the definition of “failure”: some projects were undeniable failures that <a href="https://www.baselinemag.com/c/a/Projects-Processes/Kmart-SCM-Gone-Wrong">wrecked</a> (or almost wrecked) the organizations undertaking them; others failed in other ways –vastly exceeded their initial budget, came in awfully late, or caused business disruption with severe and long-lasting effects. Still others ran into trouble, but delivered the desired value to their organizations and made them better. What is well established, however, is that out-of-control IT projects happen at higher than tolerable rates. Even in the best-run companies, they have caused major financial losses, and cost many CEOs their jobs.</p><p>Worth noting is that the failed technology projects that usually make the news are not purely “technical” (i.e., infrastructure), but involve enterprise software (<a href="https://en.wikipedia.org/wiki/Enterprise_resource_planning">ERP</a>, <a href="https://www.salesforce.com/crm/what-is-crm/">CRM</a>, <a href="https://www.investopedia.com/terms/s/scm.asp">SCM</a>, <a href="https://en.wikipedia.org/wiki/Digital_transformation">Digital Transformation</a>, <a href="https://designingforanalytics.com/resources/failure-rates-for-analytics-bi-iot-and-big-data-projects-85-yikes/">Analytics and AI</a>) that permeates all facets of an organization. Hence the attention they elicit, and the scrutiny they warrant.</p><p>There is not a definitive set of answers to “why IT projects fail”, as the circumstances of each project differ. But the autopsies of troubled projects, and testimonies from business and IT leaders, corroborate several key contributing factors. For simplicity, we’ll classify them as <strong><em>Organizational</em></strong> and <strong><em>Technical</em></strong> factors.</p><p><strong>The Organizational Factors</strong></p><p><a href="https://www.solutionweb.in/system-implementation/">System implementation</a> is an across-the-board organizational undertaking, aimed at realizing the desired value from a new system. Preparing the organization, mobilizing people, setting and managing the stage for such a project are crucial to its success. Evidence of missteps in these activities encompass:</p><p><strong>Mis-characterization:</strong> Large IT projects are too often characterized as technology endeavors, often led by the Chief Information (or Technology) Officer, with participation from middle-managers representing their functional areas to ensure that their business processes adapt to the new system. The reality is that these are massive <a href="https://en.wikipedia.org/wiki/Change_management">Change</a> projects intended to transform the way an organization makes its product, manages its suppliers, interacts with its customers, and handles its internal processes. The work of every employee is likely to be affected.</p><p><strong>Top-down Vision:</strong> The CEO sees it, maybe another one or two high-ranking executives. Everyone else either does not see the value of embarking on such an arduous journey, or is skeptical and fearful of the outcome. That lack of shared vision and buy-in, often coupled with ambiguous sponsorship from the top, quickly translates into apathy or lip service down the organization.</p><p><strong>What does this mean for me?</strong> In the absence of a compelling reason for change and a convincing sense of urgency, self-preservation inhibits humans from destabilizing their working conditions by tampering with the tools and systems that help them succeed, or cause them to lose their jobs. They will resist, and may even exert covert (or overt) efforts to derail the project.</p><p><strong>All Roses and No Thorns:</strong> The purported benefits of IT projects can be impressive. Even when the business case cannot be firmly made, there is often a high opportunity cost for not upgrading technology or transforming business processes. But there are also serious pitfalls that seldom receive the adequate focus by overconfident organizations that believe a “can do” spirit is enough to prevent catastrophes. Enterprise IT implementation is hard work. Underestimating the cost, the timeline, and the magnitude of disruption to the business and the organizational culture, can be devastating even when the benefits are eventually achieved.</p><p><strong>Broken Guiding Coalition</strong>: In a seminal <a href="https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail-2">Harvard Business Review article</a>, John P. Kotter stressed the importance of a “powerful guiding coalition”, a small group of well-placed individuals, with active support from the head of the organization, that “come together and develop a shared commitment to excellent performance through renewal” as key to successful transformation projects. Too often, the steering committee that forms around a project comprises people with competing agendas, private doubts about the merits of the project, and largely motivated by reducing risk to their functional areas, careers, and bonuses.</p><p><strong>Clever People Behaving Badly: </strong>In a case I have seen, the talented division head of an international corporation, who from the onset expressed doubt about the benefits of a global transformation project, not only refused to walk the talk and share in the grand vision, but appeared to do everything possible to undermine the project. His behavior was not lost on anyone in the broader organization, nor was the fact that he was given a pass by higher-ups because he was a rainmaker. Morale soured as lower-level managers concluded that not everyone is living up to the same commitment, cynicism grew across the company, and eventually the entire effort collapsed.</p><p><strong>Organizational Discipline:</strong> Some organizations are highly successful because of an entrepreneurial culture that encourages maverick behavior and bucking the rules. That success ingredient becomes perilous in technology projects that require high discipline, and adherence to scope, budget, and timelines.</p><p><strong>Careful to Whom You Trust Your Fate: </strong>During the scoping of an ERP implementation, I stopped by to brief the CEO of a newly acquired company on the business design that was about to be configured in the new SAP system at his division. He was alarmed and worried about how this would cripple his business, and only calmed down when I pointed out that the people he had assigned to the project came up with that flawed design. It turned out that those people were about to be laid off until the company found a new use for them on a system implementation team. They were replaced the very next day.</p><p><strong>Reality Check:</strong> In an infamous story that has become a textbook case on IT project disasters, confectioner Hershey’s botched system implementation came down to three principal reasons: 1) Squeezed deadlines: a project that was scheduled for 4 years was forced into 30 months; 2) Wrong timing: the company went live at their busiest time and missed order fulfilment for Halloween and Christmas; and 3) Approach (Big bang): to complete the implementation process, Hershey’s opted for a big bang implementation simultaneously with a CRM and Supply Chain Management packages even <a href="https://www.slackchannels.com/hersherys-erp-implementation-failure-case-study/">without testing some of its modules</a> of the systems. Stretch goals can motivate, but biting more than one can chew can be counterproductive.</p><p><em>Stay tuned for </em><a href="https://blog.fortiumpartners.com/missing-the-mark-the-riddle-of-troubled-it-projects-a0d74ba7c30e"><em>Part II</em></a><em> on the Technical Factors that imperil IT projects.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=307c8114ad41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Too Insignificant to Hack?…The risk of low cyber defenses at smaller enterprises]]></title>
            <link>https://medium.com/@bassam.fawaz/too-insignificant-to-hack-the-risk-of-low-cyber-defenses-at-smaller-enterprises-109f51a23623?source=rss-33704155f258------2</link>
            <guid isPermaLink="false">https://medium.com/p/109f51a23623</guid>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Bassam Fawaz]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 23:47:56 GMT</pubDate>
            <atom:updated>2019-09-18T21:34:14.744Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Too Insignificant to Hack?…<em>The risk of low cyber defenses at smaller enterprises</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*fz_hWvZ0JjUI-6EoBx8X4w.jpeg" /></figure><p>Steve showed up right on time to our monthly lunch get-together. But as he took his seat across from me, I noticed he was not his usual self. “Is everything all right?” I asked. “Well, not quite” came the somewhat distressed reply.</p><p>Steve is the Chief Information Officer (CIO) of a privately held $250M company in the packaged goods distribution business. Like most CIOs of smaller companies that cannot afford their own full-time information cybersecurity staff, he employs a third party IT security consulting firm to come in once a year to execute a “pen test” (a penetration test simulating a cyber-attack on the company’s system to reveal vulnerabilities and risk areas) and was satisfied that this was a good enough measure to immunize his company against cyber breaches. This latest test, however, left Steve anxious. Technology changes rapidly, and with the pace of software deployment and updates, Cloud technology that often comes into the environment uninvited, Internet of Things (IoT) devices, and fickle user behavior, what was “secure enough” last week may be a wide-open door today. The test revealed to Steve that his company’s defenses were no longer adequate, and he needed to beef up the company’s cyber security posture with a plan fit for a “grown-up” company.</p><p>After spending long hours developing a cybersecurity plan that included upgrading skills and equipment, Steve was disheartened at his management’s reaction: “This is going overboard”; “You guys in IT are paranoid”; “Who will hack us? What are we, the Pentagon?!” He felt he was speaking a foreign language trying to engage his competent leadership team in the IT security conversation. The company’s CEO echoed his executives’ views: “there are more important areas to spend money on than a remote risk like that”.</p><p>Steve was despondent. “I know we are a cyber incident waiting to happen, and no one knows how bad it will be” he confided. Worse yet, he knew very well that he would be the first casualty of a cyber-attack on his company, as heads of IT typically are–deservingly or not. He was seriously contemplating switching jobs and leaving a company he loves and a business he enjoys, just to avert becoming a victim of what he felt was inevitable.</p><p>Less than a month after our lunch meeting, I got a call from a cheerful Steve. “You would not believe what just happened!”</p><p>“Something good, I hope.”</p><p>The CEO of the company walked into Steve’s office that morning and, with an unmistakable sense of urgency, said to him, “when do you think you can have a comprehensive cybersecurity plan for me to review with you?”</p><p>“What prompted that?’ I asked.</p><p>It turns out that the CEO was on a golf outing with a few business pals the day before where the CEO of another company was sharing the nasty ransomware attack experience his company had just gone through, the pain it inflicted in areas that had not been imagined, and how the cost of recovery was still adding up. That was enough to convince Steve’s boss that this stuff is a real menace.</p><p>The story has a happy ending for Steve and his organization, but unfortunately not for scores of enterprises, especially the small to medium-sized organizations who believe they are not significant enough to matter to bad cyber actors. While cyber-attacks on high-profile companies make the news, hundreds of other companies around the world experience the brunt of cyber breaches every day, too often because they under-appreciated the value of their own data to themselves (particularly in cases of Ransomware attacks). Most of them resolve the matter quietly–pay a ransom, hire expensive recovery consultants, etc.. –Largely to avoid the disrepute that can result from such incidents. The fact is, when a company is attacked, an inevitable question will arise: how and why did it happen? And if it emerges that the incident could have been prevented, it all but shows that the company in question was too lax to pay attention to a business risk that is in the news daily.</p><p>Despite the increasing attention to corporate information security in the media, the cybersecurity conversation at an alarmingly large number of companies is still grounded in Technology when it should be raised as a business continuity threat. Consider a small sample of the consequences of a successful cyber breach of your business:</p><p>1) Exposure of competitive information</p><p>2) Loss of productivity–often for days</p><p>3) Reputation damage / diminished customer trust</p><p>4) Remediation costs</p><p>5) Litigation and liability costs</p><p>6) Penalties (if your business is in a regulated industry)</p><p>Are these matters that should be left to the “techies” to tackle?</p><p>Business leaders need not become cyber security experts, but must be confident enough in the cybersecurity stance of their firms and fully aware of the risks they will accept. The key to making this happen is to have a qualified cybersecurity officer (full-time or part-time) on their team to help them develop a cybersecurity framework, engage the entire business in cyber-hygiene education, keep them informed of threats against their companies and industries, and continually assess how effective are their defenses. Business leaders will then know enough to ask the right questions and make informed decisions about their cybersecurity investments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=109f51a23623" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>