Cesile Johnson is CTO at Core Bank, a community bank in Omaha and Kansas positioning itself as high-performing, tech forward and solutions based. She joined in June 2025 as SVP of technology and was promoted to CTO eight months later. The title changed in February. The work had been underway since day one.

Thirty years in IT across freight logistics, global services, enterprise banking, and a startup gave Johnson a consistent view of what determines whether a technology initiative holds. The tools are rarely the limiting factor. The internal foundation usually is.

"Technology is a meaningful enabler across much of this work, but its success will depend on stronger internal alignment, coordination, and execution."

Alignment Before the Stack

When Johnson arrived at Core Bank, roles were still evolving and the team was spread thin across too many responsibilities without clear lanes. Her first move was structural: understand each person, identify where they were underutilized or misaligned, rewrite the job descriptions, and rebuild the team around the bank's technology strategy.

She calls the philosophy aces in their places. From that foundation, she accelerated a pod structure she had developed across earlier roles in her career. Each pod pulls representatives from across the enterprise: technology, risk, operations, finance, legal, marketing, L&D, and the relevant business area. Each pod has an executive sponsor accountable for ensuring the work remains aligned with their strategic initiatives. Johnson holds sponsorship for AI, automation, middleware, and data.

The pod operates with a product delivery director managing the portfolio, a scrum master running two-week sprints, and a program lead breaking down the work into tasks. Business SMEs inside the pod understand the customer problem directly. The technology delivery team handles implementation. The two work in parallel rather than passing work in a handoff sequence.

She used a version of this structure at Werner, though without a formal name. At Core Bank, pilot pod work was already underway, but she enhanced it by leveraging agile methodologies and oriented it around product delivery relevant to advancing the bank's technology and business strategies.

Small, Brave Steps

Building that structure inside a community bank required credibility Johnson was still earning when the first pods launched.

"At the outset, there were questions about how effectively the pod model would operate here," she said.

The skepticism came primarily from the people doing the work. Johnson took that seriously. She spent time studying each executive individually, learning how they thought and what they needed from a new technology leader. She identified where the bank was investing in outside partners for outcomes that could be brought in-house, built the case with numbers, and delivered.

Each win accumulated. The people who had been skeptical started seeing results. The executives started relying on the model. "Showing those incremental wins really start to bring in 'this wow, this is working' comments," she said.

She describes the approach as small, brave steps. The bravery is in taking action inside organizations where the workforce has been in place for decades and the institutional history carries as much weight as the business case. Moving too fast without that credibility earns resistance that compounds.

The Constraint She Names

Johnson has nine people on her technology team supporting approximately 130 employees across the bank. She fills coverage gaps with managed service providers and staff augmentation. Her data center runs through a managed service with significant internal involvement.

When she arrived, she identified an opportunity to better define roles and create more momentum around the team's ideas. She addressed the structural opportunities first, because without that foundation the development work has nothing to land on.

"Technology had become the landing point for a wide range of initiatives."

The harder work is making sure efficiency gains are applied before more work is added to a team still developing its capabilities. That is the tension she manages actively. Building the muscle takes longer than investing in a tool.

Thirty years across industries taught Johnson that the sequence is consistent regardless of organization size or sector: understand the operations before applying the technology, put people in the right roles before building the structure, and build the structure before scaling it.

"Success depends on bringing people along throughout the journey," she said.