Do we build for people, or just for the budget?
You sit in the meeting and you already know: the feature they're asking for does nothing for the person who will use it. It pads the invoice. It flatters the client. You build it anyway, and later you wonder what any of you are actually for. You are not the only one who feels this. Your team feels it too, even when no one says it out loud. This is not one person's private failure of conscience — it is a group that keeps choosing the easy yes over the honest no. Say that plainly to each other. It changes nothing to keep it private. You cannot fix your industry this week. You cannot fix your client's whole approach to people. You can fix the next decision your team makes. That is the only place your power actually reaches — so start there.
You will not settle this by feeling guilty. Pick one project. Name one choice where the client's vanity won and the user lost. Change that one choice next time. That is the whole answer. Flourishing is not a mood you wait for — it is a decision your team makes, project by project.
What changes unlock by starting
- You stop carrying this as private guilt and start treating it as a team decision you can act on.
- You have one specific example, from this month, of choosing the person over the invoice.
- Your team has words ready for pushing back on vanity requests, instead of pretending they don't happen.
- You can name, for your next release, exactly who benefits — by name or role, not in theory.