Which work should you offshore first? Run the 3C Test.

Every leadership team that decides to build an offshore capability faces the same first decision: where to start. The instinct is to start where the pain is loudest. The close that eats a week every month. The reporting nobody fully trusts. The vendor follow-ups a COO is somehow still handling personally. Pain is a good reason to act. It is a poor way to pick the first piece of work to hand off, because the loudest pain often sits on work that is not ready to leave the building.

There is a better way to choose, and it fits on an index card.

The first pick decides the program

The first stream of work you hand to an offshore seat carries more weight than any pick after it. A first seat that works earns the second. It proves to your team that the model holds, it builds the habit of defining work before handing it off, and it gives the operator in the seat a real chance to compound. A first seat placed on work that was never ready does the opposite. The operator struggles, the team concludes offshore does not work here, and the program stalls before it starts.

That is why the book's advice is to start deliberately small. Build one seat. Prove it. Add the next. The scope of that first pick is a design decision, and the 3C Test is how you make it.

The 3C Test: clear, common, constrained

The 3C Test is a three-question readiness check from chapter 4 of Operational Alpha, run before you choose the first stream of work for a new seat. Work that passes all three questions is ready to hand to an offshore team. Work that fails any one of them is not ready yet, and the test tells you why.

Clear: can you define “done”?

Can you define “done” in one paragraph and show a good example? That is the whole question. If you can, the work can be owned by someone outside your building. If you cannot, nobody can do the work reliably, however talented they are. A missing definition was never a talent problem. Work that lives in one person's head always feels clear to that person. The paragraph is how you find out whether it actually is.

Common: does it happen weekly?

Does the work happen weekly or more? Frequency matters because repetition is where compounding happens. Standards tighten, speed increases, the work becomes portable, and resilience rises. A monthly process gives an operator twelve repetitions a year, which is not enough to build any of that. A weekly one gives fifty.

Constrained: is there an obvious bottleneck?

Is the work truly stuck right now, in a way you can point to? The best first picks sit on a live constraint: work that waits, work that gets redone, work your most senior people absorb because the structure has nowhere else to put it. A constraint gives the first seat a result the whole team can see, and relief you can feel in a quarter buys the program its second seat.

The one-page version of this test lives in the Operational Alpha toolkit, a free set of the book's working tools, fillable on the page.

What passes, and what waits

The work that passes first is usually smaller and less glamorous than the work that hurts most. The book walks a leadership team through this exact exercise, and the results are the pattern we see everywhere. Vendor coordination that a senior operator is doing personally passes cleanly: purchase orders confirmed, lead times tracked, exceptions flagged, every day. The month-end close fails as a first pick, because monthly is too infrequent for a first play, even though the pain is real. Inside that close, AR follow-ups and close prep run weekly, and that slice passes. CRM cleanup happens every Monday and consumes senior time, but nobody has ever defined “clean.” Write the definition and it passes too.

That last pattern is worth sitting with. Most work that fails the 3C Test fails on Clear, and the fix is a paragraph, an example, and an afternoon. For the rest, the book's rule is simple: if your chosen stream fails the test, go one level narrower until it passes. A close that fails contains a reconciliation that passes. A sales operation that fails contains a weekly pipeline report that passes. The default scope that works for most middle-market companies is one workflow inside one stream. Enough scope to matter, tight enough to define and stabilize.

Work that passes the 3C Test is ready to hand off. Work that fails is telling you exactly what to fix first.

The first seat is the start of something bigger

A first seat that passes the 3C Test rarely stays a single seat. The definition habit spreads, the next stream of work is easier to pick because the team now knows what ready looks like, and the seats begin to add up to a small operating layer inside the company. One of the companies we work with, a $75M PE-backed operator, grew its embedded team to 10+ seats exactly this way. Each seat earned the next. Grown seat by seat, that layer is the Mini-GCC model.

Two decisions sit next to this one. Which operating model holds the seat is its own question, and we have compared embedded versus outsourced teams in depth. And the seat is only one of four parts of the interface that makes offshore teams work. The 3C Test covers the one part only you can do.

That split is where Kayana engagements begin. The Seat belongs to the client, because only you can say what the work is and what “done” means. The 3C Test is how we help you define it, at the start of every engagement, before anyone is placed. Then we run the rest of the interface around the seat: the cadence, the community, the stewardship. You run the work. We run the interface.

Quick answers

A first seat grows into the Mini-GCC model. The full design playbook, including where the test sits in it, is chapter 4 of the book. Operational Alpha →