Measuring Time to Productivity for a Philippines Hire

Research findings

## Research question How can a buyer measure the time it takes a new Philippines-based hire to reach an agreed productivity standard without confusing speed with quality or hiding the cost of supervision? The unit is one new hire and one bounded task lane observed from the first day of live work to the first accepted independent sample. The method does not propose a universal number of weeks. It proposes a definition and an evidence trail that a second reviewer can reproduce.

## Define the standard before day one Productivity needs an observable definition. For a support lane, it might be a set of request types handled within the agreed quality and evidence standard, with no more than a stated review correction rate. For a reporting lane, it might be a weekly pack delivered on time with zero unresolved source conflicts. Write the definition, the sample size, and the acceptance owner before the hire starts. A standard invented after the first month will drift toward whatever the hire happens to be good at. It will also make comparison across hires meaningless.

## Choose checkpoints that match the learning curve A useful schedule has at least four checkpoints: orientation, supervised work, gated independence, and independent sample. The orientation checkpoint asks whether the hire can explain the lane and find the sources. The supervised checkpoint asks whether they can complete work with review. The gated checkpoint asks whether they can recognize a stop. The independent checkpoint asks whether a sample meets the standard without line-by-line correction. Each checkpoint needs a different evidence set. Do not use the same ticket-count threshold for all four.

## Separate quality from speed Record accuracy, evidence completeness, authority compliance, and customer clarity beside volume. A hire who reaches the volume target by skipping verification has not reached productivity. A hire who is accurate but slow may need tooling or process help rather than pressure. Use a small scorecard with four or five criteria and a clear minimum for each. Report the criteria separately. A single composite score hides the exact tradeoff the buyer needs to manage.

## Account for case mix New hires often receive easier work in the first weeks. That is a reasonable ramp, but it changes the meaning of the measure. Record the request mix at each checkpoint and compare the hire's sample with the lane's overall mix. If the hire has not yet handled difficult cases, the independent sample is not representative. Add a planned adverse case before declaring the ramp complete. Otherwise the first complex request becomes the real test, often without a reviewer present.

Discussion

## Include supervision cost Time to productivity is not only the hire's output. Record reviewer minutes, rework, clarification time, and the number of escalations caused by missing information. A hire who appears productive because a senior person silently repairs the work has not reduced the load. A hire who asks more questions early but needs less repair later may be the better outcome. Include the supervisor's time in the cost view, even if it is not billed to the client.

## Use a comparison that is fair If the buyer compares hires or providers, hold the lane, the tools, the sample rule, and the quality standard constant. Compare the checkpoint evidence, not only the final date. A provider that starts with a simpler queue will look faster than one that starts with complex exceptions. Report the case mix and the review intensity. If the samples are too different, describe the difference instead of adjusting it away with a ratio.

## Protect the evidence Keep the checkpoint records, the reviewed samples, the reviewer notes, and the correction log. Remove unnecessary personal data before sharing the study outside the operating team. Use stable identifiers for cases. The record should show what the hire did, what the reviewer found, and what changed. It should not become a surveillance file. The purpose is to improve the ramp and the brief, not to rank people on a single month.

Implications and limits

## Limitations A small number of hires cannot support a general claim about a labor market or a provider. The learning curve depends on the task, the tools, the reviewer, the language, and the quality of the written brief. A fast ramp in a narrow lane may not predict performance in a complex one. The method also cannot separate a hiring effect from a management effect without a stronger design. State these limits beside the result.

## Decision use Use the method to answer a narrow question: is this hire ready for the next scope, and what evidence supports that? If the answer is yes, expand one lane at a time. If the answer is no, name the missing evidence and the repair. A date on a calendar is not a productivity standard. A reviewed sample is.

## Reporting Report the hire, the lane, the checkpoints, the sample sizes, the quality criteria, the supervision minutes, and the case mix. Show the first independent sample beside the standard that was agreed before day one. If the ramp is incomplete, state which evidence is missing and when it will be collected. Keep the report short enough for an operating review and detailed enough for a second reviewer to reproduce the judgment.