Jonathan Schermer
← All work
Manufacturing company2025Role: Turnaround co-lead

A resource model that became the replan

A large SAP program was six months behind. I was brought in to help reset it, and built the model the program ended up running on.

6 months
behind schedule when I joined
10+
workstreams in one bottom-up plan
Oct 2025
go-live reached
The problem

The program had more than 3,000 Jira issues and 10+ workstreams, from order-to-cash to reporting. No one could say whether the plan was feasible, because no one could see who was overbooked and who had room.

Without that view, every replan was a negotiation of opinions.

How it works

Plan and people in, weekly capacity out

Scroll sideways to see the full diagram →
Fig. 1The model put demand and capacity on one chart, so the replan became a matter of moving work, not arguing about it. The heatmap values are illustrative.
What I did
  • Co-led the reset with a firm partner, and ran the program-wide replan meetings that won the client's buy-in.
  • Built the Python and Alteryx allocation model, and walked the client's program office through how it works.
  • Built a Jira dashboard showing the critical path by workstream. The firm later reused it as a reference for another client.
  • Wrote Python checks for duplicates, blanks and mismatches in product master data, tied to an issue that touched about 440,000 records.
  • Led executive escalations, and ran daily status and defect triage through the third integration test cycle.
Outcome

The model became the live replan, and the program reached go-live in October 2025. The client's CIO asked for me to stay on the program.

PythonAlteryxJiraCapacity planningExecutive alignment
Contact

Let's talk.

If you're building AI or platform products, I'd like to hear about it.

LinkedIn ↗