Handbag Maison Communication: Best Practices for Brands Working Across Time Zones

Question One: Why Does Communication Break When Both Sides Are Trying?

It breaks because decisions are discussed in several places and recorded in none. A choice confirmed by message on Monday, amended by call on Wednesday and assumed by everybody on Friday ends the week with three versions and no record of which one the bench is following.

Neither side is at fault in that story. Both were responsive, both were helpful, and both were answering in the channel where the question happened to arrive. The failure is structural rather than personal: without a single place where a decision becomes official, every helpful reply creates another candidate version.

The remedy is to separate discussion from decision. Discussion can happen anywhere, in any channel, at any length. A decision exists only once it is written into the specification or the decision log with a version number and a date, and until then it is a proposal.

Question Two: What Is the Single Document That Should Carry Everything?

The technical pack carries the specification and the decision log carries everything else, and between them they hold the whole programme. Any decision not in one of those two documents has not been made, however clearly it was discussed.

That sounds rigid, and in practice it is liberating, because it settles arguments that would otherwise consume days. When a question arises about whether a gusset depth was changed, the answer is in the pack at a version number rather than in somebody's recollection of a call.

• The pack holds geometry, materials, hardware, construction and tolerances, under a version number.
• The decision log holds every open question with an owner, a due date and the recorded answer.
• A change moves from discussion to decision when the pack version is bumped and the change is noted.
• The retained reference piece is the physical counterpart: what the pack describes, the reference shows.
• Everything else, including email and messaging, is discussion and is not binding on the bench.

The fourth item is worth restating because it resolves the most common dispute of all. Colour, finish and hand feel are argued about in words and settled by a retained reference held under standard lighting, which is why that piece is signed at the spec freeze.

Question Three: Who Should You Actually Be Talking To?

One named person on each side, copied rather than bypassed, with a named deputy for when they are unavailable. Communication routed through departments is communication owned by nobody, and it settles into silence without anyone deciding to ignore it.

The named person on the programme side should be able to answer without asking permission, which is a different requirement from being senior. A contact who has to consult before every reply turns a two-hour overlap into a two-day round trip.

The third card is the discipline most programmes lose. It is helpful to bring a hardware specialist into a lock discussion and unhelpful to leave them on every subsequent message, because each additional correspondent creates another place where a version can quietly appear.

Question Four: How Fast Should Each Kind of Message Be Answered?

Different messages deserve different speeds, and agreeing the three tiers in advance removes most of the irritation on both sides. Acknowledgement within the working day, a substantive answer within 24 hours, and closure of an item within 72 hours of it opening.

Acknowledgement is the underrated row. An answer of not yet, sent within hours, tells the other side the item is alive. Silence tells them nothing, and it produces the duplicate chasing that makes both sides feel the other is unresponsive.

The last row matters because a question unanswered for three days is rarely waiting for information. It is usually waiting for somebody to make a decision they would rather defer, and re-pricing it as a scope change forces the conversation that chasing never would.

Question Five: How Do You Disagree Without Damaging the Run?

Disagree about the measurement rather than about the piece. Almost every dispute on a programme resolves faster once it is restated as a number against a reference, because numbers can be checked and impressions cannot be reconciled at all.

The practical habit is to restate the disagreement in one line before answering it. A strap described as sitting wrong becomes a strap drop measuring 6 mm outside tolerance against the retained reference, and the second version has an obvious resolution while the first has an argument.

1. Restate the disagreement as a measurement with a tolerance, or as a comparison against the retained reference.
2. Agree what the reference is before discussing the deviation, since most disputes hide a disagreement about the standard.
3. Separate the commercial question from the technical one, and settle the technical one first.
4. Record the resolution in the pack or the log within 24 hours, with the version number bumped.
5. Escalate to a call at the sixth message, because by then the thread is carrying more ambiguity than it is resolving.

The fifth item is the most useful rule in this article. A thread that has run six messages without resolution is not failing for lack of effort; it is failing because text is the wrong medium for that particular disagreement, and a fifteen-minute call settles it.

Question Six: What Does Good Communication Look Like at Handover?

