Before Operating Model Design Comes Business Intent Design

Most transformation leaders are familiar with the traditional progression:

Strategy → Operating Model Design → Process Design → Technology → Automation → AI

It appears logical. Leadership establishes a strategy, teams design the future operating model, processes are redesigned, technology is implemented, automation is introduced, and eventually AI is enabled within operations.

Yet after decades of methodology refinement and sustained investment across ERP, CRM, analytics, automation, and AI, organizations continue to experience a familiar problem.

The transformation delivered what was designed.

But not necessarily what was intended.

The reason may be simpler than many realize.

A critical layer is missing between strategy and execution.

That missing layer is Business Intent Design.

Strategy Is Direction, Not Design

Strategy tells an organization where it wants to go.

Leaders define ambitions such as:

· Accelerate growth

· Improve customer experience

· Expand globally

· Increase profitability

· Become data-driven

· Embrace AI

These are essential objectives. Organizations cannot transform without them.

However, strategy creates direction, not design guidance.

Consider the strategic objective:

“Improve customer experience.”

What does that actually mean for the people responsible for transformation design?

Reducing order cycle time?

Improving first-contact resolution?

Increasing self-service adoption?

Reducing customer effort?

Improving response quality?

Increasing retention?

The answer may be “all of the above,” but strategy alone rarely specifies which outcomes matter most, which tradeoffs are acceptable, or how success will ultimately be judged.

As a result, every downstream team is forced to interpret leadership intent for itself.

That is where misalignment begins.

The Translation Problem

Most transformations encounter a hidden translation problem.

Leadership creates strategy.

The operating model team interprets it.

Process designers interpret it.

Technology teams interpret it.

Automation teams interpret it.

AI teams interpret it.

Each group acts rationally based on the information available. Yet each group can develop a slightly different understanding of what leadership intended.

The consequence is not poor execution. The consequence is fragmented execution.

Everyone is moving forward, but not necessarily toward the same destination.

This is why programs can deliver scope, milestones, and technology while still leaving executive Sponsors dissatisfied with the Business Outcomes achieved.

The intent became diluted as it traveled downstream.

The Missing Layer: Business Intent Design

Before organizations determine how they should operate, they should first define what must be true if the strategy succeeds.

That is the purpose of Business Intent Design.

Business Intent Design translates strategic direction into explicit, governed, transformation-ready Business Intent that can guide every subsequent design and delivery decision.

It asks questions such as:

· What Business Outcomes must be achieved?

· What Conditions of Success must remain true?

· What decision boundaries and exception rules must be preserved?

· What accountability must exist?

· What evidence will demonstrate success?

· How will leadership know the transformation delivered what was intended?

These questions sound simple. In practice, they establish the foundation upon which the transformation rests.

Without explicit intent, operating models become collections of assumptions. With explicit intent, operating models become purposeful design responses.

The Transformation Design Chain

A more complete transformation design chain looks like this:

Strategic Intent → Business Intent Design → Operating Model Design → Process Design → Automation → AI Enablement

Each layer serves a distinct purpose. The chain describes the broader design landscape, not a claim that one methodology or advisory firm should perform every discipline. Business Intent Design provides the governing input. Operating Model Design, Process Design, solution design, automation, and AI Enablement remain specialized downstream disciplines.

Strategic Intent

Strategic Intent answers:

“Where are we trying to go?”

It defines leadership’s vision for the future organization, including desired market position, value creation objectives, stakeholder expectations, and long-term direction.

Strategy establishes purpose and ambition. It does not fully define operational behavior.

Business Intent Design

Business Intent Design answers:

“What must be true if the strategy succeeds?”

This layer translates strategy into operationally actionable intent. Instead of relying only on broad aspirations, leadership defines measurable expectations, boundaries, accountability, and evidence requirements.

For example:

Strategic Intent:

“Deliver a superior customer experience.”

Business Intent:

· Reduce order cycle time from 10 days to 2 days.

· Resolve 95% of service inquiries within 24 hours.

· Maintain profitability thresholds.

· Preserve regulatory compliance.

· Improve customer retention rates.

Now the organization has something concrete it can design toward. Intent has become operationally meaningful.

Operating Model Design

Operating Model Design answers:

“How should the organization operate to achieve the intended outcomes?”

At this stage, leaders determine organizational structure, governance mechanisms, decision ownership, role definitions, cross-functional coordination, and ways of working.

Operating Model Design is not Business Intent Design. It consumes Business Intent as a governing input.

The operating model should not define the outcomes after the fact. The intended outcomes should shape the operating model.

The operating model is not the goal. It is a means to achieve the goal.

Process Design

