“Decision-Maker” Can Be a Misleading Phrase

The phrase suggests one person and one moment: find the right individual, get a yes, and the decision is complete.

Real organizations are often more complicated.

One person may open the door. Another may own the customer relationship. Production may control capacity. Finance may decide whether payment terms are acceptable. A technical team may approve a specification. Senior management may decide whether an exception is worth the risk.

These roles can overlap. They can also be distributed.

The practical mistake is to assume the person who speaks most actively must also control every resource needed to make the project real.

Ask What Decision Is Actually Being Made

Before asking who decides, define the decision.

Are you asking whether the company wants to continue the conversation? Whether it will reserve production capacity? Whether it will accept a lower MOQ? Whether it will change payment terms? Whether it will approve a technical change? Whether it will take contractual responsibility for a new obligation?

Different decisions can have different owners.

Authority is specific to the consequence being committed.

This is why a title alone may be insufficient. The useful question is what the person can actually cause the organization to do.

Map the Decision Path

Access

Who can get the conversation into the organization and bring the right people together?

Support

Who understands the opportunity and is willing to advocate for it internally?

Operational control

Who controls the capacity, technical work, schedule, commercial term, or execution step the project depends on?

Risk ownership

Who carries responsibility if the decision creates cost, delay, exposure, or another consequence?

The map will look different in a founder-led supplier, a larger manufacturer, a trading company, an SOE, or a multinational. HCBAW's framework is not a claim that one hierarchy describes them all.

Do Not Confuse Visibility With Authority

The most visible contact can still be extremely valuable.

A sales manager may explain the opportunity, coordinate samples, translate technical issues, and carry messages to senior management. A founder may appear only late in the process. A technical lead may quietly determine whether the proposal is feasible.

The point is not to bypass the person you are dealing with.

It is to understand which parts of the path they control and which parts require other people.

The U.S. Commercial Service currently advises foreign firms to evaluate potential Chinese partners carefully and understand relevant relationships, specializations, and risks before larger commitments. Its China market-entry guidance is consistent with the need to understand the organization behind the visible contact.

Look for Evidence of Authority in the Process

You do not need an internal org chart to learn where authority sits.

Watch what changes when a person enters the conversation.

Can they approve an exception? Can they allocate capacity? Can they resolve a conflict between departments? Can they accept a commercial downside? Can they set the next step in motion without the process resetting?

Authority becomes visible through consequences.

Title≠Authority→Observe what the person can commit

Why “Find the Boss” Is the Wrong Lesson

Theme 4 is not a power-navigation guide.

The goal is not to skip your working contact, hunt for the founder, or assume the most senior person should be brought into every conversation.

That can damage a useful relationship and still fail to solve the decision problem.

A better move is to clarify the path respectfully: what needs approval, which function owns it, what information is missing, and what would allow the project to move.

Sometimes the answer will be a senior executive. Sometimes it will be the person controlling production, finance, technical risk, or another specific dependency.

Decision Authority and Commitment Are Related—but Not Identical

Finding the relevant authority does not automatically create commitment.

A person can have the power to approve a deal and still decide not to allocate the resource. Conversely, a supportive contact can be deeply committed to helping but lack final authority.

That is why HCBAW separates two questions:

Who can decide?
and
What has the organization actually committed?

The first is an authority question. The second is a commitment question.

Once the approval path is visible, the next question is whether the organization has actually moved from support into commitment. Continue with the commitment judgment →

One Question Before You Treat a “Yes” as a Decision

Ask:

What resource, responsibility, or risk can this person actually commit?

If the answer is unclear, the next step is not necessarily escalation. It is clarification of the decision path.

Related HCBAW Insights

How to Tell If a Chinese Business Partner Is Really Committed

Continue with another HCBAW judgment page.

How to Read China Market Signals Before You Commit

Continue with another HCBAW judgment page.

How to Validate Demand in China Before You Scale

Continue with another HCBAW judgment page.