<?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 Lauren Cooney on Medium]]></title>
        <description><![CDATA[Stories by Lauren Cooney on Medium]]></description>
        <link>https://medium.com/@lcooney?source=rss-ee22193f4af5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-gWto3ixvqJNgmBO_xwfjg.jpeg</url>
            <title>Stories by Lauren Cooney on Medium</title>
            <link>https://medium.com/@lcooney?source=rss-ee22193f4af5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:24:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lcooney/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[Will Red Hat send Ginni to IBM’s CEO Hall of Fame?]]></title>
            <link>https://medium.com/@lcooney/will-red-hat-send-ginni-to-ibms-ceo-hall-of-fame-c39023962b6?source=rss-ee22193f4af5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c39023962b6</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[rhel]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[acquisition]]></category>
            <dc:creator><![CDATA[Lauren Cooney]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 16:56:51 GMT</pubDate>
            <atom:updated>2018-11-08T17:23:26.925Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_o81YbJg_qxXhHaZFWiWhQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/oqStl2L5oxI?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Clark Tibbs</a> on <a href="https://unsplash.com/search/photos/change?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Ginni Rommety must trust her instincts and leadership team tremendously well. How else does one rationalize trying to pull off one of the biggest acquisitions in software history and throw a brave, public Hail Mary pass to save the company she’s been trying to resurrect?</p><p>It’s a massive wager that puts her in the annals of IBM history alongside one of her predecessors: Lou Gerstner. And let’s be clear: IBM needs change and it needs it fast. Change that doesn’t come by making small wagers, but by placing all your silicon chips on the table.</p><blockquote><strong><em>What I *love* and focus on in this article is a great turnaround story — one that starts as the underdog, plays the odds — and comes back out on top.</em></strong></blockquote><p>Ginni is one of the few who can do this. She led the <a href="https://en.wikipedia.org/wiki/Ginni_Rometty">PriceWaterhouseCoopers’ acquisition</a> and integration. She was handed an outdated and bloated company that needed to reduce costs and improve revenue and brand fast. She cut multiple technologies that had weighed the company down, made substantial employee cuts (she should have thought through that one a bit better, but it needed to be done) and invested in critical areas by making roughly $8 billion in acquisitions over her reign.</p><blockquote>But when you are IBM, you’re in every industry, inside nearly every company and you’re a household name. When you’re IBM, small moves don’t add up to big changes.</blockquote><p>Ginni needed a big shift. Red Hat is that shift. It is a very smart shift, if Ginni can get her teams aligned and executing in a critical areas, all of which tie together in multiple ways but, more importantly, must execute hand-in-hand:</p><p>· <strong>Field/Sales:</strong> IBM’s strongest internal machine is their sales engine; how do they keep that moving and improving to drive new revenue with new solutions that a very large sales team might not understand?</p><p>· <strong>Developers:</strong> Developers drive workloads and workloads drive money… how do they incent developers to stay with the companies and attract new developers in new and different ways?</p><p>· <strong>Culture:</strong> How does this work, and how can IBM ensure that Red Hat’s very valuable employees remain with them during this acquisition?</p><p>· <strong>Technology:</strong> Are open source solutions the leading element of IBM’s new technology strategy?</p><p>Below I have outlined these four areas with suggestions and questions that need to be considered as IBM and Red Hat move through the first phases of the acquisition. It is not exhaustive, but it is a strong template for success in this scenario.</p><p>____________</p><h3><strong>Field/Sales</strong></h3><p><em>I see this as one of, if not, the most important strategic areas IBM needs to focus and seamlessly execute on</em>. IBM has a phenomenal field and sales organization, one of the best I’ve seen and worked with in the technology industry. IBM’s ability to make this acquisition work or break it will happen here. This is one of a very small number of cases where overlap with the two companies needs to occur as quickly as it can.</p><p><strong>Suggestions:</strong></p><p>(1) <strong>A “tiger” team should be jointly established, exclusively on the IBM side the areas of sales that need to understand the Red Hat GTM processes and models. </strong>IBM should select people to engage that are from each area critical to an IBM sale (field and campaign teams, pre-sales, solution sales, enterprise sales). You don’t want to break the IBM model (because it is absolutely that good), but you do want the team to understand how Red Hat sells their solutions, best practices, etc. Also required will be Red Hat learning IBM’s model, which can get complex fast (integration for one product or set of products can be highly matrixed in how they go to market although quite successful).</p><p><strong>(2)</strong> <strong>Let the majority of Red Hat continue to use their sales model, without integration into the IBM machine with the exception of shared customers if required. </strong>The tiger team mentioned above should be a small team of people highly experienced in what they do, influential in their respective teams and markets, focused on building the playbooks for the future. Knowledge of best practices, methods and integrating into the IBM sales machine critical as well as enabling utilization of tools and models that reach worldwide. Consider building similar tiger teams for each global region (Americas, EMEA, APAC, etc.) to start. After some lessons are learned and they see some successes (and failures but key here is to fail and fail fast), this can be rolled out to sales.</p><p><strong>(3)</strong> <strong>Alignment of account leadership. </strong>Account leadership is very protective of their customer, and rightly so. IBM likely has a lead and a full team under that lead focusing on one key enterprise account — let’s say a large telecommunications company. There is going to be overlap in certain areas with Red Hat. Red Hat likely structures their sales teams differently, as they are a smaller company. Overlapping accounts and supporting teams need to engage each other quickly to ensure that they are not selling competitive products/solutions into their customers. Opportunities for additional sales, revenue and services will be recognized if communication and messages are consistent across each account.</p><p>(4) <strong>Using the tiger teams outlined above and a few Red Hat experts, work with IBM sales to educate them on open source development and delivery models to market — and vice-versa with IBM.</strong> IBM is much more stringent on their release to market guidelines, but they also need to let up a bit in order to see and learn about the successful Red Hat release models and open source engineering engagement, and of course pre/sales models. Documentation and information should be shared quickly so mindset shifts and practice areas can be understood and tested as applicable in the markets.</p><h3><strong>Developers:</strong></h3><p>The face of IBM hasn’t changed much in 20+ years, and it is no longer attracting the audience that <a href="http://shop.oreilly.com/product/0636920028185.do">IBM absolutely must influence — developers</a>. Red Hat offers the opportunity to shift this image. IBM has always been active in creating developer communities that support their products and engaging in open source foundations. The big winner, <a href="https://developer.ibm.com/blogs/2018/10/28/ibm-and-red-hat-are-coming-together-and-developers-are-the-winners/">per IBM’s messaging,</a> are the developers. Over the last 10 years, technologies have become more interoperable and competing product “bake-offs” have been eliminated. There’s more overlap in developer communities, from what they use to where they congregate. Google, AWS, Salesforce, Microsoft, Digital Ocean and others have accelerated their programs in new ways, hired strong and noteworthy advocates to keep up with the times and invested heavily in them. The face, nature, roles and type of developers has changed dramatically, and recognition/alignment to that will be key — as will participating in open source in ways beyond IBM’s traditional foundation models. Red Hat will help with this if IBM is willing to learn.</p><p><strong>Suggestions:</strong></p><p>(1) <strong>Do not combine the communities.</strong> Keeping them separate is critical here. Red Hat’s community is distinctive from IBM’s in that the sites are different, navigation is different, and content is different. Merging this now would confuse audiences and frustrate developers — they wouldn’t be able to find the documentation or information they need. Provide links on each site to respective IBM and Red Hat sites but keep it simple. The question of if the communities will combine is one of timing and one of readiness — not of the companies — but of the community. Let the communities of developers dictate this one.</p><p><strong>(2)</strong> <strong>Rockstar Requirement. </strong>On the event “circuit” for developers, you have very well-known speakers from Microsoft, Amazon, Google and multiple community leaders that are well respected in their open source groups. Red Hat has quite a few of these a well. It is important that IBM find and help raise awareness of some of their core contributors to the community and to open source. There are a few that do this, but not enough. These are not executives, but actual developers from communities and projects.</p><p><strong>(3)</strong> <strong>Let the developers drive the message, not the executives. </strong>If open source is at the crux of this acquisition, then people that are well-respected in open source at IBM need to be allowed the freedom to be the thought-leaders, the risk-takers and the spokespeople of this movement. These people need to be engaged when there is an announcement, when there are executive leadership decisions on technology and more. To drive a comprehensive and cohesive message, you need it delivered from leadership top-down and trusted developers from the bottom-up. After all, <a href="https://developer.ibm.com/blogs/2018/10/28/ibm-and-red-hat-are-coming-together-and-developers-are-the-winners/">IBM has 78,000 developers trained in open source</a>. These developers need to be seen, be active, have a presence (if they so choose), and be allowed to be themselves. If this happens, developer personalities begin to emerge and shine; that will attract new developers, new communities and more.</p><h3><strong>Culture:</strong></h3><p>I often talk with big influencers in this area. <a href="https://twitter.com/johnmark">John Mark</a> does a great job tackling this in his overview of the acquisition <a href="https://medium.com/@johnmark/so-youve-been-acquired-97cb2fdf81f7">here</a>. When you’re driving due diligence on a company or assessing for acquisition, culture fit is always one of, if not, the most important thing to look at if you are planning to keep employees onboard and they are a critical asset to success, which in this case they definitely are.</p><p><strong>Suggestions:</strong></p><p><strong>(1)</strong> <strong>Keep the companies separate (after/if/when) the acquisition close occurs. </strong>This will allow Red Hat to continue the work they are doing and the inclusive of communities and open source efforts that they drive, with minimal impact. Red Hat is doing well — let them keep their focus to deliver on this.</p><p><strong>(2)</strong> <strong>Find out what Red Hat employees care about:</strong> Employees care about a few things: (1) job — do they still have one, can they still work remotely? (2) what will their pay (out) be and when, (3) what has their leadership committed to and is it something they can still be inspired from and believe in, and (4) what does this mean for their leaders, teams, management? Will they stay with the company? For how long? Can they still trust their leadership team (trust will be critical here as will mission statement and company values)?</p><p><strong>(3)</strong> <strong>Certain Red Hat leaders, managers and employees are critical and should have incentive not to leave.</strong> These employees are the ones leadership needs to focus on. Make bets here and spend the extra time as needed to ensure these people are in the “inner-circle” and know of the on-goings of the acquisition. At this stage leadership needs to already have that list and be in discussions with managers and individuals to ensure their commitment. Compensation should be on this list.</p><p><strong>(4)</strong> <strong>Leadership committing to strong and consistent internal communications with as much information as they can share (transparency is a very successful strategy) is required</strong><em>.</em> Currently there is very little out in the open regarding the strategy that the companies are going to take, other than Red Hat will be a separate division reporting directly to Ginni. This needs to be rectified, and soon. At the CxO level, leaders need to be delivering these messages into their teams and ensuring that there is no diversion (ie, political plays) in action and everyone is speaking the same language. This sets the tone for alignment at an early stage and will also hopefully help employee morale and output.</p><p><strong>(5)</strong> <strong>Customers, Customers, Customers</strong><em>.</em> Red Hat and IBM leadership teams and sales teams are likely focusing now on their customers, especially the big ones here, as this shift happens. Developer and community teams need to be doing the same in each community. Feet on the street and a consistent, clear message required for each targeted audience.</p><h3><strong>Technology Strategy</strong></h3><p>As I write this the core focus is on open source: Linux, Kubernetes and containers to drive hybrid cloud. This is what we know; nothing else has been articulated. We know the general stats of IBM developers that are trained on open source (<a href="https://developer.ibm.com/blogs/2018/10/28/ibm-and-red-hat-are-coming-together-and-developers-are-the-winners/">78,000</a>) but not how they are trained, what they are trained on, what they work on, and more. Evidently partnerships with Microsoft, AWS and others will continue (if they can be kept intact). Based on what information is public now, it looks like these will continue.</p><p><strong>Suggestions:</strong></p><p>(1) <strong>Keep the IBM and Red Hat strategies separate. Align them slowly, and learn from customers, partners and lessons learned from the past. </strong>Work with a small group of people from both companies to start to build the strategy up, and then engage a larger group to look at how to roll that out. Ask customers and partners for feedback. Do that in a group setting and then in 1:1s as answers will be different. Targeted customers and partners need to be segmented (by region, industry, audience level, revenue, ++) and strategically and selectively rolled out. Learn with a small group, take learnings and integrate what is needed, re-rollout to larger group and iterate. Train, train, train the sales teams and partner teams, consulting teams++.</p><p>(2) <strong>Once companies start to build the overall technical strategy out, establish Architecture Leadership and Engineering Leadership clearly and carefully as one technology strategy will be required with multiple divisions needed to execute upon it.</strong> One sets the strategy. One executes on it — and these two need to be aligned every step of the way. Be very clear on ownership of these. Make sure individuals representing each area are well-respected at both companies and with customers, in the industry, and know how to organize teams around them and execute. Presentation, social and partnership skills will be critical for these leaders. If either shows an agenda that is misleading or for the benefit of the individual versus the company and customers, remove them immediately. This establishment and partnership must be aligned and these leaders need to truly trust each other.</p><p>(3) <strong>Keep current development models as is, for now.</strong> <strong>Use this as a litmus test for employees.</strong> Over time development models will shift, but let shift occur with time and understanding of goals versus by force. If a team needs to be trained on something by X date per a KPI that has been established, that’s fine. Make it achievable and rewarded, also new and exciting. Training is typically better (IMHO) if it’s in-person and done in teams that need to have output of something at the end. Also use this phase to see who wants to adopt new skills and who doesn’t. Focus on re-skilling people that want to be engaged and are excited by the technology; look to potentially phase out those that don’t.</p><p>(4) <strong>Bring sales leadership from both teams into the inner circles of building these models — both architecture and engineering strategy. </strong>These folks are the ones that will execute for you — and you need them more than they need you. In order to gain trust they need to understand the strategy, what is being built and why it matters to them and their customers. Include them in feedback sessions (especially if these are with their customers) and always remember — these are their customers — not yours. Be lockstep with sales teams about timeframes for rollouts and more. It should never be about releasing when the technology is ready — the sales team and field needs to be ready as well.</p><p>In conclusion I do truly hope that Ginni, IBM and Red Hat can pull this off. It will be a very difficult turnaround and these types of overhauls happen in years, not months. The jury is still out. <em>Like I said above — I love a good underdog story — and I think it’s about time we had one.</em></p><p><strong><em>Feedback and discussions on above welcome and encouraged.</em></strong></p><p><em>__________</em></p><p><em>*Disclosure: I worked for IBM in the past: open source strategy, acquisition integration (Gluecode) and traditional product development and delivery (Information Management CTO Office). I also worked with IBM and Red Hat to take open source projects to market in prior leadership roles.*</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c39023962b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>