Skip to main content

UK–India collaboration

At RAPID speed, a bad hand-off costs a day of agent throughput. This playbook makes the two-geography model a strength (follow-the-sun) rather than a tax.

The rules​

  • Whole-feature ownership within one location — a squad owns a feature end-to-end. Fracture along product seams, never along process ones — never "UK designs, India codes". That hand-off is where the day gets lost.
  • The daily overlap window — reserved for the things that genuinely need synchronous time (decisions, unblocking, the CoP show-and-tell), not status.
  • Async-first defaults — the written artefact is the source of truth (see async comms); no one waits for a timezone to make progress.
  • Hand-off discipline — when work does cross, a hand-off note template and a "handoff-ready" checklist, so nothing is lost in translation.

Why fracture on product, not process​

Splitting a single feature across geographies by phase creates a hand-off mid-flow — exactly the drag RAPID removes elsewhere. Splitting by product means each location owns complete things and the overlap window is for collaboration, not for catching a baton. Follow-the-sun then becomes a real advantage: someone is always moving the work forward.

Standards referenced: Team Topologies (fracture planes).