We own the cost of our automation. Is that enough?
You built the thing. It works. It also means someone's job disappeared, or will. You say you own that — you answer for it. Good. But saying so, alone in a room, changes nothing for the person who lost the wage. Your team's tension is this: you feel the weight, and you mistake feeling it for carrying it. Ownership without a ledger is just a comfortable feeling with the same layoffs underneath. The workers displaced don't need your conscience. They need something concrete from you. So the question isn't whether your team is responsible. You already know you are. The real question is what you'll do this week. Do something you can point to. Say: there, that is what our ownership cost us.
No. Owning the cost is not the same as paying it. You have named the harm; now name the debt and who collects it. Choose one displaced worker, one real obligation, and discharge it this month. A clear conscience is not currency. Action is.
What changes unlock by starting
- Your team holds a concrete list of who was affected, not a vague sense of impact.
- At least one displaced worker has moved toward real support — a job, training, or income.
- Your team can answer 'what did ownership cost us' with a fact, not a feeling.
- You've built a repeatable habit of accounting for harm before you ship the next automation.