I don't get it - shouldn't one-on-ones and regular progress check-ins (be those standups, metrics (This is your #2), whatever) give you that information? None of those are easier when on-site. In fact, given today's move towards open offices, any form of 1:1 collaboration is easier remotely where you don't have to fight for precious meeting room space.
I think the core problem is that you're trying to prove "everyone is working" when we should be interested in "the work is getting done". Seeing that everyone is working doesn't actually mean progress is getting made. If you have to take steps to answer that question anyway, the first question is fairly pointless.
Also had managers that were basically invisible but kept a great crap umbrella for us. Loved them too. Ended up working a ton and getting enormous amounts of work done because trust and autonomy are huge.
I think the worst situations are when managers are too insecure to be honest with direct reports. That’s decidedly uncool and super ineffective.
Also, it seems managers get so overloaded that 1 on 1s and stand ups end up being mostly a waste of time because it’s too hard to remember all the little details.
So remote or in office isn’t really the issue. In my view, remote is superior due to productivity, flexibility and happiness, but it does require everyone to do regular video chats and pair programming.
Ironically, the in office folks have the hardest time with this because they feel they need to get up from their desk and find an overly booked conference room as you mentioned.
Simple solutions are context dependent, but could be along the lines of a) work remote if you have the discipline, b) asynchronous slack based standups, c) report status as you go in your tickets, d) every day or two peers and managers sync up 1 on 1 or in person depending on their preference, e) have clear goals as a company and a team, f) have good technical product people writing 1-3 day user story tickets including completed designs if it’s ui work, g) have good tech leads writing 1-3 day technical improvement task tickets, h) vote as a team on contentious technical decisions, then disagree and commit, i) generally chill out a bit and let work be enjoyable.
At least that’s a start...
> Also, it seems managers get so overloaded that 1 on 1s and stand ups end up being mostly a waste of time because it’s too hard to remember all the little details.
I'm not sure how the first quote doesn't count as a 1:1 - the goal isn't to have a highly formalized process, it's to have communication. Some about the specific work, some about general work and workplace, but communication.
Total agreement about the overloading of management though - I haven't had a boss in years that didn't regularly have most of their schedule booked and often double-booked. I had to fill in for my manager while he was on vacation for week and it reaffirmed my lack of desire to do management - and I only had to deal with pieces that couldn't wait a week! I sometimes think the recent shift to focus on regular management 1:1s is all about reclaiming enough time to actually know what their team is doing.
Yes, you’re right, I guess those were a form of 1 on 1s :-)
> Total agreement about the overloading of management though - I haven't had a boss in years that didn't regularly have most of their schedule booked and often double-booked. I had to fill in for my manager while he was on vacation for week and it reaffirmed my lack of desire to do management - and I only had to deal with pieces that couldn't wait a week! I sometimes think the recent shift to focus on regular management 1:1s is all about reclaiming enough time to actually know what their team is doing.
Absolutely! It’s wonderful to have empathy for this! :-D
> I don't get it - shouldn't one-on-ones and regular progress check-ins (be those standups, metrics (This is your #2), whatever) give you that information? None of those are easier when on-site. In fact, given today's move towards open offices, any form of 1:1 collaboration is easier remotely where you don't have to fight for precious meeting room space.
This is not quite the case everywhere. We have agile 5-8 person offices and people are still supposed to walk out for longer phone calls occupying one of the smaller meeting rooms.
But I actually like that different teams can mix a lot easier.
I've heard this claim for open offices a lot. I never understand it. It's not like I'm AGAINST easy collaboration. But I spend (or try to spend) more time on my own, and everyone "collaborating" around me and expecting that I can turn off my peripheral vision and hearing with a brain that is hardwired to NOT ignore those things just makes the majority of my time worse.
Plus, in the last 20 years and 5 companies (spanning 8 offices if you count office moves) I've never had adequate meeting room space (defined as: We need a space to spontaneously talk without disturbing others, can we find it trivially?) for more than a 3 month span after moving to a larger building. Hardly scientifically conclusive, but personally persuasive.
So I'm all for collaboration between people, including between teams, but I don't understand sacrificing the REST of the time in the name of that one thing.
My team shares an open office with another one, working on a different project. We see them every day.
I don't think anyone knows any name of the people in the other team.
Only if you are a contractor and you've fulfilled your contract. If you are a salaried employee I expect you to keep your hopper of tasks full so you aren't sitting around idle 95% of the day waiting for me to feed you 30 minute taskers
The "goal" in a lot of cases is nebulous (i.e. "keep developing the product", "improve stability", etc). There might not be a manager feeding you tasks every time you run out. At least in my company, you are expected to figure out on your own how to continually make the product better and proactively do it, not sit around idle after rapidly finishing the last task your manager gave you.
If you are just a dumb worker that can only work when your manager fills your queue, you are not valuable to me as a salaried employee (you are more valuable as a contractor who I can call upon for a one-off difficult task that you can then complete in 30 minutes).
Here's what I believe:
If I pay you a salary, I want (roughly) 40 hours per week of productive work at your current skill level. Note: I consider sitting around thinking about things relevant to the product or company to be productive work. If you believe your level of output deserves higher compensation than you are receiving, come talk to me or find a company that will pay what you think you are worth. However, accepting a salary and then doing tasks really fast and then going idle (watching netflix, working on side projects, etc.) until your manager cattle prods you is not acceptable for a salaried employee; that would be more appropriate for a contractor where you can idle on your own dime.
- you have an employee that works faster than others, in the same pay grade.
- You are annoyed that he or she has empty queue of work
- You expect employees to look for tasks on their own when they are done
so either that employee:
- has no creative control over the work he or she is doing and cannot move forwards on their own.
- is severely underpaid and undervalued
- is under bad management that cannot fill their work queue fast enough
All of that will lead into them doing tasks at the same speed as other ones - you just turned a good, valuable and fast employee into another drone.. or worse - they'll go work for competition, and you'll have to both suffer the loss of a good trained employee and a cost of hiring someone else.
They are not the "best employees" if they are constantly idling, waiting for me to tell them what to do next. People here seem to think the ideal manager/subordinate relationship is that of a worker thread pool where the manager fills the queue and the worker threads pull tasks off the queue.
Not so. The "best employees" are ones who can examine the current state of affairs, and then come to me and propose things to work on. The ideal manager/subordinate relationship is actually one where the workers are all artificial general intelligences that learn over time what the product is, how to improve it, and proactively create tasks to work on.
If you are a rockstar but only work as a a super-fast super-efficient thread in a worker thread pool, you are less valuable to me than a non-rockstar AGI who can dynamically recognize which tasks need to be done and only occasionally needs guidance and course-correction.
If employee is getting extra works as a reward for being efficient guess what will happen.
If you're truly doing all those things in 30m, you should be running the show.
Sometimes taking the full 8h allows you to put in the packaging to confirm you've done the "hard" part.
Sure, some unknown quantity of people can just fuck around and hide from work, but again, you're not paying me because I'm a fuck off person, yer paying me because I have the decades of experience, and because you know with certainty I'll do the damn work, find more work when I need more, and will never miss a deadline on my own fault. Everyone on HN just assumes bad faith all the time, geez....
It feels good to help people, as long as it’s with healthy boundaries so as to prevent burnout.
Most tech workers get paid a bit more than that.
I did actually signed contract that actually specifies fI'll time - 40 hours.
I you wanna count weekend thinking into it, is a different question.
It's a weak manager that's constantly concerned about their reports not being productive. Nothing in the world is easier to spot than someone who doesn't produce. You don't need to optimize for that, when it happens, deal with it. Optimize toward keeping your team motivated.
i would say that it is a very quick way for employee to reach towards a new company.
I just finished working on a fully remote contract that worked that way, every day at noon there was a conference call that never took longer than 15 minutes. It worked great. A couple manager types were on the call, and they'd share any developments on the contract side of things, feedback from the customer, things like that, but mostly they just listened and took note of potential issues and made sure they got resolved (so like if you mentioned a problem one day then didn't the next, they'd ask if it got dealt with).
Don't waste a day resolve that issue now.
We have 8 people on our current project team and we can typically finish this meeting in under 5 minutes each morning. We have some people on each coast, and half the people are remote so we do it at 10:30 am Eastern.
It keeps everyone accountable to the company and each other, and because everyone knows what everyone else is working on, it makes it easier to avoid overlap and divide up tasks in the most logical way possible.
When I've seen "things go side ways" it's almost exclusively at higher levels of management when politics create goals other than "create an amazing product". Anyone who has worked both in a large company and a small startups has likely seen the difference between "my boss's goal is for us to create a best in class product" vs "my boss's goal is for him to get L_current +1 promotion".
There are no companies that have failed because the workers have finally figured out how to sneak their way out of doing work. But workers do have a hard time being productive when "productivity" is some weird game that no one will really explain the rules to.
But the logic of blaming workers who get "off track" is a huge part of the culture we need to get rid of to have successful remote work.
It's not about blame, it's about trying to ensure the team works together cohesively, and that individuals are unblocked.
I suspect there are such companies, but that the guilty individuals weren't serious professionals. Hire bad enough 'developers' and I can see it becoming a problem.
If the job is shovelling snow, I imagine it becomes one of the management's chief concerns.
(1) all employees are trusted and unmeasured, but you have to tap people on the shoulder every once in a while to confirm that they're on track. Naturally, this is easier if everyone is on-site.
(2) everyone is accountable for producing of tickets, and you can check that everyone is at least doing some work. Check-ins can happen via comments in tickets.
(3) Everyone just does whatever they think they're supposed to be doing, and the manager only finds out something is wrong when the employee volunteers the information or the project isn't delivered on-time.
(1) is the common case, (2) requires time and skills many managers don't have (and creates @#$% Jira commentary form the peanut gallery), (3) requires building an excellent team with years of mutual trust between them, and still goes wrong all the time.
Seeing you at your desk working, and asking a casual question or two at the water cooler is by far the easiest (laziest?) way to make sure things don't go too far sideways.