3 ms·

It's good were on the same page: your employees will be motivated to further their work-related skills and efficiency, thus doing less work. My deployment proc

It's good were on the same page: your employees will be motivated to further their work-related skills and efficiency, thus doing less work. My deployment process at work used to require a ton of work, but I spent a few afternoons to automate it and now I get to do much less work.

globular-toast 6y ago
> My deployment process at work used to require a ton of work, but I spent a few afternoons to automate it and now I get to do much less work. Clearly you're just like the majority of HN readership: living in a bubble a million miles away from what is reality for very large swathes of the population. Do you truthfully believe that someone flipping burgers in Burger King is capable of inventing machines and automating processes, but they refuse to do it because they don't get paid enough? Do you not see how absurd that sounds?
- ianleeclark 6y ago
  No, but I don't think your response warranted anything serious. You said that any mcdonalds worker is inherently lazy, so I sidestepped that ridiculous sentiment. Also it's hilarious that you, the guy out there roasting all minimum wage workers, is somehow connected to the average working man.
dunnevens 6y ago
> Do you not see how absurd that sounds? Not absurd at all. The people in the front lines understand the nature of their work better than anyone. When the engineers and the front line workers can actually communicate, and the workers feel like they're being heard, then great things can happen. Not only can productivity go up from making processes more efficient, but the hard-working front line people can feel a certain amount of ownership in their positions. Which will contribute to making them even better. I've seen this in person. Once worked for a teleco's internal training department. We somehow ended up making quick access utilities for the call center desktops. When we first deployed the tool, it rarely got used. This was because we made assumptions about what they needed. So we ended up talking to the call center reps. The people stuck dealing with the front line calls all day. They had very clear ideas about what they needed and what we should do. We listened. Followed their ideas. Had them give further feedback on the betas. And it ended up probably saving the company many millions per year in terms of efficiency gains. Plus it was a huge morale boost. These people finally got someone to listen to them and helped implement changes that made their job easier. Which gave them a sense of ownership and pride. And upped employee retention.
- globular-toast 6y ago
  So you just did your job and went and collected requirements from your user base? I really don't see how this is the same thing. I worked in a large insurance company with its own call centre and we did the same thing. It's great for the business but I just don't see how this is connected to giving workers more money and freedom.

globular-toast 6y ago

> My deployment process at work used to require a ton of work, but I spent a few afternoons to automate it and now I get to do much less work. Clearly you're just like the majority of HN readership: living in a bubble a million miles away from what is reality for very large swathes of the population. Do you truthfully believe that someone flipping burgers in Burger King is capable of inventing machines and automating processes, but they refuse to do it because they don't get paid enough? Do you not see how absurd that sounds?

ianleeclark 6y ago
No, but I don't think your response warranted anything serious. You said that any mcdonalds worker is inherently lazy, so I sidestepped that ridiculous sentiment. Also it's hilarious that you, the guy out there roasting all minimum wage workers, is somehow connected to the average working man.

dunnevens 6y ago

> Do you not see how absurd that sounds? Not absurd at all. The people in the front lines understand the nature of their work better than anyone. When the engineers and the front line workers can actually communicate, and the workers feel like they're being heard, then great things can happen. Not only can productivity go up from making processes more efficient, but the hard-working front line people can feel a certain amount of ownership in their positions. Which will contribute to making them even better. I've seen this in person. Once worked for a teleco's internal training department. We somehow ended up making quick access utilities for the call center desktops. When we first deployed the tool, it rarely got used. This was because we made assumptions about what they needed. So we ended up talking to the call center reps. The people stuck dealing with the front line calls all day. They had very clear ideas about what they needed and what we should do. We listened. Followed their ideas. Had them give further feedback on the betas. And it ended up probably saving the company many millions per year in terms of efficiency gains. Plus it was a huge morale boost. These people finally got someone to listen to them and helped implement changes that made their job easier. Which gave them a sense of ownership and pride. And upped employee retention.

globular-toast 6y ago
So you just did your job and went and collected requirements from your user base? I really don't see how this is the same thing. I worked in a large insurance company with its own call centre and we did the same thing. It's great for the business but I just don't see how this is connected to giving workers more money and freedom.