Case: Finance Approval Bottleneck, Then Everyone Blames the Tool
Your invoice isn't stuck because the software is slow. It's stuck because your rules are a mess. How to map the 'Approval Fog' and fix the flow.
The Tool is Innocent
I recently audited a workflow where vendor payments were delayed by 15 days on average. The team was screaming at the software provider.
“The button doesn’t work!” they said.
I dug into the logs. The button worked fine. But the logic behind the button was: IF amount > $5,000 THEN require approval from ‘Regional VP’.
The problem? The role “Regional VP” was vacant. The system did exactly what it was told: it waited for a ghost.
The Friction: The Logic Black Box
This is Approval Fog. It happens when we hard-code bad policies into our tools.
- The “Just in Case” Approver: We add the CEO to the approval chain for $50 software licenses. Why? Fear.
- The Hidden Threshold: Nobody knows that the limit is $500, so they submit $501 and get stuck in a 2-week review loop.
- The Dead End: Requests routing to people who are on vacation or have quit.
The Flow: Map, Define, Hand off
We do not fix this by coding. We fix this by drawing.
Step 1: The Visual Map
I pull the team into a room. We draw the path of a single dollar.
- User requests X.
- System checks Budget.
- System routes to Manager.
- Manager approves.
We identify every “Stop” sign. Usually, we find that 30% of the stops are redundant. We delete them.
Step 2: The Matrix (Thresholds)
We replace vague feelings with hard numbers. We build a simple Approval Matrix.
- < $100: Auto-approve (Manager notified).
- $100 - $1,000: Manager approval.
- > $1,000: Finance Director approval.
Step 3: The Control Handoff
This is critical. I am a Process Architect, not a CFO. I build the pipes; I do not choose what flows through them.
Once the map is clean, I hand the specific control design to Klara (our Control Architect).
- I say: “The flow is frictionless now. The pipes are connected.”
- Klara says: “Good. Now I will set the validation rules to ensure we don’t accidentally launder money or violate tax law.”
Klara defines the risk. I ensure the speed.
By separating the Flow (Movement) from the Control (Permission), we get the best of both worlds. The invoice moves fast, but it never moves recklessly.
Summary: Don’t blame the tool for following your bad instructions.
- Map the path.
- Clean the rules.
- Let the experts set the controls.
FAQs
Why not just let everyone approve their own spend?
Because that is how you go bankrupt. Trust needs verification. Verification needs rules.
The process is too complex to map.
If it is too complex to draw, it is too complex to work. Simplify the rules first.
Who defines the risk?
Not me. I build the road; Finance sets the speed limit. That is why I hand off to Klara.