👋 A Note to Our Community

Hi from the LMNAs team -

In our previous edition, we explored why planning fails across organizations. We looked at forecasting challenges, reactive decision-making, and how teams often lose visibility into capacity and resources long before execution begins.

But forecasting is only half the story.

The second half reveals itself during execution—and its impact is far more damaging.

And it affects everyone.

Whether you're running:

• A manufacturing operation
• A supply chain
• A software delivery team
• An IT department

The story remains remarkably similar.

This month, we explore why execution failures rarely originate during execution itself, and how connected planning helps organizations bridge the gap between assumptions and reality.

The Universal Planning Problem

Most leaders blame delivery failures on execution.

They say:

• Projects missed deadlines.
• Resources weren't allocated properly.
• Communication broke down.
• Production schedules slipped.
• Procurement delays cascaded.
• Shipments were delayed.
• Sprints collapsed.
• Dependencies failed.

These explanations dominate executive reviews and post-mortems.

But they miss something important.

The seeds of execution failure are rarely planted during execution.

They are planted during planning.

Sometimes months before work even begins.

Execution only exposes what planning failed to see.

How Plans Become Fiction

Manufacturing Example

A production director forecasts demand.

S&OP allocates capacity.

Procurement commitments are made.

Everything looks healthy.

But by execution time:

• Supplier delays appear.
• Markets shift.
• Quality problems emerge.

Capacity buffers disappear.

Suddenly, the original plan no longer reflects reality.

IT Delivery Example

An IT leader forecasts quarterly capacity.

Teams allocate story points.

Sprint commitments are created.

Everything appears achievable.

But by execution time:

• Production incidents emerge.
• Dependencies slip.
• Compliance work appears.
• Capacity disappears.

The outcome?

Exactly the same.

The Core Problem

Every initiative starts with confidence.

Requirements are gathered.

Resources appear available.

Plans are approved.

Commitments are made.

On Day 1:

The plan looks realistic.

By Day 90:

The plan often looks like fiction.

Not because teams failed.

But because reality changed.

When Execution Becomes Protection

As delivery begins:

Teams continue:

• Tracking progress.
• Managing work.
• Meeting commitments.

Inside the execution window, everything appears under control.

But outside that window:

• Critical resources disappear.
• Dependencies move.
• Priorities shift.
• Capacity shrinks.

The execution plan survives.

The conditions needed to achieve it do not.

Eventually, teams stop executing the plan.

They start protecting it.

They:

• Replan continuously.
• Shift resources.
• Work longer hours.
• Adjust priorities.

Until even strong execution can no longer compensate for weak assumptions.

Missed commitments.

Delivery uncertainty.

Burnout.

These are not the cause.

They are the outcome.

The real issue is simple:

Planning and execution have become disconnected.

The Five Stages of Planning

Every organization operates across five interconnected stages.

Whether manufacturing or IT.

Stage 1 — Forecast & S&OP

Understanding demand and aligning strategy with capacity.

Manufacturing

• Market forecasts
• S&OP planning

IT

• Business initiatives
• Support commitments

The Disconnection

Forecasts rely on assumptions.

Capacity constraints remain invisible.

Stage 2 — Demand Planning

Turning forecasts into time-phased demand.

Manufacturing

• SKU demand
• Lead times

IT

• Features
• Support requests
• Sprint commitments

The Disconnection

Demand ignores capacity realities.

Stage 3 — Resource Planning

Securing resources required to execute.

Manufacturing

• Suppliers
• Materials
• Labor

IT

• Team allocation
• Vendors
• Dependencies

The Disconnection

Resources committed today may not exist tomorrow.

Stage 4 — Execution

Delivering work.

Manufacturing

• Production
• Quality control

IT

• Sprints
• Development
• Testing

The Disconnection

Execution inherits broken assumptions.

Unplanned work consumes capacity.

Stage 5 — Delivery & Monitoring

Measuring outcomes.

Manufacturing

• Logistics
• Customer delivery

IT

• Releases
• Production monitoring

The Disconnection

By this stage:

The plan is already broken.

Monitoring reveals problems—

but cannot prevent them.

Connected Planning in IT Delivery

Connected planning keeps all five stages aligned.

S&OP Stage

Real demand:

• Features
• Incidents
• Support work

is matched against actual capacity.

Backlog Planning

Features are prioritized based on:

• Dependencies
• Team availability
• Existing commitments

Sprint Planning

Commitments reflect:

• Production support
• Shared resources
• External dependencies

Sprint Execution

Plans evolve continuously.

Responding to:

• Incidents
• Capacity shifts
• Dependency changes

Release Management

Releases happen only when:

• Dependencies are complete.
• Upstream work is stable.

The result:

Problems become visible before commitments fail.

Sprint Comparison Example

Sprint 1 — Healthy Sprint

Characteristics:

• Stable burndown
• Consistent velocity
• Predictable delivery

Execution reflects planning.

Sprint 2 — Diverted Sprint

Characteristics:

• Gaps between planned and actual progress
• Unplanned work
• Priority changes
• Dependency delays

Diversion becomes visible early.

Before commitments collapse.

Business Value

By comparing execution patterns, teams can:

• Detect delivery diversion early.
• Investigate root causes.
• Correct problems before commitments break.

Execution becomes proactive.

Not reactive.

Connected Planning Across Industries

Organizations with strong visibility adjust plans without abandoning accountability.

Instead of saying:

"We hope this still works."

They say:

"Here is what is truly possible."

Connected planning allows organizations to adapt without chaos.

LENS IPS

LENS IPS enables connected planning across industries.

It:

• Connects workload, capacity, resources, and dependencies.
• Spans all five planning stages.
• Works across manufacturing and IT.
• Treats planning as continuous evolution.
• Provides visibility before commitments are affected.

Planning becomes something that evolves with reality.

Not something frozen in time.

Learn How LMNAs Approaches Connected Planning

Planning is universal.

Whether manufacturing products or delivering software.

The challenge remains the same.

Explore how connected planning transforms execution across every industry.

👉 Learn More About LMNAs Connected Planning Approach

Coming Next

Is Your Planning Stuck in the Execution Stage?

In the next edition, we'll explore:

• Why execution is often treated in isolation.
• How visibility disappears between stages.
• Why most organizations only manage the fourth stage.
• And why the most successful organizations connect all five stages together.

Because execution isn't where planning ends.

It's where connected planning proves itself.