28 January 20267 min read
Outsourced engagements rarely fail on skill. They fail on one of two management patterns, and both are avoidable once you can name them.
Failure mode one: the black box
Tickets go in, work comes out, and nobody talks. It feels efficient, that is the appeal, and it holds up for a few weeks, until something is delivered exactly as specified and completely wrong. The specification did not say what mattered, because the person writing it already knew and did not think to.
The fix is not more meetings. It is putting the reasoning into the ticket alongside the requirement: why this is being built, who uses it, what would make it a poor result. Three extra sentences per ticket eliminates most of this failure mode.
Failure mode two: the shadow team
The opposite pattern. The outsourced team is kept apart, a separate stand-up, a separate channel, a separate backlog, and gradually drifts, because they are working from a version of the plan that stopped being current three weeks ago.
The fix is structural: one backlog, one channel, one definition of done. If someone is doing the work, they should be in the room where the work is discussed. Separating them by contract type is how drift starts.
If you would not run your in-house team this way, it will not work better on someone you are paying by the hour.
Write more than feels necessary
Distributed teams run on written context, and the bar is higher than it is for co-located work. The useful discipline: any decision made in a call gets written down afterwards, in the place the work lives, by whoever made it. Not minutes, the decision and the reason for it.
This is worth doing even with a seven-hour overlap. Overlap means someone can ask; it does not mean the answer is preserved for the next person.
Review on a rhythm, not on anxiety
Agree in advance when you look at the work, end of sprint, twice a week, whatever fits, and then actually look at it then. Teams that skip reviews when things feel fine, and then review intensively when they feel worried, produce a pattern that reads as distrust and generates exactly the defensive reporting they were trying to avoid.
Give feedback like they are staying
The most common under-management pattern is not correcting things that would obviously be corrected in an employee, because it feels awkward with a contractor. It compounds quietly, and the person is usually relieved to hear it, having sensed something was off without being told what.