Techbanq

Engagement models · working practices

Distance forgives almost everything except unwritten decisions

A co-located team corrects misunderstandings by accident, at the coffee machine; a distributed one only corrects what is written down. The playbook is short: decisions live in documents, the overlap hours are spent deciding rather than reporting, the weekly demo shows working software, and escalation is a normal lane rather than an alarm.

Two engineers reviewing code together on one screen
  1. 01

    Written for

    CTO, Head of Digital, COO

  2. 02

    Decision

    Establish working communication practices with an offshore engineering team

  3. 03

    Languages

    EN · AR

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The mechanism

How a decision crosses two cities without a meeting

The path most decisions should take. The overlap window appears once, near the end — as the place decisions get made, not the place work gets described.

A flow of four steps — a written proposal, asynchronous review, a short decision call in the overlap window, and the decision recorded in a log — with a branch for genuine emergencies that still get written down afterwards.

  1. 01

    A written proposal

    Whoever wants the decision writes the context, the options and a recommendation — one page, in the shared space, hours before anyone needs to be awake together.

  2. 02

    Asynchronous review

    Readers comment in their own working hours. Most disagreements dissolve here, in writing, where they are cheapest.

  3. 03

    Decision in the overlap window

    What survives review gets fifteen live minutes, with the options already understood. The call decides; it does not inform.

  4. 04

    Recorded where work happens

    The decision and its reasoning land in the decision log the same day, so next quarter's "why is it built this way" has an answer with a date on it.

Always available

The genuinely urgent exception

A production incident or a hard external deadline skips the queue and goes straight to a call — and the decision is still written down afterwards. Urgency excuses the sequence, never the record.

The principle

Write first, because the coffee machine is two thousand kilometres long

The written-first principle is not a preference for documents over people; it is an acknowledgement of what distance removes. In one office, a half-understood requirement gets corrected within hours by accident — someone overhears, someone asks. Across two cities and two working days, the same misunderstanding compounds silently for a week and surfaces as the wrong feature, politely built. Writing is how a distributed team manufactures the corrections that co-location provides free: a requirement that must be written down gets examined by its own author first, and a decision in a log can be challenged by someone who was asleep when it was made.

The discipline has a second dividend that co-located teams never collect: the archive. A year of written proposals, decisions and demo notes is an induction course for every engineer who joins later, and an audit trail for every "who agreed to this" that procurement or a board ever asks. Teams that run on calls own none of that — their history left the company in the heads of whoever attended.

The rhythm

A week built around one demo and two quiet mornings

Riyadh and Lahore share most of the working day — the overlap is generous by global standards, which makes it easy to waste. The rhythm below spends it deliberately.

01

Daily, in writing

Each engineer posts progress, plans and blockers before the shared hours begin.

Blockers surface at the start of the overlap, not at its end — the day's live time goes to unblocking, not to discovering.

  • Tracker
  • Chat
02

The overlap window

The hours both cities are at their desks, minus Fridays and around prayer times.

Reserved for what needs simultaneity — decisions, design arguments, pairing. Status has no seat in this window; it already travelled in writing.

  • Calendar
  • Video
03

The weekly demo

The team shows working software — not slides, not a burndown — to the people who asked for it.

The heartbeat of the relationship. A feature that cannot be demonstrated is not done, and a misread requirement is caught seven days old instead of ninety.

  • Staging
  • Demo notes
04

The monthly step back

Both sides review the working relationship itself — what the rhythm is catching, what it is missing.

The practices get maintained like the code. A retrospective that changes one working agreement a month keeps the playbook alive rather than laminated.

  • Retro board

Language

Arabic in the stakeholder room, English in the repository

In a GCC–Pakistan engagement the language question is real and best handled by naming the boundary rather than pretending it away. Engineering runs in English — code, reviews, tickets, the decision log — because that is the working language of the discipline on both sides. The business runs wherever your stakeholders are comfortable, and in Saudi Arabia that is often Arabic: requirements arrive in it, executives review in it, and the product itself must speak it fluently.

The failure mode is the unmanaged crossing: an Arabic requirement paraphrased into English chat by whoever happened to be bilingual, losing a nuance nobody notices until the demo. The fix is ownership — a named person accountable for the crossing, requirements translated as documents rather than as conversation, and the demo run so Arabic-speaking stakeholders judge the product in the language their customers will use. Handled this way, the boundary is a checkpoint where quality is verified, not a wall where meaning leaks.

Our role

This playbook is how we already work, offered in writing

Offshore delivery is our business, so recommending these practices serves us — they are also the practices we depend on, because a communication failure costs us the same relationship it costs you.

  1. 01

    The artefacts, from day one

    Decision log, daily written updates and demo notes exist from the first week, in your tools — so the record accumulates where you can read it without asking.

  2. 02

    A calendar built around yours

    The overlap window, the demo slot and the escalation availability are set around the Gulf working week — Sunday starts, Friday off, and the afternoon hours both sides genuinely share.

  3. 03

    An escalation lane with names in it

    Two named people — one on each side — with the authority to resolve what the working level cannot, and a shared understanding that using the lane is professionalism, not accusation.

Which stakeholders attend the demo, and which language each meeting runs in, are your calls; our part is a rhythm that makes distance boring and a record that outlives everyone's memory.

Common questions

What buyers ask

Does a written-first team still hold meetings?+

Yes — fewer, shorter, and different in kind. Written-first does not mean silent; it means the reading and the arguing happen before the call, so the call itself does the one thing writing cannot: resolve a live disagreement, make a judgement call, build the trust that comes from faces and voices. A decision meeting on a proposal everyone has read takes fifteen minutes; the same meeting where the proposal is presented aloud takes an hour and decides less. The test of the practice is what your calendar contains: if standing meetings exist whose content could have been a document, the principle is being professed rather than practised.

How should we design the overlap window with a team in Pakistan?+

Start from what must be simultaneous, then protect exactly that. Pakistan sits two hours ahead of Saudi Arabia, so most of the working day is naturally shared — the design problem is not finding hours but deciding what deserves them. Put the decision call, the demo and pairing inside the window; keep status, reporting and anything readable outside it. Respect the asymmetries deliberately: the Gulf week starts Sunday while Pakistan's starts Monday, Friday is sacred on both sides in different ways, and Ramadan reshapes everyone's day. A window designed once and revisited each quarter beats a standing nine-o'clock call that survives because nobody owns deleting it.

Can an offshore team work with Arabic-speaking stakeholders and documents?+

Yes, if the crossing between languages is owned rather than improvised. The workable pattern gives each language its domain — engineering artefacts in English, stakeholder-facing sessions and documents in Arabic where that is the audience's language — and makes one named person accountable for what crosses: requirements translated as documents with room for questions, demo sessions run so Arabic-speaking reviewers judge the product in Arabic, and the product's own Arabic treated as an engineering requirement with review, not a last-minute translation pass. What to refuse is the accidental version, where whoever happens to be bilingual paraphrases requirements in chat. That works until the first nuance it silently drops turns out to have been the point.

Design the rhythm with us

A one-page working agreement — decision log, overlap window, demo slot and escalation lane — drafted for your team before an engagement starts.

Start the conversation