Konstantin “Stan”
PonomarevProgram & portfolio leadership
Menu
All case studies

Decision note · Delivery coordination

ERP delivery 2 min read

Reviewing ERP cutover readiness

At a glance

The challenge

Bring operational preparation, system loading and support into one cutover plan.

My responsibility

I ran the PMO touchpoint and coordinated plan and resource reconciliation.

The decision

I separated the delivery sequence, support allocation and external vendor decisions.

Readiness review

Four open items produced eight follow-up actions; a 20–30-hour planning gap was made explicit.

Context
U.S. healthcare client · ERP engagement
Period
2026
Jump to review findings

Context

The review in detail.

Background and context

As the ERP engagement approached cutover, operational preparation, system loading and remaining support needed one coherent plan. I ran a focused PMO touchpoint to expose mismatches before they became last-minute surprises.

The working plan and the resource estimate did not fully agree. Operational counts, system loading, EDI decisions and the non-stock workflow also sat on different paths to readiness.

The decision, illustrated

The plan and the commitment had to agree.

Two rows of zipper teeth align at one end but remain separated at the other. The open area makes the unresolved work visible.
Operating sequence
Compare the 60 planned hours with the 80–90-hour estimate for remaining work.
Support commitment
Make the 20–30-hour difference visible before agreeing the remaining delivery commitment.
Unresolved work
Keep the planning gap and open decisions visible for follow-up.

This was a readiness and resource review. The open zipper does not imply that cutover was completed.

open readiness items
4
follow-up actions
8
planned go-live date
May 4

Judgment

Making the unresolved commitments visible.

The central trade-off

Keeping the date in the plan was not enough. The operational sequence, support hours and external vendor decisions needed separate owners and an honest view of what remained open.

  1. 01

    Reconcile the sequence.

    Connected operational preparation, inventory counts, system loading and the planned May 4 go-live. Each step needed a clear handoff and an accountable owner.

  2. 02

    Expose the effort gap.

    Raised the difference between 80–90 hours of expected support and the 60 hours in the plan. The next action was to reconcile allocation and budget rather than absorb the gap silently.

  3. 03

    Keep unresolved dependencies visible.

    Separated EDI vendor selection from the immediate cutover path and retained the non-stock workflow as an open issue. The review produced eight follow-up actions.

Outcome

What the readiness review established.

  • The PMO review consolidated four open items into an actionable readiness discussion.
  • A 20–30-hour planning gap was made explicit for allocation and budget reconciliation.
  • External vendor decisions and unresolved workflow work remained visible with follow-up ownership.

Responsibility

My role and the scope of this case.

My role was program oversight, plan reconciliation and coordination. The case records the readiness review and its actions; it does not claim that every issue was resolved in that meeting or that the planned go-live occurred on time.

Hiring for similar responsibilities?

Discuss a role

A conversation about the work

Let’s talk about
the work ahead.

If you’re hiring a leader for complex programs, portfolios or products, I’d welcome a conversation.

Discuss a role

Based in Tampa, FL

Program & portfolio leadership
Product & AI leadership

U.S. work authorization
No sponsorship required

One-page profile (PDF) Connect on LinkedIn (opens in a new tab)