Blog
Notes for people who run distributed teams
Practical writing on workforce productivity, employee activity data, privacy and rollouts for contact centers, BPOs and distributed teams.
Shrinkage you cannot see: where the contact center day really goes
Workforce management counts the shrinkage it schedules. The drift between tools inside a shift never shows up in the plan, and application-level time data is the first place it becomes visible.
Corporate vs non-corporate: a fairer way to measure productive time
Name only the tools that are the job, count everything else anonymously at team level, and decide which is which on the machine before anything is uploaded. Why this one design choice changes the whole conversation.
Employee monitoring without screenshots: what a works council will accept
Screenshot tools fail works council review for a reason. Here is the data-minimization case, field by field, and the checklist to bring to the consultation.
Meeting time is not idle time: measuring remote teams honestly
Keyboard-and-mouse idle logic punishes the people who spend their day on calls. What meeting detection changes, what it does not, and what to report instead of an activity score.
Nesting new hires: a focus policy that relaxes as they go live
An allow-list during classroom training, a time-limited plan in nesting, full access on the live floor. One group move at each step, and the data to show the transition is working.
Running one productivity policy across sites in different time zones
Per-person working hours, a group tree organized by site, time zone filters in reporting, and a corporate list that is shared. How a multi-country operation keeps one policy without flattening the differences.
Rolling out a desktop agent to 500 Windows PCs without a ticket storm
A runbook for IT: pilot group, allow-listing, the silent install switch, the non-admin installer, update channels, and what users see, which should be nothing.
The security questionnaire for workforce analytics software: 24 questions to ask any vendor
A neutral checklist for IT and security teams assessing an employee activity tool, with ReclaimTime's own answers alongside, including the ones that are 'no' or 'per customer'.
The supervisor's weekly review: a 20-minute routine using time-by-team data
Four views, two questions, one note, no league table. A routine a team lead can run every Monday with the statistics page and nothing else.
Why most teams use ReclaimTime for tracking alone, and when blocking earns its place
Blocking is off by default and most organizations never turn it on. Here is where it genuinely helps, where it backfires, and how to set a policy by group without starting a war.
Window titles: the one field that deserves a privacy conversation
Of everything an activity tool records, the window title is the only field that can carry free text out of an application. Here is what it is good for, what it can leak, and how to decide.
Want to see this on your own teams?
Start with a pilot group and see the first team reports within a week.