How do we stay user-first when the numbers don't agree yet?
You say you build for what users need, holding ego and numbers loosely. Good. But you wrote to me as if this is still a fight — as if ego might win tomorrow if you stop watching it. That tells me the real trouble isn't the holding. It's the waiting. You are waiting for the dashboard to tell you the work mattered. No dashboard arrives in time to comfort you. The user you helped yesterday does not show up as a line that moves for weeks, if ever. You will sit with your team, looking at flat numbers, knowing you built the right thing — and doubt will whisper that right and effective are not the same thing. Here is what is in your power: whether you can state, plainly, what one real person needed and what you gave them. That sentence is yours to make today. The number is not.
You are not struggling to hold ego and metrics loosely — you already do. The real test is trusting the work before the dashboard confirms it. Each week, have every person state one sentence: the specific thing a specific user needed, and what you gave them. If no one can say it plainly, you have drifted.
What changes unlock by starting
- Your team can state, in one sentence each, what a real user needed this week — without checking a dashboard first.
- Slow or flat metrics stop derailing meetings; conversation returns to users instead of charts.
- Ego-driven moves get named and interrupted before they shape the roadmap.
- The team trusts the work itself as evidence of serving well, not only its score.