Meridian Financial Fixes the Seam Before Hiring a Business-Unit CTO

Situation. Meridian Financial has a commercial banking unit with its own product, engineering, and data teams. Enterprise technology provides cloud, identity, security tools, and core data services. The unit CTO leaves after repeated conflict with the enterprise CIO and CISO. The unit president says central teams are too slow. Enterprise leaders say the unit creates exceptions and surprises.

The first draft mandate asks the replacement to accelerate digital products, comply with enterprise standards, own engineering, drive data and AI, reduce cost, and strengthen security. It says nothing about dependency service levels or exception authority.

Diagnosis. The previous CTO’s behavior contributed to conflict, but the federal model also failed. The unit owns revenue commitments but cannot predict when shared identity and data work will arrive. Enterprise standards have no time-bounded exception process. The unit can fund local alternatives but does not pay the long-term enterprise integration cost.

Hiring another relationship builder without changing the decision system would make diplomacy the substitute for authority.

Federal Map. The unit and enterprise define 18 material decisions. Identity standards remain enterprise-owned. Product experience and local delivery remain unit-owned. Shared platform adoption is a joint investment decision with service obligations and an exception path. Material security risk is assessed by the CISO and accepted by the unit president or enterprise risk committee based on threshold.

The unit CTO reports to the unit president with a formal professional relationship to the group CTO. Performance input is defined. The enterprise CIO does not approve the hire, but participates in the role-design and evidence interview.

Candidate Choice. Candidate A has deep banking experience and strong enterprise relationships but has never owned a product P&L technology organization. Candidate B built digital products in retail and has strong federal operating evidence but less banking experience. Candidate C is the internal engineering SVP and knows the estate but has participated in the current bypass behavior.

The domain overlay is classified as partly learnable because risk and product leaders are strong. Candidate B demonstrates the best federal judgment. In the work sample, she proposes a time-bounded exception with shared funding, a migration trigger, and clear risk acceptance rather than choosing local or enterprise technology as a matter of principle.

Evaluation. At 90 days, the new CTO has not resolved all dependencies, but the largest decisions have owners and deadlines. At 180 days, two local exceptions are retired and one enterprise standard is changed after evidence shows it harmed customer onboarding. At one year, product delivery is more predictable, enterprise security evidence arrives earlier, and unit cost is clearer.

One platform dependency remains poor. The review does not blame the CTO for lack of control. It evaluates whether she escalated early, offered options, and made the unit consequence visible. She did.

Lesson. The company improved the seam before hiring the person expected to operate it.