Helping offshore teams own their work

The domed granite legislature building in Bangalore under a hazy sky, with a bronze statue in front

The most common way an offshore engineering team gets set up is as capacity. Requirements are written at headquarters, turned into tickets, and sent over. It never produces a team that owns anything, and a year in, the organization wonders why the remote team does not push back or catch the problems a local team would have caught.

I have spent years on both sides of that arrangement, and I think ownership is given, not grown, in specific ways that most organizations skip.

Give them a whole problem

A team cannot own a slice. If the remote team builds the screens and the home team builds the services and a third team writes the requirements, nobody owns the feature, and the remote team least of all.

So give the team a whole thing, a product area, a service, a customer workflow, with the front end, the back end, and the requirements inside one team. It is the only shape where the team can see whether what it built worked.

Give them the authority

The second thing is decision rights. If every design choice has to be approved at headquarters, the team learns to wait, and waiting across time zones costs a day each time.

The authority has to be explicit and written down, which decisions are the team's, which need a conversation, and which are someone else's, because the default in any organization is that decisions flow to the center.

Give them the people

The third thing is direct access to whoever the work is for. Product managers, customers, the support team. If all of that is filtered through a liaison at headquarters, the remote team is building from a description of a need rather than the need.

This one gets resisted, on the grounds that stakeholders are busy or the time zones are hard. I think it is the highest-value change an organization can make.

What gets in the way

The obstacle is rarely the remote team. It is the home office, which has to give up control it is used to, trust decisions it did not make, and accept that a team it sees on video will sometimes do things differently. Each of those feels like a loss to someone, and each is the price of a team that owns something.

A team that has been handed tickets for two years does not become an owner the week the arrangement changes. It takes a few cycles of making a real decision and finding that it stood, and of being wrong and not being punished, before the behavior changes.

Why it is worth it

A capacity team produces code at the rate it is fed tickets. An owning team produces outcomes, catches problems before they ship, and gets better every year. The second kind is the reason to build a remote center in the first place. The first kind is what most organizations settle for, and then blame on distance.

Photo source: https://photos.robertstowe.com/bengaluru