Are we building what people need, or just what we want?
You did not set out to serve yourself. No one does. It happens slowly — a feature you were proud of, a design you fought for, a roadmap that quietly bent toward what impressed you rather than what helped anyone. This is not a moral failing. It is what happens when skill goes unchecked. Notice what you are actually asking. Not "are we good people" — that question flatters you and changes nothing. Ask instead: in the last month, how many decisions were made because a user asked for them, and how many because they were interesting to build? Count honestly. You already suspect the answer. You cannot do this alone, and you should not try to. One person checking their own motives will always find reasons to trust them. A team checking each other will not. This is why you do this work together — not as a group therapy session, but as a standing discipline, the way you'd check a budget.
Ask, before you ship anything: who is this for, and what did they ask for? If you cannot name the person and the need, you are serving your own idea, not them. Make this question routine, not occasional. The habit of asking is the only real safeguard you have.
What changes unlock by starting
- A team habit of naming the user and the need before building, not after.
- Fewer decisions driven by what's interesting to build versus what's needed.
- A standing check — built into your process, not dependent on memory or mood.
- Less defensiveness when challenged, because the question is now routine, not personal.