Phlow Corp. launched a few years ago to solve a specific national problem: the U.S. depends on foreign sources for a significant portion of its essential medicines. Most organizations talk about digital transformation. Very few ever have the opportunity to start without constraints. Phlow did. The company landed a $354 million government contract and started building a pharmaceutical manufacturing facility from scratch. No legacy processes. No inherited systems. No technical debt to rationalize. Just a mandate to build a pharmaceutical manufacturing capability from the ground up, and do it right the first time.
When Juan Piacquadio stepped in as CIO, the mandate was not to modernize IT—it was to deliberately design how the business would operate in a digital and AI-driven manufacturing environment. He would build the entire digital ecosystem: ERP. MES. Lab Information Management System. Electronic Lab Notebooks. QMS. DCS. ICS. All of it. His career had spanned construction, medical devices, enterprise technology, energy, and payments security. He had never started from zero.
That changes how you think about IT.
When You Build from Nothing, There Are No Excuses
Greenfield work removes the friction of migration, legacy debt, and inherited decisions. It also removes every excuse. "Rather than optimizing incrementally, we focused on enabling manufacturing excellence, adding security and quality by design, and developing technology as strategic differentiation," Juan said.
Phlow was a new entrant in a contested pharmaceutical market with a government mandate and no brand history. Every technology decision either built competitive advantage or did not.
Operators Do Not Care About IT. IT Has to Close That Gap.
Juan has published research on IT/OT convergence and worked across petroleum, medical devices, and pharmaceuticals. Across all of it, his read is consistent: operators care about uptime, cycle times, and deviation management.
"One of the most persistent misconceptions in enterprise IT is that governance frameworks, architectures, and cybersecurity maturity inherently create value. They do not. Operational teams measure success differently. They care about uptime, cycle time, and deviations. If IT cannot directly influence those metrics, it remains a cost center, regardless of how advanced it appears."
The answer is for IT to meet them where they operate. At Phlow, Juan structured IT not as a governance authority but as a partner inside cross-functional teams spanning manufacturing, automation, and quality. Accountability stays with domain owners. The team functions as a unit.
"If IT and operations operate separate, accountability is fragmented—high-performing organizations operate as one team. It's not, I am IT, or I am operations. It's, we are the team assembled to deliver on these capabilities."
Getting there requires relationships built outside normal work settings, where hierarchy softens enough for people to actually talk. Cultural change needs language to make it sustainable.
Every Technology Decision Is an Organizational Decision
The hardest decisions Juan faces are not budget calls or vendor selections. They are decisions that change how people work.
"The industry is entering a phase where technology is no longer augmenting work, but redefining it. Artificial intelligence and automation are reshaping roles faster than organizations can adapt. In that context, the challenge is not selecting the right technology. It is managing the organizational consequences of adopting it. Roles evolve. Skillsets shift. Some functions disappear. Others emerge."
"It's not about workforce reduction," he said. "It's about decisions that will fundamentally transform how people contribute, requiring us to support them through reskilling, upskilling, role redesign, and new career pathways as innovative technology is implemented."
With agentic AI reshaping knowledge work across industries, he sees that pressure only increasing. These decisions often have to be conceptualized before they can be socialized. You carry the weight alone first. His response is to create the conditions for honest input before a direction is set. "Brutal honesty is currency," he said. People with subject matter expertise need to feel genuinely safe to dissent, even in front of the CIO. Accountability for the final call stays with Juan. Ownership in the process is shared.
When he evaluates which direct reports will grow into executive leaders, the criteria are not technical. Adaptability under pressure. Genuine accountability for outcomes. The capacity to understand how technology decisions land inside an organization.
"All changes, all technology changes are organizational changes," Juan Piacquadio said. "What matters is, do I know how the change will affect organizational culture and how to properly introduce it in a sustainable manner to get a high rate of adoption."