Meridian's founding principles: transforming complexity into an operational system

Transformation methodologies are everywhere. McKinsey has its own, BCG has its own, and every major consulting firm offers its own framework. Yet transformation failure rates remain stubbornly high - between 60% and 70% according to studies.

The problem isn't a lack of ideas. It's a lack of comprehensive operational systems - ones capable of translating a strategic vision into concrete actions, coordinating efforts without relying on hierarchical authority, and demonstrating value throughout the transformation, not just at its conclusion.

Meridian was built to fill this gap. Not as yet another conceptual framework, but as a proven operational approach to real-world transformations.

The three pillars: Suggest, Facilitate, Accompany

These three pillars are not sequential phases to be carried out in a linear fashion. They are approaches that the Chief Transformation Officer adopts simultaneously, adjusting their balance according to the context.

Suggest — The Role of the CTO

The CTO does not make decisions alone, but he is the one who outlines the options, clarifies trade-offs, and maintains strategic direction when the organization tends to drift toward operational matters.

In practical terms:

• Provide a comprehensive overview of the interdependencies between projects

• Identify potential friction points before they become roadblocks

• Propose compromise scenarios when objectives conflict

Real-world example: On a banking project aimed at financial advisors, the CTO suggested splitting the rollout into two phases: first, pilot branches to test how well the advisors actually adopted the system, followed by a full rollout after making adjustments. This suggestion, supported by an adoption risk assessment, prevented a large-scale rollout that would have failed in practice.

Suggest is not merely advisory. It is a strategic planning function: the CTO defines the range of possibilities before the Executive Committee makes a decision.

Facilitate — The Coherence Function

The CTO often serves as a cross-functional integrator without direct reporting lines. Meridian provides a framework for the CTO to orchestrate interdependencies, align stakeholders, and bring tensions to light rather than ignore them.

In practical terms:

• Establish governance bodies that serve as effective decision-making forums, not merely reporting committees

• Develop a common language among IT, business units, HR, and finance through shared architectural frameworks

• Identify critical dependencies before they escalate into crises

Facilitation is not project coordination. It is a political function: creating the conditions for collective action without hierarchical authority.

Accompany — The Anchoring Function

The CTO ensures that the transformation doesn't remain merely a theoretical exercise. Meridian provides a framework to help implement these changes in actual practice, at a human-scale pace.

In practice:

• Implement rapid feedback mechanisms to make adjustments in real time

• Organize workshops with teams to foster ownership, not just top-down training sessions

• Measure actual adoption, not just technical deployment

  
  

Real-world example: At Carte Client, this support took the form of peer-to-peer coaching sessions with bank advisors. The result: a 78% adoption rate within three months, compared to the 40% ceiling typically reached by traditional training programs.

Accompany is an operational anchoring function: ensuring that the transformation yields different behaviors, and that, in turn, the tools continuously adapt.

Philosophy: Transformation as a Living System

Most approaches treat transformation as a project: an initial state, a target state, and a plan for moving from one to the other. This view is reassuring but false.

Transformation is not a linear process. It is a living system: it evolves in response to feedback from the field, emerging constraints, and unexpected opportunities. An organization does not simply undergo transformation passively - it reacts, resists, and adapts.

Meridian acknowledges this reality and structures the CTO’s role accordingly:

• Iterative cycles of 3–6 months to deliver tangible value and adjust the course.

• Steering based on actual data rather than adherence to the initial plan. If metrics show that adoption is not happening, we adjust.

• Controlled experiments rather than mass deployment. We test, measure, learn, and scale up.

This philosophy radically changes the CTO’s role: they are not there to execute a master plan, but to stay the strategic course while navigating emerging complexity.

In practice: A CTO guided by Meridian does not present a fixed 18-month plan to the Executive Committee. Instead, they present a clear strategic vision, a detailed roadmap for the next six months, and hypotheses to be tested over the following 12 months. At the end of each cycle, they adjust the plan based on what has been learned.

The three guiding principles: human-centered, data-informed, architecture-driven

These three guiding principles are not mere lip service. They are design constraints that guide every decision at Meridian.

Human-centered: Transformation Starts with Behavior

A transformation that does not change employees’ actual behavior is a failed transformation, regardless of the tools deployed.

This premise requires us to:

• Foster a desire for change by truly listening to and collaborating with operational teams

• Measure actual adoption, not just technical deployment

• Make adjustments when signs indicate that teams are not on board

Meridian offers:

• The design of organic operational models that respect organizational structures, particularly in transformations involving artificial intelligence,

• Change management inspired by agile models and based on experimentation, such as Lean Change Management.

  
  

Data-driven: Making decisions based on facts, not opinions

The CTO must be able to answer three questions at any time: Where are we? What’s happening? What needs to be adjusted?

This premise requires:

• Systematically collecting operational data from day one

• Using predictive analytics to identify risks before they materialize

• Building dashboards that show reality, not what we’d like to see

  
  

Without data, executive committee discussions boil down to mere battles of opinion. With data, the CTO can make these trade-offs more objective.

Meridian offers a framework for collecting data and tracking usage trends, based on data science and machine learning models, to continuously ensure that the solutions designed are both appropriate and widely adopted.

Architecture-driven: Think in terms of systems, not silos

A transformation affects processes, IT systems, organization, skills, and data all at once. Addressing these aspects separately is a recipe for inconsistency.

This premise requires:

• Building a holistic view using shared architectural frameworks

• Mapping the interdependencies between projects before launching initiatives

• Using enterprise architecture tools to visualize ripple effects

Meridian offers the development of customized transformation frameworks, drawing inspiration from other transformation programs and tailored specifically to each organization.

In summary

Meridian’s founding principles are not mere slogans. They are design choices that distinguish a transformation that is actively driven from one that is merely endured.

• The three pillars (Suggest, Facilitate, Accompany) provide the CTO with a framework for structuring their approach

• The philosophy of the living system frees the CTO from the illusion of total control and provides a framework for navigating uncertainty

• The three principles (human-centered, data-informed, architecture-driven) ensure that the transformation remains grounded in reality

  
  

Meridian only works if these principles are put into practice, not just stated. A CTO who implements Meridian without embracing its philosophy will simply repeat the same old failures, just with different tools.

_

This article is excerpted from Chapter 3 of the Meridian Playbook. To learn more about how Gabriel Greenfield supports Chief Transformation Officers, please contact us.