How Work Moves in an Enterprise
The code is ready on Monday. Sam, your product manager at Loomwork, asks why it will not be live at Harbourline on Tuesday. The answer is that in an enterprise, a change does not just need to work. It has to pass through people, approvals and controls, each with its own calendar.
The rule
Every step has an owner and a gate: map both before promising dates.
The business process. Your tool sits inside a larger flow. At Harbourline it runs like this: shipment booked → carrier delivers → invoice arrives → clerks check it → it is approved (by Farhan up to ₹5 lakh, by Meera above that) → it is paid in the payment run on the 1st or the 15th → it is recorded in the accounts. A change to one step ripples through the others. If disputes are not settled before a payment run, carriers are paid late and relationships suffer.
Controls. Finance processes carry rules that protect against fraud and error. Segregation of duties means the person who approves an invoice cannot also change which bank account a carrier is paid into. Auditors expect a record of who approved what, and when. Your system must keep these rules, never route around them.
The gates for a change. Going live usually needs a security review; approval from a change advisory board, a regular meeting that approves changes to production systems; sometimes a contract update; and training before users switch over. Finance teams also freeze system changes around month-end close, while the books are being finalised.
The shortcut
Walk the invoice, then walk the change. First trace one invoice through the process, noting who owns each step. Then trace your release through each gate, noting its date. The go-live date is where the second walk ends.
Walk the invoice
Mailbox → clerks check → Farhan or Meera approves → treasury pays on the 1st or 15th → accounts records it.
The trap is promising a date because the code is ready. Working code is only the first gate.
Drills
Answer fast — trust the rule.
Why does month-end close matter to your go-live date?
What does segregation of duties mean here?
Your code is ready on Monday. The change advisory board meets on the Tuesday after next. Barring an emergency, when can the change go to production?
Why should flagged invoices be settled before each payment run?
Remember
- Every step has an owner and a gate: map both before promising dates.
- Shortcut: walk the invoice, then walk the change.
- Trap: promising "next week" because the code is ready.