What do you think: productivity tracking or workplace surveillance? Where's the line?
Hot take: most developer time trackers are basically surveillance software with a productivity logo slapped on top.
Random screenshots. Keyboard activity. Idle timers. “Productivity scores.”
And somehow we're supposed to believe that's helping developers do better work?
That's exactly why @Meridian caught my attention.
It automatically captures what you're working on and gives you visibility into where your workday actually went, without turning your computer into a CCTV camera for your boss.
It isn't built around “How can we monitor employees better?”
It's built around: “How can developers understand their own work better?”
The founders are developers themselves. They experienced this problem, quit their jobs, and spent the last few months building @Meridian before opening it up for beta feedback.
And with AI coding agents changing how developers work, I think understanding where your time actually goes is about to become much more important.
Personally, I'd rather use a tool that tells me “here's how you spent your day” than one that tells my manager “here's how often you moved your mouse.”
Meridian is worth watching.
Over to you! What do you think... productivity tracking or workplace surveillance? Where's the line?
Replies
I've always felt there's a big difference between measuring outcomes and measuring activity.
Same with my team. I care more about using the data to find where we can improve than policing how people work.
If someone gets their work done in 4 focused hours, why should I care how many times they touched the keyboard
The moment tracking becomes about activity instead of value, it becomes surveillance.
Time tracking reminds me of a factory mentality, where action directly results in, say, number of parts created.
But with development and other intangible work I thing a simple task tracker shows enough already.
I tend to think the line gets blurry when we start measuring how busy someone looks rather than the actual work getting done.
Some level of visibility can definitely help, especially when you’re trying to spot bottlenecks or understand where a team is getting stuck.
But once it moves into screenshots, mouse activity, keystrokes, or constant active-time tracking, I personally start questioning the value. My concern is that people may begin optimizing for the metric instead of the outcome.
I’d probably rather have slightly less visibility and a higher level of trust than the other way around.
I think the ethics behind it are paramount: do you not trust your employees to actually working want reassurance? than you have a trust problem combined with a leadership problem. if you just want to know if your workers are productive thats a different questions right? what do we spent our time on is a productivity problem and that a much less hostile problem to tackle. The former creates resentment between workforce and management. it divides! the later is pulling people together to be better. voiced correctly, tackle with transparency, checked for blaming and fingerprinting during result discussion is they key for a team thats thrives for the top team in the company or the volleyball team building exercise vs the I hope we don't get fired this morning attitude. Be real with people, be honest and it's ok even an "we are all building a better company" theme. or be ready for a riot by a demotivated, scared workforce that feels surveilled rather than optimized!
The line I’d use is control plus audience: the individual can see and correct what’s captured, sensitive work can be excluded, and raw activity isn’t exposed to a manager. Aggregate time by project can help with planning; screenshots, keystrokes, and opaque scores shift power without improving decisions. I’d also require a short retention window and an audit trail showing who viewed the data.