Alan Fink’s first major healthcare technology project put him in front of physicians who told him, directly, that they had gone to medical school to practice medicine, not to type.
He was a systems consultant from Denver with no clinical background. The technology was early voice recognition software. The physicians were accustomed to dictating their notes into a phone and having a transcriptionist return the finished document later.
The new system asked them to change that workflow entirely.
Nearly 25 years later, Fink still sees that project as one of the clearest lessons of his career. The technology was rarely the hardest part. People were.
The CIO Who Saw Something First
Fink grew up professionally outside healthcare. He implemented PeopleSoft and Lawson financial systems and, in 1999, found himself on Oahu finishing a Y2K project involving HR, payroll, financials and procurement.
Not long afterward, his consulting firm sent him to Sunnyvale to address a Lawson payroll problem at Palo Alto Medical Foundation, part of the Sutter Health network. What was supposed to be a short engagement kept bringing him back.
Each time Fink flew in from Denver, he and the CIO would have lunch. Eventually, she made him an offer. There was an emerging project involving Dictaphone voice recognition technology, and she wanted him to lead it. The opportunity required him to leave his consulting firm and work directly with the organization as a contractor. He said yes.
She saw things in me I am not sure I saw in myself. She gave me room, and she never questioned me. That is where my career took off.
Alan Fink
It was a lesson in leadership before Fink had begun thinking seriously about leadership itself: sometimes the person who changes a career is simply the person willing to trust someone before the resume fully proves the bet.
The Rollout the Doctors Fought
The first version of the voice recognition software was far from elegant. Accuracy hovered around 80 percent. The microphones relied on serial ports. The initial pilot struggled enough that Dictaphone brought Fink in to help identify the problems.
Those sessions eventually led to testing a USB microphone. Fink piloted the improved setup in several clinics, and the results changed the trajectory of the project. Executive leadership decided to expand it.
Then came the harder part.
The organization employed roughly 40 transcriptionists. Under the existing process, physicians dictated their notes by phone and waited as long as two days for a transcription to be returned for review and signature. Voice recognition compressed much of that cycle to less than an hour.
But efficiency came with a tradeoff. Physicians were now responsible for correcting and signing their own notes. Several were not enthusiastic.
With strong executive sponsorship, adoption became an organizational expectation. The technology ultimately rolled out across the medical group.
Fink says the implementation generated more than $3 million in recurring annual savings. More importantly, it taught him something he would carry through the rest of his career.
Software can be installed. Workflow has to be changed. And changing workflow means changing human behavior.
From Contractor to Builder
After roughly a year and a half, the CIO who had recruited him as a contractor told him she wanted him permanently. Fink joined Palo Alto Medical Foundation as an employee in 2003.
Over the next seven years, he created the organization’s first enterprise PMO, developed its methodology, and built and trained an eight-member project management team.
The work was less glamorous than the technology initiatives around it, but arguably more consequential. A strong project management office creates the structure through which decisions get made. It establishes how priorities compete for resources, how projects move forward, how accountability is assigned and how leadership sees what is actually happening across an organization.
Fink was building that structure from the ground up.
He also directed the Epic implementation for Camino Medical Group, part of Palo Alto Medical Foundation, and helped lead major initiatives involving PACS and data center modernization.
He still remembers warehouses filled with boxes of X-ray film. Within a few years, digital imaging made much of that physical infrastructure unnecessary. Technology kept changing. The leadership lessons did not.
Two Kinds of Leaders
Ask Fink how his philosophy of leadership developed and he talks about two bosses. One was the CIO who took a chance on him. The other taught him almost exactly the opposite lesson.
Years earlier, while working for a national restaurant organization, Fink was leading a Lawson financial systems upgrade. Testing went smoothly. Production did not. The production environment was running on an older server and operating system, something Fink says he had not been told. The system went down for roughly six hours.
His boss responded by tearing into him.
“I already knew I made a mistake. You do not need somebody going down your throat and making you feel worse. What you need is a game plan to resolve it and a way to move forward.”
That experience stayed with him.
I have heard variations of that story throughout my own career in executive search. Many leaders can identify a moment when they learned as much from poor leadership as they did from great leadership. Sometimes the lesson is simple: I will never make someone else feel the way that person made me feel.
Fink built much of his management style around that distinction.
What Good Leaders Do Instead
His description of effective leadership is uncomplicated. Good leaders listen. They allow people enough room to do the work. They understand that mistakes are part of development. They intervene when someone needs help, but they do not confuse involvement with control.
Fink structures his weekly one-on-ones around four questions: Are you doing okay? What are your plans for the week? What are your challenges? What do you need from me? Then he gives people room.
When someone begins struggling, he changes the distance.
“Not micromanaging. Bringing them closer so they are successful.”
That distinction matters. Autonomy is not abandonment. Good leaders know when to step back, but they also know when someone needs them to step forward.
Leading Through Waves of Change
A career spanning a quarter century in healthcare technology is, in many ways, a history of technologies becoming indispensable and then becoming ordinary.
Fink has worked through voice recognition, PACS, electronic health records, portfolio management platforms, cloud migrations, Microsoft 365, cybersecurity, telehealth, pandemic response and, now, artificial intelligence.
At Santa Clara Valley Health & Hospital System, he rebuilt the PMO, implemented Planview for portfolio management and led approximately 60 professionals across the PMO, Service Desk and Field Services while overseeing the migration of more than 9,000 devices.
At UCSF Benioff Children’s Hospital Oakland, he took on technology leadership responsibilities supporting a campus of more than 2,000 employees. Working within a highly matrixed environment, he helped advance Microsoft 365 migrations and EHR consolidation through partnership and influence rather than direct authority. His role required coordinating clinical systems, infrastructure, applications and operational stakeholders whose reporting lines did not necessarily lead back to him.
That kind of environment taught another lesson. Authority and leadership are not synonymous. Sometimes the only way to move something forward is to earn alignment.
When the Pandemic Changed the Assignment
Then came 2020. Like technology leaders across healthcare, Fink and his colleagues were suddenly confronting needs that had not existed weeks earlier.
One of the most immediate was telehealth.
Providers needed to see patients remotely, but many lacked the equipment to make that transition quickly. Fink remembers personally visiting technology vendors throughout Silicon Valley looking for headsets, microphones and cameras that could be put into clinicians’ hands.
It was not a grand digital transformation program. It was a scramble to solve the problem directly in front of them. And it mattered.
Later, at UCSF Health, Fink supported the enterprise COVID vaccination program, working across Information Technology, Nursing, Pharmacy, Marketing, Operations and outside partners as the health system established vaccination sites and supporting infrastructure.
The experience reinforced something technology leaders sometimes forget. During a crisis, the value of technology is not the technology. It is what it allows people to keep doing.
Cybersecurity Becomes a Leadership Issue
After serving as the senior technology leader for a 250-bed HCA hospital in San Jose, Fink became Vice President of Information Technology and HIPAA Security Officer at Planned Parenthood Northern California.
The role put cybersecurity directly within his executive responsibilities. He brought data analytics capabilities in-house, helped establish policy around responsible use of artificial intelligence and identified more than $300,000 in recurring annual savings through technology optimization and vendor and application changes.
His record there also includes a reduction in phishing susceptibility from approximately 20 percent to under 3 percent through executive-sponsored cybersecurity education and leadership engagement.
That last number interests him because the improvement was not created by another security appliance. It came through behavior. Executives participated alongside employees. Leadership signaled that security belonged to everyone.
Once again, the technology problem turned out to be a people problem.
The Risk Hiding in Yesterday’s Technology
Fink’s attention lately has turned toward another issue that sits at the intersection of governance, technology and organizational memory: legacy data.
In September, he wrote about the Aesto Health breach and the risks created when healthcare organizations retire an EHR but retain years of sensitive information elsewhere.
The Aesto incident was reported to federal regulators as affecting approximately 9.5 million individuals. That incident potentially exposed sensitive information belonging to approximately 9.5 million individuals whose information was held by a healthcare data-archiving vendor.
For Fink, the important question is not simply whether the current EHR is secure. It is what happened to everything that came before it.
Healthcare organizations may spend enormous resources securing current systems while historical data remains with outside vendors, archived platforms or repositories that attract less executive attention. The information did not stop being sensitive because the software stopped being current.
Fink wants healthcare leaders asking a deceptively simple question: Which third party holds the largest amount of patient information outside the primary EHR? And then another: Do we still need all of it?
It is the same instinct that runs through much of his career. Find the thing nobody is sufficiently accountable for. Then create ownership around it.
The Constant Beneath the Technology
The systems across Alan Fink’s career have changed repeatedly: Y2K, voice recognition, Epic, PACS, portfolio management, Microsoft 365, telehealth, cybersecurity and AI governance.
Some technologies disappeared. Others became infrastructure so ordinary that nobody thinks about them anymore.
The underlying work remained remarkably consistent. Bring structure to complexity. Get leaders aligned around priorities. Help people move through change. Give teams enough freedom to perform and enough support to recover when they struggle.
Fink’s career suggests that the executives who remain effective through successive waves of technology are not necessarily the ones most attached to a particular system. They are the ones who continue learning after the system changes.
What Comes Next
Fink is now considering the next chapter of his career at a moment when healthcare technology leadership is becoming more complicated, not less.
Cybersecurity is moving deeper into enterprise governance. Artificial intelligence is forcing organizations to write policies before they fully understand the capabilities they are governing. Legacy technology continues to create risk long after implementation teams have moved on.
His experience spans physician groups, academic medicine, county healthcare, acute care hospitals and nonprofit healthcare organizations. He has built governance structures, led clinical technology initiatives, carried HIPAA security responsibility and managed organizations through successive cycles of transformation.
But the story that explains him best may still be the earliest one.
A CIO kept having lunch with a consultant from Denver. She saw something in him. She gave him room. She trusted him with work he had never done before.
Twenty-five years later, Fink still remembers what that felt like.
Perhaps that is why so much of his own leadership philosophy comes back to the same idea: give good people room to become more than they have already proven themselves to be.
Sources & Verification
Interview material: Direct quotations are drawn from Cathy Trinh’s July 27, 2026 conversation with Alan Fink and lightly edited for length and readability. This includes his account of the Palo Alto Medical Foundation CIO who recruited him, the restaurant-chain manager whose response to a failed upgrade taught him the opposite lesson, and the four questions that structure his weekly one-on-ones.
Career facts: Career history, scope and figures are grounded in Alan Fink’s executive resume, including the voice recognition deployment and more than $3 million in recurring annual savings at Palo Alto Medical Foundation, the enterprise PMO and eight-member project management team, the Santa Clara Valley Health & Hospital System PMO rebuild and migration of more than 9,000 devices, technology leadership at UCSF Benioff Children’s Hospital Oakland, the UCSF Health enterprise COVID vaccination program, senior technology leadership for a 250-bed HCA hospital in San Jose, and the Planned Parenthood Northern California results including more than $300,000 in recurring annual savings and the reduction in phishing susceptibility from approximately 20 percent to under 3 percent.
Written clarifications: Alan Fink provided written clarifications in October 2026 that establish the 25-year healthcare technology timeline beginning in 2001, the Epic implementation scope for Camino Medical Group within Palo Alto Medical Foundation, the enterprise PMO language, the matrixed leadership description at UCSF Benioff Children’s Hospital Oakland, and the pandemic telehealth sourcing account.
Third-party verification: Palo Alto Medical Foundation is part of the Sutter Health network. The Aesto Health breach was reported as affecting 9,540,683 individuals by HIPAA Journal on September 1, 2026, and reported by SecurityWeek the same day, which identified legacy data archiving as part of Aesto’s healthcare technology services.
Executive Voices verifies the factual foundation of every feature before publication. Our editorial standards explain how.
