When a team sits on the other side of the world, it's tempting to watch them more closely. Green status dots, time trackers, screenshots every ten minutes. It feels like control.
In practice, it measures the wrong thing and drives good people away. You can't see someone typing from half a world away, and you don't need to. You need to see what gets delivered, and how well.
Why activity metrics mislead
• Hours online reward being present, not being useful. A strong engineer may solve in two hours what takes someone else two days.
• Keystrokes and screenshots measure motion, and they signal distrust. Good engineers notice, and they leave.
• Lines of code or ticket counts are easy to game. Split one ticket into five, and "productivity" goes up fivefold.
The question isn't "are they busy?" It's "is the work getting done, and is it good?"
Measure outcomes instead
Pick a small set of measures that match the role, and look at trends over a month, not single days.
|
Measure |
What it tells you |
What to watch for |
|
Sprint commitments met |
Whether planning and delivery line up |
Missing most sprints, or always under-committing |
|
Cycle time (start to merged) |
How quickly work moves through |
Tickets sitting "in progress" for weeks |
|
Review rework |
Quality on first submission |
The same review comments coming up again and again |
|
Bugs found after release |
Quality that reaches users |
Recurring bugs in the same area |
|
Response to blockers |
Whether they raise problems early |
Issues surfacing only at the deadline |
|
Documentation and handoffs |
Whether others can build on their work |
Knowledge that lives in one person's head |
For non-engineering roles, swap in the equivalent: articles published and accuracy for a writer, turnaround and revision rounds for a designer, close-on-time and error rate for a bookkeeper.
Compare like with like
The fairest benchmark for an offshore engineer is your in-house team on the same kind of work. Track the same measures for everyone, in the same way. If you only measure the remote team, you'll find problems you'd overlook at home, and they'll feel it.
Run a monthly check-in, not a daily inspection
A 30-minute monthly conversation does more than daily monitoring. Cover four things:
1. Results: what shipped this month, against what was planned.
2. Quality: anything that came back, and why.
3. Blockers: what slowed them down, including things on your side.
4. Growth: one skill or area they want to take on next.
The third point matters. A slow month is often caused by unclear tickets, missing access or late reviews. Measuring the team without measuring the system around them gives you the wrong answer.
Red flags worth acting on early
• Missed commitments for two or more sprints in a row, with no clear reason
• Going quiet: fewer questions, shorter updates, skipping optional meetings
• The same quality issues after clear feedback
• Work only moving when someone chases it
Raise these privately and early. Most have a fixable cause: unclear priorities, a skills gap, or something going on outside work.
The scorecard checklist
• ☐ Three to five outcome measures agreed per role
• ☐ Same measures used for in-house and offshore team members
• ☐ Trends reviewed monthly, not day by day
• ☐ Blockers on your side tracked too
• ☐ A monthly check-in on the calendar
• ☐ No screenshot or keystroke tracking
Where we help
You own the technical side: priorities, reviews and the measures above. We handle the human side. For every seven hires, a dedicated people manager in Kathmandu looks after attendance, morale and growth at no extra cost, and flags early if someone is struggling. And because every hire starts with a 2-week free trial, you can see real output before you commit.
Want a team you can trust without watching every minute? Get in touch and we'll help you set up a scorecard for your team.