CASE STUDY 004 - Part II· Reconnecting the Order Lifecycle

Restoring operational visibility and control across the customer order.

Case Study in Progress

Part I established the service foundation: creating greater visibility into customer demand, service activity, and the information Customer Service needs to manage its work.

Part II moves upstream.

As the transformation progressed, it became increasingly clear that Customer Service visibility alone could not solve the larger customer problem. The information needed to answer a customer often depends on an operational system that had itself become fragmented.

Stage 2 —RECONNECTING THE ORDER LIFECYCLE

SAP serves as the primary transactional system, but the customer order does not live within one transaction or one department.

It moves through a series of interconnected functions:

Quote → Order Entry → Estimating / Engineering → Planning / Purchasing → Production → Completion → Staging / Warehousing → Shipment

Each function holds part of the order story.

The challenge was that those parts were not consistently functioning as one connected operating flow.

Information, ownership, physical product movement, and customer commitment dates could become disconnected as an order moved across functions. In some areas, historical system and process decisions had created gaps between stages. In others, teams relied heavily on manual investigation, individual knowledge, spreadsheets, meetings, and physical searches to determine what was actually happening.

The result was an important realization:

The organization did not simply have a late-order problem. It had an order-visibility and execution-control problem.

THE PERFORMANCE SIGNAL

One measure made the severity of the challenge difficult to ignore.

On-time delivery was approximately 30%.

For an operation where dependable delivery performance should be substantially higher, this was not simply a Customer Service metric. It was an enterprise operating signal.

At the same time, the open-order population had grown beyond 400 open orders, creating a volume of work that made traditional order-by-order investigation increasingly difficult to manage.

Customer Service experienced the downstream consequence.

When a customer asked:

Where is my order?

Will it ship when promised?

What is preventing it from moving?

When can I realistically expect it?

The answer could require investigation across multiple functions before a credible response could be provided.

That creates a fundamental customer-experience problem:

A company cannot communicate a reliable customer commitment if it cannot reliably see the operational reality behind that commitment.

NOT ALL OPEN ORDERS ARE THE SAME

The next discovery was deceptively simple.

An open order is not necessarily an executable order.

Some orders may be ready to move through production.

Others may be constrained by missing material, components, engineering requirements, purchasing dependencies, approvals, or other unresolved conditions.

When those populations exist inside one large open-order queue, the organization risks spending significant time investigating orders individually without first answering a more fundamental question:

What can we actually produce now?

That leads to a different operating model.

Rather than treating 400+ open orders as one population, the work begins by distinguishing:

Executable Orders — the requirements necessary to move the order are available.

Constrained Orders — something specific prevents the order from progressing and requires intervention.

For constrained orders, the management requirement then becomes clear:

What is the constraint? Who owns it? What action is required? When will it be resolved?

This moves the organization away from simply reviewing orders and toward managing constraints and flow.

TRANSFORMATION STATUS

In progress.

This is Part II of a live case study documenting an active customer-operations transformation. The current work is focused on reconnecting the order lifecycle, improving operational visibility, distinguishing executable work from constrained work, strengthening cross-functional ownership, and creating a more reliable flow of information back to Customer Service.

The transformation remains underway. Future updates will document measurable results, operating changes, technology and process decisions, and lessons learned as the work progresses.

Steven Waltz

About the Author

Steven Waltz is a Customer Operations and Customer Experience executive focused on service transformation, operational excellence, global delivery, BPO strategy, AI-enabled operations, and enterprise customer experience strategy.

Next
Next

CASE STUDY 004 - Part I· From Reactive Service to a Connected Customer Operations Model