John Campbell Crighton Discusses Strategic Leadership for CTOs Driving Innovation in Tech

Growth is often mistaken for scale, but for technology organizations the real test is whether teams become more effective as they expand. That reality shows up most clearly in hiring, where rapid headcount growth can quietly introduce misalignment that erodes performance over time.

John Campbell Crighton’s approach to scaling teams centers on building durable advantages that competitors cannot easily replicate, a theme that underpins the strategies that follow. Crighton brings more than two decades of experience leading software development and embedding technology into mission-critical systems across healthcare, finance, energy, and technology. 

As Chief Technology Officer (CTO) at ONEngine, his leadership philosophy reflects a pattern across industries: slow down where it matters, design systems with intention, and prioritize long-term performance over short-term optics. Below, he shares how modern CTOs can drive sustainable innovation through disciplined systems that balance stability, trust, and incremental advancement.

Building Teams That Scale With Intent

One of the most common missteps Crighton observes among CTOs is prioritizing hiring speed over what he calls culture density. In regulated industries, where distributed teams often exceed 100 people, the pressure to fill roles quickly can create the illusion of progress. “They hire fast, onboard inconsistently, and discover six months later that they have built a collection of individuals rather than a team.” The long-term cost to that approach is cultural fragmentation, which undermines execution.

Instead, he treats hiring and onboarding as structured systems where culture is assessed before technical capability, with emphasis on intellectual curiosity, ownership, and written communication across time zones. Onboarding is managed like a product, with clear expectations, version-controlled documentation, and defined outcomes before a developer contributes production code.

Equally important is the infrastructure that sustains connection. Distributed teams require deliberate design, from asynchronous stand-ups to in-person summits that reinforce trust. Performance is measured at the team level, ensuring collaboration is rewarded as much as individual output.

Innovating Without Breaking What Works

Crighton’s approach to innovation is shaped by experience in complex environments such as electronic medical records and revenue cycle management systems, where reliability is inseparable from patient care and compliance. “Legacy is a risk profile, not a death sentence,” he says. Rather than pursuing full system rewrites, which can introduce operational and regulatory risk, he advocates for a model built on embedding, isolating, and iterating.

This begins with mapping dependencies and understanding system exposure before introducing change. AI capabilities are developed as isolated services, connected through APIs rather than embedded directly into legacy codebases. This allows new functionality to evolve independently while preserving system stability.

To mitigate risk further, new workflows operate in parallel with existing systems before deployment. “We ran the new system in shadow mode alongside the legacy process for a minimum of 30 days,” he says. Only after performance is validated does full transition occur. Every release is paired with a tested rollback procedure, ensuring resilience under pressure. The result is a model where innovation compounds over time, enhancing trusted platforms.

Retention as a Product

Crighton’s teams have achieved a 98% retention rate across more than 180 hires, a result he attributes to treating employee experience with the same rigor as customer-facing products. “Retention is won or lost in the first 90 days,” he says. Waiting for exit interviews to diagnose attrition is, in his view, a flawed approach.

His framework rests on three pillars. The first is structured career visibility, where every engineer receives a clearly defined progression plan early in their tenure. The second is manager quality, which he considers the primary variable in retention. Regular feedback loops and leadership training ensure accountability at the management level.

The third pillar is meaningful work allocation. Senior engineers are engaged in high-impact projects and architectural decisions, reinforcing both ownership and motivation. “Being consulted, genuinely consulted, is deeply motivating for high performers,” Crighton says. Together, these elements create an environment where retention is engineered proactively rather than managed reactively.

Reframing Innovation

Securing investment for innovation often hinges on how the conversation is framed. Crighton argues that boards do not resist innovation itself, but the uncertainty that surrounds it. “When a CTO walks into a budget conversation and asks for capital to modernize the platform, what a board member hears is discretionary spend with unclear return,” he says.

His approach is to translate technical initiatives into financial and strategic terms. For example, technology debt is reframed as quantifiable risk, including the potential cost of outages, compliance failures, or security incidents, while AI initiatives are positioned as drivers of competitive advantage.

He also structures investments in staged increments, often in 90-day cycles with defined success criteria. This reduces perceived risk while maintaining momentum. Collaboration with finance leadership further strengthens the case, aligning technical strategy with business priorities.

The CTO as Architect of Intelligent Systems

Looking ahead, Crighton sees AI reshaping not only software development, but the role of the CTO itself. “AI is not just changing what software does. It is changing who can build software and how fast it can be built,” he says. As engineering output accelerates through AI-assisted development, the constraint shifts toward product clarity and architectural judgment. CTOs will spend less time managing delivery pipelines and more time designing systems that integrate human and AI decision-making.

This evolution also introduces new responsibilities. Questions of data integrity, explainability, and governance are becoming central to product design and customer trust. “The CTO becomes a trust officer,” Crighton says, highlighting the growing importance of communication alongside technical expertise. Those who adapt will lead organizations that are not only more efficient but also more resilient and transparent in how they deploy intelligent systems.

Follow John Campbell Crighton on LinkedIn and YouTube or visit his website for more insights.