Business context
Cross-border teams often appear aligned because they use the same spreadsheet, dashboard or presentation. Headquarters sees a forecast, margin estimate, launch date or capacity plan; the Vietnam team sees the same numbers. Yet the figures may rest on different definitions, evidence dates and operating assumptions. One side reads “confirmed” as customer-approved. The other means internally probable. One side treats available capacity as technically possible; the other assumes material, labour and quality release are already secured.
The document is shared, but the operating truth is not. This gap matters because cross-border decisions become commitments: quotations go to customers, suppliers reserve material, factories protect capacity and finance releases working capital. By the time an assumption is exposed, several functions may already have acted on it.
Cross-border leadership therefore needs more than visibility. It needs a method to identify, test and retire assumptions before they become expensive promises.
Core management problem
Most management systems record conclusions but not the assumptions that produced them. A forecast shows volume without the customer approval event behind it. A cost model shows margin without the exchange rate, yield or logistics basis. A launch plan shows a date without distinguishing approved specification, trial completion and production readiness.
When headquarters challenges the number, the local team may hear distrust. When Vietnam later changes the number, headquarters may see weak discipline. The real problem is that neither side agreed which assumptions were provisional, who owned the evidence or when the assumption would expire.
This creates false precision. A number looks controlled because it appears in a standard template, while its meaning continues to move. Leadership then debates the output instead of controlling the evidence beneath it.
Common mistakes
The first mistake is treating one file as one version of truth. A file can be current while its inputs come from different dates or owners. The second is hiding uncertainty inside a single number. A forecast of 100,000 units may combine confirmed orders, customer indications and sales aspiration without showing the mix.
The third is allowing verbal assumptions to survive after the meeting. “The customer should approve,” “capacity should be available” and “the supplier can probably support” become operating inputs without a recorded test. The fourth is updating a figure without preserving why it changed, so the organisation cannot distinguish learning from inconsistency.
The fifth is escalating every uncertainty to headquarters. This overloads senior attention and weakens local accountability. Assumptions should travel across the border only when they affect authority, customer commitment, capital, capacity, product conformity or enterprise precedent.
Practical framework: the cross-border assumption register
Create an assumption register for decisions that cross headquarters and Vietnam. It should sit beside the operating report, not become another broad administrative database.
For each material assumption, record six fields. First, state the assumption as a testable sentence: “Customer technical approval will be received by 15 September,” not “approval progressing.” Second, classify its impact across revenue, margin, cash, capacity, quality, delivery or compliance. Third, name the evidence required to close it and the source of that evidence.
Fourth, assign one owner. The owner is responsible for obtaining or validating evidence, not merely updating a cell. Fifth, set a review date and an expiry condition. If evidence does not arrive, the assumption must not remain silently active. Sixth, define the default action: hold the quotation, limit material purchase, keep capacity unreserved, use a pricing buffer or escalate to a named authority.
Use three statuses. Open means the assumption remains unverified but is inside an approved boundary. Confirmed means the required evidence exists and the relevant record is updated. Rejected means the assumption failed and the plan, quotation or commitment must change. “Pending” without a boundary or date is not a status; it is unmanaged delay.
Connect the register to configuration discipline. When a specification, forecast, cost basis or launch date changes, record the approved version, effective date, affected decisions and superseded assumption. This prevents teams from acting on different versions of the same commercial reality.
Patrick Lee Business Lens
Growth tests whether demand assumptions are supported by customer behaviour, approval paths and repeatable economics. Manufacturing tests whether product, process, material, capacity and quality evidence support the promise. Risk identifies which unverified assumption could create irreversible cash, inventory, customer or compliance exposure.
The three lenses should evaluate the same assumption. A growth case is not ready if manufacturing evidence is missing; a technically feasible plan is not commercially sound if the customer or margin assumption is weak. Cross-border leadership creates value when it makes these dependencies visible before one function commits on behalf of the others.
Management process
Start with one recurring decision such as quarterly forecast, new-product launch, capacity reservation or price approval. Review the latest version and underline every statement that depends on a future event, external party or unverified operating condition. These are assumptions, even when presented as numbers.
Select only the assumptions that could materially change customer commitments, economics or execution. Assign owners, evidence, review dates and default actions. Review them in the existing operating meeting: close confirmed items, reject failed ones and escalate only those outside agreed authority.
Track assumption age, repeated extensions, decisions made before evidence and changes caused by version mismatch. Each month, identify which assumption repeatedly appears across customers or projects; that pattern may reveal a capability gap, weak data source or unclear enterprise rule.
Leadership implication
Alignment is not agreement with the latest slide. It is a shared understanding of what is known, what remains assumed, which evidence will decide and what happens if evidence does not arrive.
A disciplined assumption register gives Vietnam room to operate within clear boundaries and gives headquarters visibility into the few uncertainties that can alter enterprise outcomes. The result is not more reporting. It is fewer commitments built on different meanings, faster correction when facts change and a cross-border operating model that can learn without losing control.