Process Design answers:

“What work must be performed, and how?”

This layer defines workflows, activities, business rules, handoffs, controls, and exception handling.

Processes operationalize the operating model. A process should exist because it helps achieve an intended outcome, not simply because it existed before.

In a Transformation Program, detailed future-state Process Design typically occurs during implementation and remains a Delivery-Side responsibility. Sponsor-Side Business Intent Governance does not replace that work. It provides the governed intent against which the resulting process designs should be evaluated.

Automation

Automation answers:

“What can be executed consistently and efficiently?”

Automation can remove repetitive manual effort and improve scalability. However, automation does not determine whether the underlying process is appropriate.

Automation accelerates what has been designed. If the process or intent is misaligned, automation can scale that misalignment faster.

AI Enablement

AI Enablement answers:

“Where can intelligence improve decisions, recommendations, actions, and outcomes?”

AI can surface insights, recommend actions, predict outcomes, assist judgment, guide users, and identify patterns.

But AI should not define organizational intent. AI should operate within boundaries established by leadership, with humans governing the decision loop.

Otherwise, organizations risk scaling behaviors they never consciously chose.

If This Layer Was Always Missing, How Did Organizations Operate Without It?

A reasonable skeptic might ask:

“If Business Intent Design is so important, how have organizations operated and transformed for decades without it?”

The answer is that organizations did not operate without Business Intent. They operated without a formal discipline for designing and governing it.

Business Intent existed across strategy documents, executive conversations, policies, requirements, process knowledge, decisions, and institutional memory. Experienced leaders, business analysts, process owners, consultants, and employees continuously translated that fragmented intent into operational action.

When requirements were incomplete, people interpreted them. When definitions conflicted, teams reconciled them. When policies did not fit operating reality, managers exercised judgment. When implementation choices moved away from leadership expectations, Sponsors intervened.

This human interpretation layer allowed organizations to continue operating. It also contributed to many of the conditions transformation programs came to treat as normal:

· Requirements churn

· Repeated alignment meetings

· Design disagreements

· Local workarounds

· Unplanned customization

· Scope expansion

· Late-stage rework

· Testing disputes

· Outcome drift

Organizations compensated for the missing discipline by repeatedly repairing the connection between strategy and execution. The cost of that repair was absorbed throughout the Transformation Program rather than recognized as evidence of a missing layer.

Business Intent Design does not invent a new category of work. It makes explicit, governable, and durable the translation work organizations have always performed informally, repeatedly, and inconsistently.

Why AI Changes the Stakes

The rush to adopt AI is exposing weaknesses that have existed in transformation programs for years.

Many organizations are asking:

“Is our operating model ready for AI?”

An even more important question may be:

“Have we clearly defined what AI should help us accomplish?”

Before widespread automation and AI, ambiguity could often remain hidden inside human judgment. People recognized context, challenged instructions, reconciled conflicting definitions, handled exceptions, and escalated decisions that did not make sense.

As systems take on more recommendations, classifications, routing decisions, and actions, interpretation becomes executable behavior. Ambiguity that once affected a local decision can now be repeated across transactions, processes, systems, and interactions.

AI did not create Business Intent drift. It amplifies the speed, scale, reach, and persistence with which existing drift can influence operations.

That is why Business Intent Design matters now. It is not added complexity. It is a formal response to an old problem that can no longer be managed primarily through institutional knowledge, local judgment, and repeated executive intervention.

The Emerging Need for Business Intent Governance

As automation and AI expand, organizations increasingly require capabilities that help leaders:

· Define intended Business Outcomes explicitly

· Connect strategy to operational execution

· Preserve decision accountability

· Establish Outcome Evidence requirements

· Validate whether execution remains aligned with approved Business Intent

· Detect when operations drift from the outcomes leadership authorized

Historically, much of this work was informal. AI changes the consequences of leaving it that way.

The more intelligence organizations embed into operations, the more important it becomes to define what that intelligence is expected to accomplish and the boundaries within which it may operate.

Business Intent can no longer remain implicit. It must become governable.

A Question Every Sponsor Should Ask

Before approving another operating model initiative, process redesign effort, automation project, or AI program, executive Sponsors should ask a simple question:

“Have we explicitly defined what outcomes we intend to achieve, what must remain true, and how we will know we achieved them?”

If the answer is unclear, the organization may be moving too quickly into design.

Operating Model Design is critically important. Process Design is critically important. Automation is critically important. AI Enablement is critically important.

But all of them depend on something more fundamental.

Before Operating Model Design comes Business Intent Design.

The distinction may determine whether organizations merely modernize existing operations or intentionally create the future leadership authorized.