Encoding Strategic Intent: Why Communication Gaps Are an Ops Problem

By: Nhi Hong

They understood the words. They didn't understand the decision rights, the expected output, or the definition of "done."

This is the sentence most foreign founders in Vietnam eventually arrive at, usually after a project goes sideways, a deadline gets missed, or a task comes back completed in a way that bears no resemblance to what was originally asked.

The instinct is to blame the language gap. To invest in better translation, slower communication, more follow-up.

That's not wrong. But it's incomplete and in most cases, it's not the root cause.

The real problem is structural. Strategic intent is getting lost not in translation, but in the absence of explicit process, defined ownership, and measurable output standards.

Fix the structure, and most of the communication gap disappears, regardless of what language the conversation happens in.

1) The Nod Problem

Anyone who has managed a team in Vietnam for more than a few months knows this dynamic.

You explain a task clearly. The team member nods, confirms understanding, and moves forward. Two days later, what comes back is either incomplete, subtly off-brief, or in the more frustrating cases, technically correct but entirely missing the point.

The default interpretation: they didn't understand, didn't ask for clarification, or didn't speak up when they should have.

There's some truth to that. But it's not the full picture.

What's more often happening: the team member understood the task as described, but lacked the context to execute the intent behind it.

They knew what to do. They didn't know:

• What outcome you were trying to produce

• What "good" looks like versus "acceptable" versus "this needs to go back"

• What they were authorized to decide independently along the way

• At what point they should escalate versus push forward

Without those four elements encoded somewhere in a process document, a brief, a defined standard, you haven't given someone a task. You've given them a starting point and asked them to improvise the rest.

The nod isn't dishonest. It's the rational response of someone who doesn't have the information they need, in a cultural context where expressing uncertainty upward carries social risk.

2) This Is Not a Language Problem

It's worth being direct about this, because the language explanation is both intuitive and widely believed.

Yes, operating in a second language introduces friction. Yes, nuance gets lost. Yes, idiomatic phrasing can be confusing.

But consider: the same execution gaps appear in organizations where the founder and the senior team all share a first language. The same misalignment occurs between founders and expat managers. The same drift happens when strategic priorities are communicated verbally but never encoded into operational structure.

Language is a surface layer. The structural problem runs deeper.

If your team consistently executes the task but misses the intent, the question to ask is NOT "how do I communicate more clearly?",  it's "have I encoded the intent into the process itself?"

Verbal clarity is a fragile system. It depends on memory, consistency of delivery, the listener's interpretive frame, and the social dynamics in the room at a given moment. It degrades over time, across team members, and under pressure.

Structural clarity is durable. It lives in a document, a brief, a defined standard, something that exists independently of any single conversation.

The goal isn't to communicate better. It's to communicate less by encoding more.

3) The 3 Layers Where Strategic Intent Gets Lost

Between a founder's strategic intent and a team member's executed output, there are three distinct layers where meaning can break down. Most organizations focus only on the third.

Free download: HERE

Layer 1- Vision: What Are We Trying to Achieve, and Why?

This is the strategic context. Not just "complete this report" but "this report informs a decision about whether to expand to Hanoi, so the accuracy of the cost assumptions matters more than the visual presentation."

When vision is absent from a task brief, the team optimizes for what they can measure, completion, not quality. Delivery, not impact.

Most founders assume the strategic context is obvious. It rarely is, especially for team members who don't have visibility into the board meeting, the investor conversation, or the competitive pressure that's driving the urgency.

What encoding looks like: A single sentence at the top of any significant task brief that states the decision or outcome this work feeds into. Not a paragraph. One sentence.

Layer 2 - Rules: How Do We Make Decisions Along the Way?

This is the operating principles layer such as the standards, constraints, and decision criteria that govern how work gets done, not just what gets done.

When rules aren't defined, the team applies their own judgment, based on their experience, their cultural defaults, and their interpretation of what you probably want. Sometimes that's fine. Often it produces output that is technically acceptable but structurally wrong.

Examples of undefined rules that create problems:

• When something is unclear, do we ask or proceed with best judgment?

• When a deadline is at risk, do we flag early or deliver something incomplete on time?

• When a vendor quotes above budget, do we negotiate, escalate, or reject?

These aren't exotic edge cases. They're the daily micro-decisions that determine whether execution matches intent.

What encoding looks like: A set of defined operating principles from 5 to 10 short statements that govern how decisions get made within a process. Not rules for every scenario. Principles that cover the most common decision points.

