Essay · operations
The missing work was visible from inside it.
The project view held the migration as a sequence of milestones. The operating view held it as a stream of changes that kept flowing after the milestone was signed off. Both views were necessary. Only one of them could see the missing work.
Every plan is written from above the work. It has to summarize or it stops being a plan. But a summary is a decision about what not to see, and what a plan leaves out does not stop existing. It lands on whoever is standing closest to it.
I learned this from a junior seat.
The data would not sit still
I was in a junior workforce-planning role during a WFM platform migration, learning the new tool while still learning the old one. The plan for it ran to the import and stopped.
New hires arrived. People left. Shifts changed. Each one updated the old system and had to show up in the new one. Without a repeatable way to translate between them, the cutover ran on somebody entering the same change in two places and hoping the records did not drift.
I have never had much patience for repetitive manual work that a system should be doing. So I built a mapping table.
It was not sophisticated. It laid out the events that changed who was working and when, and mapped each one to the fields that had to change in both systems. Once the table existed, keeping the records aligned was a process people could run instead of a burden somebody had to absorb.
That table was my first contribution at that company outside my narrow job description. Nobody above the work was hiding the gap. The project view held the migration as a sequence of milestones, and against the milestones it was on track. The operating view held it as a stream of changes that would keep arriving after every milestone was signed off.
Both views were necessary. Only one of them could see the missing work.
Where improvement starts
After that I kept looking for places with the same shape. Two parts of the operation that did not connect. A piece of manual work someone had quietly folded into their day. A process that looked complete from above and failed at the handoff.
Those places were rarely on a project plan. They were usually where the next useful improvement started.
The distance between the plan and the day is not unique to a migration. Somebody is always paying for it. The only question is when the operation finds out. Early, while the cost is one person quietly double-entering records. Or late, when the drift has turned into an outage, a backlog, a customer complaint, or a resignation.
The cost of paying later is exactly what the dashboard cannot show in advance.
The people closest to the work
No plan sees everything, and a plan that claims to is a summary with more confidence. The question is whether anyone with the authority to change something ever asks the people who can see what the plan cannot.
They are easy to find. They are the ones absorbing the difference between the plan and the day. The agent working around a broken tool on every contact. The analyst re-keying the same numbers into two systems. The team leader covering a structural gap by hand and calling it a busy week. Each of them is holding information the operation says it wants. Each of them has also watched what happened to the last person who mentioned it, and priced the answer accordingly.
Catching a gap early is cheap. It costs a conversation and a willingness to hear that the plan was wrong. Catching it late costs whatever it turned into, at the market rate. Then somebody usually buys a bigger dashboard.
The point
The floor is where the missing work shows up first.
An operation looking for its next improvement does not need a grander plan. It needs somebody to ask the people who are already covering the difference, and it needs the person who answers to be better off for having answered. I got my start as one of those people. Everything I believe about frontline work being a capability instead of a cost line started with being given room to close a gap no plan had seen.
Want to talk about this? Email me.