A Working Agreement for Saudi–Jordan Teams: Overlap, Decisions, Escalation and Knowledge

In a distributed team, time is often lost to waiting rather than to distance. Write a one-page working agreement that covers four things: the hours both sides are reachable, based on real calendars; how decisions are made and recorded; how blockers escalate within agreed time limits; and where knowledge lives. Review it after the first month and whenever the team changes.

Nextwo ·

This guide is for engineering leaders, product owners and team leads at Saudi companies that run, or plan, a development team split between Saudi Arabia and Jordan.

Picture three moments in a distributed team. A question sits in a chat thread overnight. A design decision is made in a meeting that half the team did not attend. A production issue is escalated to someone who is on leave. None of this is about skill, and none of it is solved by more meetings. What helps is agreeing, in writing, how the team works across two locations.

The short answer: put four rules on one page before the waiting starts: shared hours taken from real calendars, decision owners and a decision log, an escalation path with time limits, and a home for every kind of knowledge. Review the page after the first month and whenever the team changes.

Part 1: Overlap

Do not assume the shared hours; write them down. For each location, record:

  • Working days and hours: the team's actual schedule, including any agreed flexibility.
  • Calendar differences: public holidays and seasonal changes to working hours on each side, checked every year against each side's official calendar.
  • Shared window: the hours when both sides are reliably available.
  • What the window is for: decisions, pairing, short daily stand-ups and quick clarifications.
  • What happens outside it: written questions, reviews and work that does not need an immediate answer.
  • Response expectations by channel: for example, how quickly chat messages, review requests and incident alerts are answered during the shared window, as set by the team.

GitLab's handbook describes that company's own practice: it starts from asynchronous communication and asks that the conclusions of offline conversations be written down. It also treats a synchronous conversation as useful when back-and-forth is blocked. It is one company's approach, not a universal rule, but it is a useful model: default to writing, switch to a call when the thread stops moving, and write down what the call decided.

Part 2: Decisions

Delays often start when no one is sure who can decide. List the decision types your team meets and fill in the table.

Decision typeWho decidesWho must be consultedWhere it is recordedObjection window
Product priorityProduct ownerTech leads on both sidesBacklogUntil the next planning session
Architecture or technical designTech leadEngineers affectedDecision log in the repositoryTwo working days
Release go or no-goRelease ownerQA and the on-call engineerRelease checklistBefore the release window
Scope change during a sprintProduct ownerTeam leadSprint notesSame day
Production accessSecurity or platform ownerTeam leadAccess logNot applicable
Adding someone to the teamHiring decision ownerTeam leadHiring recordNot applicable

The entries are examples; set your own owners and windows. A simple decision log entry needs five fields: date, decision, owner, a link to the context and the alternatives considered.

Part 3: Escalation

An escalation path works when everyone knows the levels, the time limits and which kind of problem goes where.

  1. Level 1: the two team leads, one in each location, try to resolve the blocker within an agreed time.
  2. Level 2: if it is unresolved, it moves to the engineering manager or product owner who owns the decision.
  3. Level 3: if it is still unresolved, it moves to your executive sponsor.

Separate the kinds of problem. Delivery and technical blockers follow the path above. People, HR and workplace matters follow a different path: in Nextwo's dedicated team model, Nextwo employs the team and runs payroll, HR and workplace operations, so those matters go to Nextwo as the employer, while your technical leadership keeps direction and priorities. Write both paths into the agreement so no one has to guess.

Part 4: Knowledge

Knowledge that lives in one person's head or in a private chat becomes a risk the day that person is unavailable. Agree where each kind of information lives:

  • Code and configuration: your repositories, under your access control.
  • Decisions: the decision log, linked from the relevant tickets.
  • Procedures: runbooks for deployment, incidents and access requests.
  • Onboarding: a guide a new team member can follow without someone beside them.
  • Meeting outcomes: a short written summary in the team's channel the same day.

Keep confidential and customer information in access-controlled spaces that your organization approves. What another company does with its own information does not change that.

The one-page agreement

SectionWhat to write
Team and ownersNames, roles and locations of the team leads, product owner and decision owners
Shared hoursEach side's working days and hours, the shared window and the calendar differences for the year
Channels and response expectationsWhich channel is used for what, and the expected response times during shared hours
DecisionsThe decision table and the location of the decision log
EscalationLevels, time limits and the separate path for people, HR and workplace matters
KnowledgeWhere code, decisions, procedures, onboarding and meeting outcomes live
ReviewThe date of the first review and the triggers for the next one

A worked example (hypothetical)

A hypothetical company has a product owner and a tech lead in Riyadh and five engineers in Amman. In the first month, review requests wait a day or more, and the team reopens two design decisions because the Amman engineers were not in the meeting.

The team writes its agreement. It records its actual shared hours and the holiday differences for the year. Review requests now get a response within the shared window, and design decisions are proposed in writing with a two-day objection window before they are logged. Blockers go first to the two team leads, with an agreed time limit before they reach the product owner. After the first month, the team reviews the agreement and shortens the objection window for small decisions.

When to review the agreement

  • After the first month: adjust what did not work.
  • When the team changes: new members, a new lead or a new location.
  • When a blocker recurs: the same type of delay twice usually means a rule is missing.
  • When calendars change: at the start of each year and before seasonal schedule changes.

Next step

Draft the agreement in your next planning session with both team leads and the product owner, and set the date of the first review. If you are planning a dedicated team in Jordan, Nextwo's Jordan team page explains what Nextwo handles and what stays with you.

Frequently Asked Questions

Do we need specific tools to follow this agreement?

No. Use the tools your organization already approves. What matters is that everyone knows where to ask, where decisions are recorded and how to escalate.

How long should the shared window be?

Long enough for the decisions and quick questions your team meets every day. Start from both sides' actual calendars, try it for a few weeks and adjust it at the first review.