Promoting a CIO is Easy. Designing a Technology Architecture That Lets Go, Is Not.
Oatey Co., based in Cleveland, has been manufacturing plumbing products for 110 years. It is not a tech company, it doesn’t trade publicly under the scrutiny of Wall Street, and it doesn’t need accolades for its internal decisions. When a company like this formalizes the promotion of its VP of IT to Senior Vice President and Chief Information Officer, the move deserves more than just a press release.
Liz Wells joined Oatey in 2021. Four years later, she took the formal lead of the technology function as VP of IT, and in April 2026, she was promoted to Senior Vice President, Chief Information Officer. The announcement describes her mandate with an unusual level of precision for such communications: capacity expansion, operational discipline, and a technology environment aligned with business priorities. Three distinct vectors, but one common denominator: technology serving a clear direction, not an accumulation of initiatives.
What I find intriguing is not the ascent itself but what it reveals about the strategic stance of an industrial manufacturer that chose to place the technology function at the center of its governance architecture.
The Problem of Industrial Manufacturers Faced with IT
The manufacturing industry has been caught in the same dilemma for a decade: everyone knows that technology is a priority, but few are willing to pay the price to organize it. The result is predictable. Legacy systems that no one touches for fear of breaking the production chain, digital transformation initiatives coexisting with 2003 spreadsheets, and fragmented IT budgets spread across dozens of competing projects without a clear chain of command.
The most destructive pattern is not the lack of investment. It is investment without renunciation. Medium and large manufacturers invest in ERP, automation, cybersecurity, data analytics, and factory connectivity, all at the same time, with the same declared urgency and with teams that do not have the capacity to execute six fronts simultaneously and in depth. The result is that everything progresses, but nothing consolidates. The company does not digitalize; it partially digitalizes across various fronts at once, which is effectively the same as not digitalizing at all.
In that context, the description of Wells' mandate during her year as VP of IT says more than it appears. "Expanding capabilities, reinforcing operational discipline, and advancing in a sophisticated technological environment" is not a list of achievements; it is the logical sequence of a transformation executed with prioritization logic: first build internal discipline, then advance in sophistication. Those who invert the order purchase expensive technology that operates on a broken operational foundation.
What a Promotion Reveals About Corporate Governance
Promotions to the C-Level are not just recognitions. They are signals of power assignment, and power determines what conversations happen in the boardroom and which do not. When a company elevates its CIO to Senior Vice President, it is sending a very specific message to the rest of the organization: technological decisions are no longer subordinate to business decisions; they are part of the same level of deliberation.
This matters concretely. A VP of IT negotiates their budget with the CFO. An SVP and CIO sits at the same table where the company's direction for the next five years is discussed. The difference is not ceremonial. It is the difference between technology being late to strategic conversations or shaping them from the outset.
Oatey is a manufacturer with over a century of operations. That longevity implies layers of processes, systems, and organizational habits that accumulate friction over time. That the company waited to consolidate internal leadership before raising the formal rank of the CIO suggests a coherent decision-making sequence: first demonstrate execution capability, then expand the mandate. This is not what companies that confuse speed with strategy do.
The Discipline of Not Wanting to Transform Everything at Once
The Oatey press release uses a phrase that deserves emphasis: "technological environment aligned with business priorities." At first glance, it sounds like standard corporate language. However, read closely, it’s a statement of renunciation.
Aligning technology with business priorities means, necessarily, that some possible technological capabilities were left out of the plan. It means that someone, in some budget meeting, advocated for an initiative, and the response was: not now, that’s not in our priority line. That "no" is the most difficult strategic asset to build in any organization, and it is the one most frequently destroyed when the pressure to show transformation overshadows the discipline of maintaining a focus.
Industrial manufacturers that fail in their technological transformations do not fail due to a lack of investment or talent. They fail because they attempt to modernize the supply chain, customer experience, production plant, and management systems simultaneously, with the same team, in the same budget cycle, under the same quarterly performance pressure. Dispersion is not an execution failure; it is a strategic design failure that occurs before the first project even starts.
Oatey has spent a century choosing what to do well and what to leave out. That its governance model seems to reflect the same logic is not a cultural coincidence. It is consistency.
The Coming Test
Wells’ elevation to CIO does not close a cycle. It opens one. Her new mandate includes the development and execution of Oatey's IT strategy, which for a manufacturer of this scale and trajectory implies decisions that will hurt: which legacy systems to retire, which suppliers to consolidate, what capabilities to build internally, and which to permanently outsource.
Each of these decisions has internal losers. Areas that lose autonomy over their own tools, suppliers that lose contracts, teams that must learn to operate differently. The formal authority of the title does not resolve that friction. Clarity about what strategic problem the company is trying to solve with its technological architecture resolves it, and the willingness to stick to that direction despite resistance.
That is what separates a CIO who manages IT from a CIO who designs competitive advantage. And this difference is not measured by the job title.
Executives who build lasting organizations do not do so by accumulating capabilities until something works. They do so by precisely choosing the few bets they will support with the entire organization behind, casting off the rest without nostalgia. The C-Level that does not feel the weight of what it left on the table probably never made a true strategic decision.
