When Brent Gifford joined P1FCU six years ago, the credit union was pushing $2 billion in assets and had never fully matured into the organization that size required. The IT team was ten or eleven people. Information security — for a financial institution at that scale — was handled by one person working roughly twenty hours a week. There was no data strategy. There was no succession path in key technical roles.

Gifford was hired to fix all of it.

Over the next six years, he built a proper security program, doubled the IT team, mentored one of his VPs into the ISO role to eliminate a conflict-of-interest reporting structure, and developed the data function to the point where the organization hired a dedicated Chief Data Officer and took it entirely off his plate. He now leads a team of roughly sixty people spanning IT, information security, digital services, and the call center.

The perspective he brings to developing other IT leaders is not theoretical. It was built on the work.

The Wrong Problem

When Gifford sits in organizational meetings with newer technology leaders, the tell is consistent. A problem surfaces, and the first instinct is to propose a technical solution.

"Many times we put tech in and it just runs bad processes faster," he said. "The answer is to start with the process and make sure the process is clean and what you want it to be. Then tech can be the enabler to make it work as you want it to work."

Gifford learned this from one of his first CEOs and mentors, who always made a statement and asked a question when Gifford's first instinct was new technology. The statement was "Lipstick on a pig is still a pig," and it was immediately followed up with the question "Are you intending to deliver a pig?" Given the starkness of the example, it permanently changed the way Gifford thinks about an issue and a proposed resolution.

The reflex is trained, not malicious. Technology leaders have spent careers building comfort with technical solutions, and that comfort becomes the default even when the situation calls for something else. Reaching for process discipline instead of a new tool is a skill that has to be deliberately developed. It does not come with the CIO title.

The System He Built to Fix It

Gifford's answer is not a coaching conversation. It is a structural requirement. Every leader and key individual contributor on his team spends one full week per year shadowing frontline, member-facing employees.

The point is not exposure. It is recalibration — and it happens annually because the blindness comes back.

"We're so close to the technology and process that many times that friction is either ignored by us because we're so used to it, or we just expect, being in IT, that there will be some friction," he said.

Members do not grade on a curve. The experience P1FCU delivers is measured against Amazon and Netflix, not against last year. His engineers see that live, in an actual member interaction — not in a dashboard metric. They watch what friction costs in real time. They stop explaining it away.

The week does not just change what people see. It changes how they frame the work when they return.

The Moment CIOs Lose Their Seat

For tech leaders who reach the executive table, a different test begins. They are expected to represent IT while simultaneously serving the enterprise. Those roles are in tension, and the failure mode is predictable.

"When the conversation turns to why isn't technology doing this, you can't become defensive," Gifford said. "You have to put yourself into the other mode where we're talking about the enterprise. It is their perception, whether it's real or exaggerated or not. It has to be dealt with."

CIOs get attacked at the executive table. Perception beats reality in those rooms. The moment you respond as a defender of your function — instead of as a partner in solving the enterprise problem — you lose standing. It does not matter if your position is technically correct. What matters is whether the people across the table trust you to put the organization first.

The leaders who navigate this successfully, in Gifford's experience, are not suppressing the instinct to defend their team. They have replaced it with a different one.

The Hardest Calibration

Gifford has spent thirty-one years in a field where something genuinely new arrives every six to nine months. Staying current is not optional. But the hardest leadership lesson he has had to carry is knowing when not to chase it.

"Those new and shiny things may not be what the organization needs," he said. "Sometimes they just need the old system that's in place to be polished and to be nurtured."

Separating personal interest from organizational priority sounds simple. In his experience, it takes years — sometimes longer. The transition from high-performing technologist to executive is not complete until that gap is closed.

Peace Over Paycheck

Gifford has maintained the same two or three mentors for roughly twenty years. The relationships have lasted because he proved, consistently, that the input mattered.

"A mentor who doesn't feel that their mentorship is of value or being taken seriously is not going to give that kind of effort twenty years down the road."

He is thirty-one years in, still mentoring thirty others, still learning. One principle he returns to now — and passes on — is simpler than any framework he has built.

"Peace over paycheck."

The conditions in which you do the work shape what you are able to build, what you are able to give, and how long you can sustain it. No title or tenure changes that calculus. It is, in his view, the kind of lesson that takes a full career to earn the right to say plainly.