Layer 3 :Tasks: What Specifically Needs to Happen?

This is where most organizations focus all their attention: the specific steps, actions, and deliverables.

Task-level clarity is necessary but insufficient. A team can execute every task correctly and still produce an outcome that misses the strategic intent, because Layers 1 and 2 were never defined.

What encoding looks like: A documented process with specific steps, named owners, defined inputs, and measurable outputs, including an explicit standard for what "complete" means.

4) SOP Design That Works Across Language Gaps

Standard Operating Procedures have a poor reputation in SME environments, usually because most SOPs are written for compliance rather than execution.

A compliance SOP documents what happened. An execution SOP enables consistent output.

The difference is in the design. Specifically, a useful SOP for a cross-cultural, multilingual environment has five elements and the sequence matters:

Free download: HERE

1. Purpose 

One sentence: why does this process exist? What outcome does it produce, and for whom?

This is Layer 1 embedded directly into the SOP. Every person executing the process can see the intent, not just the steps.

2. Trigger 

What initiates this process? A specific event, request, or threshold, not "when needed."

Ambiguous triggers are a primary source of inconsistent execution. "When the report is ready" is not a trigger. "When the monthly revenue report is finalized and reviewed by the Finance Manager by the 5th of each month" is a trigger.

3. Steps with Named Owners 

Sequential steps, numbered, each with a named role (not person) as owner. Avoid passive voice. "Finance Manager reviews and approves" rather than "report is reviewed."

4. Decision Points 

The most commonly skipped element. At every point in the process where judgment is required, document the decision rule explicitly: if this condition, then this action; if that condition, escalate to [role].

This is Layer 2 embedded into the process. It removes the need for every team member to independently re-derive the correct response to common scenarios.

5. Output Standard 

What does "done" look like? What is the specific, verifiable standard that must be met before this output moves to the next step or person?

Vague output standards ("completed to a high standard") produce vague execution. Specific standards ("report contains all five sections, figures reconcile to source data, reviewed by the Finance Manager before distribution") produce consistent execution.

5) The Structural Fix: Three Actions to Take This Week

Redesigning communication across an organization is a multi-month project. But there are three high-leverage actions you can take in the next five working days that will produce visible results.

Action 1: Identify your three most frequently miscommunicated processes.

Not the most important processes. The ones that most consistently produce output that doesn't match your intent. These are your starting points, not because they're strategically critical, but because the gap is currently visible and measurable.

Action 2: For each one, define the output standard before rewriting the process.

What does "done correctly" look like, specifically? Write it down. One paragraph. Share it with the person who owns the process and ask them to react. The gaps in their understanding will surface immediately, and you'll learn more in ten minutes than in ten follow-up conversations.

Action 3: Add a "purpose" line to your next five task assignments.

Before you brief any significant task this week, add one sentence at the top: "This feeds into [decision/outcome]." That's it. Measure whether the output is more aligned with your intent than it would have been otherwise.

These aren't permanent fixes. They're diagnostic tools and they'll tell you where the structural investment needs to go.

6) The Underlying Principle

The way to reduce communication friction isn't to communicate more. It's to build structures that carry the meaning you'd otherwise have to deliver verbally, repeatedly, in every conversation.

When intent is encoded into the process, it doesn't depend on a good brief. When standards are explicit, they don't depend on the founder being available to define "good" at the moment. When decision rules are documented, team members stop waiting for permission they were never told they needed to ask for.

This is what it means to treat communication as an operational design problem rather than a people problem.

The team isn't failing to understand. The system isn't giving them enough to work with.

7) What This Connects To

In the previous article “System-Led Execution: A Practical Definition for FDI SMEs”, we defined the three components of system-led execution: process clarity, role clarity, and governance rhythm.

Communication breakdown is almost always a symptom of gaps in the first two. When processes don't encode intent, and when roles don't carry explicit decision rights, verbal communication becomes the load-bearing structure and it's not built for that.

In the next article, we'll look at how this structural approach to communication applies specifically when localizing an operating model for the Vietnam context and which elements of your global playbook need to be redesigned, not just translated.

>> Download the 3-Layer Communication SOP Template

A fill-in framework structured around the Vision >> Rules >>Tasks model. Designed for cross-cultural operating environments: language-light, visually structured, and built around output standards rather than activity descriptions.

Download the SOP Template >> HERE

----

OPS FOR SCALE by SOSP Consulting Group

Operational architecture for foreign founders building businesses in Vietnam. 

Previous: System-Led Execution

Next: Operating Model Localization