4 ms·
From my experience once you have ~1,000 employees AND a complicated org chart/raci/etc then it’s fairly easy for people to do little work and hide. In smaller o
by soared 5y ago
From my experience once you have ~1,000 employees AND a complicated org chart/raci/etc then it’s fairly easy for people to do little work and hide. In smaller orgs too many people see you, and in orgs that are running efficiently if you don’t do your job it causes issues.
Tons of people hiding at oracle from my experience :)
- pphysch 5y agoWe had a remote freeloader find a position at Oracle before his short-term contract with us was done. Onward and upward :)
- Tade0 5y agoI'll do you one better. My friends from a team I used to be in had a guy who simply didn't know how to code. My friend would at times act as a ghostwriter(for free) so that the poor bastard wouldn't get fired. Eventually the guy was promoted. The Dilbert principle is real.
- MattGaiser 5y agoManagement often spends so little time with you that the difference between them perceiving lots of work and little work comes down to what you say in your daily standup.
- dvtrn 5y agoI’m a fully remote worker. To my managers the work I do is a lot. To me it’s about 4 hours a day. There’s no deceit in this. What I tell them I’m working on is what I’m working on, what I’ve declared as ‘finished’ is factually ‘finished’. To the company, I’m still contributing the things I agreed to, responsive to the people who come to me for help (as a senior) and on track with the projects assigned to me. When the wall comes and I just cannot will myself to stare at the same problem anymore, that’s it for the day. Sometimes that takes longer than others, sometimes it’s 5 hours instead of four. Sometimes it’s a whole 8 hour day. So..matter of perspective, I guess. The agency and autonomy are nice, though. Some people want a shorter work day given. I’ve just decided to take it.
- Seattle3503 5y ago> To me it’s about 4 hours a day. There’s no deceit in this. What I tell them I’m working on is what I’m working on, what I’ve declared as ‘finished’ is factually ‘finished’. I've come to realize this isn't always a mistake on management's part. I work at a company where developers use the full day to get tasks done because there is so much on our road map. There is absolutely no slack, when something new comes up, something else needs to drop. We are hiring, but now I spend some of my time training them. I've seen friends work for companies that keep some % of their experienced developers time idle so those devs tackle issues that might pop up.
- democracy 5y agoHa! We could be on the same team. The person would sit with someone to get help for each of his tasks. Eventually he was the only one promoted.
- agumonkey 5y agoI want to know how this happens :)
- gitfan86 5y agoMy problem with big orgs is how inefficient they can be. At IBM I worked 5 hours a week and still was in the top 20% of my team.
- user123456780 5y agoI used to work for a government organisation and it was the same. Once I got disillusioned with what I was doing I would put in bare minimum effort which was, show up for standup every day, filibuster a bit then checkout. I was still one of the highest out-putters in the department.
- agumonkey 5y agoI just quit a vaguely similar kind of environment because there's always a few internal wars and suddenly people invent shit about who is the reason nothing happens and spread lies to save their ass.
- giaour 5y agoThe way you phrased that, I'm not sure if you were a programmer or a senator.
- divbzero 5y agoShowing up for standup every day might be more than what’s required for senators.
- agumonkey 5y agoAnd then there's turnover. People might just never get to know those people. Some may proactively avoid contacts through various means so nobody steps into their office only to realize nothing happens.