We automate people's jobs. Now what do we owe them?
You built the system. It does the work faster, cheaper, without complaint. That was the job, and you did it well. Now a different question has walked in: what happens to the people it replaced? You did not ask for this question. It arrived anyway. This is not guilt. Guilt is soft and it passes. This is your judgment catching up to your skill. You measured success by output for a long time, and it worked, so you kept measuring that way. Now you suspect output was never the whole measure. You are right to suspect it. Your team feels this differently — some feel nothing, some feel it constantly, and neither side says so out loud. That silence is the actual problem. Not the automation. The silence about what it costs, and who pays.
You are not guilty for building something that works. You are responsible for what you do with what it reveals. Stop debating whether automation is good or bad in the abstract. Name who bears the cost, sit with your team, and decide what you owe them now.
What changes unlock by starting
- Your team has a written, specific answer to what you owe the people your work displaced.
- You stop hiding behind 'the market decided' and can state your own reasoning plainly.
- You can point to one concrete action taken, not just a conversation held.
- Future decisions weigh the cost to displaced people alongside the gain in output, as a matter of habit.