Infrastructure Reimagined
By the mid-2010s, IBM was in the middle of a profound shift. For decades, the company had been synonymous with physical infrastructure, mainframes that powered banks, data centers that hosted governments, and hardware innovations that shaped the way enterprises ran their operations. But the industry was changing. Cloud platforms like Amazon Web Services and Microsoft Azure were redefining delivery models, and enterprise clients were no longer satisfied with static outsourcing contracts or siloed IT. They wanted hybrid solutions that blended the stability of on-premises systems with the flexibility of the cloud.
IBM responded by repositioning infrastructure as a strategic asset, not just a cost center. Delivery hubs in Poland, India, and other locations became central to this transformation, allowing IBM to scale services globally while hybrid architectures gave clients the confidence that their most critical workloads could run securely across both private and public environments. This was a strategic shift, but in the long run it was about resilience and how long the model would last. In a world where downtime meant lost trust, infrastructure had to become both more agile and more reliable.
At the heart of this change was the recognition that infrastructure depended on a combination of people, processes, and the ability to continuously adapt, which keeps technology relevant. The delivery centers in places like Poland were more than low-cost alternatives. They began consolidating knowledge, skills, and leadership that could be distributed globally. Infrastructure was now both technical and human.
The Challenge of Unlearning
When I joined IBM in 2015, I carried with me a toolkit that I thought would be indispensable. Years in banking and channel sales finance had given me credentials as a Lean Six Sigma Black Belt. I knew how to define, measure, analyze, improve, and control. I could optimize workflows, reduce waste, and deliver efficiency. These were the skills that had built my career and reputation, and represented the pinnacle of human knowledge, a golden bullet that could enable any highly effective solution.
What became clear in that moment was that infrastructure evolves in cycles, much like the technologies it supports. Skills that once defined expertise can quickly become historical artifacts when industries shift direction. Organizations that succeed through these transitions do not discard past knowledge entirely, but they reposition it within a broader system of capabilities. The challenge for individuals and enterprises alike is to recognize when proven methods must give way to new perspectives so that experience becomes a foundation for renewal rather than a constraint.
But inside IBM, I quickly realized those tools didn't carry the same weight. The conversations around me weren't about DMAIC cycles or statistics. They were about human-centered design, mindfulness, Agile rituals, and co-creation. It was a different language, and at first I felt like a cassette tape in the era of mp3. The confidence I had built in my past roles evaporated in meetings where colleagues spoke in frameworks I recognized only from a distance.
Instead of efficiency metrics, colleagues working in Austin spoke about empathy maps. Instead of rigid project plans, mobile device experts in the Czech Republic relied on sprints and retrospectives. Instead of top-down directives, IBMers on five continents favored facilitation, co-creation, and iterative learning. To thrive, I needed to let go of my reliance on the tools I had mastered and embrace different methods while learning a new language. That was a time of learning new skills and un-learning old ones.
I soon discovered IBM's system of digital badges, micro-credentials that recognized skills in areas ranging from Agile practices to design thinking. This was IBM's way of creating an infrastructure of continuous learning. Instead of relying on static titles or diplomas, IBM encouraged employees to build visible portfolios of evolving skills. Rather than proving what we had done in the past, IBMers had to show what we could do next.
Learning environments like this change the way organizations think about capability. When skills are visible and continuously updated, knowledge stops being hidden within job titles or departments. It becomes part of a shared infrastructure that allows teams to assemble expertise quickly and respond to new challenges. In that context, professional development is no longer a periodic event but an ongoing process that strengthens both individual careers and the resilience of the enterprise.
At first, the idea of collecting badges felt trivial, like filling out a digital sticker book. But the more I engaged, the more I understood the value of gamification in learning, especially because there were different levels. Badges were symbolic, signaling adaptability. They told managers, colleagues, and even clients that you were up to date, curious, and willing to grow. They also created transparency, anyone could look at your digital profile and see your competencies. In that sense, digital badges were brilliant because they democratized expertise.
I threw myself into that idea, signing up for training in Agile, mindfulness, and design thinking. There were workshops on facilitation and co-creation, teaching me how to guide groups through wicked problems using post-its, empathy maps, and journey frameworks. The more badges I collected, the more confident I became in this new language. And soon, something shifted: the student became a coach.
When I felt confident, organizing workshops became my next step, helping colleagues navigate transformation projects using design methods and showing teams how they could think with creativity and empathy, unlocking progress in ways that efficiency tools never could. Slowly, I realized I was no longer trying to prove my old expertise. I was building a new kind of value and thinking again like the young designer that worked for MTV in the 1990s.
Infrastructure Beyond Machines
This personal journey mirrored what IBM was doing at scale. Just as I had to expand my definition of value beyond efficiency, IBM had to expand its definition of infrastructure beyond machines, and teach customers and teams what the new approach could do. Infrastructure now included the systems that allowed people to learn, adapt, and collaborate.
A workshop could be as critical to resilience as a backup data center. It could uncover insights and create bonds between teams and stakeholders. A culture of agility could make the difference between a successful transformation and a failed one because teams could work more effectively. And just as IBM was building delivery hubs in Poland to decentralize capabilities, I was building my own hub of new skills to decentralize any dependence on a single way of working.
Infrastructure was becoming distributed in technology, in geography, and in human capability. That was the foundation of a resilience approach that both the company and employees would have for a decade to come. Looking back, un-learning was not bad at all; it became the essence of transformation. That showed me that organizations and individuals alike must get rid of old assumptions to remain relevant. For IBM, that meant redefining infrastructure to compete in a hybrid cloud world. For me, it meant trading my identity as a Black Belt efficiency expert for the role of a learner, coach, and facilitator.
In both cases, the result was a more resilient way to operate. Infrastructure, whether corporate or personal, is strongest when it is flexible, adaptive, and human-centered. That principle would guide not only IBM's strategies in the years ahead but also my career path, reshaping how I approach challenges, opportunities, and transformation.
Resilience, in the end, was the thread running through both IBM's transformation and my own. For IBM, resilience meant building infrastructure that could resist disruption, adapt to hybrid cloud architectures, and empower clients to thrive in uncertain markets. For IBMers, it meant more than un-learning; it meant rebuilding and embracing new methods that made us more flexible than the tools we once relied on. Resilience was not about holding on to the past but about creating systems of technology, processes, and people that could evolve continuously. That shift turned internal structure from a monolithic foundation into a living framework capable of scaling, bending, and growing with every challenge.