My machines will take people's jobs. Am I responsible for that?
You did not create the choice between efficiency and people — the world had that trade before you were born. But you are the one holding the lever now, and that is not nothing. Pretending the machine made itself, or that someone else would have built it anyway, is the comfort of a man who wants the gain without the weight. Here is the honest split. You do not control the market, the shareholders, the speed of the technology, or whether another team builds the same thing with less care. You do control the design choices in front of you, the timeline you set, the warning you give, the severance you fight for, the retraining you fund, the honesty of your language when you announce it. Most teams in your position do one of two false things: they drown in guilt and build nothing useful, or they build in silence and call it inevitable. Neither is responsibility. Responsibility is specific. It has a name, a date, and a next action.
Yes. You built the thing; you own what it does. Responsibility is not guilt — it is the work still in front of you: how you build it, who you warn, what you fund, what you say truthfully. Stop asking whether you're responsible and start asking what you'll do with that fact today.
What changes unlock by starting
- A short, specific list of what your team controls in this decision, separate from what it doesn't
- One concrete commitment made to affected workers, with a date attached
- Language for the announcement that you could say to someone's face without flinching
- A team that stops arguing about guilt and starts arguing about the next decision