At handover, communication becomes documentation: the inspection result, the closed correction list, the reconciled documents and the retained reference piece, all signed and stored together. What was said during the programme matters far less at that point than what was written.

Inspection result

AQL 2.5 under ISO 2859-1, recorded against the run rather than summarised

Correction list

Every item raised during sampling and bulk, closed and confirmed in writing

Retained reference

A signed piece held under standard lighting for the re-order

Glossary

Around 40 shared terms, so a word means the same thing on both sides

Version history

Every pack revision from 1.0 to freeze, retrievable rather than overwritten

Contact record

The two named individuals and their deputies, for the re-order

Document pack

Packing list, commercial documents, test reports and the inspection result

The glossary is the item that sounds trivial and prevents the most damage. Around forty shared terms covering edges, seams, panels, finishes and hardware mean that a word like skiving or burnishing describes the same operation on both sides of the exchange.

The Formats That Work, and the Ones That Do Not

Three formats carry almost all productive communication on a programme: a marked-up drawing, a photograph taken from a fixed angle, and a one-line decision. Three formats carry almost all the unproductive kind: a long paragraph, a voice note, and a forward of a previous thread.

• A marked-up drawing with the change circled and the version number written on it, returned within 24 hours.
• A photograph taken from one of three fixed angles, so two photographs taken a fortnight apart can be compared.
• A one-line decision stating what was decided, who decided it and which document it now lives in.
• Not a paragraph describing a defect in prose, which produces a different reading on each side.
• Not a voice note, which cannot be searched, quoted or attached to a specification.
• Not a forwarded thread, which carries every previous ambiguity along with it.

The fixed-angle rule deserves emphasis. A bench walk-through of six to eight photographs taken from three agreed angles turns into a comparable record across the whole programme, while photographs taken wherever the photographer happened to stand do not.

Time Zones, Language and the Two-Hour Overlap

Agree a fixed two-hour daily overlap and protect it. Two hours of real-time conversation each day removes more delay than any amount of asynchronous messaging, because most programme questions are settled in minutes once both sides are awake at once.

The third item is what makes the window efficient rather than merely pleasant. A list of six questions sent the previous evening turns two hours into thirty minutes of answers and ninety minutes of next steps, which is a different outcome from two hours spent catching up.

Five Templates Worth Keeping

Five message forms cover most of what a programme requires, and having them written in advance is what keeps a decision from turning into a discussion. Each is short enough to be read and specific enough to be acted on without a follow-up question.

1. The decision: what was decided, who decided it, which document it now lives in, effective from which version.
2. The correction: the measurement, the tolerance it fell outside, the reference it was measured against, and the date expected.
3. The approval: what is being approved, the version number, and the explicit statement that it is approved.
4. The block: what is waiting, on whom, since when, and what it is delaying on the critical path.
5. The close: what was corrected, how it was verified, and confirmation that the item is closed.

The fourth template is the one programmes avoid using, and it is the one that would save them the most time. Naming a block explicitly, with the number of days it has been waiting, converts a silent delay into an item somebody has to answer.

The second template deserves a note on tone. A correction written as a measurement is not a complaint, and houses receiving them this way respond faster, because the message tells them exactly what to change rather than asking them to interpret dissatisfaction.

When Communication Becomes the Problem Itself

Communication has become the problem when the volume of messages rises while the number of closed decisions falls. That pattern means the programme is discussing rather than deciding, and adding more messages will make it worse rather than better.

The corrective is unglamorous: stop the thread, hold the call, write the outcome into the pack or the log within 24 hours, and bump the version. Programmes that follow that loop consistently spend less time communicating and reach decisions sooner than those that do not.

Our programme works to MOQ 500 pcs per style and colourway, with sampling at 6-10 working days and bulk at 35-50 days on FOB Xiamen terms, inspected to AQL 2.5 under ISO 2859-1. It runs across 7 production lines with about 200,000 pcs per month of capacity and export experience since 2014, delivered through our validated partner factory Quanzhou Yingming Bags, an SGS-validated site.

Frequently Asked Questions

People Also Ask