Coordinate Across Regions Without Friction

Proof required

Submit a regional coordination map (diagram or table) showing decision flows, resource allocation pathways, and escalation channels between central and at least two regional teams, plus a written analysis of at least 500 words identifying three specific breakdown points with their operational consequences. ADVERSARIAL VERIFICATION: a named regional director, head of regional operations, or multi-site operations consultant (5+ years in multi-location management) must read the map and analysis and provide written confirmation that the breakdown points are genuine coordination failures, not aspirational improvements.

What gets checked

• Regional coordination map covering decision flows, resource allocation, and escalation channels for ≥2 regions
• 500-word analysis with three breakdown points each with an operational consequence
• Written confirmation from a named regional/multi-site operations professional (5+ years) that the breakdown points are genuine

Common mistakes

• Mapping the formal coordination structure (org chart, reporting lines) rather than the actual coordination pattern — regional coordination failures are almost always invisible in formal documentation; they appear in what gets escalated, what gets ignored, and what gets decided at the wrong level
• Identifying breakdown points only from the central team's perspective — regional teams consistently have a different view of where coordination fails; the map must include at least some perspective from regional teams directly
• Describing coordination gaps as communication problems ('we need better communication') without identifying the specific mechanism that breaks — a breakdown point has a causal structure: who makes which decision with what information, and where the information or authority is missing

Resources

What a verifier looks for

• The coordination map must include regional team perspectives — ask how the submitter gathered information from regional teams (interviews, surveys, review of escalation logs)
• Each breakdown point must have a named operational consequence — 'regions feel unsupported' is a consequence; 'the south region's procurement requests require 3 escalation steps to reach budget authority, averaging 11 days' is an operational consequence
• The confirming reviewer must have multi-site management experience — a central operations manager who has never worked in or managed regional teams does not satisfy the requirement

Proof required

Submit a regional coordination improvement report covering: (1) two improvements implemented with their target breakdown points; (2) evidence of implementation in at least two regions (meeting records, updated delegation matrices, shared dashboards, or equivalent); (3) evidence of changed coordination patterns after ≥6 weeks — this may include: escalation frequency changes, decision cycle time changes, regional lead feedback, or reduced central team time spent on decisions that should be regional. ADVERSARIAL VERIFICATION: your named regional operations reviewer reads the improvement design before implementation and provides written feedback on whether the improvements address the coordination mechanism or only the communication symptom.

What gets checked

• Two improvements implemented with evidence in at least two regions
• Evidence of changed coordination patterns after ≥6 weeks — not just implementation evidence
• Reviewer pre-implementation feedback confirming the improvements target coordination mechanisms

Common mistakes

• Improving central team processes without changing what regional teams experience — if the improvement only changes how the central team works internally, it will not alter regional coordination
• Introducing a new coordination mechanism (weekly sync, shared dashboard) without defining how it changes who makes which decisions — coordination mechanisms only improve coordination if they change authority, information flow, or escalation pathways
• Gathering feedback only from central team members about whether regional coordination has improved — regional leads are the primary evidence source for whether coordination has changed

Resources

What a verifier looks for

• Evidence must come from at least two regions — improvement evidence only from the central team does not demonstrate regional coordination change
• Changed coordination patterns must be documented — ask the submitter to describe one specific coordination event that would have been handled differently under the old process
• Reviewer pre-implementation feedback is the core adversarial check — ask whether the improvements change authority, information flow, or escalation pathways, or only add another communication channel

Proof required

Submit your regional coordination improvement report and a record of the challenge session: names and professional roles of both panellists, date and duration (≥30 minutes), and notes on at least three challenges posed and your responses. A written statement from the primary regional operations reviewer (50+ words) confirming that the improvements have changed coordination patterns in at least two regions. ADVERSARIAL VERIFICATION RULE Level 2: live session required.

What gets checked

• Regional coordination improvement report: M1 mapping + M2 evidence + scaling recommendations
• Challenge session with ≥2 named multi-site operations panellists, duration ≥30 minutes, ≥3 challenges documented
• Written statement from primary reviewer (50+ words) confirming changed coordination patterns in ≥2 regions

Common mistakes

• Presenting coordination improvements without evidence from regional team members — central team reports of improved coordination are not the same as regional team confirmation that coordination has changed
• Not addressing scalability in the recommendations — a good panel will ask whether the improvements depend on specific individuals or relationships that would not transfer to additional regions
• Choosing panellists without multi-site management experience — a panel of central team leads cannot evaluate whether regional coordination has genuinely changed

Resources

What a verifier looks for

• Both panellists must have direct multi-site or regional management experience — a general operations role without cross-location responsibility does not satisfy the requirement
• ADVERSARIAL VERIFICATION RULE Level 2 requires a live synchronous session of ≥30 minutes
• The reviewer statement must confirm changed coordination patterns in ≥2 regions specifically — a statement about the quality of the presentation does not satisfy this requirement