The Real Cost of Not Knowing Where a PO Is

I got asked "where's that PO?" ten times in a single week.

Not by the same person. By finance, by the department head, by a vendor who hadn't heard anything in twelve days. Each time, I had to go find someone, who had to go find an email, who had to check a shared drive that may or may not have been updated.

What I noticed was not the inefficiency. It was the lying. Not malicious lying — the polite kind. "I'll get back to you on that." "I think it's with the CFO." "Should be approved any day now." Nobody actually knew. Everyone acted like they did.

That is what a broken procurement process really costs: it turns competent people into confidence actors. Finance builds cash flow projections against commitments that may not exist. Vendors calibrate their trust in you based on whether your calls mean something. Managers make resourcing decisions on the assumption that approvals are moving — because no one has told them otherwise.

When we brought procurement into the ERP, the immediate win was not speed. It was that "I don't know" became an honest answer for the last time. After that, anyone could see exactly where a PO sat, who had it, and since when.

The process did not change that much. The accountability did.

Turns out, visibility is not a nice-to-have. It is the thing that makes everything else you're managing actually true.